



So this just kind of takes all that out of the way.Īnd makes it so you know I haven’t even thought about or touched or even dealt with anything that had to be activated.Īnd you know in several years since I set this up at my current company. You know, connections get dropped and the server has issues because of that. Here we need KMS activation to avoid this. Then, sorry you’ve not activated anymore. If you went from 2012 R2 to 2016 and you forgot to activate the 2016 box and then suddenly you’ve been running this new system of software. Like you’re going from 2016 to 2019, or you’re doing those kinds of upgrades, and you want to make sure that you know your keys are in place. You’re transferring data from one version of the server to the new version of the server. You run it, you shut it down or you’re going through upgrades. If you need to bring up a server to do something for two or three months, you have a test project, there’s no issue right you bring it up. This just really takes all the worry and concern and things about activating out of the way. It doesn’t matter what hardware it’s on, it gets activated. So that when it launches all the settings are there You can preload these keys and stuff them into an image in VMware.

You would use this key or whatever corresponding key that you’re going to be using.įirst, you have to update the batch file that you’re going to run on that system. You’re going to use this key if you have Windows Pro on your network. This is the key that you use if you’re going to be doing the 2016 standard. So everybody in the world is going to use the same key. If you’re going to be activating a Windows Server 2019 and you have a standard server. These keys can be found on a chart that gets updated at Microsoft. In KMS Activation of Windows Servers, we use an activation key to activate a server.
