TPBPIT
asked on
Removing DNS and Demoting server
I have a couple DCs that all have DNS on them. There is one that I'm going to move to VMWare and want to demote it and remove DNS before I shut it down and bring it up in a VMWare session. There are no FSMO Roles on this particular box, but it does have a copy of the GC on it. Likewise, I plan on reusing the NetBIOS name of this box on the new VMWare session. Also, I plan on it being a DC and DNS server again and using the same IP address.
My question is what order do I need to remove DNS and do the demote in? Specific steps would be helpful and any known pitfalls would be great.
My question is what order do I need to remove DNS and do the demote in? Specific steps would be helpful and any known pitfalls would be great.
Last Comment
Brian Pierce
It would be wise to demote the machine and then remove DNS. If its going to be down for a while then it may be wise to make sure that any clients that use this server as their DNS server are pointed to al alternate DNS server.
Move the GC using AD Sites and Services:
http://support.microsoft.com/kb/295419
AFAIK you don't need to specifically remove DNS, just demote (using dcpromo). But if you really wanted to you could remove DNS from Add/Remove Programs/Windows Components.
Use dcpromo again in the VM to promote to a DC.
Steve :)
http://support.microsoft.com/kb/295419
AFAIK you don't need to specifically remove DNS, just demote (using dcpromo). But if you really wanted to you could remove DNS from Add/Remove Programs/Windows Components.
Use dcpromo again in the VM to promote to a DC.
Steve :)
1. Remove the GC role (and verify AD replication of this change)
2. Verify no FSMO roles (and verify AD replication of this change)
3. Verify no clients/servers are pointing to this DNS server through DHCP or static assignment..
4. Verify final replication of AD.
5. dcpromo the server.
6. Remove DNS or at least Disable the service.
2. Verify no FSMO roles (and verify AD replication of this change)
3. Verify no clients/servers are pointing to this DNS server through DHCP or static assignment..
4. Verify final replication of AD.
5. dcpromo the server.
6. Remove DNS or at least Disable the service.
ASKER
mren08, how do I verify the final replication of AD? Likewise, is there an easy way to check where the FSMO roles reside? I haven't done that in a few, several years.
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
to check FSMO role holders see http://www.petri.co.il/determining_fsmo_role_holders.htm, there is also a link a page showing how to transfer then if you need to
ASKER
Thanks. Its been several years since I had to do this and I didn't want to screw it up.
Windows Server 2003
Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).
129K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
