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.

@zedogado said in How to configure ldap settings correctly:

was successful" seems to indicate your login credentials ar

you're right.leave ou blank,it worked!thank you!

If it's the only database that's running on there, then it really doesn't matter.

I tried your script, I set it as a condition for a login policy and it works fine for me. However, there is an issue with the message modules when set to run with a login policy, it looks like I only set it up to work with checkin/startup policies, and it results in the toec-ui crashing. That is most likely why you are seeing the error you posted, it indicates that toec-ui is not running. I'll need to fix this in the next release.

@daodio2

You probably don't have compatible ethernet drivers for that ThinkCentre installed in your WIE.