Is the Windows 7 KMS Key used at any point in OSD for the client or is the key used exclusively for the KMS Host?
I've activated a KMS Host (this is currently a Windows Server 2003 server running license service 1.2). That's set and ready to authorize our KMS computers (I realize we need at least 25 clients before it starts working).Regarding our preparation for deployment of Windows 7 Pro KMS.....I have just installed and captured a fat image that I'm about to deploy via SCCM 2007 SP2 OSD. Traditionally, we would enter a product key for Windows XP in the task sequence part. However, when I did this during a build and capture test I just completed, the build failed because I had the key entered (I guess that's a big no-no). So, I removed the key and it worked just fine. Build and Capture completed successfully. I then proceeded to set up the client with required software (i.e. "fat" image) and threw in a capture disc to grab that image and toss it up on the server. That's done.Now, I've created an operating system image through the SCCM console, a task sequence, and advertisement. In the task sequence though, I did not choose to enter the Windows 7 KMS Key. Normally with XP, I would input our volume license key here.With that out of the way, I suppose my question is should I have added the Windows 7 KMS Key in the task sequence or does entering the key even matter? Does the Windows 7 KMS key get used anywhere other than the KMS host??
December 24th, 2009 2:19am

KMS keys are used only to create KMS systems; they are not the equivalent of the legacy volume license keys (VLK). The rough equivalent of a VLK is the multiple activation key (MAK). Never use a KMS key unless you are standing up a KMS. Clients activating against a KMS -- aka KMS clients -- do not require a key. That's part of the "beauty" of the KMS scheme, you never have to enter or give out a key.To directly answer the question, don't put any key in the TS for Vista/7/2008/2008 R2 clients that will activate against your local KMS. Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
December 24th, 2009 5:17am

Hi Tyson, As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as "Answered" as the previous steps should be helpful for many similar scenarios. In addition, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks,Yog Li - MSFT
December 30th, 2009 3:13pm

Doesn't look like anyone linked him the "Volume Activation Technical Reference Guide" Technet entry. I actually came across this post as I was setting up our KMS server and was still a little confused after reading this. So here is the Technet entry about KMS: http://technet.microsoft.com/en-us/library/ee355153.aspx And if you go down to the "KMS Client setup keys": http://technet.microsoft.com/en-us/library/ee355153.aspx#EFAA Those keys are the client side key you actually enter in your build, Tyson. Like they said above only use the KMS key on the KMS server, and the appropriate client key on the client. -CD
Free Windows Admin Tool Kit Click here and download it now
March 22nd, 2010 6:02pm

Ah, this just seems to answer my question. I know the difference between KMS and MAK so that's not the issue. I was rather wondering whether to enter a key in my TS for OSD or not. I thought that every client needs the freely available KMS key to authenticate against the KMS server which in turn authenticates at Microsoft which it's own KMS-key to activated the clients. But as it seems like the only key I have to enter is the KMS key on the server itself while keeping the appropriate box "Enter the license information for installing windows" in my SCCM TS empty. Am I right so far ?
October 22nd, 2010 1:18pm

You can enter the common KMS client key in the TS but this isn't required because Windows 7 will use this key by default. If you open pid.txt on the Windows 7 source media (I think it's in the sources directory), you will see the common KMS client key.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
October 22nd, 2010 5:30pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics