Customizing the Interface with Features on Demand with windows server 2012

Features on Demand can be used to remove specific roles and features. By cherry-picking which components reside on your server, you can save disk space. In Hyper-V virtual machines, Features on Demand reduces the footprint of a virtual machine—insome instances, removing particular roles and features can reduce the size of a virtual machine by more than one gigabyte.

Figure 1. Minimal Server Interface

This is one of my favorite features in Server 2012. I’m not quite sure why Microsoft isn’t singing the praises of Features on Demand and hitting administrators over the head repeatedly about how great it is, instead of going on about Server Core install recommendations. Minimal Server Interface is a far better and more flexible option than simply going with a Server Core install if you don’t want the full GUI; it’s a customized GUI
that you pretty much design based on your management needs.

Another big advantage in Server 2012 over previous server versions is that in prior versions of Windows servers, you could disable server roles and features, but the binary files for them remained on the server. With Server 2012, however, these files are fully removable. Uninstalling files associated with server roles and features is a state called “disabled with payload removed.”

To remove these roles and features, you can use a PowerShell cmdlet. For instance, to remove Windows Explorer, Internet Explorer, and all dependent components, you can run the command:

Uninstall –WindowsFeatures Server-Gui-Shell –remove

Once you remove a role or disabled a feature with payload removed, you can reinstall it. Reinstalling requires access to an installation source (typically on the installation media). Use the PowerShell command Install-Windows Feature with the –Source parameter. If you don’t specify a source, Windows will attempt to download the needed files using Windows Update.

Deploying Minimal Server Interface for windows server 2012

Windows Server 2012 also offers an interface that is between Server with a GUI and Server Core: the Minimal Server Interface. With an initial Server with a GUI install, you can convert to the Minimal Server Interface through Server Manager. Minimal Server Interface removes components of the Server Graphical Shell, including Internet Explorer 10, Windows Explorer, the desktop, and the Start screen. The Microsoft Management Console (MMC), Server Manager, and a subset of Control Panel are retained.

To convert Server with a GUI to a Minimal Server Interface, from Server Manager launch the Remove Roles and Features Wizard. Select from the features list Graphical Management Tools and Infrastructure (see Figure 1).

Figure 1. Converting Server with a GUI to Minimal Server Interface

Click Next. Check the box next to “Restart the destination server automatically if required.” Click Remove. When prompted, allow automatic restarts. (See Figure 2.)

Figure 2. Allowing automatic restarts

Converting windows Server 2012 with a GUI to Server Core

To convert from Server with a GUI to a Server Core installation with Windows Power‐Shell, run the following cmdlet:

Uninstall-WindowsFeature Server-Gui-Mgmt-Infra -restart

Successful execution of the preceding cmdlet starts the removal process of the server shell (see Figure 1).

 

Figure 1 Converting Server with a GUI to a Server Core install

The server reboots once the graphical interface is removed. When the server comes back up, after login, the core interface is loaded.

 

If you convert to a Server Core installation, Windows features, server roles, and GUI management tools that require a Server with a GUI installation will be uninstalled automatically. You can specify the -WhatIf option in PowerShell to see exactly which features will be affected by the conversion.

Converting Windows Server 2012 Core to Server with a GUI

To convert a Server Core install into a Server with a GUI install, you will need to create a folder to mount a Windows Imaging File (WIM). WIM files are images of the operating system and reside on the installation media, in the sources folder. The image file that gets mounted is the install.wim file, which is located inside the sources folder.

To get started, first run the command mkdir from the command prompt to create a directory named mountdir. The syntax is mkdir c:\mountdir. (See Figure 1.)

Figure 1. Creating a directory named mountdir for mounting the WIM file

After you run the mkdir command, the mountdir folder is listed under the root of the C:\ drive (see Figure 2).

Next, you need to find the index number associated with the Server with a GUI image you want to install. For example, I am converting from Server Core with the Datacenter edition of Windows Server 2012. I want to find the Server with a GUI image located on my installation media and the index number that references that image. To do so, use the Dism command at an elevated command prompt. The proper syntax is runas /user:administrator to elevate permissions within the command prompt. Click Enter, and you will be prompted to enter the administrator password.

Figure 2. Newly created mountdir directory

Then run the following to get the correct index number (also shown in Figure 3):

Dism /get-wiminfo /wimfile:drive where installation media is located:\sources\install.wim

Figure 3. Command to locate the index number of the appropriate Server with a GUI image

Upon successfully running the command, you’ll see the Deployment Image Servicing and Management tool load. Find the index number of the Server with a GUI image you want to install (see Figure 4).

Figure 4. List of image files and associated index numbers


Mount the appropriate image file with the following command (also shown in Figure 5):

