Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have recently installed a KMS Server in our domain and deployed 75 new Windows 7 machines using an image I made using Acronis True Image. There are 2 variations of this image rolled out currently.
When I go to activate the machines it returns that the KMS count is not sufficient.
On the server with a slmgr /dlv it shows:

Key Management Service is enabled on this machine.
Current count: 2
Listening on Port: 1688
DNS publishing enabled
KMS Priority: Normal

KMS cumulative requests received from clients: 366
Failed requests received: 2
Requests with License status unlicensed: 0
Requests with License status licensed: 0
Requests with License status Initial Grace period: 1
Requests with License statusLicense expired or hardware out of tolerance: 0
Requests with License status Non genuine grace period: 0
Requests with License status Notification: 363

Is it to do with the fact that I've used the same image for all the PC's? If so how do I get round this. Would changing the SID help?

OK knowing I've been thick whats the best way to rectify the situation. Can I sysprep the machines to OOBE on each individual machine? Or would NewSID work?

share|improve this question
Why the buggery did you use TrueImage and not say, WDS to get clean installs, then GPOs to install software? – Tom O'Connor Jul 22 '11 at 8:56
This may help: (Though I haven't used it since NT4.0, so it may not) – SmallClanger Jul 22 '11 at 9:02
Though, now that I read a bit more, I'm leaning towards the 'not':… – SmallClanger Jul 22 '11 at 9:31
up vote 5 down vote accepted

Well, lets jsut say ignoring documentation is never wise, and you did so. Your images should be sysprepped and thus geneate unique identities. as they obvfiously are not - you are in trouble.

share|improve this answer
OK knowing I've been thick whats the best way to rectify the situation. Can I sysprep the machines to OOBE on each individual machine? Or would NewSSID work? – Joe Taylor Jul 22 '11 at 12:34
NewSID may destroy a Vista or Win7 machine. MS has removed it from their website and pointed to an article on why it's was a bad idea from the get-go. Use sysprep. – Chris S Jul 22 '11 at 12:59
@chris S - Use Sysprep oobe? – Joe Taylor Jul 22 '11 at 13:04
@Joe Taylor, yep, SysPrep, OOBE, not Generalized, Reboot or Shutdown (doesn't matter much, though reboot would likely get things done quicker). – Chris S Jul 22 '11 at 13:07
Installed WDS and took the time to learn to do it the proper way. Its a much better way that the method I'd originally used. – Joe Taylor Oct 3 '11 at 12:27

The CMID of the workstation needs to be unique. As TomTom pointed out, sysprep is the way to go and is a requirement regardless of your imaging process, otherwise the operating system is unsupported by Microsoft. Sysprep does way more than just change your sid or cmid.

Scott McArthur who is a Senior Support Escalation Engineer at Microsoft wrote a blog that goes in to detail about this exact issue here:

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.