Microsoft added a wide range of cloud-based features to Windows Server 2019, but the first step to the cloud can trip up admins who encounter activation problems with the server OS.
Windows Server 2019 requires license activation after 180 days, otherwise the system will shut down. With multiple server workloads, it’s not efficient to log in to each machine and manually activate them. There are also times when entering a valid key from the Volume Licensing Service Center (VLSC) will not work. Errors and key rejection can happen, often for no apparent reason. To avoid frustration with the server GUI, it’s beneficial to learn how to activate the Windows Server 2019 license through alternative methods such as the command line or Key Management Services (KMS).
Why use Windows Server 2019?
A switch to Windows Server 2022 might be a bit premature for many organizations who might prefer a more battle-tested server OS, while Windows Server 2016 might lack the more advanced functionality sought by some companies.
Windows Server 2019 offers important enhancements and a few years of updates that should placate even the wariest of admins who prefer stability over cutting-edge features. Some advantages in Windows Server 2019 over Windows Server 2016 include:
- a unified management center for both networking and ecosystem monitoring;
- scalable, expanded storage up to 64 TB, plus replication for disaster recovery;
- better performance in Storage Space Direct — up to two times faster according to Microsoft — through improvements in mirror-accelerated parity; and
- cloud-based file witness sharing.
Perhaps most fundamentally, Windows Server 2016 was not built for hybrid environments, making data management trickier for admins.
Windows Server 2019 also bakes in two modern technologies: AI and IoT support. Windows Server 2019 uses artificial intelligence for smarter predictions based on analytics. Microsoft added this feature to help admins lower operating costs. Devices on connected IoT platforms, such as servers and machines, can seamlessly share and back up data.
Microsoft updated Server 2019’s security features, added better support for Linux VMs, tweaked subsystem containers for easier development and updated its Remote Desktop Services functionality. This newest version also integrates with Windows Admin Center.
But the key to unlocking all this functionality is to activate Windows Server 2019 to avoid disruptions after deployment.
Activation via the command line and Software License Manager
Tapping into the elevated command line is a reliable way to access the Software License Manager (SLMGR), also called the Windows Software Licensing Management Tool. Interacting directly with SLMGR handles activation and access to license information.
There are some potential issues that come with working via the command line. Accidental commands will typically generate an error message, but it’s possible to harm the environment. Certain SLMGR parameters can also alter registry information. Double check the command before execution to avoid problems.
This SLMGR uses parameters to deliver specific instructions. The parameters act like extensions and use the following format: slmgr /[parameter].
The SLMGR parameters fetch licensing information, alter licensing information and execute activation for Windows Server 2019.
Here are some common SLMGR parameters:
- /dli: displays basic license and activation information;
- /dlv: displays detailed license and activation information;
- /xpr: displays the expiration date of an installed license;
- /upk: uninstalls the existing license key;
- /cpky: removes license key information from the registry;
- /ipk [XXXXX-XXXXX-XXXXX-XXXXX-XXXXX]: changes the 25-digit license key or tries to activate the license if the provided key does not currently; and
- /ato: forces immediate online activation, which is especially useful when KMS servers or Microsoft’s VLSC online activation servers aren’t reachable.
The primary extension used with activating Windows Server 2019 is /ipk, often used if there are issues using the VLSC.
Activate Windows Server 2019 with the command line
The following example command activates a license key. Navigate to the system32 folder from the command line, replace the Xs with the 25-digit license key and press Enter to execute the command:
slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
A pop-up dialog box will show if the operation failed or succeeded. Microsoft recommends a server restart after a successful activation attempt. After a reboot, Server Manager will show the activated server.
If a server is missing from Server Manager, there might be an activation error. Open the command line and enter the slmgr /ato command. A Windows Script Host pop-up will display an error message that explains why the Multiple Activation Key was invalid. Either use another activation key or contact Microsoft for support.
KMS is an alternative activation method
Another way to handle VLSC activation is to use KMS, a client-server model for volume activation.
KMS clients connect to a KMS server, also called the KMS host, on the network for activation. A KMS host can be a VM or physical machine. To activate a computer running Windows Server 2019, the KMS host must use one of the following OSes: Windows Server 2012 R2, Windows Server 2016 or Windows Server 2019.
How to find and use the KMS Host license key
To set up a KMS host requires obtaining the KMS Host key. Use the following steps to activate the KMS host:
- From the VLSC website, navigate to License > Relationship Summary > Click Current Active License ID > Product Keys and copy the Windows Srv 2019 DataCtr/Std KMSfrom the keys list.
- Open the command prompt, type slmgr /ipk followed by the 25-digit KMS host product key and press Enter. Then, use slmgr /ato to activate the host key.
The server also needs the Volume Activation Services server role installed either from Server Manager or via this PowerShell command:
Install-WindowsFeature -Name VolumeActivation -IncludeManagementTools
The KMS host should then announce its presence on the network for KMS clients, such as a Windows Server 2019 machine. The KMS client should activate automatically, which remains valid for 180 days until it renews the activation via the KMS host.
Editor’s note: This article was revised in 2024 by TechTarget editors to improve the reader experience.
Microsoft released their newest version of their server operating system almost one year ago on October 2, 2019. I have had Windows Server 2019 running in my lab environment since November 2018. It is certainly not advisable to be on the bleeding edge of technology in your production environment and to test thoroughly any new product before committing to it. Major version releases of operating systems are one such technology that falls squarely into that category.
Here is Microsoft’s comparison chart between 2008 R2, 2012 R2, 2016 and 2019: https://www.microsoft.com/en-us/cloud-platform/windows-server-comparison.
On the surface, Windows Server 2019 looks just about like Windows Server 2016. There aren’t many changes to the user interface between the two operating system environments either so if you are already used to Windows Server 2016, Windows Server 2019 is a familiar face. It is mature enough now after being a year old that I have been putting it into client production environments.
Note: Remember with every major release version change of operating systems (2003 & 2003 R2, 2008 & 2008 R2, 2012 & 2012 R2, 2016, and now 2019) in addition to the basic server licensing, corresponding user CALs (Client Access Licenses) are required to go along with them.
Once you have logged into the Microsoft Volume License Center and acquired the key needed to activate the operating system, it should be as simple as opening Server Manager, navigating to the Local Server page, clicking the Not activated link and punching in the key, right?
With a few recent installations of Windows Server 2019 I have found that even when I’m 100% sure I’ve copy/pasted or typed in the key correctly, it is still not accepted and consequently not activated. Instead of using the GUI, repeatedly unsuccessfully, I have found the command line tool to do the same to be dependably effective. The tool is the Windows Software Licensing Management Tool and can be accesses via elevated command line using slmgr.vbs.
There are a variety of parameters to use with slmgr.vbs including:
- /dli (This will show basic license and activation information.)
- /dlv (This will show detailed license and activation information.)
- /xpr (This will show the current expiration date of the license installed which is most useful when using a KMS key with a local KMS activation server on the network.)
- /upk (Be careful with this one as it will uninstall your current license key.)
- /cpky (Also be careful with this one as this removes license key information from the registry.)
- /ipk *****-*****-*****-*****-***** (This will change your license key to the one entered. If there was no key entered previously this command will also attempt to activate the license based on the license key type.)
- /ato (This will force an online activation immediately. This could be useful if you have already entered the new key but was not online with either the KMS server for the network or unable to reach Microsoft’s activation servers.)
When a new installation of Windows Server 2019 that is not accepting the key from the GUI, the /ipk parameter is what we would use. From an elevated command prompt, enter (where the asterisks are your actual license key):
slmgr.vbs /ipk *****-*****-*****-*****-*****
Microsoft recommends restarting your server following using this command. Doing these in combination should show an activated server from Server Manager on next boot.
If it does not, run this from an elevated command prompt:
slmgr.vbs /ato
It will likely give you an error with a reason why it wasn’t able to activate using the provided key like this for example:
An issue like the one above will need to be rectified by either using a different MAK key that has activations left, or a call into Microsoft.
Do you have questions? Don’t hesitate to reach out to our IT experts for help!
This publication contains general information only and Sikich is not, by means of this publication, rendering accounting, business, financial, investment, legal, tax, or any other professional advice or services. This publication is not a substitute for such professional advice or services, nor should you use it as a basis for any decision, action or omission that may affect you or your business. Before making any decision, taking any action or omitting an action that may affect you or your business, you should consult a qualified professional advisor. In addition, this publication may contain certain content generated by an artificial intelligence (AI) language model. You acknowledge that Sikich shall not be responsible for any loss sustained by you or any person who relies on this publication.
Table of Contents
As you know, Windows Server is a specialized operating system which is designed for server only. In today’s post, I will show you how to activate Windows in your VPS or dedicated server for FREE using KMS client product keys. So you can renew it whenever you want. Actually, the license will be renewed automatically every 7 days by default. In this way, just do it one time and forget it completely.
Before you begin
- If you’re using an evaluation edition of Windows Server. Let’s follow this post to convert then activate it to the licensed version.
- The methods work with Windows Server 2022/2019/2016, Windows Server version 1809, 1803, 1709. and Windows Server 2008/2012 (R2).
- KMS license is valid for 180 days only. But it will be renewed automatically before the expiration date if you are online. However, you can renew your Office manually anytime (even when its expired) by running the activation command or script again.
As you can see in the below screenshot, we’re using a copy of Windows Server 2019 Standard and it is not activated. We need to activate it to made it function normally and remove the licese watermark on the desktop.
Method 1: Manual activation
The first way, we can use the Windows Command Prompt (CMD) to activate the Windows Server 2019 Standard license free forever.
1️⃣ Click on the search icon, type cmd in the Windows search box, right click on the best match Command Prompt then select Run as administrator.
2️⃣ Copy, right click to paste all below commands into CMD window at once then hit Enter.
cscript //nologo %windir%\system32\slmgr.vbs /ipk N69G4-B89J2-4G8F4-WWYCC-J464C
cscript //nologo %windir%\system32\slmgr.vbs /skms kms.msgang.com
cscript //nologo %windir%\system32\slmgr.vbs /atoNote
Note: If you see the error 0xC004F074, it means that your internet connection is unstable or the server is busy. Please make sure your device is online and try the command “ato” again until you succeed.
3️⃣ Your Windows Server 2019 Standard is activated using a KMS key. It’ll reactivate after every 7 days automatically. So, your Windows is permanently activated.
::Output
C:\>cscript //nologo %windir%\system32\slmgr.vbs /ipk N69G4-B89J2-4G8F4-WWYCC-J464C
Installed product key N69G4-B89J2-4G8F4-WWYCC-J464C successfully.
C:\>cscript //nologo %windir%\system32\slmgr.vbs /skms kms.msgang.com
Key Management Service machine name set to kms.msgang.com successfully.
C:\>cscript //nologo %windir%\system32\slmgr.vbs /ato
Activating Windows(R), ServerStandard edition (de32eafd-aaee-4662-9444-c1befb41bde2) ...
Product activated successfully.Note
Tip: Why we need cscript in the commands. By just executing a vbs script file, output gets sent to dialog boxes, which need your interaction. Using cscript, the desired output gets printed to your current stdout.
4️⃣ Finally, check activation status of your Windows Server again. Open Windows Settings then check Windows Activation.
Method 2: Using PowerShell
The second way, we can use the Windows PowerShell to activate the Windows license. The steps are similar with using cmd method, but the commands would be changed a little bit.
1️⃣ Click on the search icon, type powershell in the Windows search box, right click on the best match Windows PowerShell then select Run as administrator.
2️⃣ Copy, right click to paste all below commands into CMD window at once then hit Enter.
cscript //nologo $env:systemroot\system32\slmgr.vbs /ipk N69G4-B89J2-4G8F4-WWYCC-J464C
cscript //nologo $env:systemroot\system32\slmgr.vbs /skms kms.msgang.com
cscript //nologo $env:systemroot\system32\slmgr.vbs /ato3️⃣ Your Windows Server 2019 Standard is activated using a KMS key. It’ll reactivate after every 7 days automatically. So, your Windows is permanently activated.
#Output
PS C:\> cscript //nologo $env:systemroot\system32\slmgr.vbs /ipk N69G4-B89J2-4G8F4-WWYCC-J464C
Installed product key N69G4-B89J2-4G8F4-WWYCC-J464C successfully.
PS C:\> cscript //nologo $env:systemroot\system32\slmgr.vbs /skms kms.msgang.com
Key Management Service machine name set to kms.msgang.com successfully.
PS C:\> cscript //nologo $env:systemroot\system32\slmgr.vbs /ato
Activating Windows(R), ServerStandard edition (de32eafd-aaee-4662-9444-c1befb41bde2) ...
Product activated successfully.Method 3: Using batch script
The benefits of this method are:
- When activating with the batch script, you don’t have type the activation commands manually on each client computers.
- The script can activate all Windows client (7/8/8.1./10/11) and Windows server (2008/2008R2/2012/2012R2/2016/2019/2022) editions.
- The script can be used on either Windows 64-bit or Windows 32-bit.
- You don’t need to know which Windows edition you’re using. Script detects your Windows edition automatically then activates it.
This one is not recommended anymore due to the new update of Microsoft. In case, if you have to use the batch script for automation, you can continue with below steps:
1️⃣ The first step is download the batch script to your computer by clicking on the below button. Our script is safe, but you should verify the security and contents of any script from the internet you are not familiar with.
2️⃣ Right click on downloaded zip file then extract it.
3️⃣ Navigate to the extracted folder. Right-click on the batch file, select Run as administrator to run the batch file with admin rights.
Windows may give you a pop-up window saying Windows protected your PC. You would receive a popup if you attempt to run or install an application that Windows doesn’t recognize. To run the script, click on the More info link then click Run anyway button.
The script will run automatically. If has no issue, you should see the below screenshot. The Windows has been activated. You can now press any key to close the command prompt window.
::Output
.....................................................................................
#Project: Activating Microsoft software products for FREE without additional software
.....................................................................................
#Supported products: Microsoft Windows 7/8/10/11/2022/2019/2016/2012R2/2012/2008
.....................................................................................
You're using: Microsoft Windows Server 2019 Standard
.....................................................................................
.....................................................................................
Activating your Windows using product key: N69G4-B89J2-4G8F4-WWYCC-J464C
Product activated successfully.
.....................................................................................
Your Windows license details:
Description: Windows(R) Operating System, VOLUME_KMSCLIENT channel
License Status: Licensed
Product Key Channel: Volume:GVLK
Partial Product Key: J464C
Volume activation expiration: 259200 minute(s) (180 day(s))
Press any key to close this window.If you want to create your own batch script by yourself. You can click on the below button to retrieve the code:
@echo off
color f0
mode con cols=98 lines=30
title Activate Windows license for FREE - msgang.com
cls
echo .....................................................................................
echo #Project: Activating Microsoft software products for FREE without additional software
echo .....................................................................................
echo #Supported products: Windows 7/8/10/11/2008/2008R2/2012/2012R2/2016/2019/2022
echo .....................................................................................
for /f "tokens=* delims== " %%i in ('"powershell -c (Get-CimInstance Win32_OperatingSystem).Caption"') do (set edition=%%i)
echo You're using: %edition%
echo .....................................................................................
::Microsoft Windows 10
if /i "%edition%" equ "Microsoft Windows 10 Home" (set productkey=TX9XD-98N7V-6WMQ6-BX7FG-H8Q99)
if /i "%edition%" equ "Microsoft Windows 10 Home N" (set productkey=3KHY7-WNT83-DGQKR-F7HPR-844BM)
if /i "%edition%" equ "Microsoft Windows 10 Home Single Language" (set productkey=7HNRX-D7KGG-3K4RQ-4WPJ4-YTDFH)
if /i "%edition%" equ "Microsoft Windows 10 Pro" (set productkey=W269N-WFGWX-YVC9B-4J6C9-T83GX)
if /i "%edition%" equ "Microsoft Windows 10 Pro N" (set productkey=MH37W-N47XK-V7XM9-C7227-GCQG9)
if /i "%edition%" equ "Microsoft Windows 10 Pro for Workstations" (set productkey=NRG8B-VKK3Q-CXVCJ-9G2XF-6Q84J)
if /i "%edition%" equ "Microsoft Windows 10 Pro N for Workstations" (set productkey=9FNHH-K3HBT-3W4TD-6383H-6XYWF)
if /i "%edition%" equ "Microsoft Windows 10 Enterprise" (set productkey=NPPR9-FWDCX-D2C8J-H872K-2YT43)
if /i "%edition%" equ "Microsoft Windows 10 Enterprise N" (set productkey=DPH2V-TTNVB-4X9Q3-TJR4H-KHJW4)
if /i "%edition%" equ "Microsoft Windows 10 Education" (set productkey=NW6C2-QMPVW-D7KKK-3GKT6-VCFB2)
if /i "%edition%" equ "Microsoft Windows 10 Education N" (set productkey=2WH4N-8QGBV-H22JP-CT43Q-MDWWJ)
if /i "%edition%" equ "Microsoft Windows 10 Enterprise LTSC 2019" (set productkey=M7XTQ-FN8P6-TTKYV-9D4CC-J462D)
if /i "%edition%" equ "Microsoft Windows 10 Enterprise LTSC 2021" (set productkey=M7XTQ-FN8P6-TTKYV-9D4CC-J462D)
if /i "%edition%" equ "Microsoft Windows 10 Enterprise LTSB 2016" (set productkey=DCPHK-NFMTC-H88MJ-PFHPY-QJ4BJ)
if /i "%edition%" equ "Microsoft Windows 10 Enterprise 2015 LTSB" (set productkey=WNMTR-4C88C-JK8YV-HQ7T2-76DF9)
if /i "%edition%" equ "Microsoft Windows 10 Enterprise Evaluation" (set productkey=NPPR9-FWDCX-D2C8J-H872K-2YT43)
::Microsoft Windows 11
if /i "%edition%" equ "Microsoft Windows 11 Home" (set productkey=TX9XD-98N7V-6WMQ6-BX7FG-H8Q99)
if /i "%edition%" equ "Microsoft Windows 11 Home N" (set productkey=3KHY7-WNT83-DGQKR-F7HPR-844BM)
if /i "%edition%" equ "Microsoft Windows 11 Home Single Language" (set productkey=7HNRX-D7KGG-3K4RQ-4WPJ4-YTDFH)
if /i "%edition%" equ "Microsoft Windows 11 Pro" (set productkey=W269N-WFGWX-YVC9B-4J6C9-T83GX)
if /i "%edition%" equ "Microsoft Windows 11 Pro N" (set productkey=MH37W-N47XK-V7XM9-C7227-GCQG9)
if /i "%edition%" equ "Microsoft Windows 11 Pro for Workstations" (set productkey=NRG8B-VKK3Q-CXVCJ-9G2XF-6Q84J)
if /i "%edition%" equ "Microsoft Windows 11 Pro N for Workstations" (set productkey=9FNHH-K3HBT-3W4TD-6383H-6XYWF)
if /i "%edition%" equ "Microsoft Windows 11 Enterprise" (set productkey=NPPR9-FWDCX-D2C8J-H872K-2YT43)
if /i "%edition%" equ "Microsoft Windows 11 Enterprise N" (set productkey=DPH2V-TTNVB-4X9Q3-TJR4H-KHJW4)
if /i "%edition%" equ "Microsoft Windows 11 Education" (set productkey=NW6C2-QMPVW-D7KKK-3GKT6-VCFB2)
if /i "%edition%" equ "Microsoft Windows 11 Education N" (set productkey=2WH4N-8QGBV-H22JP-CT43Q-MDWWJ)
if /i "%edition%" equ "Microsoft Windows 11 Enterprise Evaluation" (set productkey=NPPR9-FWDCX-D2C8J-H872K-2YT43)
::Microsoft Windows Server 2012
if /i "%edition%" equ "Microsoft Windows Server 2012" (set productkey=BN3D2-R7TKB-3YPBD-8DRP2-27GG4)
if /i "%edition%" equ "Microsoft Windows Server 2012 Essentials" (set productkey=HTDQM-NBMMG-KGYDT-2DTKT-J2MPV)
if /i "%edition%" equ "Microsoft Windows Server 2012 Standard" (set productkey=XC9B7-NBPP2-83J2H-RHMBY-92BT4)
if /i "%edition%" equ "Microsoft Windows Server 2012 Datacenter" (set productkey=48HP8-DN98B-MYWDG-T2DCC-8W83P)
::Microsoft Windows Server 2012 R2
if /i "%edition%" equ "Microsoft Windows Server 2012 Essentials" (set productkey=KNC87-3J2TX-XB4WP-VCPJV-M4FWM)
if /i "%edition%" equ "Microsoft Windows Server 2012 R2 Standard" (set productkey=D2N9P-3P6X9-2R39C-7RTCD-MDVJX)
if /i "%edition%" equ "Microsoft Windows Server 2012 R2 Datacenter" (set productkey=W3GGN-FT8W3-Y4M27-J84CP-Q3VJ9)
::Microsoft Windows Server 2016
if /i "%edition%" equ "Microsoft Windows Server 2016 Essentials" (set productkey=JCKRF-N37P4-C2D82-9YXRT-4M63B)
if /i "%edition%" equ "Microsoft Windows Server 2016 Standard" (set productkey=WC2BQ-8NRM3-FDDYY-2BFGV-KHKQY)
if /i "%edition%" equ "Microsoft Windows Server 2016 Datacenter" (set productkey=CB7KF-BWN84-R7R2Y-793K2-8XDDG)
::Microsoft Windows Server 2019
if /i "%edition%" equ "Microsoft Windows Server 2019 Essentials" (set productkey=WVDHN-86M7X-466P6-VHXV7-YY726)
if /i "%edition%" equ "Microsoft Windows Server 2019 Standard" (set productkey=N69G4-B89J2-4G8F4-WWYCC-J464C)
if /i "%edition%" equ "Microsoft Windows Server 2019 Datacenter" (set productkey=WMDGN-G9PQG-XVVXX-R3X43-63DFG)
::Microsoft Windows Server 2022
if /i "%edition%" equ "Microsoft Windows Server 2022 Standard" (set productkey=VDYBN-27WPP-V4HQT-9VMD4-VMK7H)
if /i "%edition%" equ "Microsoft Windows Server 2022 Datacenter" (set productkey=WX4NM-KYWYW-QJJR4-XV3QB-6VM33)
::Microsoft Windows 8
if /i "%edition%" equ "Microsoft Windows 8 Pro" (set productkey=NG4HW-VH26C-733KW-K6F98-J8CK4)
if /i "%edition%" equ "Microsoft Windows 8 Enterprise" (set productkey=32JNW-9KQ84-P47T8-D8GGY-CWCK7)
::Microsoft Windows 8.1
if /i "%edition%" equ "Microsoft Windows 8.1 Pro" (set productkey=GCRJD-8NW9H-F2CDX-CCM8D-9D6T9)
if /i "%edition%" equ "Microsoft Windows 8.1 Enterprise" (set productkey=MHF9N-XY6XB-WVXMC-BTDCT-MKKG7)
::Windows Server versions 20H2, 2004, 1909, 1903, and 1809 (Semi-Annual Channel versions)
if /i "%edition%" equ "Microsoft Windows Server Standard" (set productkey=VDYBN-27WPP-V4HQT-9VMD4-VMK7H)
if /i "%edition%" equ "Microsoft Windows Server Datacenter" (set productkey=WX4NM-KYWYW-QJJR4-XV3QB-6VM33)
::Microsoft Windows 7
wmic os get caption | find /v "Caption" > %temp%\ver.txt
set /p edition=<%temp%\ver.txt
echo.%edition% | findstr /C:"Microsoft Windows 7 Professional" >nul 2>&1
if not errorlevel 1 (set productkey=FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4) else (break)
echo.%edition% | findstr /C:"Microsoft Windows 7 Enterprise" >nul 2>&1
if not errorlevel 1 (set productkey=33PXH-7Y6KF-2VJC9-XBBR8-HVTHH) else (break)
::Microsoft Windows Server 2008 R2
echo.%edition% | findstr /C:"Microsoft Windows Server 2008 R2 Standard" >nul 2>&1
if not errorlevel 1 (set productkey=YC6KT-GKW9T-YTKYR-T4X34-R7VHC) else (break)
echo.%edition% | findstr /C:"Microsoft Windows Server 2008 R2 Enterprise" >nul 2>&1
if not errorlevel 1 (set productkey=489J6-VHDMP-X63PK-3K798-CPX3Y) else (break)
echo.%edition% | findstr /C:"Microsoft Windows Server 2008 R2 Datacenter" >nul 2>&1
if not errorlevel 1 (set productkey=74YFP-3QFB3-KQT8W-PMXWJ-7M648) else (break)
::Microsoft Windows Server 2008
echo.%edition% | findstr /C:"Microsoftr Windows Serverr 2008 Standard" >nul 2>&1
if not errorlevel 1 (set productkey=TM24T-X9RMF-VWXK6-X8JC9-BFGM2) else (break)
echo.%edition% | findstr /C:"Microsoftr Windows Serverr 2008 Enterprise " >nul 2>&1
if not errorlevel 1 (set productkey=YQGMW-MPWTJ-34KDK-48M3W-X4Q6V) else (break)
echo.%edition% | findstr /C:"Microsoftr Windows Server 2008 Datacenter" >nul 2>&1
if not errorlevel 1 (set productkey=7M67G-PC374-GR742-YH8V4-TCBY3) else (break)
echo .....................................................................................
echo Activating your Windows using product key: %productkey%
cscript %windir%\system32\slmgr.vbs /upk >nul 2>&1
cscript %windir%\system32\slmgr.vbs /ckms >nul 2>&1
cscript %windir%\system32\slmgr.vbs /cpky >nul 2>&1
cscript %windir%\system32\slmgr.vbs /skms kms.msgang.com >nul 2>&1
cscript %windir%\system32\slmgr.vbs /ipk %productkey% >nul 2>&1
cscript %windir%\system32\slmgr.vbs /ato | find /i "successfully"
echo .....................................................................................
echo Your Windows license details:
echo.
cscript %windir%\system32\slmgr.vbs /dlv | find /i "Description"
cscript %windir%\system32\slmgr.vbs /dlv | find /i "Licensed"
cscript %windir%\system32\slmgr.vbs /dlv | find /i "Channel:"
cscript %windir%\system32\slmgr.vbs /dlv | find /i "Partial"
cscript %windir%\system32\slmgr.vbs /dlv | find /i "expiration"
echo.
echo Press any key to close this window.
pause >nul@echo off
color f0
mode con cols=98 lines=30
title Activate Windows license for FREE - msgang.com
cls
echo .....................................................................................
echo #Project: Activating Microsoft software products for FREE without additional software
echo .....................................................................................
echo #Supported products: Windows 7/8/10/11/2008/2008R2/2012/2012R2/2016/2019/2022
echo .....................................................................................
for /f "tokens=* delims== " %%i in ('"powershell -c (Get-CimInstance Win32_OperatingSystem).Caption"') do (set edition=%%i)
echo You're using: %edition%
echo .....................................................................................
::Microsoft Windows 10
if /i "%edition%" equ "Microsoft Windows 10 Home" (set productkey=TX9XD-98N7V-6WMQ6-BX7FG-H8Q99)
if /i "%edition%" equ "Microsoft Windows 10 Home N" (set productkey=3KHY7-WNT83-DGQKR-F7HPR-844BM)
if /i "%edition%" equ "Microsoft Windows 10 Home Single Language" (set productkey=7HNRX-D7KGG-3K4RQ-4WPJ4-YTDFH)
if /i "%edition%" equ "Microsoft Windows 10 Pro" (set productkey=W269N-WFGWX-YVC9B-4J6C9-T83GX)
if /i "%edition%" equ "Microsoft Windows 10 Pro Education" (set productkey=6TP4R-GNPTD-KYYHQ-7B7DP-J447Y)
if /i "%edition%" equ "Microsoft Windows 10 Pro Education N" (set productkey=YVWGF-BXNMC-HTQYQ-CPQ99-66QFC)
if /i "%edition%" equ "Microsoft Windows 10 Pro N" (set productkey=MH37W-N47XK-V7XM9-C7227-GCQG9)
if /i "%edition%" equ "Microsoft Windows 10 Pro for Workstations" (set productkey=NRG8B-VKK3Q-CXVCJ-9G2XF-6Q84J)
if /i "%edition%" equ "Microsoft Windows 10 Pro N for Workstations" (set productkey=9FNHH-K3HBT-3W4TD-6383H-6XYWF)
if /i "%edition%" equ "Microsoft Windows 10 Enterprise" (set productkey=NPPR9-FWDCX-D2C8J-H872K-2YT43)
if /i "%edition%" equ "Microsoft Windows 10 Enterprise N" (set productkey=DPH2V-TTNVB-4X9Q3-TJR4H-KHJW4)
if /i "%edition%" equ "Microsoft Windows 10 Education" (set productkey=NW6C2-QMPVW-D7KKK-3GKT6-VCFB2)
if /i "%edition%" equ "Microsoft Windows 10 Education N" (set productkey=2WH4N-8QGBV-H22JP-CT43Q-MDWWJ)
if /i "%edition%" equ "Microsoft Windows 10 Enterprise 2016 LTSB" (set productkey=DCPHK-NFMTC-H88MJ-PFHPY-QJ4BJ)
::Microsoft Windows 11
if /i "%edition%" equ "Microsoft Windows 11 Home" (set productkey=TX9XD-98N7V-6WMQ6-BX7FG-H8Q99)
if /i "%edition%" equ "Microsoft Windows 11 Home N" (set productkey=3KHY7-WNT83-DGQKR-F7HPR-844BM)
if /i "%edition%" equ "Microsoft Windows 11 Home Single Language" (set productkey=7HNRX-D7KGG-3K4RQ-4WPJ4-YTDFH)
if /i "%edition%" equ "Microsoft Windows 11 Pro" (set productkey=W269N-WFGWX-YVC9B-4J6C9-T83GX)
if /i "%edition%" equ "Microsoft Windows 11 Pro Education" (set productkey=6TP4R-GNPTD-KYYHQ-7B7DP-J447Y)
if /i "%edition%" equ "Microsoft Windows 11 Pro Education N" (set productkey=YVWGF-BXNMC-HTQYQ-CPQ99-66QFC)
if /i "%edition%" equ "Microsoft Windows 11 Pro N" (set productkey=MH37W-N47XK-V7XM9-C7227-GCQG9)
if /i "%edition%" equ "Microsoft Windows 11 Pro for Workstations" (set productkey=NRG8B-VKK3Q-CXVCJ-9G2XF-6Q84J)
if /i "%edition%" equ "Microsoft Windows 11 Pro N for Workstations" (set productkey=9FNHH-K3HBT-3W4TD-6383H-6XYWF)
if /i "%edition%" equ "Microsoft Windows 11 Enterprise" (set productkey=NPPR9-FWDCX-D2C8J-H872K-2YT43)
if /i "%edition%" equ "Microsoft Windows 11 Enterprise N" (set productkey=DPH2V-TTNVB-4X9Q3-TJR4H-KHJW4)
if /i "%edition%" equ "Microsoft Windows 11 Education" (set productkey=NW6C2-QMPVW-D7KKK-3GKT6-VCFB2)
if /i "%edition%" equ "Microsoft Windows 11 Education N" (set productkey=2WH4N-8QGBV-H22JP-CT43Q-MDWWJ)
if /i "%edition%" equ "Microsoft Windows 11 Enterprise Evaluation" (set productkey=NPPR9-FWDCX-D2C8J-H872K-2YT43)
::Microsoft Windows Server 2012
if /i "%edition%" equ "Microsoft Windows Server 2012" (set productkey=BN3D2-R7TKB-3YPBD-8DRP2-27GG4)
if /i "%edition%" equ "Microsoft Windows Server 2012 Essentials" (set productkey=HTDQM-NBMMG-KGYDT-2DTKT-J2MPV)
if /i "%edition%" equ "Microsoft Windows Server 2012 Standard" (set productkey=XC9B7-NBPP2-83J2H-RHMBY-92BT4)
if /i "%edition%" equ "Microsoft Windows Server 2012 Datacenter" (set productkey=48HP8-DN98B-MYWDG-T2DCC-8W83P)
::Microsoft Windows Server 2012 R2
if /i "%edition%" equ "Microsoft Windows Server 2012 Essentials" (set productkey=KNC87-3J2TX-XB4WP-VCPJV-M4FWM)
if /i "%edition%" equ "Microsoft Windows Server 2012 R2 Standard" (set productkey=D2N9P-3P6X9-2R39C-7RTCD-MDVJX)
if /i "%edition%" equ "Microsoft Windows Server 2012 R2 Datacenter" (set productkey=W3GGN-FT8W3-Y4M27-J84CP-Q3VJ9)
::Microsoft Windows Server 2016
if /i "%edition%" equ "Microsoft Windows Server 2016 Essentials" (set productkey=JCKRF-N37P4-C2D82-9YXRT-4M63B)
if /i "%edition%" equ "Microsoft Windows Server 2016 Standard" (set productkey=WC2BQ-8NRM3-FDDYY-2BFGV-KHKQY)
if /i "%edition%" equ "Microsoft Windows Server 2016 Datacenter" (set productkey=CB7KF-BWN84-R7R2Y-793K2-8XDDG)
::Microsoft Windows Server 2019
if /i "%edition%" equ "Microsoft Windows Server 2019 Essentials" (set productkey=WVDHN-86M7X-466P6-VHXV7-YY726)
if /i "%edition%" equ "Microsoft Windows Server 2019 Standard" (set productkey=N69G4-B89J2-4G8F4-WWYCC-J464C)
if /i "%edition%" equ "Microsoft Windows Server 2019 Datacenter" (set productkey=WMDGN-G9PQG-XVVXX-R3X43-63DFG)
::Microsoft Windows Server 2022
if /i "%edition%" equ "Microsoft Windows Server 2022 Standard" (set productkey=VDYBN-27WPP-V4HQT-9VMD4-VMK7H)
if /i "%edition%" equ "Microsoft Windows Server 2022 Datacenter" (set productkey=WX4NM-KYWYW-QJJR4-XV3QB-6VM33)
::Microsoft Windows 8
if /i "%edition%" equ "Microsoft Windows 8 Pro" (set productkey=NG4HW-VH26C-733KW-K6F98-J8CK4)
if /i "%edition%" equ "Microsoft Windows 8 Enterprise" (set productkey=32JNW-9KQ84-P47T8-D8GGY-CWCK7)
::Microsoft Windows 8.1
if /i "%edition%" equ "Microsoft Windows 8.1 Pro" (set productkey=GCRJD-8NW9H-F2CDX-CCM8D-9D6T9)
if /i "%edition%" equ "Microsoft Windows 8.1 Enterprise" (set productkey=MHF9N-XY6XB-WVXMC-BTDCT-MKKG7)
::Windows Server versions 20H2, 2004, 1909, 1903, and 1809 (Semi-Annual Channel versions)
if /i "%edition%" equ "Microsoft Windows Server Standard" (set productkey=VDYBN-27WPP-V4HQT-9VMD4-VMK7H)
if /i "%edition%" equ "Microsoft Windows Server Datacenter" (set productkey=WX4NM-KYWYW-QJJR4-XV3QB-6VM33)
::Microsoft Windows 7/2008/2008R2/LTSC
@for /f "tokens=3*" %%i in ('Reg Query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v ProductName 2^>Nul') do Set "editionx=%%i %%j"
if /i "%editionx%" equ "Windows 7 Professional" (set productkey=FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4)
if /i "%editionx%" equ "Windows 7 Enterprise" (set productkey=33PXH-7Y6KF-2VJC9-XBBR8-HVTHH)
::Microsoft Windows Server 2008 R2
if /i "%editionx%" equ "Windows Server 2008 R2 Standard" (set productkey=YC6KT-GKW9T-YTKYR-T4X34-R7VHC)
if /i "%editionx%" equ "Windows Server 2008 R2 Enterprise" (set productkey=489J6-VHDMP-X63PK-3K798-CPX3Y)
if /i "%editionx%" equ "Windows Server 2008 R2 Datacenter" (set productkey=74YFP-3QFB3-KQT8W-PMXWJ-7M648)
::Microsoft Windows Server 2008
if /i "%editionx%" equ "Windows Server (R) 2008 Standard" (set productkey=TM24T-X9RMF-VWXK6-X8JC9-BFGM2)
if /i "%editionx%" equ "Windows Server (R) 2008 Enterprise" (set productkey=YQGMW-MPWTJ-34KDK-48M3W-X4Q6V)
if /i "%editionx%" equ "Windows Server (R) 2008 Datacenter" (set productkey=7M67G-PC374-GR742-YH8V4-TCBY3)
if /i "%editionx%" equ "Windows 10 Enterprise LTSC 2019" (set productkey=M7XTQ-FN8P6-TTKYV-9D4CC-J462D)
if /i "%editionx%" equ "Windows 10 Enterprise LTSC 2021" (set productkey=M7XTQ-FN8P6-TTKYV-9D4CC-J462D)
if /i "%editionx%" equ "Windows 10 Enterprise Evaluation" (set productkey=NPPR9-FWDCX-D2C8J-H872K-2YT43)
if /i "%editionx%" equ "Windows 11 Enterprise Evaluation" (set productkey=NPPR9-FWDCX-D2C8J-H872K-2YT43)
if /i "%editionx%" equ "Windows 10 Enterprise 2015 LTSB" (set productkey=WNMTR-4C88C-JK8YV-HQ7T2-76DF9)
::Microsoft Windows Server 2008
::wmic os get caption | find /v "Caption" > %temp%\ver.txt
::set /p edition8=<%temp%\ver.txt
::Microsoft Windows Server 2008
::echo.%edition8% | findstr /C:"Microsoftr Windows Serverr 2008 Standard" >nul 2>&1
::if not errorlevel 1 (set productkey=TM24T-X9RMF-VWXK6-X8JC9-BFGM2) else (break)
::echo.%edition8% | findstr /C:"Microsoftr Windows Serverr 2008 Enterprise " >nul 2>&1
::if not errorlevel 1 (set productkey=YQGMW-MPWTJ-34KDK-48M3W-X4Q6V) else (break)
::echo.%edition8% | findstr /C:"Microsoftr Windows Serverr 2008 Datacenter " >nul 2>&1
::if not errorlevel 1 (set productkey=7M67G-PC374-GR742-YH8V4-TCBY3) else (break)
echo .....................................................................................
echo Activating your Windows using product key: %productkey%
cscript %windir%\system32\slmgr.vbs /upk >nul 2>&1
cscript %windir%\system32\slmgr.vbs /ckms >nul 2>&1
cscript %windir%\system32\slmgr.vbs /cpky >nul 2>&1
cscript %windir%\system32\slmgr.vbs /skms kms.msgang.com >nul 2>&1
cscript %windir%\system32\slmgr.vbs /ipk %productkey% >nul 2>&1
cscript %windir%\system32\slmgr.vbs /ato | find /i "successfully"
echo .....................................................................................
echo Your Windows license details:
echo.
cscript %windir%\system32\slmgr.vbs /dlv | find /i "Description"
cscript %windir%\system32\slmgr.vbs /dlv | find /i "Licensed"
cscript %windir%\system32\slmgr.vbs /dlv | find /i "Channel:"
cscript %windir%\system32\slmgr.vbs /dlv | find /i "Partial"
cscript %windir%\system32\slmgr.vbs /dlv | find /i "expiration"
echo.
echo Press any key to close this window.
pause >nulMethod 4: Using PowerShell script
The last way, we can active Windows license using a PowerShell script. The script details can be found at my GitHub. When using the PowerShell script, you can active all Windows editions (Cliens and Server editions) included: Windows 7/8/10/11 and Windows Server 2008/2012/2016/2019/2022.
This method works similar with the batch script method but you don’t need to download anything. And we had no pop-up window saying Windows protected your PC anymore.
All you need to do is open PowerShell as administrator then run below command.
The script will run automatically. If has no issue, you should see the below output. The Windows Server 2019 Standard has been activated free forever.
#Output
========================================================================================
Description: Activating Microsoft software products for FREE without additional software
Website: https://msgang.com
Script by: Leo Nguyen
For detailed script execution: https://win.msgang.com
========================================================================================
You're using Microsoft Windows Server 2019 Standard
Activating your Windows license...
Done!
========================================================================================
Product Key Channel: Volume:GVLK
License Status: Licensed
========================================================================================
(*)Visit https://msang.com for more products.Conclusion
Hello Friends! My name is Leo, and I’m excited to share everything I know about activating Microsoft software products. In the past, I managed several YouTube channels on this topic, but they were taken down by Microsoft. That’s why I decided to start this blog to keep the conversation alive without interruptions. I’m committed to sharing my knowledge and insights for as long as possible!
If you would have any questions or concerns, please leave your comments or visit my Discord server. I would be glad to explain in more details. Thank you so much for all your feedback and support!
Want to activate others Microsoft products for free? You can follow the below posts:
- Windows 7/8/8.1/10/11
- Windows Servers 2008/2012/2016/2019/2022
- Microsoft Office 2013/2016/2019/2021 (included Visio and Project)
Windows Server с ролью Volume Activation Services может выступать в качестве KMS (Key Management Service) сервера, позволяющий выполнять активацию в корпоративной сети компьютеры с корпоративными (Volume) редакциями операционных систем Windows Server и Windows 10/11. В этой статье мы покажем, развернуть и настроить собственный KMS сервер на базе Windows Server 2022, 2019 и 2016, и использовать его для активации компьютеров.
Содержание:
- Установка роли KMS Host на Windows Server
- Активация KMS сервера на Windows Server с помощью CSVLK ключа
- Как выполнить активацию клиентов Windows на KMS сервере?
Установка роли KMS Host на Windows Server
Для развёртывания собственного KMS сервера вам нужно установить роль Volume Activation Services на любой из хостов с Windows Server 2022, 2019 или 2016. Если у вас в домене уже развернут KMS сервер с Windows Server 2016 или 2019, такой сервер можно использовать для активации клиентов с более новыми Windows Server 2022 и Windows 11 (в этом случае этот раздел можно пропустить и сразу перейти к активации KMS сервере).
- Установите на сервере роль Volume Activation Services из консоли Server Manager или воспользуйтесь следующей PowerShell командой для установки роли:
Install-WindowsFeature -Name VolumeActivation -IncludeAllSubFeature –IncludeManagementTools
- Включите правило Windows Firewall, которое разрешает доступ к KMS серверу:
Enable-NetFirewallRule -Name SPPSVC-In-TCP
(правило открывает доступ к серверу по порту TCP 1688).
Активация KMS сервера на Windows Server с помощью CSVLK ключа
Далее вам нужно активировать ваш KMS сервер с помощью персонального CSVLK ключа (также называется KMS host key). Ранее CSVLK ключи можно было получить из личного кабинета на сайте Microsoft Volume Licensing Service Center (VLSC), но недавно они были перемещены в Microsoft 365 Admin Center (MAC)
По умолчанию KMS host ключи отсутствуют в личном кабинете MAC для пользователей open agreements, вместо них предлагается использовать ключи многократной активации MAK (Multiple Activation Keys). Вы можете запросить генерацию CSVLK ключа в техподдержке Microsoft с помощью специальной формы запроса VLSC Support, где нужно указать ваш номер соглашения, название продукта, количество хостов планируемых к активации через KMS и цель развертывания KMS сервера.
- Авторизуйтесь в Microsoft 365 Admin Center, и перейдите в раздел Billing -> Your products -> Volume licensing -> Downloads & keys -> выберите продукт -> View keys. Скопируйте KMS host key Windows Srv 2022 DataCtr/Std KMS;
Всегда используйте KMS Host Key для максимальной версии Windows Server, доступной в вашем личном кабинете. KMS сервер, активированный более новым ключом сможет активировать все предыдущие версии Windows
- Установите новый KMS ключ на сервере командой:
slmgr /ipk <новый_KMS_host_ключ_Windows_Server_2022>Совет. Если KMS сервер активирован ключом для предыдущей версии Windows Server, сначала нужно удалить его:
slmgr /upk - Активируйте ваш KMS сервер на серверах активации Microsoft:
slmgr /ato
(с сервера должен быть прямой доступ в интернет к серверам активации Microsoft хотя бы на время активации). Либо вы можете активировать KMS сервер по телефону (для этого нужно запустить графическую утилиту Volume Activation Tools); - Чтобы опубликовать SRV запись в DNS, которая позволит клиентам автоматически находится KMS, выполните команду:
slmgr /sdns - Перезапустите службу Software Protection:
Restart-Service -Name sppsvc - Проверьте, что ваш KMS сервер активирован успешно:
slmgr.vbs /dlv
Убедитесь, что в поле Description указано
VOLUME_KMS_WS22 channel
, а в License status –
Licensed
. - Теперь вы можете активировать на вашем KMS сервере все поддерживаемые версии Windows, включая Windows 11 и Windows Server 2022.
KMS хосты с предыдущими версиями Windows Server (новее чем WS 2012R2) и новым KMS ключом (Windows Srv 2022 DataCtr/Std KMS) можно использовать для активации более последних Windows Server 2022 и Windows 11. Для этого достаточно установить на хостах последние кумулятивные обновления (через Windows Update или вручную).
Как выполнить активацию клиентов Windows на KMS сервере?
Чтобы активировать Windows компьютеры в вашей на вашем KMS сервере, на них должное быть установлен специальный GVLK ключ (Customer Specific Volume License Key). GVLK ключи это публичные общедоступных ключи, которые указывают на то, что данный компьютер активируется на KMS сервере.
Полный список клиентских GVLK ключей для всех поддерживаемых продуктов доступен на сайте Microsoft (https://learn.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys).
Определите версию и редакцию Windows на вашем компьютере с помощью PowerShell команды:
Get-ComputerInfo | select OsName
В данном случае это Windows 10 Pro. Найдите и скопируйте GVLK ключ для этой версии по ссылке выше. В нашем примере KMS Client Product Key — W269N-WFGWX-YVC9B-4J6C9-T83GX.
Установите ключ на клиентский компьютер с помощью команды:
slmgr /ipk W269N-WFGWX-YVC9B-4J6C9-T83GX
Если ваш компьютер добавлен в домен AD и для KMS хоста в DNS опубликована специальная SRV запись, то при следующей перезагрузке компьютера Windows сама выполнит активацию на KMS сервере.
Также вы можете указать имя и порт сервера KMS активации вручную:
slmgr /skms kms-server.winitpro.ru:1688
Чтобы активировать Windows на вашем KMS сервере, выполните команду:
slmgr /ato
Проверить статус активации Windows:
slmgr /dlv
В этом случае
VOLUME_KMSCLIENT channel
и
License status: Licensed
указывают на то, что операционная система на этом компьютере активирована на KMS сервере. Клиент активируется на 180 дней и автоматически продляется каждые 7 дней (если KMS сервер доступен).
Также можно проверить статус активации Windows с помощью команды
Get-CimInstance SoftwareLicensingProduct -Filter "Name like 'Windows%'" | where { $_.PartialProductKey } | select Description, LicenseStatus
Ознакомительные версии Windows Server нельзя активировать на KMS, сначала придется конвертировать редакцию согласно гайда.
16 февраля 2025 г. 12:39
2552
Содержание:
- Шаги для активации Windows Server через CMD
- Активация разных версий Windows Server через командную строку
- Что делать, если активация не удалась
- Вывод
Активация Windows Server 2025 через командную строку — удобный способ для системных администраторов и опытных пользователей. Этот метод позволяет быстро активировать систему без использования графического интерфейса.
Шаги для активации Windows Server через CMD
Перед началом убедитесь, что у вас есть действующий лицензионный ключ, а также стабильное подключение к интернету. Если всё готово, следуйте инструкции.
1. Открытие командной строки от имени администратора
Для выполнения активации сначала необходимо запустить командную строку с правами администратора:
- Нажмите правой кнопкой мыши на значке «Пуск».
- Выберите «Командная строка (администратор)» или «Windows PowerShell (администратор)».
После выполнения этих действий откроется окно командной строки, в котором можно вводить команды.
2. Установка ключа продукта
После открытия командной строки введите следующую команду, заменив XXXXX-XXXXX-XXXXX-XXXXX-XXXXX на ваш лицензионный ключ:
slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
Эта команда зарегистрирует введённый ключ в системе. Если у вас еще нет ключа, очень выгодно и быстро можно приобрести по ЭТОЙ ссылке.
3. Активация Windows Server
После успешного ввода ключа необходимо выполнить активацию системы. Для этого используйте следующую команду:
slmgr.vbs /ato
Подождите завершения процесса. Если активация прошла успешно, система выдаст соответствующее уведомление.
Активация разных версий Windows Server через командную строку
Процесс активации одинаков для всех версий Windows Server, однако иногда могут возникнуть нюансы. Активации Windows Server 2022 Standard через командную строку может потребовать предварительное удаление старого ключа. В этом случае перед установкой нового ключа выполните команду: slmgr.vbs /upk
Активация Windows Server 2019 Standard через командную строку аналогична, но если система не принимает ключ, попробуйте проверить его через команду slmgr.vbs /dlv, чтобы убедиться, что используется правильная версия.
Если требуется активация Windows Server 2016 через командную строку, но система не активируется, возможно, проблема связана с отключенной службой лицензирования. Для её включения используйте команду: sc config sppsvc start= auto & net start sppsvc
Активация Windows Server 2012 R2 через командную строку требует подходящего ключа, поэтому важно убедиться, что используемый ключ подходит именно для данной версии. Если активация не проходит, попробуйте запустить проверку статуса лицензии командой: slmgr.vbs /xpr
Что делать, если активация не удалась
Если при выполнении команды возникла ошибка, попробуйте следующие действия:
- Проверьте подключение к интернету — возможно, сервер Microsoft недоступен в момент активации.
- Убедитесь, что используемый ключ продукта действителен и вводится без ошибок.
- Перезагрузите сервер и повторите процедуру активации.
- Проверьте статус активации с помощью команды: slmgr.vbs /xpr
Если Windows Server по-прежнему не активируется, возможно, потребуется обратиться в службу поддержки Microsoft.
Вывод
Активация Windows Server через командную строку — это быстрый и эффективный способ, особенно полезный для системных администраторов. При наличии лицензионного ключа процесс занимает всего несколько минут.