Account Synchronization between AD & Project Server 2003

[Johnnie Rotten]

Hello,

We've aligned some AD security groups with Project Server groups. All the
groups can successfully synchronize, there seems to be a quirk with the Team
Member group.

The synch creates a PWA account for the team member; this is not necessarily
good because when we try to modify the enterprise resource pool through MSFT
Project Pro we receive a domain account mis-match error. Essentially the
message says we already have someone (PWA team member) with this account you
can't create another one.

We've deleted the PWA account and created the Team Member in the Enterprise
Resource Pool. There are no errors encountered by the Team Member during
PWA logon to manipulate Assigned Tasks or generated when the Enterprise Pool
is saved.

So, is this a feature not a bug? We should create the resource explicitly
with the MSFT Project Pro (Enterprise Resource Pool) and only synchronize
the AD security groups with Project Server Groups like Executives, Project
Managers, or Portfolio Managers?

-Johnnie

 

[Johnnie Rotten]

Hello Again,

We un-installed the product (test environment) and deleted the associated
database. A fresh install was then accomplished.

Using PWA > Admin > Server Configuration > "Active Directory Group to
Synchronize" we were able to populate the Enterprise Resource Pool from a
"Team Members" AD Group. The synch process created a PWA account &
associated entry into the Enterprise Resource Pool.

Before, we setup PWA > Admin > Manage users and groups > Groups to
associate an AD group with a Project Server group. This caused the
behaviour I was asking about in the previous post.

I would *think* that both procedures would arrive @ the same result. I
guess not.

-Johnnie