Product key in answer file with kms
-
I’m curious to know the answer to this, if you have a kms server in your environment do you have a product key in your unattend.xml file? or do you leave product key field blank or add something to the unattend.xml file to tell it to look for the KMS?
-
We always create our golden images unactivated with no key installed. When the image is deployed and then connected to AD, the workstation then looks up the KMS server in AD and registers itself.
-
@george1421 Can post a sanitized version of your unattended.xml file? I’m not sure what i should have in it to tell the workstation to find the kms server
-
@The-Dealman Here is a clean version of the unattend.xml file. But we don’t specifically put anything in the unattend.xml file that even hints about licensing. https://forums.fogproject.org/post/87392
I didn’t setup our KMS server, but I’m pretty sure there is something in AD or (most likely) DNS that points to the KMS server. From my perspective the clients just “magically” know how to find the KMS server and register. I’d ask the people who setup KMS but sadly they are no longer with the company.
If you look at this article: https://interworks.com/blog/ijahanshahi/2015/04/13/volume-activation-windows-configuring-kms-ad-roles-windows-2012-2012r2/ specifically at the graphic for configuring the volume activation tool there is a tick bock for DNS. I also know we had to enable a specific port in our off site datacenter’s firewall to allow clients off site to be able to maintain connection to the KMS server. Sorry I can’t be more help on the KMS side of imaging.
-
@george1421 Yeah it looks like by adding this to the xml file cscript /B C:\windows\system32_slmgr.vbs /ato resolved it on my machines. Thanks for the help.
