Licensing Questions Thread, KMS Count stuck at 5 in Technical; KMS setup on Win2k3 server and seemed to be working fine.
Office 2010 count now at 6
Win7 count was ...
21st March 2011, 04:10 PM #1
KMS Count stuck at 5
KMS setup on Win2k3 server and seemed to be working fine.
Office 2010 count now at 6
Win7 count was 5 and I'v been messing with win7 installations etc and it's been steadily rising after each rebuild etc.
However today I've done 2 or 3 re-ghosts of win7 (after sysprep) and the count on the KMS still reads 5.
I've checked the event log on the server and it is seeing the requests:
Event Type: Information
Event Source: KmsRequests
Event Category: None
Event ID: 12290
An activation request has been processed.
For more information, see Help and Support Center at Events and Errors Message Center: Basic Search.
Any ideas what might suddenly be going wrong?
I've been checking the count at the server by typing:
21st March 2011, 04:12 PM #2
I found that ghosting the machines was a bad thing for KMS unless you are using SCCM or WDS. If you are not using either of those it wont count properly.
21st March 2011, 04:28 PM #3
Why should ghosting make any difference - it's only recreating a windows 7 build that has just been sysprep'd?
Originally Posted by nephilim
Surely any mis-counting could only be attributed to a SYSPREP issue not a GHOSTING one?
21st March 2011, 04:30 PM #4
nope, its the physical ghosting. Because you are taking a machine that is already done and using that as your base. If you were to use a WDS or SCCM image where it adapts to the machine without any additional hassle it will count fine. WDS and SCCM also require sysprepping as well, so the sysprep wont have anything to do with it.
22nd March 2011, 10:43 AM #5
I thought the whole point of the sysprep operation was that it "stripped" off the build anything that made it unique - and thus ready for cloning - or ghosting
Have I misunderstood?
22nd March 2011, 10:46 AM #6
when you sysprep it still uses the unique identifier in the NIC. When you ghost (even with sysprep) it will try to put the unique identifier of the original machine
24th March 2011, 02:00 PM #7
Its not the fault of your image, its how kms works. Unlike mak activations, kms knows if a computer has been activated before and does not count it as an extra activation. Computers with KMS reactivate quite frequently with the server anyway. Image a different computer and the count will go up I'm sure.
By FN-GM in forum EduGeek.net Site Problems
Last Post: 7th April 2010, 12:59 PM
By DaveP in forum Jokes/Interweb Things
Last Post: 31st March 2010, 11:27 AM
By Ric_ in forum General EduGeek News/Announcements
Last Post: 3rd February 2010, 04:30 PM
By FN-GM in forum General Chat
Last Post: 26th July 2007, 11:59 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)