just copy it from setlocal until the goto:loop line. The only thing that needs to be changed is the yourkmshost, which should be replaced by the ip or FQDN of your kms host. Then simply run this in a Windows 7 Enterprise client, (as administrator) and enter the number of activations required.
Number of activation required should be entered "set /p X=how many time do you want to run" here right?
No, you only change the kmshost, save the file as a batch file, run it (as admin), once you run it, it will prompt for the number, just enter 25 (or whichever number you require).
^ yep, that is the site I got it from, allthough I made a small change to the original. That small change (/skms) is needed if someone lacks the dns infrastructure to make the required srv record so that clients automatically point to the kms server.
I am trying to understand why we have to go thru so many steps to perform W8 activation. Following are my understandings of the requirements for current W8 activation. Windows 8 Requirements: We have to setup a VM because W8 does not allow use of Localhost. We have to have a 25+ count for activation requests to begin to be successful due to requirement for standard KMS server. Previous Solution for Windows 7: The original KMSEmulator performed the server side KMS using LocalHost without requiring 25 prior activation requests. Question: Once the proper KMS activation handshake has been determined, why can't the KMSemulator be upgraded to support this and run on a VM? This would avoid the 25+ activation requests and all of the token copying etc. Would this be feasible?
Cleaned up version, replace the red parts with proper values actvate.cmd Code: @ECHO OFF setLocal EnableDelayedExpansion set /p X=how many time do you want to run ? :loop set /a N+=1 if !N! gtr !X! goto :eof CLS echo Cycle number: !N! echo. taskkill /im sppsvc.exe /f echo. del C:\Windows\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform\tokens.dat /q attrib -H C:\Windows\System32\*.C7483456-A289-439d-8115-601632D005A0 del C:\Windows\System32\*.C7483456-A289-439d-8115-601632D005A0 /q cscript //nologo %systemroot%\system32\slmgr.vbs /ipk GVLKKEY cscript //nologo %systemroot%\system32\slmgr.vbs /skms kms.yourdomain.com:port cscript //nologo %systemroot%\system32\slmgr.vbs /ato goto :loop
Please keep in mind that the min. 25 client count is for Windows 8 (and windows 7 if used) while for Server 2012 that count is min. 5 Server 2012
Correct, but as I understand the leaked key is just a client key, so it won't activate any server version.
As said, the batch file will prompt, so do not change it. Just run it (as admin) and enter the number of times to run.
As I understand, we have to use VM because the backed up activation is only for the hardware in the VM. Hardware changes -> host deactivates.