Solved

Demote Windows Server 2012 Domain Controller

Posted on 2013-11-07
5
954 Views
1 Endorsement
Last Modified: 2013-11-11
Ok, so I just installed a new Windows 2012 server and promoted it to a domain controller in an existent 2003 domain. The 2003 domain controller is still, running, I haven't done anything with it.  The servers have probably been replicating about a day by time anyone reads this. The Windows 2012 server is a hyper V machine. It is running the domain controller on the host as I have not created any virtual machines yet.  I've decided after researching that it would be better to just leave the host as a member server to save resources and spin up a virtual machine as the 2012 domain controller instead.  My question is, what is the best way to demote the 2012 server back to a member server?  It shouldn't have any negative impact on the domain since it is still on a functional level of 2003, correct?  Please give me steps.  Thanks.
1
Comment
Question by:schmad01
5 Comments
 
LVL 24

Expert Comment

by:Sandeshdubey
ID: 39632803
You can refer this to demote the DC http://terrytlslau.tls1.cc/2012/03/domain-controller-demotion-on-windows.html  http://technet.microsoft.com/en-us/library/jj574104.aspx.Demoting the Win2012 DC should not have negative impact.Howvere ensure that fsmo role is move to old DC if you have transfered the fsmo role to Win2012 DC.
0
 
LVL 7

Expert Comment

by:Sumit Gupta
ID: 39632871
It should be fine. But remember to transfer those FSMOs to those Windows 2003 domain controller if the Windows 2012 holds some roles.
In addition, hope you have not upgrade your functional level, if you raised functional level to windows 2003 above, then we could not demote the Windows 2012 DC, but should demote those Windows 2003 DCs.
0
 

Author Comment

by:schmad01
ID: 39633193
The functional level is at windows 2003, not above.  The windows 2003 server still holds all fsmo roles. Should be ok to procede, correct?
0
 
LVL 34

Accepted Solution

by:
Seth Simmons earned 500 total points
ID: 39633795
schmad01 - go ahead and demote the server

sumit - with that 2003 DC still in place the functional level can't be raised anyway so that is a non-issue here

if the new 2012 domain controller will run under hyper-v then don't do away with the 2003 server without building another physical box else if you have to reboot that 2012 physical server, the virtual machine isn't started yet and nothing to login to and will screw yourself
0
 

Author Closing Comment

by:schmad01
ID: 39640590
Thank you.
0

Featured Post

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

In this article, we will see the basic design consideration while designing a Multi-tenant web application in a simple manner. Though, many frameworks are available in the market to develop a multi - tenant application, but do they provide data, cod…
A project that enables an administrator to perform actions within a user session context not just at the time of login but any time later on day(s) or week(s) later.
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …

830 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question