Dism /mount-wim /WimFile:drive where installation media is located:\sources\install.wim /Index:#_from_step_2 /MountDir:c:\mountdir/readonly
This again launches the Deployment Image Servicing and Management tool. The Server with a GUI image is mounted. After the message “The operation completed successfully” appears on screen, the image mount is complete. The final step requires installing the GUI from the mounted image
with PowerShell. Launch PowerShell by simply typing powershell at the command line.Again, you must run PowerShell with the administrator account’s elevated permissions for the installation to work.

 Run the cmdlet:

Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell –Restart –Source c:\mountdir\windows\winsxs

Figure 5. Mounting the image file

If the cmdlet is successfully executed, you will see the GUI installation start within PowerShell (see Figure 6).

Figure 6. The GUI installation process within PowerShell

After install, the server reboots. When the server comes back up, the Ctrl-Alt-Delete screen is displayed. Login and the Server Core interface are now replaced with the full Windows 2012 Server shell.

You can also use Windows Update as the source, instead of a WIM file, by using this Windows PowerShell cmdlet (make sure you have an Internet connection):

Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell –Restart

Windows Server 2012 with a GUI installation procedures

Download a Windows Server 2012 evaluation here.

Download a Windows Server 2012 evaluation here.

Download a Windows Server 2012 evaluation here.

Download a Windows Server 2012 evaluation here.

Download a Windows Server 2012 evaluation here.

Download a Windows Server 2012 evaluation here.

Download a Windows Server 2012 evaluation version here.

Download a Windows Server 2012 evaluation here.

Download a Windows Server 2012 evaluation here.

Download a Windows Server 2012 evaluation here.

After you’ve inserted the installation media into the CD-ROM, DVD, or USB flash drive, or executed an install from the network, the install wizard begins. The first screen prompts you to click “Install now” to get the install process up and running (see Figure 1).

Figure 1. First screen of a Server 2012 installation

The install wizard then prompts you to select installation preferences such as language, time and currency format, and keyboard or other input device settings, as shown in Figure 2.

Figure 2. Installation preferences

Next, select the installation mode. For a Server with a GUI install, the selection option is Windows Server 2012 Enterprise (Server with a GUI Installation), as shown in Figure 3. Click Next to continue.

Figure 3. Server installation mode options

You are then asked to check a box to agree to the license terms. You cannot continue with installation if you don’t check the box (see Figure 4). Once you do, click Next.You’ll then select the option to perform a fresh install of Server 2012 or an upgrade from Server 2008 R2 (see Figure 5). Select “Custom: Install Windows only (advanced)” for a new install, or “Upgrade: Install Windows and keep files, settings, and apps” for an upgrade.
Now, select how you want to partition drives and the location to install Server 2012, as shown in Figure 6. Typically, most server administrators will create a system partition for loading the server operating system. You can create another partition for the rest of the space on the hard drive(s) and then allocate it into volumes after install, depending on your storage needs.

Figure 4. License terms agreement

Figure 5. Select the installation type: Custom for a new install, or Upgrade for upgrading from Server 2008 R2

Figure 6. Setting up drive partitions

I do recommend installing the operating system—in this case, Server 2012—on its own system partition and then creating separate partitions to store data. The partition and volumes containing the server data are what is usually included in regularly scheduled backup jobs. This way, if the server gets damaged or corrupted, you can reinstall the OS if you have to and then can restore data from backup. This is good practice on small desktop servers with one or two drives, or larger rack-mounts with up to eight drives. Configurations will vary depending on any RAID (Redundant Array of Inexpensive Disks) configurations deployed, but it’s best to keep the server install on a separate partition from data.

In this screen, you can also load third-party drivers that may be needed for Windows 2012 to recognize connected devices.

Windows then copies the server files to the hard disk, and after they’re installed, Server Core installation is complete. The next screen you will see is the Administrator login window (see Figure 7). Windows will prompt you to create a local Administrator’s password.

Figure 7. Initial local Administrator login

If you’ve worked with Windows Servers before, you’ll notice that the interface changes in Server 2012’s login screen from previous versions of Windows Server. One of the newinterface features is an eyeball icon in the password field (see Figure 8). Clicking it and holding down the left mouse button after entering a password will change the password characters from asterisks to the actual values.

After you log into a Server Core install of Server 2012, all you will see is a command prompt screen—no desktop icons, no Start button, and no Windows Explorer (see Figure 9). Any tasks you perform after install must be done through the command line.

Figure 8. The eyeball icon changes asterisks to text

After the GUI mode install finishes, you’ll see the Ctrl-Alt-Delete page, which pulls up the login screen (see Figure 9). This page is the first introduction to the new Windows 8–style look in Server 2012.

Press Ctrl-Alt-Delete to bring up the local Administrator login screen, as shown in Figure 10.

Figure 9. Windows 8–style login

Figure 10. Administrator login screen

After login, Windows Services loads, personalized settings are established, and you are brought to the Server 2012 desktop. The Server Manager dashboard opens by default (see Figure 2-13). Server Manager has a tile-based interface refreshed from Server 2008 R2. Server Manager and other components of the full desktop interface are explored in
more depth in further posts .

