Quickly Convert from Core to GUI

Stop the command line madness!

Windows Server 2012 R2 on a VMWare vSphere 5.5 Virtual Machine


After accidentally installing a Windows Server 2012 R2 Core only version for my new Exchange 2016 server I went searching on the internet for the correct process to convert from Windows Server 2012 R2 Core to GUI.

A quick search revealed numerous web sites with the knowledge needed to go from Windows Server 2012 R2 Core to GUI. However, none of them worked for me. I tried this command and that. I found the correct index and used that in the next command however the process always failed with and error.


Error Message:
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. 
Use the source option to specify the location of the files that are required to restore the feature.
Error: 0x800F0906

After a few more failed attempts I stumbled on a very quick and easy way to make the change from Windows Server 2012 R2 Core to GUI. Let me add that I was doing this on a VMWare vSphere 5.5 virtual machine.


1.      Mount the Windows Server 2012 R2 installation ISO to the virtual machine CD
2.      Restart the Windows Server 2012 R2 VM
3.      Once the server has started, in the Administrators console type D: then hit “ENTER”
4.      You should see the installation media files. Type setup.exe then hit “ENTER”
5.      Select the Windows Server 2012 R2 with GUI
6.      Select Advanced install as you cannot upgrade the Windows Server 2012 R2 Core to GUI
7.      Accept the prompt that says “All files and folders will be deleted”
8.      Run the install like normal



It should be that simple. Or I can say that it was for me. This method took way less time than actually finding and trying to run everything command line. I hope it helps you. 

Comments

Post a Comment

Popular posts from this blog

Exchange 2016 - Error adding mailbox databases copies to new DAG server

Image
Exchange 2016 Database Availability Group Error adding mailbox databases copies to new DAG server I have 2 existing Exchange 2016 servers that are part of a DAG with 5 databases. After adding a new Exchange 2016 server to the existing DAG then trying to “Add database copy” I received the below error. The seeding operation failed. Error: An error occurred while running prerequisite checks. Error: The specified database isn't configured for replication and therefore cannot be used to perform seed operations. [Database: 12345, Server: NewEamilServer.something.COM] The database list shows the new Exchange server listed under the “SERVER WITH COPIES” column. However, looking at the details on the right-hand pane tells a different story. Passive Unknown Copy queue length: 0 Content index state: Unknown Clicking on the “View details” link shows us other errors. Error Message: “The database file wasn't found after log replay. The cop...
Read more

Configure Message Delivery Restrictions on a resource mailbox in Exchange 2016

We just recently migrated from Exchange 2010 to 2016. In addition to our user mailboxes we also migrated a couple dozen conference room mailboxes or resource mailboxes as they are referred to in Exchange 2016. All our conference rooms are set to auto booking for everyone except on a particular conference room that is reserved for the executives. Only the executives and their administrative assistants are allowed to book meetings to this conference room. To limit the other employees for booking the executive conference room I used the Message Delivery Restrictions, Accept Messages From, Only Senders in the Following List option in Exchange 2010. I have eight people in the list. Since our move to Exchange 2016 we have had one executive leave the company, one executive admin leave the company, and one admin change responsibilities to cover for the one admin that left. I needed to make the changes to the Only Senders in the Following List option for the executive conference ro...
Read more
Image
 MICROSOFT TEAMS TELEPHONY Configure Microsoft Teams users for Enterprise Voice   Basic Steps   #1 Does user have Office 365 user account #2 Check Microsoft Phone License is assigned #3 Get User Password Permission #4 Add user to Azure AD group #5 Get-CsOnlineUser -Identity "username@domainname.com" | fl RegistrarPool,OnPremLineUriManuallySet,OnPremLineUri,LineUri #6 Set-CsUser -Identity  "username@domainname.com"  -EnterpriseVoiceEnabled $False -HostedVoiceMail $False #7 Set-CsUser -Identity  "username@domainname.com"  -EnterpriseVoiceEnabled $true -HostedVoiceMail $true -OnPremLineURI tel:+15555555555 #8 Grant-CsOnlineVoiceRoutingPolicy -Identity  "username@domainname.com"  -PolicyName "VoiceRouteName" #9 Grant-CsTenantDialPlan -Identity  "username@domainname.com"  -PolicyName "DialPlanName" !!! -Huge  cavoite  here. Each user that you intend to enable for enterprise voice must have the appropriate licensing. If th...
Read more