@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.

@theopenem_admin No problem - thanks for the response!

@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

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

@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()

Yes please. This would help so much. The dashboard for the openem is so empty. No charts or events or data besides how many computers there is.

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.

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.

@paddymccdrc

i try and is ok thank you for your reply

It's correct. There is no virus. It's because Toec can elevate and impersonate users but obviously that's intentional. It's used for the new Winget functionality. The virus scanner is complaining about this file.

https://github.com/jdolny/Toec/blob/master/Toec-Services/ServiceRunAs.cs

@theopenem_admin Yeah i get that, but I found a program, which installs only without specifying any scope in the command. I guess it's a problem of the package maintainer, but it's better to have us as system admins specify, which scope we wish to apply from e.g. a drop-down menu in the winget module.