VAMTKMS Office 2. Hey there folks. Also having the same issue here. I have tried to install the Office 2. KMS Host via Script. After running the script and waiting several seconds, the volume activation assistant opens. First it asks me to wether use Active Directory Activation or choose a kms host. Active Directory is not an option for me, because i am running two 2. An Office 2010 KMS host is required if you want to use KMS activation for your volume license editions of Office 2010 suites or applications, Microsoft. KMS 20161102. 20170617 1111. KB/Media/0000582/00001s.png' alt='Install Kms Host Office 2017 Professional' title='Install Kms Host Office 2017 Professional' />AD Servers and dont want to update anything ther yet. So I chose the option KMS host. I also dont have a KMS host, so I typed in the VAMT server itself and clicked next. It successfully accepts the kms host. In the next step ist wants me to install a KMS Host key. I copied the Office 2. It tells me like An error occured, solve the error and repeat the step. Description The software licensing service detected an invalid keyI did search the internet yesterday for a few hours for finding a solution to solve this problem. Every Thread I found had some good advices, but at the end it run into nothingness. Anybody having some more ideas yet Best regards,C3dy. Citrix PVS Enabling KMS licensing on a v. Disk. When streaming a Windows machine the Windows license can be managed by a Key Management System KMS. Activate your Office 2016 Professional Plus within seconds Believe it or not, KMSPico 10. Citrix describes it as follows KMS volume licensing utilizes a centralized activation server that runs in the datacenter, and servers as a local activation point opposed to having each system activate with Microsoft over the internet. To ensure KMS is working correctly the Windows machine needs to be prepared for KMS, this involves setting the right license key and re arming the license. Citrix has done a pretty good job describing different scenarios in CTX1. In this article Ill explain what steps you can take to build a PVS v. Disk where licensed are managed by KMS and how to troubleshoot some known caveats. How to prepare your image. Creating a Citrix PVS v. Disk for Windows machines that are licensed by a Key Management System KMS consists of the following eight steps 1 Create v. Disk. Build your image as you normally would install your OS, applications and apply the required configuration and upload the using the imaging wizard. Build a new image and select the Key Management Service KMS in the Microsoft Volume Licensing dialog. After the v. Disk is created and the target device is assigned to the new v. Disk reboot the machine. Boot from Network or the Boot Device Manager via ISO or VHD so the machine will mount the v. Disk in private mode. After you logon with a user with administrative privileges the files are converted from volume C to the v. Disk, in other words the content of the C drive is copied to the v. Disk on the PVS server. After the content is copied click Finish to continue to the shell. Cleanup windows activation. To start with a clean setup we can cleanup the Windows activation. Run a command prompt with elevated privileges run as administrator and issue the following commands. Net Stop Sp. PSvc. Del C WindowsService. ProfilesNetwork. ServiceApp. DataRoamingMicrosoftSoftware. Protection. Platformtokens. Net Start Sp. PSvc. Net Stop Sp. PSvc. Del. C WindowsService. ProfilesNetwork. ServiceApp. DataRoamingMicrosoftSoftware. Protection. Platformtokens. Net Start Sp. PSvc. Source How to rebuild the Tokens. Activation Tokens file in Windows 7 8. Install KMS product key  WindowsNow we need to ensure that Windows has a KMS product key instead of a OEM or VLK. From an elevated command prompt Run the Software Licensing Management Tool Sl. Mgr and install the KMS product key IPK for your Windows version. See the tables attached to this article for the KMS client key for your Windows version. Activate Windows. To verify that the license key is a KMS license key and the license can be activated by a KMS server we can test the activation. Run the Software Licensing Management Tool Sl. Mgr and activate Windows ATO. Verbose information about the licensing can be retrieved with the Software Licensing Management Tool. As you can see the License Status is Licensed. If you have any other result first troubleshoot that see Microsoft Tech. Net How to troubleshoot the Key Management Service KMS. Re arm Windows license. Since were going to distribute this v. Disk to multiple machines we need to reset it to a non activated state using the rearm command. Run the Software Licensing Management Tool Sl. Mgr and reset the licensing status of the machine Re. Arm. Do    NOT    reboot the machine. If you have exceeded the maximum of 3 allowed rearms an error message is thrown Error 0x. C0. 04. D3. 07 The maximum allowed number of re arms has been exceeded. You must re install the OS before trying to re arm again. This can be solved by setting the following registry key HKLMSOFTWAREMicrosoftWindows NTCurrent. VersionSoftware. Protection. PlatformSkip. Rearm 0x. REGDWORD. Install KMS product key OfficeIn case youve installed Microsoft Office and need to license it via KMS,  nearly the same steps are required. Run the Office Software Protection Platform Os. PP. vbs and install the product key In. PKey for your Office version. In. PKey lt Product. Key 1cscript. In. PKey lt Product. Key See the tables attached to this article for the KMS client key for your Office version. You can verify if Office generated a Client Machine ID CMID by running the Office Software Protection Platform tool with dcmid. Re arm Office license. Just like Windows, Office also needs to be to reset to a non activated state using the rearm command. Run the Office Software Protection Plafrom Rearm OSPPREARM tool from the x. C Program FilesCommon Filesmicrosoft sharedOffice. Software. Protection. PlatformOSPPREARM. EXE. C Program Files x. Common Filesmicrosoft sharedOffice. Software. Protection. PlatformOSPPREARM. EXEC Program FilesCommon Filesmicrosoft sharedOffice. Software. Protection. PlatformOSPPREARM. EXEor. C Program Filesx. Common Filesmicrosoft sharedOffice. Software. Protection. PlatformOSPPREARM. EXE8 Put v. Disk in Standard mode. Unlock v. Disk. Shut down the target device and wait until the v. Disk changes from locked 1 to unlocked 0. Set Access Mode. Open the properties of the v. Disk and set the Access Mode to Standard Image multi device, read only access and verify that Key Management Service KMS is selected at the Microsoft Volume Licensing tab. Whats important to know is that the Citrix PVS Stream Service at the moment will mount the v. Disk, execute a Kms. Prep or Kms. Reset if this has been done before and then unmount it again. Soldadinho Cristina Mel. This only happens if you change the Access Mode from Private to Standard. If the Access Mode is already in Standard and KMS is selected, the image is NOT updated. As Citrix describes in Managing Microsoft KMS Volume Licensing Note When preparing or updating a KMS configured v. Disk that will be copied or cloned, it is important to complete the final KMS configuration task, which is to change the v. Disk mode from Private Image Mode to Shared Image Mode, before copying or cloning the v. Disk to other Provisioning Servers. Also, both the. pvp and. KMS configuration of the original v. DiskError. In case the following error is thrown An unexpected MAP error occurred Failed to map v. Disk, no Driver there are two possible problem. The drivers are not installed correctly or 2 the account configured at the Streaming service had insufficient privileges. Drivers are not installed correctly. The first problem is easy to detect and solve. Try to mount the v. Disk right click on the v. Disk Mount v. Disk from the Provisioning Services Console on the PVS server. If that does not work the drivers are not correctly installed. Go to C Program FilesCitrixProvisioning Servicesdrivers, right click on cfsdep. Install. 2 Insufficient privileges. If youre able to mount the v. Disk from the Provisioning Service Console then the Citrix PVS Stream Service has insufficient privileges. The account configured to run the Citrix PVS Stream Service needs to have the Perform volume maintenance tasks SEMANAGEVOLUMENAME privilege. The reason this privileges is required is because the Citrix PVS Stream service need to mount the v. Disk in order to execute the Kms. Prep Kms. Reset. See CTX1. By default only the local Administrators group has the SEMANAGECOLUMENAME privilege assigned. The problem can be solved by making the AD account, or NETWORK SERVICE when log on as Local System account is used, member of the local Administrators group.