Figure 11. The new Server Manager dashboard

Windows Server Core 2012: installation procedures

Download a Windows Server 2012 evaluation here.

Download a Windows Server 2012 evaluation here.

Download a Windows Server 2012 evaluation here.

Download a Windows Server 2012 evaluation here.

Download a Windows Server 2012 evaluation here.

Download a Windows Server 2012 evaluation here.

Download a Windows Server 2012 evaluation version here.

Download a Windows Server 2012 evaluation here.

Download a Windows Server 2012 evaluation here.

Download a Windows Server 2012 evaluation here.

After you’ve inserted the installation media into the CD-ROM, DVD, or USB flash drive, or executed an install from the network, the install wizard begins. The first screen prompts you to click “Install now” to get the install process up and running (see Figure 1).

Figure 1. First screen of a Server 2012 installation

The install wizard then prompts you to select installation preferences such as language, time and currency format, and keyboard or other input device settings, as shown in Figure 2.

Figure 2. Installation preferences

Next, select the installation mode. For a Server Core install, the selection option is Windows Server 2012 Enterprise (Server Core Installation), as shown in Figure 3. Click Next to continue.

Figure 3. Server installation mode options

You are then asked to check a box to agree to the license terms. You cannot continue with installation if you don’t check the box (see Figure 4). Once you do, click Next.You’ll then select the option to perform a fresh install of Server 2012 or an upgrade from Server 2008 R2 (see Figure 5). Select “Custom: Install Windows only (advanced)” for a new install, or “Upgrade: Install Windows and keep files, settings, and apps” for an upgrade.
Now, select how you want to partition drives and the location to install Server 2012, as shown in Figure 6. Typically, most server administrators will create a system partition for loading the server operating system. You can create another partition for the rest of the space on the hard drive(s) and then allocate it into volumes after install, depending on your storage needs.

Figure 4. License terms agreement

Figure 5. Select the installation type: Custom for a new install, or Upgrade for upgrading from Server 2008 R2

Figure 6. Setting up drive partitions

I do recommend installing the operating system—in this case, Server 2012—on its own system partition and then creating separate partitions to store data. The partition and volumes containing the server data are what is usually included in regularly scheduled backup jobs. This way, if the server gets damaged or corrupted, you can reinstall the OS if you have to and then can restore data from backup. This is good practice on small desktop servers with one or two drives, or larger rack-mounts with up to eight drives. Configurations will vary depending on any RAID (Redundant Array of Inexpensive Disks) configurations deployed, but it’s best to keep the server install on a separate partition from data.

In this screen, you can also load third-party drivers that may be needed for Windows 2012 to recognize connected devices.

Windows then copies the server files to the hard disk, and after they’re installed, Server Core installation is complete. The next screen you will see is the Administrator login window (see Figure 7). Windows will prompt you to create a local Administrator’s password.

Figure 7. Initial local Administrator login

If you’ve worked with Windows Servers before, you’ll notice that the interface changes in Server 2012’s login screen from previous versions of Windows Server. One of the newinterface features is an eyeball icon in the password field (see Figure 8). Clicking it and holding down the left mouse button after entering a password will change the password characters from asterisks to the actual values.

After you log into a Server Core install of Server 2012, all you will see is a command prompt screen—no desktop icons, no Start button, and no Windows Explorer (see Figure 9). Any tasks you perform after install must be done through the command line.

Figure 8. The eyeball icon changes asterisks to text

Figure 9. The Server Core install interface


Although the interface of Server Core is sparse, you can still perform almost any tasks from the command prompt. For example, install PowerShell by running the command sconfig at the command prompt (see Figure 10). You can also perform administrative duties from the command line—such as joining the server to a domain or workgroup,renaming the server, or configuring networking settings—and other tasks with the Sconfig utility.

Figure 10. Running the Sconfig utility from the command prompt

Important information for x64-based operating systems for windows server 2012

Ensure that you have updated and digitally signed kernel-mode drivers for Windows Server 2012
If you install a Plug and Play device, you may receive a warning if the driver is not digitally signed. If you install an application that contains a driver that is not digitally signed, you will not receive an error during Setup. In both cases, Windows Server 2012 will not load the unsigned driver.
If you are not sure whether the driver is digitally signed, or if you are unable to boot into your computer after the installation, use the following procedure to disable the driver signature requirement. This procedure enables your computer to start correctly, and the unsigned driver will load successfully.
To disable the signature requirement for the current boot process:

1. Restart the computer and during startup, press F8.
   
2. Select Advanced Boot Options.
   
3. Select Disable Driver Signature Enforcement.
   
4. Boot into Windows® and uninstall the unsigned driver.
   

For more information, see http://go.microsoft.com/fwlink/?LinkId=66577.