Logo
Windows XP
Windows Vista
Windows 7
Windows Azure
Windows Server
Windows Phone
PREGNANCY
 
 
Windows Server

Windows Server 2012 : Enabling and disabling the graphical interface in Hyper-V

7/22/2013 5:39:15 PM

Server Core has many installation benefits, but there are a few situations where the GUI is better and provides more options; for example, when we need to troubleshoot a problem on the server. Even with the handy tools from the previous task, nothing replaces the full server installation.

Windows Server 2012 allows the GUI installation and uninstallation; making our job easier when the GUI is necessary and providing all the benefits of a Server Core installation when you need it. It also allows a third option that enables the graphical management tools.

The three options available on Windows Server 2012 are as follows:

  • Server Core: This option provides default installation with command line interface only
  • Minimal Server Interface: This option comes with the Server Manager, Microsoft Management Console (MMC) and some Control Panel options
  • Server Graphical Shell: This option allows for a full graphical interface server

By installing Windows Server with Server Core, you can save up to 3 GB of disk space, when the necessary components for the graphical interface are not present.

This recipe will show how to enable all the three options.

Getting ready

To follow the recipe make sure you have a Server Core installation of Windows with the installation media inserted onto the server.

How to do it...

The following steps will show you how to install the minimal server interface from a Server Core installation and how to enable the full graphical interface.

  1. From the Server Core command line, type PowerShell to load PowerShell.

    To identify the index number that need to be used in order to enable the graphical interface, type the following command line, where D:\ is the path for the Windows Server installation DVD drive.

    Get-WindowsImage –ImagePath D:\Sources\Install.wim
    
  2. A list with the index number will be displayed, as shown in the following screenshot. Make a note of the number of the type of Windows Installation you want to enable in the next step. In this demonstration, the index number 2 will be used.
    How to do it...
  3. Create a new temporary folder to mount the WIM file with the following command:
    New-Item C:\Sources –Type Directory
    
  4. To mount the image file in the directory created in the previous step, type the following command by specifying the index number obtained in step 3.
    Mount-WindowsImage –ImagePath D:\Sources\Install.wim –path C:\Sources –Index 2 -ReadyOnly
    
  5. With the mounted image, type the following command to enable the Server Graphical Management Tool and the Infrastructure option.
    Install-WindowsFeature Server-Gui-Mgmt-Infra –Source C:\Sources\Windows\Winsxs
    
  6. Restart the server and wait for the feature to be configured. It will take a couple of minutes.
  7. To enable the full graphical interface, open Server Manager by typing servermanager.exe.
  8. In the Server manager dashboard, click on Add roles and features.
  9. In the Add Roles and Features Wizard, click on Next four times.
  10. In Features, expand User Interfaces and Infrastructure, select the option Server Graphical Shell as shown in the following screenshot, and click on Next:
    How to do it...
  11. To complete the installation, in the Confirm installation selections page, click on Install.

    Note

    You can also install the full graphical interface with the following PowerShell command:

    Install-WindowsFeature Server-Gui-Shell
    
  12. After the setup, you need to restart the server. You can check the Restart each destination server automatically if required option to automatically restart the server.
  13. Having enabled the GUI, we can now see how to uninstall the GUI from the full server installation. In the Server Manager window, click on Manage and then Remove Roles and Features.
  14. In the Before You Begin screen, click on Next four times.
  15. Then, in Features, clear the check box for the Server Graphical Shell option and click on Next.
  16. Confirm the uninstallation by clicking on Remove and wait for the server to be restarted.

How it works...

When Server Core is installed, it doesn't contain the necessary installation files to enable the graphical interface options. It helps to deploy your server core installations with much lesser disk space requirements. For environments where server deployment is done via OS deployment server, you can save a couple of gigabytes with Server Core. After the installation, you will be able to enable the graphical interface. But the installation files should be provided so that the operating system can install and configure the new features. You can use a local DVD drive or a shared folder containing the source folder of the Windows Server installation media.

With the minimal server interface, components such as Windows Explorer and Internet Explorer are not installed. However, Server Manager, Microsoft Management Console (MMC) and some control panel options that are available, which provide you the basic tools to manage your Server Core without the need to use command line.

The Server Graphical Shell installs all the graphical components, thus transforming your server into a full server installation.

With this new feature, it is now easier to allow the GUI only when needed, for example for a troubleshooting scenario or perhaps an installation of a new service.

