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
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
No comments:
Post a Comment