Joining a Web Server to a Domain

Current Situation:
Two Machines:
        Server #1 - Exchange Server | current Domain Controller for small company (about 10-15 users)
        Server #2 - Web Server with Virtual Machine software installed so that Development Web Server is on the same box | also houses database used by website | was the old Domain Controller for company, and although it is not acting as such, it still has AD installed and thinks of itself as a Domain Controller.

I am wanting to add Server #2 to the Domain of Server #1.  I am thinking that I need to uninstall/disable AD from Server #2 and then add it to Server #1 as you would any computer.  This seems to me, too simple of a project though to be correct…..or is it?  Is there any special configurations I need to do when adding a web server to a domain?

Side Note:  I didn’t set this up, just the situation I was hired into a few weeks ago.  Currently working on getting a 3rd machine to separate the production web server and the development web server; but right now it is working.  
LVL 10
Who is Participating?
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.

Chris DentPowerShell DeveloperCommented:

I strongly recommend you don't do it.

MS do not support an Exchange Server changing it's Domain Role after installation (by either making it a Domain Controller, or demoting it to a Member Server if it already is a DC).

This is covered by this KB Article:

P1ST0LPETEAuthor Commented:
No, I'm keeping the Exchange Server as the Domain Controller.  I want to add the web server to the Exchange Server's Domain.
Chris DentPowerShell DeveloperCommented:

Oh I'm sorry, misunderstood (clearly).

Last time I switched the domain for an IIS server it decided it would be fun to play with the IUSR accounts (despite them all being local user accounts).

If it's a small environment that's generally not much of a problem at all and can be very quickly corrected.

But that was the only problem I ran into. If IIS is running on a DC then it gets a little more tricky, it configures the IUSR account as a Domain Account, which after DCPromo would cease to exist.

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

P1ST0LPETEAuthor Commented:
Yes, IIS is running on a DC, but it's a DC that is inactive.  All workstations in office are connected to the Exchange DC.  So basically have two domains in the office right now, and I only want one.  Since all workstations are connected to the Exchange Server DC, I figured I could make the Web Server no longer a DC, and join it too they Exchange DC.
Not really sure the process on all this though, and I don't want make the website inaccessible.
I've never joined a server to a domain before, only workstations.  Wasn't thinking it was too much different.
Chris DentPowerShell DeveloperCommented:

The process is identical. The only extra step you have is the DCPromo to make it a Member Server again (from it's current situation).

I don't think there's much of an easy way around a little downtime to fix any issues with IIS. However, the amount of work really is quite minimal for a website or two, it's only when you scale that up to several hundred that things start to get a bit rushed.


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
P1ST0LPETEAuthor Commented:
What exactly is the DCPromo?
Chris DentPowerShell DeveloperCommented:

That's the program you will use to stop it being a Domain Controller:

"although it is not acting as such, it still has AD installed and thinks of itself as a Domain Controller."

It will remove that and turn it into a Stand Alone server (no domain membership). Then you can join it to the new Domain and you're done.


As said Chris-Dent:

1- Demote Server 2 from domain controller to standalone server, for this use DCPROMO which will uninstall active directory on it.
2- If you are using static IP on server2, make sure name resolution works between him and server 1 domain, I recommend you set it as DNS client of Server1 supposing it is a DNS server.
3- Add server2 to Server 1 domain.

That's it.
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
Microsoft Server OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.