[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now


Promote Application Server and Demote Domain Controller Windows 2003 Server

Posted on 2006-04-10
Medium Priority
Last Modified: 2008-03-17
Current Environment: I have a single Windows 2003 Server that is a Domain Controller with AD and is running DNS. I have a single Windows 2003 Server that is a basic application server.
Goal: I want the single Windows 2003 Server that is the DC with AD and DNS to become purely an Application Server not running DNS. I want the single Windows 2003 that is a basic application server to become the DC with AD and DNS.
Can you outline a step-by-step procedure and in what order I must do to achieve my goal. I want all accounts (user and computer) to be pulled over onto the new DC.
Question by:donaljcox
  • 3
  • 2
LVL 51

Expert Comment

ID: 16421510
What kind of servers are these?  If they are brand name servers with similar low-level hardware it may be possible to simply move the drives between servers.

LVL 10

Expert Comment

by:Walter Padrón
ID: 16421611
Hi donaljcox ,

The order is, first promote your app server then demote your DC

Steps outlined here http://www.experts-exchange.com/Operating_Systems/Windows_Server_2003/Q_21800163.html

Author Comment

ID: 16421620
HP and Dell. However, I cannot afford to move drives between servers.The current AD server is running an important database so I do not want to do this.
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

LVL 51

Accepted Solution

Netman66 earned 500 total points
ID: 16421703
Then promote the App server, move the FSMO roles, then demote the current DC.  Don't forget to make the App server a GC before demoting the original server.

If any of these servers has Exchange, you CANNOT change the role of the server it's installed on - Exchange will break.


Author Comment

ID: 16421719
Exchange is not on any of the servers. Do I need to add DNS before I promote the App server or do I do this afterwards ?
LVL 51

Expert Comment

ID: 16421785
Do it afterwards.

Once the App server is a DC, make it a GC.  
Make sure the DNS zones are all AD Integrated on the original DC.
Install DNS to the App server.  DO NOT create anything manually.
Restart Netlogon service on the new DC.
Wait for DNS to replicate.
Move the FSMO roles gracefully and allow an hour of steady state before demoting anything.
Turn off the old DC to test the client connectivity before you demote it.  You'll spot any issues once the old DC is off.

You should be good to go.


Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

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

The HP utility "HP Lights-Out Online Configuration Utility for Windows Server 2003/2008" could be of great use when it comes to remotely configure a HP servers ILO WITHOUT rebooting the server. We would only need to create and run scripts using thi…
Many of us need to configure DHCP server(s) in their environment. We can do that simply via DHCP console on server or using MMC snap-in on each computer with Administrative Tools installed in a network. But what if we have to configure many DHCP ser…
Integration Management Part 2
As many of you are aware about Scanpst.exe utility which is owned by Microsoft itself to repair inaccessible or damaged PST files, but the question is do you really think Scanpst.exe is capable to repair all sorts of PST related corruption issues?

834 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