AD Enterprise Resource Pool Synchronization & Domain Users Group

[Mukesh Parmar]

One of our clients wants each and every user in there AD to be added as an
resource in MOPS. So my best bet was to use the Domain Users group as an
Active Directory Group to Synchronize with MOPS server. Coz it will be a
dynamic group, as soon as new users are added to AD the user will
automatically added to MOPS as a resource.
But when actually doing it nothing happens means no Users are getting
synced/added to MOPS, on the other hand a group which i had specifically
created for MOPS syncs up properly, means if i add a user to that group and
initiate a manual Sync the users account reflects as a resource in MOPS. And
if i replace this custom group with Domain users group on the AD Enterprise
Resource Pool Synchronization page no users are synced.

And the problem is the client has more than 2000 users so it will be
impractical for going through normal manual addition of users..

Can someone shed a light on how can i add all the users to MOPS
automatically and why is the domain users group not syncing up with MOPS ???

Note:- I know that the users will be added as simple team members and i have
to manually assign additional rights to users i.e Project Manager, executive
etc... Which will be done later manually.

 

[Jonathan Sofer [MVP]]

Could it be that the number of users are simply too large in the domain
users group? Are you seeing any errors in the queue or in any log files on
the server itself?

On another note, is the client aware that they will technically have to pay
PWA license fees for their entire organization using this approach even if
only a smaller subset of the users actually use the system?

Jonathan

 

[Mukesh Parmar]

Hey Jonathan,

Thanks for the quick reply

1. Yes thats what i was guessing, but is this a known issue or something
else ??
Will try the same with different numbers of users in a fresh lab setup...
2. No errors in the Queue.
3. Only error in event viewer i can correlate with this is the following

Event Type: Error
Event Source: Office SharePoint Server
Event Category: Project Server Active Directory Synchronization
Event ID: 7718
Computer: [Edited]
Description:
Standard InformationSI Entry Point:
Project User: [Edited]
Correlation Id: dc232384-765f-4bfb-b4cf-661f413dd672
PWA Site URL: http://project/PWA
SSP Name: MOPS_SharedServices
PSError: Success (0)
Project Server Active Directory Group Synchronization is initializing
(reading settings and user information from the Project Server database).

4. This is on a lab environment with a replica of there actual AD, will
update them with the license part, if they are not aware of the same.

-- Mukesh

 

[Gary Chefetz]

Mukesh:

If I recall correctly, the AD synch doesn't like built-in Global groups. It
has been a while since I attempted this, but I do remember not being able to
use Domain Users in a very small organization with fewer than 100 users in
AD. The key here is to implement a change to your on-boarding process to
make sure that users are added to the Sync group that you create.

Hey Jonathan,

Thanks for the quick reply

1. Yes thats what i was guessing, but is this a known issue or something
else ??
Will try the same with different numbers of users in a fresh lab setup...
2. No errors in the Queue.
3. Only error in event viewer i can correlate with this is the following

Event Type: Error
Event Source: Office SharePoint Server
Event Category: Project Server Active Directory Synchronization
Event ID: 7718
Computer: [Edited]
Description:
Standard InformationSI Entry Point:
Project User: [Edited]
Correlation Id: dc232384-765f-4bfb-b4cf-661f413dd672
PWA Site URL: http://project/PWA
SSP Name: MOPS_SharedServices
PSError: Success (0)
Project Server Active Directory Group Synchronization is initializing
(reading settings and user information from the Project Server database).

4. This is on a lab environment with a replica of there actual AD, will
update them with the license part, if they are not aware of the same.

-- Mukesh

Could it be that the number of users are simply too large in the domain
users group? Are you seeing any errors in the queue or in any log files
on
the server itself?

On another note, is the client aware that they will technically have to
pay
PWA license fees for their entire organization using this approach even
if
only a smaller subset of the users actually use the system?

Jonathan