Well, I was able to figure this out myself. I had to add a CORS module to IIS10 and configure that in the TOEMS-API web.config.

Sorted it myself in the end.

Never reallt dealt with LDAP before, so when I ran dsquery to get the info I needed for the LDAP settings, I`d also copied the CN=USERS part.

I was staring at the settings and wondered if that meant it was only searching within Users in the AD, so I removed it, the test was still succesfull, so then I re-ran the Sync, which was also successfull but now I can see computers and my AD structure.

Frank.

@theopenem_admin said in Non-working shortcut when created via Toec:

I suspect that wscript.shell needs a user context instead of service.

Interesting enough, the following works fine in Toec to create a Chrome shortcut pointing to a specific web site.

$shell = New-Object -comObject WScript.Shell
$shortcut = $shell.CreateShortcut("C:\Users\Public\Desktop\ETA Test Site - Chrome.lnk")
$shortcut.TargetPath = "C:\Program Files\Google\Chrome\Application\chrome.exe"
$shortcut.Arguments = "https://www.eta-i.org"
#$shortcut.WorkingDirectory = ""
$shortcut.Save()

As far as I know, File Copy Modules do not act on the WIE. They describe files that the WIE should add to a computer when imaging it. If "Is Driver" is enabled, it will then use DISM to install the files on the newly imaged computer.

If you want the WIE to add drivers to a computer as part of imaging it, you configure that at Images -> {specific image} -> Image Profiles -> {specific profile} -> File Copy

@tylerloch Possible it could be related to Dell's SafeBIOS:

Rather than storing BIOS and Firmware information on the hardware itself, which is susceptible to corruption, Dell SafeBIOS delivers an off-host BIOS and Intel ME verification capability.

https://www.delltechnologies.com/asset/en-us/products/security/technical-support/dell-safebios-datasheet.pdf

@theopenem_admin No problem - thanks for the response!

@txiong
Please disregard post.
Solution was either reviewing and saving (no changes) all my com server setting and/or binding toems-api and toems-ui to use 'All Unassigned' . Wasn't sure if the initial config had the binding to 'All Unassigned', but its now working.

Okay, I figured it out by reading the manual for another, unrelated module. For those who struggle with the same problem:

Create a script module with the content

if (! (Get-Process X)) { Exit -1 }

where "X" is the name of the process. You can use * as a wildcard, e.g. X* will match any process whose name starts with "X". Set the "Success Codes" value to "-1" and toggle "Use As Condition". Save the module with some name you can remember, e.g. "Check if X is running"

Now, when creating a policy, you can use this module as a condition in the "Conditions" tab and it will only run if the process is not running.

@theopenem_admin Problem Resolved Thank you. AT least this is here now for others to see if needed!

@mardedude

Same issue hier.
I have also post it at the forum.
link forum post

@tmowdy Yes, I've confirmed the information is correct. I think the cause of this is the image file was too large. Switching to SMB resolves this for me.

@chavi Thank you Chavi for your reply.
I successfully installed my config on my new server.
The problem was the mysql export.