Set up New KMS Server (2012) for Windows 7 Clients?

[JRA]

Hi all - I'm sorry if this one turns out painful. I'm totally lost at this point.

 

The LA used to allow us to use their KMS servers, but this has now been turned off. Consequently, my newly-imaged machines are not authenticating.

 

I've been following THIS guide, but when it comes to entering a key, what key do I need from the VLSC? Next guide I've read HERE says "Look for a key called “Windows Srv 2016 DataCtr/Std KMS” but I don't want to install it on a 2016 server.

 

Urgh, what am I doing??

 

Thanks anyone for anything!

[DJ-1701]

If you have already licensed the servers with a MAK key it shouldn't try and use a KMS key.

The key mentioned basically authenticates Windows Server 2016 and below using KMS, including client versions (Windows 7, Windows 8, Windows 10).

 

You can always contact VLSC to ask for a KMS key for Windows 7 specifically which would show up on Keys and Downloads, but this can take some time.

[JRA]

Thanks for that! It's the clients rather than the servers tbh; I'm worried the whole network will suddenly tell people Windows isn't genuine. They've previously been on an LA KMS server, but that's now off and so I need to set up my own one. Just another little corner of this network I've discovered here...

 

So, if I enter that key at the relevant part of the setup instructions and proceed, will all be ok?

 

Thanks again!

[DJ-1701]

For new kit, it should be fine. It might take a little while for some of the existing kit to see your new server as the KMS host but they will switch over, in rare occasions sometimes they don't like switching servers, but you can use slmgr.vbs to point them to right server if they ever say they are no longer activated.

 

https://www.howtogeek.com/245445/how-to-use-slmgr-to-change-remove-or-extend-your-windows-license/

 

If you were using Windows 8 and above, I would suggest using ADBA (Active Directory Based Activation), it's so much easier. Add to the domain and activated.