Sign in
 
HomeOnline20132010Other VersionsLibraryForumsGallery
TechCenter >
> 
> 
PS2010 - Resource Sync not working for particular users

Answered PS2010 - Resource Sync not working for particular users

  • Friday, May 11, 2012 9:08 PM
     
     
    Sign In to Vote
    0

    Hi,

    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?

    Thanks

     

All Replies

  • Monday, May 14, 2012 3:07 AM
     
     
    Sign In to Vote
    0

    Hi there,

    What happens if you add one of the affected user from Group B to Group A and then try to sync

    Check the AD group type of Group B as well if necessary compare with Group A.

    Hrishi Deshpande – DeltaBahn Senior Consultant
    Blog | < | LinkedIn

     
  • Monday, May 14, 2012 10:14 PM
     
     
    Sign In to Vote
    0

    Well,

    It seems I am having this exact issue

    http://social.technet.microsoft.com/Forums/da-DK/projserv2010setup/thread/28c2f9f8-7eff-47fb-9318-7eb31a3f3b5c

    Remove deativated users is NOT an option.

    Is ms making a hotfix for this?

     
  • Monday, May 14, 2012 10:37 PM
     
     
    Sign In to Vote
    0

    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.

    Hrishi Deshpande – DeltaBahn Senior Consultant
    Blog | < | LinkedIn

     
  • Monday, May 14, 2012 10:44 PM
     
     
    Sign In to Vote
    0
    Besides the one is described earlier.
     
  • Wednesday, May 16, 2012 2:36 PM
     
     
    Sign In to Vote
    0

    Hrishi.

    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.

    Thanks

     
  • Thursday, May 17, 2012 11:35 PM
    Owner
     
     Answered
    Sign In to Vote
    0

    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.

    Best regards,

    Brian.

    Blog | Facebook | Twitter | Posting is provided "AS IS" with no warranties, and confers no rights.
    Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page