At the time of this post, Server 2016 does not support running the Volume Activated Services Tool. It will crash and not respond when activating at the end. Specifically, you will see the following Vmw.exe has stopped working.
Kms Activator For Office 2016
A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available. As per this Microsoft TechNet article, an VAMT installation only applies to Windows 8.1 and below To get past this and activate on Server 2016, we will install and activate the KMS host by using an elevated command prompt. First we need to install the Volume License Packs.
For this post you will only need to install the 2016 pack for what we are going to do, but I have installed both Office 2013 and 2016 license packs, it doesn’t hurt. Microsoft Office 2013 Volume License Pack Microsoft Office 2016 Volume License Pack Run the license pack setup and check click here to accept the Microsoft Softw are License Terms. Click Continue.
I have my KMS Host running on Server 2008 R2 and have about 30 thin clients running Windows 7 Enterprise via Citrix. I previously had Office 2013 running on these clients. I uninstalled Office 2013 and then installed Office 2016.
I installed the KMS key into my Server 2008 R2 host. That key shows as genuine and licensed on the host. However, none of my clients are able to activate automatically. I get the error listed above if I try running cscript ospp.vbs /act on the client. I installed the Office 2016 volume licence pack as one Microsoft article suggested but it had no effect.
I use VAMT on my host server. Does anyone have any other ideas? I Googled it like crazy and tried everything I could come up with.
I even installed the hotfix that would fix cohosting of 2010 and 2013. Is it possible that the cohosting is the problem though?
Update: Problem has been solved. I created a new base vDisk, thus making a new Windows 7 OS and Office 2016 installs. This gave me the rearm counts I actually needed to reset the machine IDs and lock down the image so that when the image is deployed to the clients, Office couls activate. In addition, I discovered that there was an erroneous KMS Host entry in my DNS. I deleted that and my clients were able to contact the correct KMS Host. So everything is working fine.
Windows Server 2016 KMS – Office 2016 & Server16/Win10 KMS Recently, we found that Server 2016 standard was having issues using the volume activation tools that are built in. Instead of using the VAT role, we elected to build our KMS server through command line. In this tutorial, I will walk you through the steps necessary to complete your new KMS install using Server 2016 Standard. We are installing a KMS server for Server 2016, Windows 10, and Office 2016 Pro Plus clients. (Other versions also activate as it is backwards compatible.) Note: We are using VMware Hypervisor 6.5 (Free), and our KMS server is running as a VM using Windows Server 2016 Standard (with desktop experience). Screen capture images can be browsed here. Create a Windows Server 2016 Server (any edition).
Set the timezone, name (and join) your server with your Active Directory. Enable Remote Desktop and set a static IP address (optional). Check for, and install, all windows updates. Reboot the server.
Install the Volume Activation Services Role through the server manager. Click next through the entire process leaving the defaults. (This GUI is what crashes for us, which is why we are using command line.).
Reboot the server once the installation completes. Visit the Microsoft Volume Licensing Center and obtain your KMS keys for Office 2016 and Server 2016. Keep these for future reference. While on the volume site, download “Office Professional Plus 2016 Key Management Service Host”. It will be an ISO file. Extract the ISO to C: kms or an appropriate location.
Microsoft Office
Use an elevated command prompt for all of the following steps. Install the Office 2016 KMS Host pack (What we extracted to C: kms). cd c: kms. cscript kmshost.vbs. After the VAT popup appears, close VAT and hit enter twice to return to a standard command line.
Install the KMS keys for Windows and Office, one at a time, waiting for the confirmation that the key has been installed prior to continuing to the next. slmgr.vbs -ipk.
slmgr.vbs -ipk. Export the licensing information. This is for two reasons. First, to make sure both keys have been inserted correctly, and to obtain the activation ID. cd c: windows system32. cscript slmgr.vbs -dlv all C: kms export.txt.
cscript must be used to export the information into a txt file. Open the recently created export.txt file, and scroll to the licensed products. Copy the Activation ID‘s for both products and keep for the next step.
NOTE: The Activation ID and Application ID are NOT the same, so make sure you obtain the correct ID. The easiest way to find the correct product is to locate the Installation ID. It will only be present on the two products that we have installed a key on (even though we will not be using the Installation ID.). Activate your product keys. Do each command one at a time, waiting for the confirmation before moving to the next. slmgr.vbs -ato. slmgr.vbs -ato.
Confirm that your products are activated and licensed. cscript slmgr.vbs -dlv all C: kms export2.txt. Confirm that the two products identified before have “licensed” as their licensing status. Now your server is licensing clients. There are thresholds that will determine when activation starts.
Code it right keygenguru. Windows Server will activate after a count of 5. Windows 10 will activate after a count of 25. Office 2016 will activate after a count of 5.
Additional Information about KMS: A Server 2016 KMS key will activate all server editions up to 2016. It will also activate all Windows Client editions up to Windows 10 including 7, 8 and 8.1. The Office 2016 Professional Plus key will activate both Pro Plus and Standard Office 2016 installations. Post navigation.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |