After you complete the installation of Windows Server 2022, the next step is activating the operating system. Windows Server 2022 gives you a few different options when it comes to activation.
Activating and Servicing Windows
In the past, many administrators would use the Volume Activation Management Tool (VMAT) to activate both Microsoft operating systems and Microsoft products like Office. You can still use VMAT to activate Microsoft products like Office, but with the release of Windows Server 2022, there are some new ways to help you activate the operating systems.
So let’s take a look at some of the different activation options that you have with Windows Server 2022 operating system.
Key Management Service
Windows Server 2022 Key Management Service (KMS) gives your Windows computers an easy and automated way for them to get activated. KMS allows your computers to get activated right on your local network without you having to contact Microsoft. For this to happen, you must set up a KMS client- server network. KMS clients are able to contact KMS servers as long as your network uses either a static TCP/IP configuration or you have a Domain Name System (DNS) server setup.
To configure KMS hosts systems, you must configure and retrieve Volume Activation information. Do so by using a Software License Manager (referred to as SL Manager) script (Slmgr.vbs). You can run this script on a local system or on a remote system, but it needs to be run from a user’s account that uses an elevated command prompt. KMS host systems can be any Windows client operating system running Windows Vista or higher and any Server above Windows Server 2003.
To create or modify the Slmgr.vbs script, you can use either the Wscript.exe or the Cscript.exe application. Slmgr.vbs uses the Wscript.exe scripting engine by default. After you make any changes to the Slmgr.vbs script, you must restart the Software Licensing Service. You can do so by using the Services Microsoft Management Console (MMC) or by running the net stop and net start commands at an elevated command prompt (net stop sppsvc and net start sppsvc).
The Slmgr.vbs script has different command- line switches that you can use. Table 3.1 describes some of those switches.
TABLE 3.1 Slmgr.vbs switches
/ato
This switch is used for retail and volume system editions with a KMS host key or a Multiple Activation Key (MAK) installed. The /ato command prompts Windows to try to do an online activation. For any systems that are using a Generic Volume License Key (GVLK), this will make the system attempt to do a KMS activation.
/cdns
This switch allows you to disable KMS host automatic DNS publishing.
/cpri
You can use this switch to lower the priority of KMS host processes.
TABLE 3.1 Slmgr.vbs switches (continued)
| Parameter | Description |
| /dli | You can use this switch on the KMS host to view the current KMS activation count. |
| /dlv | When you use this switch, the license information for the installed operating system is displayed. |
| /ipk | This command will try to install a 5×5 product key. |
| /sai activationInterval | This switch allows you to change how often a KMS client attempts to activate itself when it cannot find a KMS host. The default setting is 120 minutes, but you can change the interval by replacing ActivationInterval with the number of minutes you want to set. |
| /sdns | This switch allows you to enable KMS host automatic DNS publishing. |
| /spri | This switch allows you to set the CPU priority of the KMS host processes to Normal. |
| /sprt PortNumber | Using this switch allows you to change the default TCP communications port on a KMS host from 1688 to whichever port you want to use. To change the default port number, replace the PortNumber switch with the TCP port number you want to use. |
| /sri RenewalInterval | This switch allows you to change how often a KMS client attempts to renew its activation by contacting a KMS host. If you need to change the default of 10080 (7 days), just replace RenewalInterval with the number of minutes you want to use. |
To run Slmgr.vbs remotely, you must supply additional parameters. You must include the computer name of the target computer as well as a username and password of a user account that has local administrator rights on the target computer. If run remotely without a specified username and password, the script uses the credentials of the user running the script:
slmgr.vbs TargetComputerName [username] [password] /parameter [options]
Automatic Virtual Machine Activation
Another Windows Server 2022 activation method is called Automatic Virtual Machine
Activation (AVMA). The main advantage of AVMA is that it works the same way a
Activating and Servicing Windows
proof- of- purchase works. Once there is proof that the Windows Server 2022 operating system is used in accordance with Microsoft Software License terms, AVMA allows you to install virtual machines on that Windows Server operating system without using or managing product keys for each virtual machine.
AVMA attaches the virtual machine activation to the properly activated Hyper-V machine during the startup process. One of the nice advantages to using AVMA is that AVMA will provide you with real- time reporting data. When your virtual servers are properly activated using volume or OEM licensing, AVMA gives your organization many benefits, like the ability to activate virtual machines in remote areas as well as activate virtual machines even if no Internet connection is present.
Another advantage of AVMA activations is that virtual machines are activated as long as the Hyper- V server is legally licensed. This helps consulting companies in the fact that they do not need to access client virtual machines to activate the machines as long as the Hyper-V server is properly licensed. Also, hosting companies can use the server logs to help keep the virtual machines running properly.
AVMA requires Windows Server 2022 with the Hyper- V role installed. AVMA can also run on Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, and Windows Server 2019 if needed. Table 3.2 shows the Windows Server 2022 AVMA (5×5)
Keys that are available from Microsoft’s website along with the keys for Windows Server 2019 (https://docs.microsoft.com/en- us/windows- server/get- started- 19/ vm- activation- 19).
TABLE 3.2 Windows Server AVMA keys
| Windows Server 2022 | AVMA Key |
| Datacenter | W3GNR- 8DDXR- 2TFRP- H8P33- DV9BG |
| Standard | YDFWN- MJ9JR- 3DYRK- FXXRW- 78VHK |
| Windows Server 2019 | AVMA Key |
| Datacenter | H3RNG- 8C32Q- Q8FRX- 6TDXV- WMBMW |
| Standard | TNK62- RXVTB- 4P47B- 2D623- 4GF74 |
| Essentials | 2CTP7- NHT64- BP62M- FV6GG- HFV28 |
Active Directory–Based Activation
One of the best advantages of using Windows Servers is the ability to install Active Directory onto your corporate network. Active Directory is just a centralized database of objects for a corporation; that centralized database is called a domain.
If your company is running Active Directory, you can use this to your advantage when it comes to activation. Active Directory–Based Activation (ADBA) allows you to activate computers right through the domain connection.
Many organizations have remote locations and at these locations there is company- owned software that needs to be registered. Normally administrators would use a retail key or a
Multiple Activation Key (MAK) to get these products activated. The nice thing about ADBA is that as long as the computers are connected to the domain, the software and products can be activated through the domain.
When you join a Windows computer to the domain, the ADBA will automatically activate the computer’s version of Windows either online with Microsoft or through the use of an activation proxy.
Leave a Reply