automating user rename...

Ben_inform

Hi ,

Does anyone find the rename process one of the clunkiest in worksite administration? We have over 1800 users and frequently need to rename users when a new user in AD comes in but the user pre-exists in worksite. (Yes I know we could make the AD unique but thats the way it is here, AD names are re-used).

Currently when the AD synch fails to import the user (because it pre-exists in worksite from an old user) , we have to create a new virtual account in worksite called _OLD and then rename the clashing account to the _OLD account. This will often fail due to checked out docs etc, so then we resolve the conflicts and then complete the rename in each of 4 databases. After this we can re run the AD Synch tool and the new user comes in.

This is a very manual and tedious process that takes heaps of time so I was wondering what other people do and if they have this issue ? I suppose an obvious thing would be to not re-use old AD account names but that is not my decision.

Thanks for your views,

Ben.

SandraMcGorrery

Hi Benji

We have (or will have after rollout) the same issue and were contemplating the same rename manual process....

The concern here is also with users attempting to search for ex-employee documents. Do they have to be educated to search using the _OLD names for ex-authors/operators? Is this consistently applied to ALL staff who leave or just those with clashing names?

Also, does security group membership update after the rename? All those Restricted Matter groups .... imagine a new starter got access through inheriting a secured-name!