Worked like a charm, I could test both our KMS servers instead of having to wait. 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). The tool will actually submit enough key-activation requests to your server that it will start the activation process. They have a neat tool that seem to take care of this problem. So what to do, well I googled it and found 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.
#Kms office 2016 count increase windows 7#
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. 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.
So you have installed a Microsoft KMS server, but it tell you that it cant serve your clients as the count is too little!?
0 kommentar(er)
