Windows 8 KMS Activation

I mean to say when you have to attain count up to 25 to start activating clients(First time), use script with rem
For later use or once a day, remove rem.

Hope its clear now....

 

You could simply remove the line and paste it below the :Loop bit and then remove the rem, this way it will simply start the service once instead of multiple times. Why anyone would run the script daily is beyond me, surely ony running it at the moment you need to re-active the os again (after 180 days) would be more than sufficient.

 

You need to login to view this posts content.

 

Normally no, but then again, normally someone running a kms server does not need a script to maintain the count, as they would have at least 25 clients, either servers or workstations. In this case we are talking about people at home, who might have only a few machines, in which case maintaining the count does not make sense.

 

Replying again coz i found that system stooping SPPSVC service itself & kicks it again when required. So not to worry if its stopped.
You can check it by starting this service & recheck after some time.

 

weather you have few or 1000 machines. you have to maintain count else after 30 days count will starts dropping below threshold of 25.

Its up to you change it the way it works best for you. FYI most of time taskkill /im sppsvc.exe /f don't work but using it just for safer side. I am using net stop sppsvc /y three times in script coz sometime service don't stop with single attempt.

 

So each time this script runs, it makes the KMS server thinks it is a new PC? If so that is a very nice find but if someone could explain how it does this as I want to learn how it does

 

You can learn it manually.
Stop service sppsvc
Go to C:\Windows\System32\spp\store & delete files
go to C:\Windows\System32\spp\store\cache & delete files
Start service
Run command prompt run slmgr /dlv & check PC info under Settings for activation.

Compare result & congratulations you learned that what script is doing?

Its deleting Key & PC ID used for activation. Don't ask me why not to use slmgr /upk

 

Thank you good sir. I just tested mine and it is working 100% (changed some code to make it look like this)

Code:

REM Increment KMS to 25 so it starts activating clients 
REM save as a bat file.
REM Windows 8 Enterprise/pro inbuilt KMS Client key used in this one.
setLocal EnableDelayedExpansion
set /p X=how many time do you want to run
:loop
set /a N+=1
if !N! gtr !X! goto :netstart
echo your task goes here
taskkill /im sppsvc.exe /f
net stop sppsvc /y
net stop sppsvc /y
net stop sppsvc /y
del C:\Windows\System32\spp\store\tokens.dat /q
del C:\Windows\System32\spp\store\tokens.dat.bak /q
attrib -H C:\Windows\System32\spp\store\data.dat
del C:\Windows\System32\spp\store\data.dat /q
del C:\Windows\System32\spp\store\cache\cache.dat /q
cscript %systemroot%\system32\slmgr.vbs -ipk GVLKKEY
cscript %systemroot%\system32\slmgr.vbs /ckms
cscript %systemroot%\system32\slmgr.vbs /skms kms.yourdomain.com
cscript %systemroot%\system32\slmgr.vbs /ato
goto :loop
:netstart
net start sppsvc /y

 

Actually it does not matter the count dropping under 25, as the script will bring it up to 25 in one run through. I am using a kms with server 2012 key for two months now, and I only bring it up when needed and then simply run the script to get it up to 25 again.

 

You need to login to view this posts content.

 

I like to be able to activate every system out of the box, as i have a Hyper-V server running 24/7 it is much easier for me to run one client VM daily (completely automatic) on that same Hyper-V server that maintains the client count on the KMS Host then to have to manually push the client count whenever I attach a new system to the network

 

You need to login to view this posts content.

 

Sure, if you have hyper-v running 24/7 anyway, it does make sense to sacrifice 256 MB of ram for a kms host on my 24/7 server that is not possible anymore without shutting down other vm's that offer "more critical" services.

I simply use it on my desktop machine, which does have 24 GB, but that one I shut down each day, otherwise my electricity bill might be through the roof Then again, I usually just use retail keys from msdn, I use kms just for temporary servers and workstations that I delete after a while anyway, no reason to waste a retail key for them.

 

If you have limited RAM that could be a issue, but if you have plenty it is a no brainer

Addendum to my previous post, i can control when and how i install my own PC's, but if you have a KMS (like me) up for family and close friends you never know when they will try to contact the KMS host. (Windows Server 2012 C channel, Office 2010)

 

You need to login to view this posts content.

 

So all you need is a single client trying to activate daily and the count never drops below 25? Would just lowering the refresh interval using slmgr /sri on your day-to-day workstation be enough?

 

You need to login to view this posts content.

 

Still having problems with connecting to my KMS from outside my network. I have setup no-ip and it is updating it when needed. I have opened the port on my router to the port I am using (65000). I also have turned off all firewalls everywhere. I am able to access the net and local PCs from the KMS and vice versa. So is there anything I am missing?

 

You need to login to view this posts content.