Instant Provisioned machines are unable to register with the KMS server. The machine count on the licesnse server fails to increment due to the Computer Machine ID not being unique to the management server.
When using Microsoft Sysprep or a Direct Sysprep, you are performing a Sysprep
Two methods are outlined, one using a nonactivated template and the other
using an activated template.
How to ...
• Use a Nonactivated Template Method
• Use an Activated Template Method
Use a Nonactivated Template Method
Instant Provisioning makes a copy of the template and does not run a full
Sysprep on the newly created computer. This may cause issues with the current
Microsoft licensing.
When using Microsoft Sysprep or a Direct Sysprep, you are performing a Sysprep
on the computer being provisioned, which causes a new CMID to be generated
for each new computer. Instant Provisioning makes a copy of the computer and
vWorkspace injects the computer name and other information into the image
1. Do the following on your template that has been joined to a domain:
a) Install Instant Provisioning setup.
b) Validate that the KMS server is configured for your template.
Check the registry key to see if it is populated with the KMS server.
HKLM\Software\Microsoft\WindowsNT\CurrentVersion\SoftwareProtectionPlatform
If the KMS server is not set, use the following command to set it:
SLMGR -skms <My KMS server name>
c) Verify that the KMS Server is in the registry key mentioned above.
d) Verify whether the template has already been activated by running the following in an elevated command prompt.
SLMGR /dlv
If the Windows Script Host window contains a section on Key Management Service Client information, then the KMS template has been activated.
If the template has been activated, run the following command from an elevated command prompt to deactivate it.
SLMGR /rearm
2. Stop and then disable the Software Protection Platform Service, from the services window, that is running on the template. This command prevents your template from reactivating itself.
3. Copy and paste the following script into Notepad, and save as
EnableSPPSVC.vbs.
Option Explicit
On Error Resume Next
Public Sub StartApplication(App, WindowStyle)
dim aShell
set aShell= CreateObject("WScript.Shell")
aShell.Run App,WindowStyle
set ashell=nothing
end sub
StartApplication "%SYSTEMROOT%\system32\sc.exe config sppsvc
start=delayed-auto",0
StartApplication "%SYSTEMROOT%\system32\sc.exe start sppsvc",0
on error goto 0
4. Add the script, EnableSPPSVC.vbs, to the following folder:
C:\Program Files(x86)\Quest Software\Instant Provisioning\VBScripts
This script is launched by the Instant Provisioning service when the new VM first starts, enabling the Software Protection Platform Service to activate the new VM according to the KMS settings
5. Shut down the template image. You can start provisioning computers once you update the template on the vWorkspace Management Console.
Use an Activated Template Method
• VMware Linked Clones Activated Template Method
• Hyper-V and VMware Snap Clones Activated Template Method
VMware Linked Clones Activated Template Method
1. Start up the KMS-activated template.
2. Make changes to the KMS-activated template, as appropriate.
3. Create a snapshot of the changed KMS-activated template.
4. Run the following command from an elevated command prompt:
SLMGR /rearm
5. Shut down the template image.
6. Use the rearmed snapshot of the KMS template for provisioning.
If additional changes need to be made to the template, return to the snapshot that was created of the KMS template, and continue the process from step 2.
Hyper-V and VMware Snap Clones Activated Template Method
1. Start up the KMS-activated template.
2. Make changes to the KMS-activated template, as appropriate.
3. Shut down the template image.
4. Create a copy of the template by copying the template VHD and create a new template.
5. Turn the new template on.
6. Run the following command from an elevated command prompt:
SLMGR /rearm
7. Shut down.
8. From the vWorkspace Management Console, import the new template so that it can be used.
9. If additional changes need to be made, return to the original template and complete the above steps.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center