support Posted October 6, 2011 Share Posted October 6, 2011 We recently had a customer report an issue with a specific Active Directory account not synchronizing with Passwordstate - as part of Security Group memberships. In the end it turned out to be caused by the accounts' userPrincipalName attribute being missing, which was suspected to be a legacy of a prior NT4 domain environment. If you experience any issues with AD accounts not synchronizing, things to check are: 1. The userPrincipalName attribute being missing 2. If the Passwordstate Windows Service is reporting any errors in your Application Event Log on your web server 3. If you have reached the number of registered user accounts in Passwordstate (Client Access Licenses) - you cannot synchronize more AD Accounts than available licenses Regards Click Studios Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now