KACE Product Support

For KMS you’ll enter one of the keys on this list, not your own. Yours goes only on your KMS server.
KMS Keys: http://technet.microsoft.com/en-us/library/ff793409.aspx

For MAK Keys you’ll need to leave your key out of the scripted install and select the OS you wish to install (rather than autoselect using key). You’ll need to create post install tasks to handle the key input and activation.
MAK Keys: http://blogs.technet.com/b/deploymentguys/archive/2009/03/30/deploying-windows-7-vl-with-mak-multiple-access-keys-using-mdt-2010.aspx

Postinstall tasks will be BAT script items and will have the following commands (I often separate them into 2 tasks):




Task Name:

Configure Client using VL MAK


Command Line:

cscript.exe c:\windows\system32\slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX





Task Name:

Activate the machine using the VL MAK


Command Line:

cscript.exe c:\windows\system32\slmgr.vbs /ato

Check your unattended.xml file for two product key entries. If you have one in <settings pass="windowsPE"> and one in <settings pass="specialize">, try removing the one in the <settings pass="windowsPE"> section. Check this post out.

Here is a link to KMS keys on the technet website.
[link]http://technet.microsoft.com/en-us/library/ff793421.aspx[/link]
These work every time!

Then to cserrins point, come back and apply your keys with a post install task.

We have been using Win 7 scripted installs without entering a key, although we have to select Win 7 enterprise for which version of the OS to install in the unattend wizard. It connects to our KMS with no problems. Machines on our network can use DNS to find the KMS server address. Don't have to run slmgr.vbs at all.

Yeah, if you're using the volume license media you don't need to put in a key for kms with sysprep. In fact, you want to use the stock volume license key so that someone that steals a machine can't get your kms/mak key.