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)
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?
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?
Huh?? Why not catch the exception, handle it and return to the point of exception.. or insert a WAIT? This script might work but it's very rudimentary..
Sounds like a new version of this korean "fake activator" (KJ XXXX). See no reason using such stuff. Regards
Hey im hate to burst your bubble but this is not just for server 2012, it also does windows 8 pro as i just tested it and it worked.
so i'm supposed to open cmd and run this: slmgr.vbs -ipk ok-i-guess slmgr /skms kms.dant.net.ru slmgr.vbs -ato ???