Hi, This is Scott McArthur, a Supportability Program Manager for Windows and Surface. With the launch of Windows Server 2016 I wanted to share some information on volume activation: • 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 • • • 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: • • Once updated you need to obtain a Windows Server 2016 CSVLK.

Do the following • Log on to the • 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” If you are unable to locate your product key please contact the 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 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 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.

I'm struggling with kms and office 2016. After installing kms and activating. Same problem here too. Windows server 2008 r2 kms and office 2016 pro plus.

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 Hope this helps with your Windows Server 2016 deployments Scott McArthur. • Memory Management, Performance, Printing, Terminal Server • Debugging, Hangs, Tools • DFSR, Certificates, Group Policy • Espanol, Portugues • SMS MOM • Scalable Networking, OCS, Communications Server • Windows Essential Business Server • Microsoft Application Virtualization, SoftGrid, Softricity • DPM related issues • BDD Team • Vista Team Blog • Microsoft GTSC Bucharest / Covering topics such as: Windows Server, Failover Clustering, Performance, Printing, Core OS, AD, Deployment, WSUS, SCOM/SCCM Product Team Blogs. New Windows Server 2016 Standard configured with KMS. DNS publishing disabled. Suryaputhri Serial Actress here.

GPO created to handle client connectivity. Since activating Windows Server 2016 KMS key and Office 2010/2013/2016 I am getting a duplicate version of Windows showing in SLMGR /DLV. Here is the info: Description: Windows(R) Operating System, VOLUME_KMS_WS16 channel This license is not in use. Please confirm this is from running slmgr /dlv all, and not just /dlv. If from /dlv all, this is expected.

Notice that the entries are not the same. One says license not in use. The only entry that matters for the OS KMS activation is that which is in use and reported by running slmgr /dlv.