Discussion Locked

User Names

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am the new netwok admin at a small company. We are nt server 4, which is our PDC. The problem is username within our company. They make no sense ie. 9999hem, 1034jek, you get the drift. I am going to be moving to AD soon but want to correct this problem without going to every pc and copying their settings over to their new users profile. Is there an low impact way of doing this.
Thanks for any help.

5 replies

by p.j.hutchison

I suggest devising a new username scheme, get it approved by your boss(es). Inform users of their new names and when its done then rename them all to the new scheme. It should not affect permissions or passwords.
Then you are ready to move to AD.

by otl

Appears original user names were "picked" by the users, using employee numbers/initials would help clean up the system of dead users. If it does not exist in HR then user does not exist. This does require coordination between you and HR, but is well worth the time !

by curlergirl

It depends on whether you need to change the user's display name or only the logon name. If it's just the user's name (i.e., full name or display name), then I would change them now under WinNT. If you need to change the user's logon ID, it is much easier to change those in Win2K with AD than it is with NT. In that case, I would recommend converting with the old user names. In either case, devise a specific "protocol" for naming users that you will carry through with all new and old users. In Win2K, if you need to change the display name (that is, the users full name and/or alias), you can change the existing user names simply by right-clicking on the name in the AD Users list and choosing "Rename." If it's the user's logon ID that you need to change, then you can change that by editing the properties of the users and changing the Win2K logon ID.

As for the profile issue, what I would recommend is going to roaming profiles. If you go to roaming profiles, then the user's profiles are stored on the server rather than on each individual's workstation. It's a little bit of work to set up, but once you have it set up and working properly it saves a LOT of time during conversion and it ensures that users won't lose their profile information even if their workstation crashes. You can find info on how to set up roaming profiles by going to www.microsoft.com/support, selecting Windows NT Server for your lookup and searching for "roaming profiles".

Hope this helps!

by acetaylors

Poster rated this answer. Thanks for the advice to wait until a convert to AD. That makes much more sense than trying to do that under NT.

This discussion is closed to new replies.