Ugrading Windows Server 2008 R2 from Standard to Enterprise

Ugrading Windows Server 2008 R2 from Standard to Enterprise

Log onto the server you want to upgrade

To get DISM
#1 - Right ckick on Windows PowerShell, select Run as Administrator

To Find Out Current Server Edition
#2 - Type in: DISM /online /Get-CurrentEdition
Output:
Current Edition : ServerStandard
To Find Out Possible Editions to Upgrade To
#3 - Type in: DISM /online /Get-TargetEditions
Output:
Target Edition : ServerDataCenter
Target Edition : ServerEnterprise

To Run the Actual Ugrade
#4 - Type in: DISM /online /Set-Edition:ServerEnterprise /productkey:ABCDE-ABCDE-ABCDE-ABCDE-ABCDE 

The process will change the product key, remove the Standard package, install the Enterprise package, then ask for a reboot. After reboot I would check for any updates.

A couple of issues:
* - The server can not be a DC
* - The product key will not be acceted if it a VLK that is the same for Standard and Enterprise edtions.

* - You must use a default KMS key to run the upgrade. The generic KMS client key for Windows 2008 R2 Enterprise is 489J6-VHDMP-X63PK-3K798-CPX3Y

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