[mdt] Product Key Question

[Chuckster]

I've finally managed to get an EES agreement. I have set up a KMS server and installed the key for 'Windows 2012 R2 for Windows 10'.

 

Now, when it comes to deploying Windows 10 do I need to install a product key or do I simply leave it blank?

 

 

 

If it's the former, do I specify a KMS client key as such from here: https://technet.microsoft.com/en-us/library/jj612867(v=ws.11).aspx

Edited June 22, 2016 by Chuckster

[Steve21]

You need to use the KMS client key for Windows, so it looks at the KMS etc as you said above that link

 

Steve

[ChrisH]

It should automatically be in KMS mode for the client if you leave the setting as you have it. Assuming your KMS server is set up correctly it should activate.

[sparkeh]

Leave as is and as long as KMS is working and you meet the minimum count for Win 10 activation (25) you should be fine. Edited June 22, 2016 by sparkeh

[Geoff]

When I sorted out my Win10 LTS image I just left the key blank. On the deployment task I actually hide that screen so you never see it. The machines I've imaged pick up the KMS and activate fine.

[sted]

DONT put your kms key there unless you want every pc you deploy to be a kms server (and you don't)

 

ive found on some laptops I had to put the generic windows 10 key in or they wouldn't activate afterwards until I did it manually (again no big deal but may as well add it in the task sequence to start with)

[FN-GM]

I leave my Windows 7 & 10 enterprise installs without a key. They then activate via KMS automatically.