Friday, May 11, 2012 9:08 PM
Project Server 2010, February updates.
User database is around 10k, I have like 100 users that are not being synced from AD.
User A is on Group G
User B is on Group G
Group G is mapped to be a resource group on PS2010.
User A gets synced, so a resource is created.
User B doesn't get synced, and a resource is not created.
The account for User B is not disabled.
No errors show up on Sharepoint Logs, all succeeded.
What can be wrong?
Monday, May 14, 2012 3:07 AM
Monday, May 14, 2012 10:14 PM
It seems I am having this exact issue
Remove deativated users is NOT an option.
Is ms making a hotfix for this?
Monday, May 14, 2012 10:37 PM
I don’t think the issue discussed on above thread is similar.
In that scenario users were not Part of PWA , due to some reason users were deactivated in AD itself (generally when user leave the organization, users are not deleted instead marked as inactive) hence AD sync was failing
In your case users from both the groups are active users.
Also this is not an bug in the product. When AD sync feature is used in PWA, project server will read only specific attributes and update the same in project server database. It’s one way traffic. If the user is marked as inactive in AD, project server won’t be able to read the information and as a result AD sync will partially fail, only active users will be updated in PWA.
To narrow down the issue further please try adding one user from group B to A and then try AD sync, depending on the result we may need to decide further steps to fix the issue.
Reviewing ULS log will also help to understand the reason.
Monday, May 14, 2012 10:44 PMBesides the one is described earlier.
Wednesday, May 16, 2012 2:36 PM
Thanks for your answer, maybe I wasn't clear, I am facing that issue too, I am not relating them.
About the first issue, I am not able to do group changes, this is a big company and every user operation must be justified.
Thursday, May 17, 2012 11:35 PMOwner
There is a fix coming for the issue with AdminNTAccountNotFound error when the AD Sync comes across a user who has been de-activated in AD Andres. At this time we anticipate the fix being in the June 2012 Cumulative Update - but I can't make a definate promise on this as we are still working on it.
- Marked As Answer by Brian Smith - MSFTMicrosoft Employee, Moderator Thursday, May 17, 2012 11:36 PM