Skip to main content

Error when moving from Core to full GUI in Server 2012

By

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>

Labels:

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
Post a Comment

Popular posts from this blog

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

By
This was an interesting observation from one of my Windows Server 2012 classes.  While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted.  When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places.  First off in the Active Directory Administrative Center.  This is what caused the initial confusion.  Take a look.  This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3.  Test3 is a valid, functioning user account.  Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...
Post a Comment
Read more

Sticky Key problem between Windows Server 2012 and LogMeIn

By
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 .
6 comments
Read more

Backup and Restore AD LDS with DSDBUTIL.exe

By
Active Directory Lightweight Directory Services allow you to create a directory service that allows applications to have access to user accounts, groups, and authentication similar to Active Directory Domain Services.  The big advantage here is that the schema of the directory service will not be bound by the rules of an Active Directory database.  Exchange 2007/2010, for example, use an instance of AD LDS on the Edge Transport Server to provide for user authentication from the internet.  Because your Active Directory database is not exposed to the internet, this is more secure. Applications will handle most of the dirty work should they require AD LDS.  You may want to make sure the database is being backed up and also have a restore plan in place.  Should the database become corrupt, the application that uses that database will fail.  This document will walk you through backing up and restoring an instance of AD LDS using the dsdbutil.exe command. Fi...
6 comments
Read more