Recently, I decided to add a second domain controller to my mikefrobbins.com domain. The existing server and this new server that will become a domain controller both run the Microsoft Windows Server 2012 operating system and both were installed with the default installation type of server core (no GUI). Even though the GUI can be turned on and off in Windows Server 2012 (unlike in Windows Server 2008 and 2008 R2), I prefer not to add the GUI unless absolutely necessary.
You have a server which runs the Windows Server 2008 R2 with SP1 operating system that was installed using the “Server Core Installation” option (no-GUI): ](/images/2012/04/ps2-2008r2core01.png" height=“480)You’ve given this server a name, added it to the domain, configured the IP address settings, and configured options 1 -3 in the “Configure Remote Management” portion of sconfig as shown in the following image: ](/images/2012/11/sc-ps3-failure1.png” height=“503)PowerShell version 2 works fine on the server, but you’ve been tasked with loading PowerShell version 3 on it.
You have a fresh installation of Windows Server 2012 that was installed using the default installation type of server core installation (no-GUI). This server will be the first domain controller in a brand new Active Directory forest. Log into the server and launch PowerShell by typing “powershell.exe”. You’ll need to first add the AD-Domain-Services role to the server: Add-WindowsFeature AD-Domain-Services The installation of this role completes and a restart is not required:
While at TechEd last month I heard two things that I’ve been preaching for a while. Server Core installation (no-GUI) is the recommended installation type beginning with Windows Server 2012. I’ve been saying this for a while when it comes to Windows Server 2008 R2. Server Core: Reliability and Uptime In each of three datacenters that I support there are multiple Hyper-V servers that run Windows Server 2008 R2 w/SP1 with the Core Installation (Server Core).