M
Mark Byington
How I think WSS in PWA 'synchronizes' a project site in Project Server 2003:
When a PWA site is 'synchronized', WSS checks a user in the current list
to see if it's a valid windows account. IF account has a valid windows
domain\userid, the process leaves it in the user list.
It also checks PWA for any 'new' users. That is, any users on PWA that are
not in the WSS user list, and adds them.
If a user has more than one valid domain/userid the only one WSS should
recognize, is the one defined in PWA, since PWA can only have one
domain\userid per account. We have some users who have valid windows account
in more than one domain for administrative reasons or to perform some special
functions that are not accessible to all domains.
It seems to me that WSS should only if it's a valid user account in PWA
since windows validity is verified BY PWA when the account is added/changed
and the 'save' button is pressed.
The way WSS in EPM is working now seems to be faulty logic to me.
When a PWA site is 'synchronized', WSS checks a user in the current list
to see if it's a valid windows account. IF account has a valid windows
domain\userid, the process leaves it in the user list.
It also checks PWA for any 'new' users. That is, any users on PWA that are
not in the WSS user list, and adds them.
If a user has more than one valid domain/userid the only one WSS should
recognize, is the one defined in PWA, since PWA can only have one
domain\userid per account. We have some users who have valid windows account
in more than one domain for administrative reasons or to perform some special
functions that are not accessible to all domains.
It seems to me that WSS should only if it's a valid user account in PWA
since windows validity is verified BY PWA when the account is added/changed
and the 'save' button is pressed.
The way WSS in EPM is working now seems to be faulty logic to me.