Demoting a DC
-
Friday, November 16, 2012 6:39 PM
what can i do to demote a dc while users are logged on ? i have 3, going down to 2...besides doing it before / after hours, ( which is doable)
Thx
Steven J Einhorn
All Replies
-
Friday, November 16, 2012 7:21 PM
Run DCPROMO, this wizard will take less than 30 minutes. Before you demote the DC make sure everything in your domain is pointing to functioning DC's. If you do not do that first after the demotion you will here about issues real fast.- Marked As Answer by Trapps Friday, November 16, 2012 7:42 PM
-
Friday, November 16, 2012 7:22 PMi did already transfer all the roles...
Steven J Einhorn
-
Friday, November 16, 2012 7:25 PM
Before you demote the dc ensure that dns setting of the client PC is pointing to other two online DC(preferred/alternate dns setting) this may be in DHCP options or the TCP/IP settings.
Also ensure that both DC are configured with DNS/GC role.Also check the health of other DC's before you proceed run dcdiag /q and repadmin /replsum to check the same.I would recommend to perfrom the demotion of DC during non business hours if possible.
How to demote/decommision the Servers
http://technet.microsoft.com/en-us/library/cc740017(WS.10).aspx (how to demote a DC)
http://technet.microsoft.com/en-us/library/cc755937(WS.10).aspx (how to decommisioning a DC)
http://technet.microsoft.com/en-us/library/cc771844(WS.10).aspx (how to removing a DC from a Domain)Hope this helps
Best Regards,
Sandesh Dubey.
MCSE|MCSA:Messaging|MCTS|MCITP:Enterprise Adminitrator | My Blog
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.- Marked As Answer by Trapps Friday, November 16, 2012 7:42 PM
-
Friday, November 16, 2012 7:27 PMall clients are pointing to new dc...dns all set,,,health all good...my concern was that some users may have grabbed that dc when they logged on this morning
Steven J Einhorn
-
Friday, November 16, 2012 7:33 PM
That is good, make sure your DHCP, Memeber servers, workstations, etc point to the other DC's and not the DC being demoted. Once it is demoted go onto your functioning DC and in DNS under your DNS zone properties select Name Servers tab and remove the demoted DC from the list if it is in there, next go into AD Sites and services and delete the demoted DC object ( You will know it is ok to delete if you do not see an NTDS settings object under the server name.)
-
Friday, November 16, 2012 7:37 PMwe are all static ip's here...but i will make that change in the zones...thx !
Steven J Einhorn
-
Friday, November 16, 2012 7:41 PM
AD replicates all the the user information so you should be good. There is a possiblity that a workstation may fail to logon if that happens restarting it or restarting the netlogon service should fix it.
By removing the DC from the DNS Server list your systems should not try to go to it for DNS Resolution of any kind
-
Friday, November 16, 2012 7:42 PM
yea,,,thats true...i will probably do it before my users head in Monday morning...its all good and ready to roll!
Thx
Steven J Einhorn
-
Friday, November 16, 2012 7:44 PM
If the demotion is graceful then all the records will be removed automatically however cross check the dns zone,AD sites and services and DC OU if the demoted DC object is present then remove the same.Regrading the clients there should be no problem other server will response to client query assuming that dns setting is pointing to other online DNS servers.Best Regards,
Sandesh Dubey.
MCSE|MCSA:Messaging|MCTS|MCITP:Enterprise Adminitrator | My Blog
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.- Marked As Answer by Trapps Friday, November 16, 2012 7:45 PM
-
Friday, November 16, 2012 7:46 PMyes correct, thx
Steven J Einhorn