Other -----------------
- Windows Server 2012 : Managing a Server Core installation using sconfig
- SQL Server 2012 : Running SQL Server in A Virtual Environment - EXTENDED FEATURES OF VIRTUALIZATION
- SQL Server 2012 : Running SQL Server in A Virtual Environment - VIRTUALIZATION CONCEPTS
- SQL Server 2012 : Running SQL Server in A Virtual Environment - COMMON VIRTUALIZATION PRODUCTS
- What's new and improved in SharePoint 2013 : Creating an asset library
- What's new and improved in SharePoint 2013 : Using the Office Store
- What's new and improved in SharePoint 2013 : Customizing the interface
- What's new and improved in SharePoint 2013 : Creating a new site
- System Center Configuration Manager 2007 : Configuring Desired Configuration Management
- Extending Dynamics GP with Free Software : Preventing date errors with DocDateVerify, Executing SQL from the Support Administrator Console
- Extending Dynamics GP with Free Software : Checking Dynamics GP spelling with Willoware
- Microsoft Lync Server 2010 : Planning for Voice Deployment - Enhanced 911
- Microsoft Lync Server 2010 : Planning for Voice Deployment - Media Bypass
- Microsoft Lync Server 2010 : Planning for Voice Deployment - Network Configuration, Call Admission Control
- SQL Server 2012 : Running SQL Server in A Virtual Environment - WHY VIRTUALIZE A SERVER?
- SQL Server 2012 : Running SQL Server in A Virtual Environment - AN OVERVIEW OF VIRTUALIZATION
- Windows Server 2012 Group Policies and Policy Management : Understanding Group Policy (part 3) - GPO Filtering, Group Policy Loopback Processing
- Windows Server 2012 Group Policies and Policy Management : Understanding Group Policy (part 2) - Group Policy Link Enforcement, Group Policy Inheritance, Group Policy Block Inheritance
- Windows Server 2012 Group Policies and Policy Management : Understanding Group Policy (part 1) - GPO Storage and Replication
- Windows Server 2012 Group Policies and Policy Management : Local Group Policies, Domain-Based Group Policies
 
 
Most view of day
- Managing Windows Small Business Server 2011 : Adding a Terminal Server (part 3) - Configuring RD Licensing
- Windows Phone 8 : Working with the Windows Phone Software (part 7) - Removing Multimedia Content - Removing a Video from Your Phone
- Windows Phone 8 : Developing for the Phone - The Phone Experience (part 4) - Understanding Idle Detection, The Tilt Effect
- Maintaining Dynamics GP : Troubleshooting issues with a DexSQL log
- System Center Configuration Manager 2007 : Operating System Deployment - Drivers
- Workflow in Dynamics AX 2009 : Workflow Life Cycle (part 2) - Creating the Workflow Document Class
- Using Wireless Bluetooth Devices : Adding Bluetooth-Enabled Devices
- Adobe Dreamweaver CS5 : Working with Multimedia and Online Tools - Using ActiveX Controls
- Windows Server 2008 R2 high-availability and recovery features : Installing and Administering Failover Clustering (part 6) - Add primary storage to cluster, Configure service or application
- System Center Configuration Manager 2007 : Available Reports and Use Cases (part 2) - Reporting on Sites, Reporting on Configuration Manager Operations
Top 10
- SQL Server 2012 : Understanding Latches and Spinlocks (part 3) - Latching Example - With Latching
- SQL Server 2012 : Understanding Latches and Spinlocks (part 2) - Latching Example - Without Latching
- SQL Server 2012 : Understanding Latches and Spinlocks (part 1) - Latching Example
- SQL Server 2012 : Latches and Spinlocks - Symptoms (part 2) - Measuring Latch Contention, Measuring Spinlock Contention , Contention Indicators
- SQL Server 2012 : Latches and Spinlocks - Symptoms (part 1) - Recognizing Symptoms
- Integrating SharePoint 2013 with the Office Applications (part 10) - Microsoft Outlook - Lists and Libraries
- Integrating SharePoint 2013 with the Office Applications (part 9) - Microsoft InfoPath - Customizing the Document Information Panel and List Forms
- Integrating SharePoint 2013 with the Office Applications (part 8) - Microsoft InfoPath -Deploying a Form Via Central Administration, Rendering a Form Using the InfoPath Form Web Part
- Integrating SharePoint 2013 with the Office Applications (part 7) - Microsoft Access - Access Services
- Integrating SharePoint 2013 with the Office Applications (part 6) - Microsoft Access
 
 
Windows XP
Windows Vista
Windows 7
Windows Azure
Windows Server
Windows Phone
2015 Camaro