How does KMS (Windows Server 2008 R2) differentiate clients?
- by Joe Taylor
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?