none
Converting an Image to use KMS instead of MAK - MDT RRS feed

  • Question

  • Hi

    I origionally set up a deployment share with an image configured to use a MAK key. However, Ive been advised to modify this to use an MKS server instead. Ive added a task sequence  to run the command C:\Windows\System32\slmgr.vbs -skms mskms.example.com:1688 but what else would i need to change to ensure the activation uses MKS rather than MAK? The reason I know that it is still using MAK is that I now get an error during the build process which says "The activation server reported that the Multiple Activation Key has exceeded its limit". If I change the product key and use a different MAK key then activation is succesful but I really need to change the process so the task sequence code above takes care of the activation.

    All ideas welcome!

    Tuesday, September 10, 2013 2:59 PM

Answers

All replies

  • Delete the MAK key from the Unattend.xml (if present), and make sure no rules (CustomSettings.ini) are setting it. You should not need to set the KMS Server in the Task Sequence, the client will look up he KMS Server via the DNS KMS entry.

    / Johan


    Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

    Tuesday, September 10, 2013 4:23 PM
    Moderator
  • I believe I removed the key from the xml and upon checking its definitely not there and there's nothing re: activation in the cuistomsettings.ini

    The only thing that springs to mind is that the original VM base image is activated, but i would have thought the capture/sysprep would remove all information? The process I use is to update the VM on a regular basis and use snapshots to record the image before I capture it, that works well for version control and prevents my base image from getting sysprepped as I revert back to the most recent snapshot following each capture. (Hope this makes sense).

    We have nothing set up in DNS for the KMS, would this be a requirement if its actually stipulated in the task sequence?


    • Edited by vmixture Tuesday, September 10, 2013 5:28 PM
    Tuesday, September 10, 2013 5:27 PM
  • Yes, sysprep normally "resets" the activation... And as far as KMS registration goes, by default the KMS Server tries to register the needed info in DNS, but you can absolutely run slmgr.vbs if you want to.

    / Johan


    Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

    Tuesday, September 10, 2013 8:22 PM
    Moderator
  • In your unattended file just replace the MAK Product key with the according KMS Client Key (GVLK).

    http://technet.microsoft.com/en-us/library/jj612867.aspx 

    • Marked as answer by vmixture Friday, September 13, 2013 9:43 AM
    Thursday, September 12, 2013 12:29 PM
  • I added a command to the task sequence using slmgr /ipk <setup key> which replaces the exisitng MAK with a KMS Client Setup Key ( http://technet.microsoft.com/en-us/library/ff793421.aspx ) , The used slmgr.vbs -skms kmsserver.com:1688 to manually point to the kms server (we dont have DNS set up yet) and finally slmgr.vbs /ato to activate.

    All works well.

    Thanks everyone!

    Friday, September 13, 2013 10:01 AM