Error when moving from Core to full GUI in Server 2012

If you are installing the full GUI on your Server core 2012 and receive this error, it is an easy fix.

Install-WindowsFeature : The request to add or remove features on the

specified server failed.

Installation of one or more roles, role services, or features failed.

The source files could not be downloaded.

This simply means that your installation files need to be made available to PowerShell to do this. To correct this, insert your installation media or map a drive to the installation source on your network. Now add he –Source parameter to your Install-WindowsFeature cmdlet pointing to Windows folder to complete the installation

Import-Module ServerManager

Imstall-WindowsFeature –IncludeAllSubfeature User-Interfaces-Infr –Source <SourcePath>

Comments

Anonymous said…

it seems when updating windows (currently 10 hotfixes) that this scenario doesn't work anymore. Nor online or offline

November 23, 2012 at 5:20 AM

Anonymous said…

Any suggestion on what the source might be? I have tried just about everything I can think of (d:\, d:\sources\sxs, d:\setup.exe) What should the source be?

November 25, 2012 at 9:38 AM

Jason Yoder, MCT said…

Mount a windows installation image using this command. I am assuming your D: is your DVD drive.

Mkdir c:\mount

dism.exe /mount-image /imageFile:d:\sources\install.wim /index:4 /mountdir:c:\mount /readonly

Install-WindowsFeature -IncludeAllSubfeature User-interfaces-infra -source:c:\Mount\Windows

The first command makes a directory to mount the image. The second mounts the image. The third will install the feature.

To dismount this image:

Dism.exe /unmount-Wim /mountdir:c:\mount

November 26, 2012 at 5:36 AM

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this. First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction. The code below is correct. My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection. In all cases, this will disrupt the user. First, you need PowerShell remoting enabled on the target machine. You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target. Remember, the target needs to be online and accessible to you.

Jason Yoder, MCT

Search This Blog