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.

Jun 06, 2016. //technet.microsoft.com/en-us/library/mt703272.aspx to install Visio 2016 Standard Volume. My Office 365 install is on. Contact our KMS server. During installation the Volume Activation Tool will appear at the console window; you can either use the ADBA or KMS. MS Office 2016 KMS activation method.

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 Update 1/9/2018: This issue was resolved in the following KB: 3201845 Cumulative Update for Windows 10 Version 1607 and Windows Server 2016: December 9, 2016 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 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. 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. Office KMS activation entries can be obtained with either the activation ID in conjunction with the slmgr /dlv command or using the Office commands. VOLUME)KMS_WS16 means you have the Windows Server 2016 KMS CSVLK (host key). Happy to answer this for you, and very capable. Installing any OS CSVLK on a KMS host replaces the previous one.

If you install the Windows Server 2016 CSVLK on a KMS host that has the Windows Server 2012 for Windows 10 CSVLK installed, it will replace it. The Windows Server 2016 CSVLK, when installed, activated, and with the minimum threshold met, will activate all OS-KMS capable VL builds as it has in the past.

As per a post above, an update to existing documentation for Server 2016’s CSVLK capabilities is pending. Thanks for the information, we have the same problem with vmw.exe fault, activation with the command line succeeded. It is good to know, that I am not alone with this problem: Faulting application name: Vmw.exe, version: 10.0.14393.0, time stamp: 0x57898799 Faulting module name: ntdll.dll, version: 10.0.14393.0, time stamp: 0x578997b2 Exception code: 0xc0000374 Fault offset: 0x0f73e3 Meanwhile, I want to note, that activation of the Office 2010 / 2013 via the KMS hosted on Windows Server 2016 will not work without some modifications.

Office 2016 works ok, as it is supported under this OS. However, in mixed environment, there old versions of Office are still used and gradually staged, you may need to configure activation of the all Office versions available – 2010, 2013, 2016. Unlike Windows, for Office you have to install keys and activate each version separately – activation for Office 2016 will not cover Office 2010. If you just try to install Microsoft Office 2010 KMS Host License Pack (or 2013) it will fail with the “Unsupported operation system” error.

This is a expected behavior, but running in compatibility mode will not fix it. Instead, you should: 1) Install Office KMS Host Licence Pack (version 2010, for example). Ignore the OS error. 2) Go to C: Program Files (x86) MSECache OfficeKMS and patch the kms_host.vbs file.

After code block ‘ win8 or greater If (Ver(0) = “6” And Ver(1) >= “2”) Or (Ver(0) >= “7”) Then folder = “win8” Exit For End If insert another one (taken from Office 2016) ‘future OS’s If (CInt(Ver(0)) >= 10) Then folder = “win8” Exit For End If 3) Continue installation and activation process by running cd C: Program Files (x86) MSECache OfficeKMS cscript kms_host.vbs It will install the Office key files into the KMS store, and activate it (for Office 2010) or try to do so (for Office 2013+, if you face the vmw.exe bug too). 4) Repeat 1-3 for Office 2013, it will owerwrite kms_host.vbs. Then install Office 2016 key files as usual, installer will work without modifications, it is fully supported.

Now you can better understand, why after Windows 8 we have a Windows 10 – even Mocrosoft code sometimes fail to check versions properly. Ok, now you have to activate the Office – but if you, like I do, face te vmw.exe error, it has to be done via the command line and product GUID. Office 2010 – activate slmgr /ato bfe7a195-4f8f-4f0b-a622-cf13c7d16864 And check activation (and activated clients, if any) slmgr /dlv bfe7a195-4f8f-4f0b-a622-cf13c7d16864 Office 2013 – activate slmgr /ato 2E28138A-847F-42BC-9752-61B03FFF33CD Office 2016 – activate slmgr /ato 98ebfe73-2084-4c97-932c-c0cd1643bea7 If activation online fails for any product, it may be needed to import proxy settings from IE into systev via the netsh winhttp import proxy source=ie command. You can reset them back to (nothing) via netsh winhttp reset proxy. Now your new KMS server will activate Windows and Office (all available KMS versions).

We have received a Windows 10 LTSB 2016 KMS key, but not a Server 2016/Win 10 LTSB 2016 key. We are currently running on a Server 2012 R2/Win 10 LTSB 2015 KMS setup. Client systems that are upgraded from LTSB 2015 to LTSB 2016 seem retain their ability to activate, but an attempt to create a new base build with LTSB 2016 fails to activate. Is their no way to obtain the correct key to continue to use our KMS without buying Server 2016 licenses.

We’ve purchased 16 cores worth of licenses to address this problem, but they only came with MAK keys. I emailed VLSC to get a “Windows Srv 2016 DataCtr/Std KMS” key so that we could activate Windows 10 Enterprise 2016 LTSB using our windows server 2012R2 server as the host and I got this reply: “Daniel, I will not be able to provide you a Windows Srv 2016 DataCtr/Std KMS because your license (OLP id removed) is only entitled for the Windows Server 2012 R2 version.

You may verify this information in the VLSC under Licenses >Relationship Summary where you will find your license details.” Are we screwed over? Hi All, I’m a little vexed with our KMS server as it stands. Brand new Server 2016 build in a new 2016 domain with all windows updates installed etc We are using DNS not active directory to publish. I have managed to activate the OS and desktops are able to activate with this server. So i know it will work when it is activated. However, i cannot get office 2016 pro plus to activate on this server.

I am getting the error “kms indicates two revision levels are incompatible”. This error occurs if i use the GUI or slmgr and which ever activate mode ether telephone or online. I have installed the office pack from VLSC and get the same error. I am 100% sure i am using the correct licence key.

If anyone can help it would be much appreachated. Kind regards, David. Hello Erick, There is an update mentioning SRV2008R2 and KMS-Server. This was relased late in november. FILE: Windows6.1-KB3079821-x64.msu Greeting Switzerland/Therwil This update extends KMS for Windows 7 Service Pack 1 (SP1) and Windows Server 2008 R2 SP1 to enable the activation of Windows 10-based clients. Autodesk Revit 2014 Keygen Xforce 2016 on this page.

Note This hotfix is the prerequisite to enable Windows 10 client KMS activations on a Windows 7 or Windows Server 2008 R2 KMS host. After you install this hotfix, the Windows 10 host key (CSVLK) can be installed and activated on the Windows 7 KMS host, and the “Windows Srv 2012R2 Data Ctr/Std KMS for Windows 10” host key (CSVLK) can be installed and activated on the Windows Server 2008 R2 KMS host. We have installed a new Windows Server 2016 KMS Server and I have been successful in activating Windows Server 2016, Office 2010 and Office 2016. Free Download Program Waldorf Lector Vocoder Rapidshare Downloads.

However, when I am using Windows 7 and 10, KMS Keys to activate, then it is giving me the below error: Error: 0xC004F050 The Software Licensing Service reported that the product key is invalid I have verified with my Licensing guys and in the VLSC Portal, the Keys used seems to be of KMS only. Any help to resolve this should be helpful. Thanks in advance.