So you have installed a Microsoft KMS server, but it tell you that it cant serve your clients as the count is too little!?

See the thing is that Microsoft has decided, that in order to make a KMS server only work for corporations, a KMS server need to recieve a certain number of activation requests before starting to issue licenses.  The idea is (from my understanding) that if some home user got his/her hands on a KMS server key he/she could not make the KMS server work as he/she did not have 25 machines (25 being the number of Windows 7 requests needed to jumpstart the KMS server for Winows 7), and hence a KMS server would only work for companies.

Well, in a perfect world (like the one Microsoft dream up) you would just wait, and eventually the count on your KMS servers would go up and the KMS would start activating clients – however if you like us have 2 kms servers and want to be sure both are working, well the wait approac was not my first choise as I would then need to revisit the process later to check up on it.

So what to do, well I googled it and found;

They have a neat tool that seem to take care of this problem. (Mirrored file)

The tool will actually submit enough key-activation requests to your server that it will start the activation process.

Now a cautious person may thing uhhh do I want to run some third party tool on my KMS server, hmm I would not – so I ofcause ran the tool on a non-admin workstation after checking on (it had a few hits on VirusTotal but I would expect this from a tool like this and no direct links to any know malware was found, so I my stomack said ok as long as it was run on a test machine as a non-admin).






Worked like a charm, I could test both our KMS servers instead of having to wait.

Furthermore, check this site for some valuable debugging tips;

Alternate solution (Script);

I afterwards found a different approach, a script that does more or less the same – quite clever if it works (I did not test this), but I dont see why it should not..

Script below;

In the place where you run the script place two empty files;



— <SCRIPT – You need to modify it so it reflects your KMS server and the directory run in> —

@echo off
for %%i in (. . . . . . . . . . . . . . . . . . . . . . . . . .) do call :Act %skms%
slmgr /ato
sc stop sppsvc
goto :end
sc stop sppsvc
xcopy “7B296FB0-376B-497e-B012-9C450E1B7327-5P-0.C7483456-A289-439d-8115-601632D005A0” “%systemroot%\system32\*” /H /R /K /Y
xcopy “7B296FB0-376B-497e-B012-9C450E1B7327-5P-1.C7483456-A289-439d-8115-601632D005A0” “%systemroot%\system32\*” /H /R /K /Y
sc start sppsvc
cscript.exe “%systemroot%\system32\slmgr.vbs” /skms %1
cscript.exe “%systemroot%\system32\slmgr.vbs” /ipk FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4
cscript.exe “%systemroot%\system32\slmgr.vbs” /ato
sc stop sppsvc