FIFBA
asked on
Problems after renaming domain controllers and member servers (2003/2000).
I'm inheriting a 2003 Windows Network configured as follows:
1-2003 Small Business Server (domain controller and Exchange server, all FSMO roles)
1-2003 Server acting as a redundant domain controller
2-2000 Member Servers for additional services (DHCP, File Server, etc.)
Here are some recent changes that I am aware of...
I know that 2 new servers were added to this environment (the 2003 servers). Both of the 2000 boxes were demoted from domain controllers making the 2003 servers the only domain controllers. Everything is running at 2000 functional level. After the upgrades were completed, the machines (including domain controllers) were renamed. I know this is a new feature in 2003...All documentation I see says that the forest must be operating at 2003 functional level in order to change DC names, however I verified that the forest is running at 2000 level (not sure if this is a factor or not).
And now the problem...
Ever since these events took place, the backup server (2000 server running Backup Exec 10D) is unable to successfully authenticate with the 2003 small business server only in order to collect data via a remote agent. After digging through the 2003 SBS, I see that the old 2000 servers are still listed by their old names in Active Directory Sites and Services. Both of the 2003 servers are listed correctly. In Active Directory Users and Computers both 2003 servers are listed correctly as domain controllers. I am looking through event viewer and everything looks clean, no NTFRS, DNS, or Directory service errors..
How do I attack this problem? I am looking over Microsoft Article ID 316826. Is this what I need to do to resolve? I am unable to communicate with the person who performed the upgrades, etc. so I'm not sure what procedure was followed for renaming the domain controllers, etc. Hopefully someone with some experience renaming 2003 domain controllers and/or 2000 servers can point me in the right direction.
1-2003 Small Business Server (domain controller and Exchange server, all FSMO roles)
1-2003 Server acting as a redundant domain controller
2-2000 Member Servers for additional services (DHCP, File Server, etc.)
Here are some recent changes that I am aware of...
I know that 2 new servers were added to this environment (the 2003 servers). Both of the 2000 boxes were demoted from domain controllers making the 2003 servers the only domain controllers. Everything is running at 2000 functional level. After the upgrades were completed, the machines (including domain controllers) were renamed. I know this is a new feature in 2003...All documentation I see says that the forest must be operating at 2003 functional level in order to change DC names, however I verified that the forest is running at 2000 level (not sure if this is a factor or not).
And now the problem...
Ever since these events took place, the backup server (2000 server running Backup Exec 10D) is unable to successfully authenticate with the 2003 small business server only in order to collect data via a remote agent. After digging through the 2003 SBS, I see that the old 2000 servers are still listed by their old names in Active Directory Sites and Services. Both of the 2003 servers are listed correctly. In Active Directory Users and Computers both 2003 servers are listed correctly as domain controllers. I am looking through event viewer and everything looks clean, no NTFRS, DNS, or Directory service errors..
How do I attack this problem? I am looking over Microsoft Article ID 316826. Is this what I need to do to resolve? I am unable to communicate with the person who performed the upgrades, etc. so I'm not sure what procedure was followed for renaming the domain controllers, etc. Hopefully someone with some experience renaming 2003 domain controllers and/or 2000 servers can point me in the right direction.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I think there are around 40 users.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Even with 40 users I might be tempted to just blow the whole thing out and start over. I would much rather look at a domain and say "Yes, I'm confident that this is configured correctly because -I- did it", rather than "Good grief, what -else- did Skippy my Genius Predecessor do wrong that I haven't found out about yet?"
ASKER