Posted on 28/11/2017 by sie
Каждый раз пишу памятку по активации систем, потому что каждый раз какие-то засады.
Эта памятка по настройке KMS на Windows Server 2016, который позволяет активировать все серверные и клиентские ОС Windows, а также все версии Office.
Как найти ключ KMS для Windows и Office:
- Log on to the Volume Licensing Service Center (VLSC).
- Раздел License.
- Раздел Relationship Summary.
- Выбрать License ID для вашего активного контракта Active License.
- На открывшийся странице выбрать Product Keys.
- В таблице найти ключ «Windows Srv 2016 DataCtr/Std KMS» или «Office 2010/2013/2016 Suites and Apps KMS»
Установка KMS:
- Ставим систему Windows Server 2016 любой редакции
- Компонент KMS можно поставить, а можно явно не ставить – при установке KMS ключа он будет установлен и запущен, но правило в фаерволе надо обязательно включить через GUI или PowerShell:
Enable-NetFirewallRule -Name SPPSVC-In-TCP
- Устанавливаем ключ KMS из командной строки с повышенными правами:
slmgr -ipk <KMS key for Windows 2016>
- Активируем его:
slmgr –ato
- Устанавливаем лицензионные паки для Office в такой последовательности:
Office 2010: https://www.microsoft.com/en-us/download/details.aspx?id=25095 – есть проблема, см. решение ниже.
Office 2013: https://www.microsoft.com/en-us/download/details.aspx?id=35584
Office 2016: https://www.microsoft.com/en-us/download/details.aspx?id=49164
- При запуске установки каждый пак будет запрашивать ключ KMS – вводим его или копируем. Если ключ правильный, то он будет установлен.
- Затем пак будет пытаться активировать ключ. Если напишет, что не смог, то открываем командную строку с повышенными правами и выполняем:
slmgr -ato <Activation ID продукта>
Office 2013: slmgr -ato 2E28138A-847F-42BC-9752-61B03FFF33CD
Office 2016: slmgr -ato 98ebfe73-2084-4c97-932c-c0cd1643bea7
Office 2010: slmgr -ato bfe7a195-4f8f-4f0b-a622-cf13c7d16864
slmgr -dlv <Activation ID продукта> — получить сведения.
- Полный список ключей и их статусов можно вывести командой (там же видно Activation ID — чтобы не искать где-то):
cscript slmgr.vbs -dlv all
При установке лицензионного пака для Office 2010 вы получите ошибку, что ОС не поддерживается. Обходной путь:
- После аварийного завершения установки пака открыть директорию C:\Program Files (x86)\MSECache\OfficeKMS
- Отредактировать VBScript файл в этой директории, заменив «folder=unknown» на «Folder=Win8».
- Из командной строки с повышенными правами запустить этот скрипт.
Полезные ссылки:
- How to troubleshoot the Key Management Service (KMS)
- По ошибке пака Office 2010
- KMS Activation for Windows Server 2016
- Памятка по активации Windows 10 и Office 2016
- Еще раз про активацию Microsoft Office
- Памятка по активации Office 2013
- Памятка по активации Office 2010
Filed under: Office, Windows | Tagged: KMS, Office, Office 2010, Office 2013, Office 2016, Windows |
Asked by: Mr. Dr. Max Richter M.Sc. | Last update: July 19, 2023
star rating: 4.9/5 (71 ratings)
After installation or update of your KMS server, activate it with CSVLK (so called KMS Host Key). You can get this key on Microsoft Volume License (VLSC) website. The key you need is called Windows Srv 2016 DataCtr/Std KMS and is located in License -> Relationship Summary -> Product Keys.
How do I enable KMS on Windows Server?
Information Right Click on the Start menu and select Command Prompt (Admin) Run the command cscript slmgr. vbs -skms fsu-kms-01.fsu.edu to configure computer for the KMS activation server. Run the command cscript slmgr. vbs -ato to activate the computer with the KMS server. Finally run cscript slmgr.
How do I activate KMS?
To enable the KMS host computer to activate Office, you must install the Office Volume License Pack and enter your KMS key on the KMS host computer. Then, you need to activate the KMS key over the internet or by telephone.
Where is my KMS Licence key?
These KMS clients keys, also known as Generic Volume License Keys (GVLK), are public and can be found in the KMS Client Setup Keys page. From the client perspective, you can use the slmgr. vbs script to manage and view the license configuration.
How do I setup a KMS Client Server?
Manually assign a KMS host to a KMS client On a KMS client, open an elevated Command Prompt window. Depending on your implementation, follow one of these steps: To assign a KMS host by using the FQDN of the host, run the following command: cmd Copy. cscript \windows\system32\slmgr.vbs -skms <KMS_FQDN>:<port>.
Can’t find the KMS server?
How do I troubleshoot KMS activation issues? Check your Internet connection. Upgrade your Windows OS. Check if the computer is activated. Check if you have more than 25 clients. Check the client communicated with the host. Open the right port. Configure DNS properly for multiple KMS hosts.
How do I find my KMS server?
Finding the KMS Server on your network is fairly easy. On a Windows 2008 R2 Server or Windows 7 client, run “slmgr. vbs /dlv” on the server and it should return the name of the KMS Server.
Is KMS activation legal?
Solutions like KMSpico to bypass legitimate activation spoofing a Key Management Services server is illegal. Consumers should not endeavor on activating Windows through those means. Activation servers (KMS) through an organization or educational institution is legal, and should be used for those intents and purposes.
Is KMS activation safe?
Microsoft’s Defender will find the KMS activater as a threat and other antivirus software will also do it. We have no information if this kind of tools have malware, we simply advise not to use it. If you do want to use illegal software please use it at your own risk.
How do I find my kms DNS?
To check that the proper DNS record for KMS Server Auto-Discovery exists: open a CMD prompt. type: nslookup -type=SRV _vlmcs. _tcp. If a DNS record is found, it should be displayed. Remember: the client must have a Primary DNS suffix configured for this to work.
How do I check my kms Licence count?
Slmgr. vbs and the Software Licensing service Version Information. At the top of the slmgr. Name. This indicates the edition of Windows that is installed on the KMS host system. Description. This is where you see the key that is installed. License Status. Current Count. Listening on Port.
What is a KMS client setup key?
To use KMS, you need to have a KMS host available on your local network. Computers that activate with a KMS host need to have a specific product key. This key is sometimes referred to as the KMS client key, but it is formally known as a Microsoft Generic Volume License Key (GVLK).
How do I find my KMS server IP?
Look for the KeyManagementServiceName data and this should return your KMS server. Do a ping of this and it should then return you the IP address of the KMS server. Run «slmgr /dlv» and you will get the KMS host name.
How do I activate Server 2019 Standard?
Login to Windows Server 2019. Open Settings and then select System. Select About and check Edition. If it shows Windows Server 2019 Standard or others non-evaluation edition, you can activate it without reboot.
How do I activate Server 2016?
Trouble Activating Windows Server 2016 1) Click the Windows button in the lower left of your screen and type slui 3 as pictured below. Press enter or click the slui 3 icon towards the top. 2) You now are able to enter your product key. 3) Enter your product key and click Next. 4) Your server is now activated. Click Close.
What is online KMS activation?
The Key Management Service (KMS) is an activation service that allows organizations to activate systems within their own network, eliminating the need for individual computers to connect to Microsoft for product activation.
Why is my kms not working?
If a KMS host fails, you must install a KMS host key on a new host and then activate the host. Make sure that the new KMS host has an SRV RR in the DNS database. If the clients do not use auto-discovery, you must manually update the KMS client computers that were assigned to the failed KMS host by running slmgr.
Where is Slmgr VBS located?
Where to Enter Slmgr Commands. While Slmgr. vbs is stored in the System32 and SysWOW64 folders, commands that interface with the file need to be entered into Command Prompt.
How can I tell if Windows server is activated?
Start by opening the Settings app and then, go to Update & Security. On the left side of the window, click or tap Activation. Then, look on the right side, and you should see the activation status of your Windows 10 computer or device.
Why does Office keep asking me to activate?
This can happen if you don’t uninstall the pre-installed version of Office on your new PC before installing a volume license version of Office. To stop the prompts for activation, make sure your Office uses volume licensing and then update the registry.
Core Infrastructure and Security Blog
4 MIN READ
First published on TechNet on Oct 24, 2016
Hi everyone. Graeme Bray here with a quick article around KMS and Server 2016. KMS and Server 2016 you say? Shouldn’t I be using Active Directory Based Activation? Yes, you should, but in case you are not, let’s go over the pre-requisites to activate Windows Server 2016 via KMS. ********* UPDATE (5/5/17)***************** The requirements have been updated below to remove and add a required update. There was a supersedence change that makes 3058168 superseded by the July 2016 Update Rollup. Additionally, there is often an error saying that the update is not applicable to your machine. To fix this issue, you need to install the latest Servicing Stack Update (SSU) for 2012 or 2012 R2. Their KB’s and links are below: Windows Server 2012 R2 / KB3173424 https://support.microsoft.com/kb/3173424 Windows Server 2012 / KB3173426 https://support.microsoft.com/kb/3173426 ******************************************* First, lets review the pre-requisite updates that must be installed. If your KMS host is running Windows Server 2012, you need two updates: * https://support.microsoft.com/kb/3058168 (NOTE: This has been superseded by the July 2016 Update Rollup) o Direct Download: https://www.microsoft.com/en-us/download/details.aspx?id=47649 (NOTE: This has been superseded by the July 2016 Update Rollup) * https://support.microsoft.com/kb/3172615 o Direct Download: https://www.microsoft.com/en-us/download/details.aspx?id=53316 If your KMS host is running Windows Server 2012 R2, you need two updates: * https://support.microsoft.com/kb/3058168 (NOTE: This has been superseded by the July 2016 Update Rollup) o Direct Download: https://www.microsoft.com/en-us/download/details.aspx?id=47622 (NOTE: This has been superseded by the July 2016 Update Rollup) * https://support.microsoft.com/kb/3172614 o Direct Download: https://www.microsoft.com/en-us/download/details.aspx?id=53333 If your KMS host is running Windows Server 2008 R2: * There is no update to allow Windows Server 2008 R2 to activate Windows Server 2016. Windows Server 2008 R2 is in extended support. During this phase, we only release security updates and do not release updates that add additional functionality. Lets review what these updates add: * The first update allows the activation of Windows 10 from Windows 8, 8.1, and Windows Server 2012 R2 based systems. * The second is an update rollup that allows KMS to activate Windows 10 1607 long-term servicing branch (LTSB) systems and Windows Server 2016 clients. KMS License Key After that, all you need to do is add your KMS License Key from the Volume License site. But wait, how do I find my KMS License Key?! Have no fear, there is a KB article (and detailed steps) for you! Retrieve KMS License Key from the VLSC for Windows Server 2016. To resolve this problem, follow these steps: 1. Log on to the Volume Licensing Service Center (VLSC). 2. Click License . 3. Click Relationship Summary . 4. Click License ID of your current Active License. 5. After the page loads, click Product Keys . 6. In the list of keys, locate Windows Srv 2016 DataCtr/Std KMS 7. Install this key on the KMS host. https://support.microsoft.com/kb/3086418 Client Licensing After your KMS host is activated, use the Client Setup Keys to activate your shiny new Windows Server 2016 hosts. https://technet.microsoft.com/library/jj612867.aspx What is a client setup key you ask? A CSVLK is the key that is installed, by default, on your Volume License media that you pulled down day 1. If you are using volume license media, no key change is required. If you are converting an install from Retail, MSDN, etc, you will want to use the client setup key to convert to a Volume License key to allow activation. Active Directory Based Activation Graeme, this sure seems like a lot of work to get KMS working for Windows Server 2016. Is there a better way to do this? The recommendation at this point is to leave your existing KMS system alone. Whether it is running on Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2, continue to service the machine via security and quality updates. Allow your KMS system to activate down-level operating systems and Office installs (Windows 7, Windows Server 2008/2008 R2, and Office 2010). Utilize Active Directory Based Activation (ADBA) for all new clients (Windows 8, 8.1, Windows Server 2012, 2012 R2, 2016, Windows 10, Office 2013, and Office 2016). Active Directory Based Activation provides several key benefits: 1. Activation is near instantaneous when a system is brought online. As soon as the system talks to Active Directory, the system is activated. 2. One less server to maintain and update. Once all downlevel (2008 R2 & prior) systems are migrated, you can remove your KMS host. 3. AD-Based activation is forest wide. KMS hosts require additional configuration to support multiple domains. Have more questions? Q: Where can I get even more details around KMS and AD Based Activation? A: Refer to these other posts by one of my colleagues, Charity Shelbourne. https://blogs.technet.microsoft.com/askpfeplat/2013/02/04/active-directory-based-activation-vs-key-management-services/ https://blogs.technet.microsoft.com/askpfeplat/2015/11/09/kms-migration-from-2008-r2-to-windows-server-2012-r2-and-kms-activation-known-issues/ Q: Can Microsoft help me with this process? A: Absolutely! Reach out to your TAM and you can engage Premier Field Engineering for assistance. Thanks for reading! Graeme «Keeping KMS easy» Bray
Updated Feb 20, 2020
Version 3.0
Activating Windows Server 2016
So it’s time to make sure we start thinking about activating Windows Server 2016 in our environments.
If you manage on premises environments with one or more AD domains or even forests you might be in a situation where Active Directory Based Activation (ADBA) is the easiest solution. If you set this up you’ll enjoy automatic activation of the OS after joining domain configured with ADBA. This is what I use for the Office and Windows editions that support it. It’s fast and easy to set up.
Now when you’re hosting IAAS services this might not be your best approach as that means it will need to be set up in the AD of your tenants. Something your most often don’t manage or control if an AD is even present. You also need the right versions of both AD and client software and operating systems to use this. That can also be an issue on premises. But don’t worry. Both Key Management Service (KMS) and Automatic Virtual Machine Activation (AVMA) will work for IAAS and for on premises in these situations.
I actually support 2 on premises environments where ADBA is being used for the recent OS and Office versions while KMS is still around for the older OS versions. That way as the old OS versions are phased out the KMS infrastructure can be retired as well.
KMS Server activation
You can use a Windows Server 2012 R2 or 2016 server as a KMS server. I just made sure my KMS server was fully patched before I attempted to install and activate the Windows Server 2016KMS key. That means that on Windows Server 2012 R2 you want KB3172614 installed as this enable support for Windows Server 2012 R2 as a KMS server host to activate Windows Server 2016. See https://support.microsoft.com/en-us/help/24717/windows-8-1-windows-server-2012-r2-update-history. For Windows Server 2016 this means don’t do anything unless you have all the zero day patches installed.
First we take a look at the current situation by running slmgr.vbs /dlv
Uninstall the current KMS key using slmgr.vbs /upk, please use an elevated command prompt
Now you can install the new Windows 2016 KMS key on your KMS server. If you run in to any issues here, restarting the KMS Service can help ((“net stop sppsvc” and “net start sppsvc“) . Try that first.
slmgr.vbs /ipk JOINT-THENA-VYBOY-SNOCR-ACKS!
The key listed here is for all you wannabe pirates out there, sorry, this is the navy. If you’re, looking for illegal keys, cracks, keygens, activators or dodgy KMS virtual machine for Windows activations and such this is not the place .
If you now run slmgr.vbs /dlv you’ll see that the license status is “notification” as the server hasn’t been activated yet.
You now need to activate your server with the KMS key first by running slmgr.vbs /ato
We can now look at what’s installed now by running slmgr.vbs /dlv again. As you can see we’re in business to activate all our Windows Server 2016 and any OS version below that if t supports KMS activation.
Now in Windows 2012 R2 and later we also have the Volume Activation Tools feature you can install and use to do this, just like you use this for the ADBA setup.
Activate guest VMs on Hyper-V hosts
Configure Guest VMs activation with AVMA
If you’d like to leverage AVMA, which is especially handy as a IAAS hoster, you’ll need to use Windows Server 2016 or 2012 R2 Datacenter on your Hyper-V hosts and activate them by your chosen method (MAK, KMS, ADBA). You also need to use Windows Server 2016 or 2012 R2 Standard/Datacenter in the guest VMs. As long as your Hyper-V hosts is activated, every new guest deployed on them will be activated automatically. That’s it. There’s no need for a KMS or ADBA configuration for the guest (tenant VMs) or even an internet connection. The later is great for more secured environments. Easy peasy.
The only thing you need to do is use the AVMA client key in the slmgr /ipk. These are public ones actually just like the KMS clients keys.
There are two things to note: The first,a s you can read in the link to the AVMA documenation above:
“AVMA requires a Microsoft Virtualization Server running Windows Server 2012 R2 Datacenter or Windows Server 2016 Datacenter. A Windows Server 2016 AVMA host can activate guests that run the Datacenter, Standard or Essentials editions of Windows Server 2016 and Windows Server 2012 R2. A Windows Server 2012 R2 AVMA host can activate guests that run the Datacenter, Standard or Essentials editions of Windows Server 2012 R2.”
This means a Windows Server 2012 R2 Host cannot activate Windows server 2016 VMs. You can upgrade “cheaply” that way, let’s put it like that.
Secondly make sure the VM has Data Exchange turned ON in Integration Services. That’s the mechanism leveraged to make AVMA work. You should have that on anyway, really, I mean it 🙂
Configure Guest VMs activation with KMS
The public client KMS keys for VLK media can be found here: Appendix A: KMS Client Setup Keys I’ve only included a screnshot of the Windows Server KMS client keys here. More info is in the TechNet page.
To make sure a Windows Server 2016 Datacenter VM can activate via a KMS serer install use the below commands to replace a MAK key for example:
slmgr.vbs /ipk CB7KF-BWN84-R7R2Y-793K2-8XDDG
slmgr.vbs /ato
NOTE: all these keys can be used within a template or via unattented installation config files.
,
- Updating your existing KMS hosts to support Windows Server 2016
- Setting up a new Windows Server 2016 KMS host
- Activating Windows 10 Enterprise 2016 LTSB
Updating existing KMS Hosts
If your KMS host is Windows Server 2012 you need to install the following updates
- Update: activate Windows 10 from Windows 8 or Windows 8.1, and Windows Server 2012 or Windows Server 2012 R2 KMS hosts
- July 2016 update rollup for Windows Server 2012
- Verify the version of sppsvc.exe and ensure that it is updated to at least version 6.3.9600.18376.
If your KMS host is Windows Server 2012 R2 you need to install the following updates:
- Update: activate Windows 10 from Windows 8 or Windows 8.1, and Windows Server 2012 or Windows Server 2012 R2 KMS hosts
- July 2016 update rollup for Windows 8.1 and Windows Server 2012 R2
Once updated you need to obtain a Windows Server 2016 CSVLK. Do the following
- Log on to the Volume Licensing Service Center (VLSC).
- Click License.
- Click Relationship Summary.
- Click License ID of their current Active License.
- After the page loads, click Product Keys.
- Look for a key called “Windows Srv 2016 DataCtr/Std KMS”
Once you have the key then run the following commands at elevated cmd prompt
1. Install the Windows Server 2016 CSVLK
Cscript.exe %windir%\system32\slmgr.vbs /ipk
2. Activate the Windows Server 2016 CSVLK
Cscript.exe %windir%\system32\slmgr.vbs /ato
Windows Server 2008 R2 is not supported as a KMS Host for Windows Server 2016 or Windows 10 Enterprise 2016 LTSB edition
Setting up new Windows Server 2016 KMS host
If you want to setup a new Windows Server 2016 KMS host normally you can use the Volume Activation services role wizard or command line to configure the KMS host.
We are aware of issue where when you run the Volume Activation Services role wizard, it will report the error “vmw.exe has stopped working” during the product key management phase of the wizard
Microsoft is investigating this issue and will update this blog when a fix is available but in meantime you will need to configure it using the steps below
1. Open elevated cmd prompt
2. Install the Windows Server 2016 CSVLK
cscript.exe %windir%\system32\slmgr.vbs /ipk <insert Windows Srv 2016 DataCtr/Std KMS CSVLK here>
3. Activate the Windows Server 2016 CSVLK
Cscript.exe %windir%\system32\slmgr.vbs /ato
If system does not have internet connectivity do the following to activate via the command line:
1. Open an elevated command prompt
2. Obtain the Installation ID
Cscript.exe %windir%\system32\slmgr.vbs /dti
3. Look up Microsoft phone activation number using phone number listed in %windir%System32\SPPUI\Phone.inf
4. Call the number and follow the prompts to obtain the confirmation ID
5. Apply the confirmation ID (do not include hyphens)
Cscript.exe %windir%\system32\slmgr.vbs /atp
6. Wait for a success message (numbers blurred on purpose)
7. Verify that the license status shows licensed:
Cscript.exe %windir%\system32\slmgr.vbs /dlv
Windows 10 Enterprise 2016 LTSB Edition volume activation
Note: In addition to activating Windows Server 2016 the “Windows Srv 2016 DataCtr/Std KMS” KMS host(CSVLK) key also activates Windows 10 Enterprise 2016 LTSB edition