Loading…
The new Windows Server 2019 has been already made available by Microsoft and the first problem i encountered was rather strange. When you attempt to change the product key for your Windows Server 2019 GUI version you will get the frustrating message that the key is not for the version of Windows Server you installed.
You can always change the product key using the slmgr.vbs script.
slmgr.vbs /ipk #####-#####-#####-#####-#####
slmgr.vbs /atoThis entry was posted in Windows Server 2019 and tagged Windows Server 2019. Bookmark the permalink.
- Блоги
- »
- Рабочий процесс Netmate
- »
- Блог технического специалиста
24.05.201315:5624.05.2013 15:56:13
Иногда требуется изменить ключ продукта в Windows 8 и Windows Server 2012, однако «кнопки» для изменения ключа в этих ОС нет, в отличие от предыдущих версий. Для изменения ключа запустите командную строку от имени администратора и используйте следующую команду:
slmgr -ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
где XXXXX-XXXXX-XXXXX-XXXXX-XXXXX — ключ продукта.
Подробнее об активации и изменении ключа тут
http://support.microsoft.com/kb/929826
Sergei
17.12.2013 21:29:53
Такое чувство что у Microsoft с каждой версией операционка дебильней и дебильней
Андрей
16.02.2015 10:55:58
Согласен, интерфейс все тупее и тупее — нужно наводить мышкой где — то в углу что бы нащупать нужные вкладки. Хотя бы Shell есть на панели.
Если при попытке сменить ключ продукта с помощью
slmgr.vsb -ipk
вылезает ошибка типа:
Run “slui.exe 0x2a 0xC004F069” to display the error text
то нужно делать так:
DISM.exe /Online /Get-TargetEditions DISM /online /Set-Edition:ServerStandard /ProductKey:ENTER-YOUR-SERIAL-FROM-TABLE /AcceptEula
Windows Server 2019 Datacenter WMDGN-G9PQG-XVVXX-R3X43-63DFG Windows Server 2019 Standard N69G4-B89J2-4G8F4-WWYCC-J464C Windows Server 2019 Standard Retail Q28NV-6P69W-4D4QT-QRCDW-J8HYD Windows Server 2019 Essentials WVDHN-86M7X-466P6-VHXV7-YY726 Windows Server 2019 Azure Core FDNH6-VW9RW-BXPJ7-4XTYG-239TB Windows Server 2019 Datacenter Semi-Annual Channel (v.1809) 6NMRW-2C8FM-D24W7-TQWMY-CWH2D Windows Server 2019 Standard Semi-Annual Channel (v.1809) N2KJX-J94YW-TQVFB-DG9YT-724CC Windows Server 2019 ARM64 GRFBW-QNDC4-6QBHG-CCK3B-2PR88
Windows Server 2016 Standard Semi-Annual Channel (v.1803) PTXN8-JFHJM-4WC78-MPCBR-9W4KR Windows Server 2016 Datacenter Semi-Annual Channel (v.1803) 2HXDN-KRXHB-GPYC7-YCKFJ-7FVDG Windows Server 2016 Datacenter Semi-Annual Channel (v.1709) 6Y6KB-N82V8-D8CQV-23MJW-BWTG6 Windows Server 2016 Standard Semi-Annual Channel (v.1709) DPCNP-XQFKJ-BJF7R-FRC8D-GF6G4 Windows Server 2016 ARM64 K9FYF-G6NCK-73M32-XMVPY-F9DRR Windows Server 2016 Datacenter CB7KF-BWN84-R7R2Y-793K2-8XDDG Windows Server 2016 Standard WC2BQ-8NRM3-FDDYY-2BFGV-KHKQY Windows Server 2016 Essentials JCKRF-N37P4-C2D82-9YXRT-4M63B Windows Server 2016 Cloud Storage QN4C6-GBJD2-FB422-GHWJK-GJG2R Windows Server 2016 Azure Core VP34G-4NPPG-79JTQ-864T4-R3MQX WNCYY-GFBH2-M4WTT-XQ2FP-PG2K9
И теперь можно выполнить:
slmgr.vbs /ipk <your product key> slmgr.vbs /ato
When installing Windows Server 2019, as with previous versions of Windows, you are prompted to enter the product key during installation, however if you are waiting for licensing to arrive, you can skip this and continue building your server. Once the licensing arrives, you can enter the product key from the Settings app, but in my case, clicking the Change Product Key button resulted in absolutely nothing. The window did not pop up, no error in the event logs, nothing at all. In this article, I will show you how to enter your product key manually using command line utilities, then activating using the same utility.
- Click Start and type CMD in the Start Search menu
- Right Click and choose Run as administrator
- To remove any existing product key (in case you used a trial key), enter and run the command slmgr.vbs /upk .
- Clear the product key from registry by running slmgr.vbs /cpky
- To enter your new product key, use the command: slmgr.vbs /ipk xxxxx-xxxxx-xxxxx-xxxxx where the x’s are your actual product key.
- Lastly, activate Windows by entering the command slmgr.vbs /ato
- Windows is now activated.
From my research, this appears to be a fairly common issue. Some users reported completely reloading Windows and entering the key from the start to resolve the issue, but if you have already configured the server or workstation, that’s not really an option. After running the above commands, my servers were activated and running normally. So far, this is my only hiccup with Server 2019.
Source :
https://technogecko.net/guides/change-product-key-does-nothing-windows-server-2019-windows-10-1809/