One of my customers lost their Windows NT domain server to a power outage/surge. All restoration efforts have failed - no drivers for replacement hardware, old standby server not stable enough to do domain migration to Windows Server 2003.
We want to start out new. I have got a new Windows Server 2003 setup an running. I did some testing on the new server with a new AD / Domain setup. I decided to create a new Domain name with new user names and passwords. However, I seem to have created a lot of work at the client side of things.
This is the primary problem I am experiencing:
When I add the computer (windows XP Pro) to the new domain by using the "change domain" function I get a new user created with the name of the domain attached to the name (nnnnn.dddd) in my users list. So I end up with a new Desktop environment for the user. Not what I want. This happens whether I use the old domain user name or the new domain user name.
I was considering recreating the domain on Windows Server 2003 and naming it the same as the old NT domain, so that the user name would end up being the same as it was. My hope is that the desktop, software installs and working environment would be the same as it was.
By the way, what is the difference between the two methods of adding a computer to a domain. 1) Network ID and 2) Change. I have used the Change for my early atempts at making this as painless as possible.