Changing Windows Domains -

[Mark Byington]

Does anyone know how Sharepoint in PWA handles changing Windows domains.
When I am notified a users daomain has changed from A_Dom\xxxxx to
B_Dom\xxxx, I update their user info through Admin in PWA.

I also 'synchronize' projects they are assigned to in WSS. When I then list
the users for that project in WSS, usually the user is listed twice, once
with each domain. (We do not use Active Directory)

Can anyone tell me what's happeneing here and if I can avoid this?

Thanks

 

[Shawn W.]

I bet one is a project server account, and the other is a windows
account...right?

Shawn W.

 

[Gary L. Chefetz [MVP]]

Mark:

The key is the windows account. When it changes, the synch process sees this
as new resource, so it adds the user as a new user. We've had to write
supplemental routines to correct things like this, and things like people
changing their names due to marriage.

 

[Nator]

Where can I get my hands on one of these "supplemental routines". I
have the same problem. Literally hundreds of Project Server accounts
have been created over the last year from office changes.

 

[Gary L. Chefetz [MVP]]

Nator:

This one of our for-profit activities.<g>

 

[Mark Byington]

Shawn,

No, we only use Windows authentication...no Project Server accounts have
been set up.

 

[Mark Byington]

As it turns out, I'm updating the changed domain user in PWA and WSS before
the Server specialist disables the old account under the 'old' domain.

If I wait until the old domain/account is 'disabled', the problem doesn't
occur.

Have a good day.

 

[Mark Byington]

Here's what I NOW suspect happens: When a PWA site is 'synchronized', WSS
checks a user in the current list to see if it's a valid windows account. If
the 'old domain' account hasn't been disabled (i.e. it's still valid), 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.

So, because the old domain\userid is still valid, WSS leaves it alone, AND
adds the new domain\userid which it found on PWA.

It seems to me that WSS should check for validity AND if it's a valid user
account in PWA at the same time. The way it's working now seems to be faulty
logic to me.

 

[Gary L. Chefetz [MVP]]

Definitely not able to handle the real world all the time.