Promote Application Server and Demote Domain Controller Windows 2003 Server

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.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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.

Walter PadrónCommented:
Hi donaljcox ,

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

Steps outlined here
donaljcoxAuthor Commented:
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.
IT Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

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.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
donaljcoxAuthor Commented:
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 ?
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.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.