Now we have the Windows Server 2012 and Windows 8 RTM bit form our Volume License we need to get some housekeeping done. The first thing we do is setup or update our KMS Service.

Sep 1, 2015 - Recent Windows clients and servers require generic KMS Client activation keys when activating against volume KMS hosts. These setup keys. Tugilgan kunga sherlar ukamga. Apr 5, 2016 - I recently setup a Server 2012 R2 (Standard Edition) KMS server. I was able to add the product keys for numerous OSs up to Windows 8.1.

In our case it is running on Windows Server 2008 R2 so we need to do a couple of things. Install the following update: An update is available for Windows 7 and Windows Server 2008 R2 KMS hosts to support Windows 8 and Windows Server 2012 as described in. This is also the place where you can request this hotfix.

If you don’t install this hotfix registering a Windows Server 2012 KMS will throw an Error: 0xC004F050 The Software Licensing Service reported that the product key is invalid So request the hotfix and install it from an elevated command prompt. Just follow the instructions and you’ll be fine Once you’ve clicked OK the installation will start After that’s finished you will be asked to restart the server.

Just restarting the KMS service (' net stop sppsvc' and ' net start sppsvc') doesn’t suffice. Now we have that out the way we can start putting our brand new KMS key into action. Let’s take a look at what is already running: slmgr.vbs /dlv => clearly the Windows 2008 R KMS key Uninstall the current KMS key using slmgr.vbs /upk, please use an elevated command prompt Now you can install the new KMS key.

The key listed here is obviously a demo one If you run in to any issues here, restarting the KMS Service can help. Try that first. Slmgr.vbs /ipk NOPEI-AMNOT-GIVIN-GITTO-YOU!! Now activate your brandnew KMS key running slmgr.vbs /ato Show what’s up and running now by running slmgr.vbs /dlv again and as you can see we’re in business to activate all our Windows Server 2012 and Windows 8 hosts.

Life is good. Thank you for this post, but could you please help me out a bitso our KMS doesn’t go down because of my lack of understanding. I currently have a KMS running on a 2008 R2 slmgr.vbs /dlv reveals it’s a VOLUME_KMS_R2_C. It activates Win 7, Server 2008 and R2 and Office 2010. We only have Software Assurance for Windows 8, we won’t have any licenses for Server 2012.

We also won’t be migrating to Office 2013. What’s the procedure in this case. If I uninstall the VOLUME_KMS_R2_C and just enter the Win 8 KMS key that probably won’t do? Any suggestions are appreciated.

If you also need to activate servers, even if only down lever ones from W2K12, you can’t replace the KMS key with VL client one as that would only alow for client OS activation. You could set up a seperate KMS for Servers without auto discovery and take it from there. Or use MAK/VAMT for the servers you have some options here. Office 2010 KMS can always be reinstalled in a breeze (my experience) if you need to or mess things up. No much worries there. Also see and Thanks for reading and good luck! Thank you for your reply.

Such a shame I can’t just somehow add a Win8 VL key to my existing KMS. Can I set up a new KMS for Win8 only? I don’t want to deal with MAK activations. If so how do I go about doing this, so there’s no autodiscovery and having two KMS servers in one domain? Which switch is then used to activate a Win8 client to that KMS (I’ll be deploying them through MDT and can probably add a Run Command Line)? Or can this be done through GPO, so it’s pointed to the correct KMS? BTW the two links you posted are both the same.

Thanks in advance for your help. Great post, thank you. I have 2 questions though 1. On the VLSC site my organization has more than one KMS product key available. Does it matter which one I use?

Should I use the one with the same license ID as the old key that I’m replacing? After uninstalling the current key and installing the new key, will the Current Count be reset to zero?

If so, do I have to install 25+ new clients or 5+ new servers to continue activating or will the clients/servers activated with the old key help this somehow? Read the KB => The KMS key activates: •Windows Server 2008 R2 •Windows Server 2008 •Windows 8 •Windows Server 2012 •Windows 7 •Windows Vista There is no requirement to have any W2K12/Windows 8. So it doesn’t matter, you can do that update, never even install a new KMS activation key and even if you do never activate any Windows Server 2012 / Windows 8. Even if that counter is reset doens’t matter either. The moment you reach the required number it just starts counting again.There is nothing dangerous or magic about that counter bar from people’s tendency to sit around watching it count. KMS if done well is set en forget until a new OS arrives and that you just update the KMS host. Nothing to worry about and if you have Volume Licensing so Microsoft support will help you when in doubt.