Thứ Năm, 23 tháng 5, 2024

How to Convert (Upgrade) Windows Server Evaluation to Full Version

 Microsoft invites everyone to explore the features of the Windows Server platform with the StandardEvaluation or DatacenterEvaluation trial editions. You can download an ISO or VHD image with the free version of Windows Server 2022, 2019, 2016, or 2012 R2 from the Microsoft Evaluation Center website by completing a short form (https://www.microsoft.com/en-us/evalcenter). This edition of Windows Server is for evaluation, testing, or training purposes only and is not for commercial use. Once you install Windows Server Evaluation, you have 180 days to test its capabilities.

Suppose you are running production tasks on the Windows Server Evaluation. In that case, there is a way to convert it to a full Windows Server edition, while keeping your data and without reinstalling the operating system.

How to Extend Windows Server Free Evaluation Period

If you are using the Evaluation version of Windows Server, the current edition and the time remaining before the grace period expires are displayed on the desktop (Windows License valid for 180 days).

windows server 2019 standard evaluation license valid for 180 days

You can also get the remaining grace period of Windows Server with the command:

Slmgr /dli
slmgr timebase_eval channel serverstandarteval edition

Name: Windows, ServerStandardEval edition
Description: Windows Operating System, TIMEBASED_EVAL channel
License Status: Licensed
Timebased activation expiration: xx min (xx days)

The Windows Server free trial period can be legally extended 5 times for 180 days by using the command:

slmgr /rearm

This means that the maximum time the evaluated Windows Server can be used is 3 years (180 days * 6).

After the trial period expires, Windows Server starts requiring activation and shuts down every hour with the following messages in the Event Viewer logs

Log Name: System
Source: USER32
Event ID: 1074
The process C:\Windows\system32\wlms\wlms.exe Server1 has initiated the shutdown of computer Server1 on behalf of user NT AUTHORITY\SYSTEM for the following reason: Reason Code: 0x80000000
Shutdown Type: shutdown
The license period for this installation of Windows has expired. The operating system is shutting down.

Or:

The license period for this installation of Windows has expired. The operating system will shut down every hour.

The desktop background will turn black, and a notification “Windows Licenses is expired” will appear in the lower right corner.

windows server 2019 evaluation license is expired desktop message

Upgrade Windows Server Evaluation to a Full Retail Version

Microsoft allows Windows Server Evaluation to be upgraded to a full retail Standard or Datacenter edition.

Here are some upgrade restrictions:

  • You can upgrade to the same or higher edition of Windows Server. For example, ServerStandardEval can be upgraded to ServerStandard or ServerDatacenter;
  • It is not recommended to convert a host with the AD domain controller role. You must first demote DC to a member server. This requires the domain to have at least one additional DC to which you can move FSMO roles;
  • If NIC Teaming is configured on the server, it must be disabled before upgrading.

The first step is to ensure that you have an evaluation version of Windows Server installed:

DISM /online /Get-CurrentEdition

DISM /online /Get-CurrentEdition - ServerStandardEval

List the editions of Windows Server that you are eligible to upgrade your evaluation copy to:

DISM /online /Get-TargetEditions

Editions that can be upgraded to:
Target Edition : ServerStandard
Target Edition : ServerDatacenter

DISM /online /Get-TargetEditions

This means that you can upgrade your ServerStandardEval to ServerDatacenter or ServerStandard.

Use the PowerShell command to check your version of Windows Server:

Get-ComputerInfo | select OsName, WindowsEditionId

check that Windows Server Evaluation is installed

You can convert both the full GUI version of Windows Server as well as Windows Server Core.

To convert an evaluation Windows Server into a full version, you will need to use the public KMS client setup key (or Generic Volume License Key, GVLK) for your version of Windows Server. For a complete list of GVLK keys for all versions of Windows, visit the Microsoft website Key Management Services (KMS) client activation and product keys.  The complete list of keys for all of the supported versions of Windows Server can be found in the table below:

OS version/EditionStandardDatacenter
Windows Server 2022VDYBN-27WPP-V4HQT-9VMD4-VMK7HWX4NM-KYWYW-QJJR4-XV3QB-6VM33
Windows Server 2019N69G4-B89J2-4G8F4-WWYCC-J464CWMDGN-G9PQG-XVVXX-R3X43-63DFG
Windows Server 2016WC2BQ-8NRM3-FDDYY-2BFGV-KHKQYCB7KF-BWN84-R7R2Y-793K2-8XDDG
Windows Server 2012 R2D2N9P-3P6X9-2R39C-7RTCD-MDVJXKNC87-3J2TX-XB4WP-VCPJV-M4FWM

In this case, we are going to upgrade the Eval edition to the full retail version of Windows Server 2022 Standard. Find and copy the GVLK key for the target version and edition of Windows Server from the table, and then run the following command:

dism /online /set-edition:ServerStandard /productkey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx /accepteula

dism /online /set-edition:ServerStandard /productkey

If you need to change the OS to the Datacenter edition, use the /set-edition:ServerDatacenter parameter and the appropriate GVLK from the table.

Restart your computer and check that your evaluation copy of Windows Server has been converted to a full retail edition.

Upgrade evaluated to Windows Server 2022 Standard

If a KMS server is deployed in your local network, you can use it to activate your Windows Server OS using the following commands:

slmgr /skms kms-srv.woshub.com:1688
slmgr /ato

If you have a Windows Server MAK, Retail, or OEM key, you can activate the OS as usual: online or by phone.

Delete the current GVLK key:

slmgr.vbs /upk
slmgr.vbs /cpky

Enter your MAK or retail key

slmgr.vbs /ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

Activate a Windows Server instance:
slmgr.vbs /ato

Check that Windows is activated (LicenseStatus = 1 – indicates that this copy of Windows has been successfully activated):

Get-CimInstance SoftwareLicensingProduct -Filter "Name like 'Windows%'" | where { $_.PartialProductKey } | select Description, LicenseStatus

PowerShell: check Windows Server activation

Errors When Converting Windows Server Evaluation to Full

Some users complain that DISM /set-edition command sometimes gets stuck at 10%. If the command hangs for more than 20 minutes, we recommend that you stop the Software Protection Service (Stop-Service sppsvc -Force) and restrict access to the Internet on the host (you can simply unplug the Ethernet LAN cable).

Possible DISM errors:

  • If you specify your retail or MAK key instead of a public GVLK key in the DISM command, an error will appear:
    Error 1168
    The specified product key could not be validated.
    Check that the specified product key is valid and that it matches the target edition.

    Indicates that you have specified your MAK or Retail key instead of the public GVLK key in the DISM command. Always use the Microsoft GVLK key when upgrading to Windows Server edition. You can later replace the public KMS key with your product key.
    Error 1168 The specified product key could not be validated

  • The current edition cannot be upgraded to any target editions

    It means you are trying to upgrade from Datacenter Edition to Standard. This upgrade path is not supported;

  • Error: 50. Setting an Edition is not supported with online images

    This most likely indicates that the server has the Active Directory Domain Controller (AD DS) role deployed. Converting Windows Server Edition on domain controllers is not supported;

  • This Windows image cannot upgrade to the edition of Windows that was specified. The upgrade cannot proceed. Run the /Get-TargetEditions option to see what edition of Windows you can upgrade to

    The error appears when you try to convert Windows Server Evaluation Datacenter to Standard. You cannot upgrade Eval Datacenter to Standard. You must convert the ServerDatacenterEval edition to ServerDatacenter. Specify the public KMS key for the Windows Server Datacenter edition in the DISM command.

Read More

Configure KMS Activation Host on Windows Server 2022/2019/2016

 Windows Server running the Volume Activation Services role can act as a KMS (Key Management Service) server, allowing you to activate computers with volume editions of the Windows Server and Windows 10/11 operating systems in a corporate network. In this article, we will show you how to install and configure KMS Host on Windows Server 2022, 2019, or 2016, and how to use it to activate Windows on client computers.


Install KMS Host Role on Windows Server

To deploy your own KMS server, you must install the Volume Activation Services role on any of the hosts running Windows Server 2022, 2019, or 2016. If you already have a KMS host on Windows Server 2016 or Windows Server 2019, you can use this existing server (in this case, this section can be skipped). Clients running newer Windows Server 2022 and Windows 11 can be activated using such a KMS host.

  1. Install the Volume Activation Services role on your server from the Server Manager console or using the PowerShell commandInstall-WindowsFeature -Name VolumeActivation -IncludeAllSubFeature –IncludeManagementToolsinstall volume activation service role on windows server 2022
  2. Enable a Windows Firewall rule that allows clients to access the KMS server: Enable-NetFirewallRule -Name SPPSVC-In-TCP (this will open port TCP 1688 on the server).

Activate KMS Host Running Windows Server with CSVLK

Next, you need to activate your KMS server with a personal CSVLK key (also called a KMS Host Key). Previously, CSVLK keys could be obtained from your account on the Microsoft VLSC website (Volume Licensing Service Center), but this has recently been moved to the Microsoft 365 Admin Center (MAC).

By default, KMS host keys are not available in the MAC personal account for open agreement users, instead, Multiple Activation Keys (MAC) are suggested. You can request the generation of a CSVLK key from Microsoft Technical Support using the special VLSC Support request form, which requires you to provide your agreement number, product name, the number of hosts you plan to activate with KMS, and the purpose of the KMS server deployment.
  1. Sign in to Microsoft 365 Admin Center and go to Billing -> Your products -> Volume licensing -> Downloads & keys -> Select your product -> View keysCopy the KMS host key for Windows Server 2022; download csvlk kms host key from microsoft admin center
     You should always use the KMS Host Key for the maximum version of Windows Server that is available in your account. A KMS host that is activated with a more recent key will be able to activate all of the previous versions of Windows.
  2. Install a new KMS key on the server using the command: slmgr /ipk <KMS_host_key_Windows_Server_2022>
    Tip. If the KMS host was enabled with a key for an earlier version of Windows Server, you must first remove the KMS host key: slmgr /upk
  3. Activate your KMS server against the Microsoft activation servers: slmgr /ato (your server must have direct internet access during activation). Or you can activate the KMS host by phone (run the graphical Volume Activation Tools from the Server Manager);
  4. To publish an SRV record in the DNS to allow clients to automatically discover the KMS host in the domain, run the command: slmgr /sdns
  5. Restart the Software Protection service: Restart-Service -Name sppsvc
  6. Ensure that your KMS server has been successfully activated. Run the command: slmgr.vbs /dlv Make sure the result includes: Description = VOLUME_KMS_WS22 channel and License status = Licensed.
  7. You will now be able to activate all supported versions of Windows on your KMS server, including Windows 11 and Windows Server 2022.
KMS hosts that are running Windows Server 2019 and 2016 and have a new KMS key installed (Windows Srv 2022 DataCtr/Std KMS), can be used to activate the latest builds of Windows Server 2022 and Windows 11. This requires that the hosts have the latest cumulative updates installed (via Windows Update or manually).

How to Activate Windows with a KMS License Server

A special GVLK (Generic Volume License) key must be installed on Windows computers to activate them against your KMS server. GVLK keys are public keys that indicate that this computer will be activated on the KMS server. Visit the Microsoft website for a complete list of client GVLK keys for all supported versions of Windows (https://learn.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys).

You can use PowerShell to find out the version and edition of Windows that is installed on your computer:

Get-ComputerInfo | select OsName

cmd: check windows version and edition

In this case, it is Windows 10 Pro. Find and copy the GVLK key for this OS version from the link above. In our example, the KMS Client Product Key for Windows 10 Pro is W269N-WFGWX-YVC9B-4J6C9-T83GX.

Public GVLK keys for Windows KMS clients

Install the GVLK key on the client computer using the command:

slmgr /ipk W269N-WFGWX-YVC9B-4J6C9-T83GX

slmgr /ipk: install gvlk key

If your computer is joined to the AD domain and a special SRV record has been published in DNS, Windows will automatically activate on the KMS host during startup.

The KMS server name and port on the client device can also be set manually:

slmgr /skms corp-kms1.woshub.com:1688
Run the following command to activate Windows on your KMS server:
slmgr /ato
Check the Windows activation status:
slmgr /dlv

In this case, the VOLUME_KMSCLIENT channel and License status: Licensed values indicate that the Windows OS on this computer is activated through the KMS server. The client is activated for 180 days and is automatically renewed every 7 days (if the KMS server can be reached).

activate windows client on kms server

You can also check the Windows activation status using the command:

Get-CimInstance SoftwareLicensingProduct -Filter "Name like 'Windows%'" | where { $_.PartialProductKey } | select Description, LicenseStatus

powershell - check windows kms activation status

The evaluation version of Windows Server cannot be activated on KMS; you must first convert it to a full version according to the guide.
Read More