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).
As with most things in IT, the answer is that it depends. It depends on whether or not the server was installed with the Full Installation or with the Server Core Installation. It also depends on what your definition of installed is. If the server was installed with the Full Installation (GUI) then PowerShell is installed (enabled) by default, but if it was installed using the Server Core Installation (no GUI) then PowerShell is not installed (not enabled) by default.
Last week, I published a blog on Installing SQL Server Denali CTP3 on Server Core and then SQL Server 2012 RC0 was made available for download so I thought I’d write an updated blog since the issues I ran into with the installation seem to be resolved. One of the new features in SQL Server 2012 is official support from Microsoft for installation on Server Core. There’s an MSDN article on Install SQL Server 2012 on Server Core and another MSDN article on Install SQL Server 2012 from the Command Prompt that has a detailed list of all the different parameters.
One of the new features in SQL Server Denali CTP3 is support for installation on Server Core. There’s an MSDN article on Installing SQL Server Denali on Server Core and another MSDN article on Install SQL Server Denali from the Command Prompt that has a detailed list of all the different parameters. Based on the first article, the setup routine should enable and/or install all of the necessary prerequisites, but that simply isn’t the case from what I found.
I recently ran into an issue where I couldn’t start any additional virtual machines on a Hyper-V server that was running Windows Server 2008 R2 Enterprise Edition - Core Installation (no GUI). After a little research, I determined that the operating system had created a pagefile of over 100 gigabytes in size which was using up the majority of the DAS in the server. The server has 96GB of RAM which is the reason why the operating system automatically configured such a large pagefile.
There are multiple reasons why you might want to run the Dell System E-Support Tool (DSET) on your Dell PowerEdge server. It could be because Dell Support has requested it or you’re trying to diagnose a problem or you simply want to know what version of BIOS your server is running without having to reboot it. This tool is especially useful when it comes to Windows Server 2008 R2 core installation since many other utilities will not run on server core.
To change the serial number on your Windows Server 2008 Core Installation, run “slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX” where X is your new serial number. Wait for the popup confirmation message that the serial number has been changed: Run “cscript c:\windows\system32\slmgr.vbs -ato” to activate the operating system: µ
Problem: You receive an error Virtual Disk Manager “The RPC server is unavailable” when attempting to remotely manage Hyper-V Server 2008 or Windows Server 2008 Core Installation: Solution: Run the following command on the client and on the server: netsh advfirewall firewall set rule group="Remote Volume Management" new enable=yes You have the option of using the Server Configuration menu on the server side if your using Hyper-V Server 2008. Select option 4, Configure Remote Management:
Problem: You’ve closed your command prompt window on Hyper-V Server 2008 or Windows Server 2008 Core Installation and need to re-open it: Solution: Start Windows Task Manager by pressing Ctrl & Shift & Esc. Click File>New Task: Type cmd.exe and click ok: You now have a new command prompt window: µ