Exchange 2013 Cluster - Part 3 - Setup 2012 Active Directory

Exchange 2013 Cluster - Part 3 - Setup 2012 Active Directory

So, in order to have Exchange, you have to have Active Directory, at least since Exchange 2000.  In times past, in order to install AD, you would run dcpromo on the server (usually after adding to the domain) and after a few deceivingly simple questions, an AD DC server you would have. Voila.

Now to install AD, there's more steps to fit into the new "role and feature" paradigm.

1. Run the Add Roles and Features wizard.
   
2. Choose next, next, next to get to where you can choose "Active Directory Domain Services".
3. You will get a prompt about installing additional related features like this.  Click Add Features.

4. After that, you're Role selection screen should look like this. Click Next.

5. On the Features selection page, you'll notice Group Policy Management is already selected.
6. Click next, next, Install.
7. Once that finishes, in the top right of Server Manager, there will be a flag with an exclamation sign and if you click on it you will see the following. Click the link to Promote this server...

8. After that the wizard will prompt you what kind of DC you want, in my case for a test domain, I will be creating a new Forest and will chose such option and click Next.

9. Some checks will be performed in DNS and NetBIOS to make sure this domain doesn't already exist anywhere THAT THIS MACHINE CAN FIND. 
1. NOTE: this doesn't mean it doesn't exist anywhere but because of the current DNS settings and network location, it can't find it anywhere else.  Remember NetBIOS has broadcast ability.
10. On the next screen, choose the functional level and DC capabilities and enter the DS Restore password.
1. There's usually not (read: never) much reason to uncheck DNS or GC...its really the only way to make sure all DC's are created equal (aside from FSMO roles which are malleable....word of the day!!!).
11. After you click next, you'll get some nonsense about can't create a delegation, but that's because in my case (as in most cases) you don't control the ROOT dns servers (e.g .com)! Just click Next.
1. This would not be true (I believe) in the case of making a subdomain such as  sub.domain.com. In this case, the install could contact the owner of domain.com and setup a delegation.  Note: I could be wrong on that whole last sentence, but I'm confident.
12. NetBIOS will broadcast to make sure this domain doesn't already exist anywhere THAT THIS MACHINE CAN FIND.  Confirm the desired NetBIOS name and click Next.
13. I generally leave the default file paths (you may not do this in production depending on the (expected) size of your AD. Next.
14. Now you will get a lovely summary screen of all those life choices you just made.

15. Make note of the View Script button (circled in red) which will show you the glorious power of Powershell to do everything the last 8 steps did. Click Next.
1. In my case it looks like...
1. Import-Module ADDSDeployment Install-ADDSForest -CreateDnsDelegation:$false -DatabasePath "C:\Windows\NTDS" -DomainMode "Win2012" -DomainName "test.com" -DomainNetbiosName "TEST" -ForestMode "Win2012" -InstallDns:$true -LogPath "C:\Windows\NTDS" -NoRebootOnCompletion:$false -SysvolPath "C:\Windows\SYSVOL" -Force:$true
16. Checks will be run, security warnings will be ignored and INSTALL!
17. After running the install, the server will reboot and you are DONE!!.
18. Now go fix the DNS settings and so the Internet will still work.

Special Note: If you'd like to use PowerShell to do ALL OF THE ABOVE...use this Scripting Guy TechNet Blog article.

Next:  Part 4 - Exchange install in the Main Site.