cdavidson0724
asked on
Question after upgrading NT4 PDC to Windows 2003 DC
My company is in the planning phases of upgrading from an NT4 domain to Active Directory (I know...I know, what took so long?). Right now I am playing around with different migration/upgrade strategies in our test lab and have come accross something interesting...
I took my NT4 PDC and used the Windows 2003 CD to upgrade it to an Active Directory DC. The upgrade process went smoothly. Prior to the upgrade, I had a member server and a workstation joined to my old domain. Once I upgraded the NT4 PDC to 2K3, both of the domain member machines seemed to have immediate membership in the new AD domain. If you view the domain membership inside of systems properties, newdomain.com is listed, as it should be. However, when you initially log on to either of these machines you see the name of the old domain and the name of the local machine in the log onto box. The name of the new domain does not show up in the log onto box. When you log onto the domain controller, you see the name of the old domain in the log onto box, not the new domain. Also, when I view the ACL on shared folders and such, groups and users are listed as OLDDOMAIN\group, not NEWDOMAIN\group. Everything seems to work, I'm just wondering how to remove these references to the old domain. Thanks in advance.
I took my NT4 PDC and used the Windows 2003 CD to upgrade it to an Active Directory DC. The upgrade process went smoothly. Prior to the upgrade, I had a member server and a workstation joined to my old domain. Once I upgraded the NT4 PDC to 2K3, both of the domain member machines seemed to have immediate membership in the new AD domain. If you view the domain membership inside of systems properties, newdomain.com is listed, as it should be. However, when you initially log on to either of these machines you see the name of the old domain and the name of the local machine in the log onto box. The name of the new domain does not show up in the log onto box. When you log onto the domain controller, you see the name of the old domain in the log onto box, not the new domain. Also, when I view the ACL on shared folders and such, groups and users are listed as OLDDOMAIN\group, not NEWDOMAIN\group. Everything seems to work, I'm just wondering how to remove these references to the old domain. Thanks in advance.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I beleve that netbios name goes away when you raise the domain funcinal level from 2003 interm to 2003 native
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Good points guys...
I actually am using .local on my AD domain name. My old domain is an acronym for my company, lets say ABCD, and my new domain is the actual company name, companyname.local. I will raise the domain functional level from Windows 2003 interim and see if that clears this up.
I actually am using .local on my AD domain name. My old domain is an acronym for my company, lets say ABCD, and my new domain is the actual company name, companyname.local. I will raise the domain functional level from Windows 2003 interim and see if that clears this up.
Most domains use the netbios name as the prefix of the FQN name. Unless you have a specific reason I would just create the domain with the same name as the netbios, it will make things less confusing.
For example:
If you current domain is called ABCD then I would name the W2k3 domain ABCD.local
For example:
If you current domain is called ABCD then I would name the W2k3 domain ABCD.local
ASKER
Point taken...
I raised the functional level to Windows 2003 and the NetBIOS name is still around. I will certainly consider using ABCD.local as the production domain name when the time comes, but for the sake of knowing, is there any way to change the NetBIOS name of a domain without causing disruption to domain users and computers?
I raised the functional level to Windows 2003 and the NetBIOS name is still around. I will certainly consider using ABCD.local as the production domain name when the time comes, but for the sake of knowing, is there any way to change the NetBIOS name of a domain without causing disruption to domain users and computers?
Here is a KB Article on how to change the netbios name of your domain while it's still NT4. Once you change the name then do your upgrade to AD. Remember to create a new BDC (can be an old pc) and take it offline before starting...this will be your backup.
http://support.microsoft.com/kb/q178009/
http://support.microsoft.com/kb/q178009/
ASKER