Archive for the ‘licensing’ Tag

Use a KMS outside of the domain

Tuesday, May 10th, 2016

I had an issue where we needed a small domain to register it’s Windows 2012 virtual machines to the main KMS of the company.

The problem was the small domain had it’s own IP range and it’s own DNS. I attempted to activate the virtual machines and received a message reporting the KMS was not resolvable in DNS.

Since this was a tiny domain and the DNS would not be managed, I needed another way to activate the virtual machines.

Looking at the options of the slmgr script, I found what I needed.

slmgr.vbs /skms <ip address>:<port number>

This tells the system where to look for the KMS and what port to use.

After the “OK” message, I simply attempted activation via:

slmgr.vbs /ato

The virtual machines activated.

 

 

What type of windows licesense do I have?

Saturday, September 5th, 2015

Any reasonable sized Windows development shop will find itself using both Volume Licensed and MSDN software. Due to the nature of the MSDN licensing; sometimes you have to verify the licenses. The question asked is “How do you tell the difference?”

In my particular instance, a simple command will give you information to make the distinction.

slmgr /dli

(use CTRL + C to copy output from the resulting window)

---------------------------
Windows Script Host
---------------------------
Name: Windows(R), Enterprise edition
Description: Windows(R) Operating System, VOLUME_KMS_W10 channel
Partial Product Key: *snip*
License Status: Licensed
*snip*

If you notice where it displayed “channel” you will see the word “VOLUME”

This particular install uses a volume license.

The following was taken from a test server:

---------------------------
Windows Script Host
---------------------------
Name: Windows Server(R), ServerStandard edition
Description: Windows Operating System - Windows Server(R), VOLUME_KMSCLIENT channel
Partial Product Key: *snip*
License Status: Licensed
Volume activation expiration: 249240 minute(s) (173 day(s))

Key Management Service client information
 Client Machine ID (CMID): *snip*
 KMS machine name from DNS: *snip*
 KMS machine extended PID: *snip*
 Activation interval: 120 minutes
 Renewal interval: 10080 minutes
 KMS host caching is enabled

Another volume license.

In time I will update this with output from an OEM, Retail, and MSDN.

Add a new product key to Windows 8 or Server 2012

Friday, March 15th, 2013

I had a request to add a purchased product key to a server running a trial version of server 2012.  We are still learning the new layout so of course the question was how?

A quick check found we could change it via a GUI.  There is the command line; but, I wanted to use the GUI.

To change the license simply enter:

slui 3

This will bring up the following window:

activation

Simply cut and paste the new license, click Activate and the change will happen.