Read access should be sufficient, we don't make any changes to AD itself, only read from it.
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
Does the Windows Authentication use these Registered LDAP Servers for authentication, and if so are there any special permissions needed for authentication? We had the user account for the registered server overprivileged and when removing permissions it seems that users could not login to ePO with their AD user account until we reverted the permissions changes we made.
Windows authentication should use the ldap server that the epo server itself discovers - you don't have to have a registered ldap server to log into the console with a windows account. I would suggest maybe taking away the rights one at a time to see which one affected user logins. Are you using user autocreation or creating the accounts manually? The only permissions I am aware of for a windows account is that if the account is used to connect to the database, it has to have logon rights to the epo server and be a local administrator. But that is different than console login accounts.
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.
Thousands of customers use our Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership: