I`ve updated our KMS server with the Windows Srv 2012R2 DataCtr/Std KMS for Windows 10 key from our VLSC site, and the clients have been set the KMS key in advance for Win10 enterprise.

I noticed that when doing slmgr.vbs /ato on the windows clients, they activate, but the version of Windows changes from Enterprise to Pro.

Any ideas or input would be greatly appreciated.

Thanks

If I stand up a 2012R2 KMS Server and use the Windows Srv 2012R2 DataCtr/Std KMS for Windows 10 Key all Servers Standard/DataCtr/Enteprise and Windows Workstation Windows 10 Below will be activated by this KMS Server? All the KMS Keys at Microsoft VLSC with KMS are only for if you are setting up a machine with that OS and want it to be a KMS right?

Next Question if I use 2012R2 will 2016 activate or would it be best to stand up a 2016 KMS?

The way i understand this i would need to do the following:

Stand-up 2012R2 & Use this Key Srv 2012R2 DataCtr/Std KMS for Windows 10

Add Office Keys 2010/2013/2016

And this will cover my servers and desktops... is a correct assumption?

I've set up VAMT 3 and would like to use a remote SQL database. Not difficult, however our SQL instance is clustered. This presents a new challenge, which I think I have a solution to, but to get there I need to be able to manually change the connection string that VAMT uses. I can only assume it's stored within the .MSC file some where/how.

Is this possible? Does anyone know how to achieve this change?

Cheers!

MRaybone.

Windows Srv 2012R2 DataCtr/Std KMS for Windows 10

Step 7.Test the KMS server configuration

To test the KMS server configuration, open a cmd prompt as shown below and enter

slmgr /ato

depending on whether you have less that 25 computers online or not you'll see different messages as shown below, note that in this example I'm specifying the kms host manually, you do not need to do that if DNS is working properly

(more details about that here)

cheers

niall

Related Reading

• Activating Windows 10 on Windows Server 2008 R2, Windows Server 2012 and 2012 R2 KMS hosts. - http://blogs.technet.com/b/yongrhee/archive/2015/08/05/activating-windows-10-on-windows-server-2012-and-2012-r2-kms-hosts.aspx
• Error 0xC004F015 when you try to activate Windows 10 Enterprise on a Windows Server 2012 R2 KMS host - https://support.microsoft.com/en-us/kb/3086418?sd=rss&spid=18611

https://support.microsoft.com/en-us/kb/3058168

Important Do not install a language pack after you install this update. Otherwise, the language-specific changes in the update will not be applied, and you will have to reinstall the update. For more information, see Add language packs to Windows.

This update is provided as an optional update in Windows Update. For more information about how to run Windows Update, see How to get an update through Windows Update.

The following files are available for download from the Microsoft Download Center:

Operating system Update All supported x86-based versions of Windows 8.1

Download the package now. All supported x64-based versions of Windows 8.1

Download the package now. All supported x64-based versions of Windows Server 2012 R2

Download the package now. All supported x86-based versions of Windows 8

Download the package now. All supported x64-based versions of Windows 8

Download the package now. All supported x64-based versions of Windows Server 2012

Download the package now.

Note

The update for Windows RT 8.1 or Windows RT can be obtained only from Windows Update.

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

cheers

niall

I had to rebuild our server running KMS, since the rebuild clients are not automatically activating. Pretty basic install, server OS is Windows Server Standard 2008 R2, activated using VL Windows Server 2008 R2 KMS key, enabled firewall for KMS, and checked that the DNS VLMCS record had been created.

So what is happening is that the client does not automaticall change from MAK to KMS, I have to manually run "/ipk FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4" using the microsoft KMS key to change it. Then I have to manually specify the KMS server using the "/skms" command. If I do all this and the count is 25 it will activate.

Client

 

Microsoft ® Windows Script Host Version 5.8
Copyright © Microsoft Corporation. All rights reserved.

Software licensing service version: 6.1.7601.17514

Name: Windows® 7, Professional edition
Description: Windows Operating System - Windows® 7, VOLUME_MAK channel
Activation ID: 9abf5984-9c16-46f2-ad1e-7fe15931a8dd
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 55041-00172-007-174153-03-1033-7601.0000-1542014
Installation ID: 004132561416519403578295156233172955014925186024976125
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
Partial Product Key: VJ6Y3
License Status: Licensed
Remaining Windows rearm count: 2
Trusted time: 17/03/2015 09:45:28

 

NSLOOKUP from Client

 

C:\Windows\system32>nslookup -type=srv _vlmcs._tcp.xxx.xxx.xx
Server: qehdc1.xxx.xxx.xx
Address: 192.168.111.9

_vlmcs._tcp.xxx.xxx.xx SRV service location:
priority = 0
weight = 0
port = 1688
svr hostname = qehwsus1.xxx.xxx.xx
qehwsus1.xxx.xxx.xx internet address = 192.168.111.13

 

Server

Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>cscript slmgr.vbs /dlv
Microsoft ® Windows Script Host Version 5.8
Copyright © Microsoft Corporation. All rights reserved.

Software licensing service version: 6.1.7601.17514

Name: Windows Server®, ServerStandard edition
Description: Windows Operating System - Windows Server®, VOLUME_KMS_R2_B chann
el
Activation ID: c99b641f-c4ea-4e63-bec3-5ed2ccd0f357
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 55041-00168-313-762504-03-2057-7601.0000-0752015
Installation ID: 014925801852060651446993734576005235317582513131186852
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88342
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88343
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88345
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88344
Partial Product Key: FBG9V
License Status: Licensed
Remaining Windows rearm count: 2
Trusted time: 17/03/2015 09:42:32

Key Management Service is enabled on this machine
Current count: 6
Listening on Port: 1688
DNS publishing enabled
KMS priority: Normal

Key Management Service cumulative requests received from clients
Total requests received: 29
Failed requests received: 0
Requests with License Status Unlicensed: 0
Requests with License Status Licensed: 3
Requests with License Status Initial grace period: 14
Requests with License Status License expired or Hardware out of tolerance: 0

Requests with License Status Non-genuine grace period: 0
Requests with License Status Notification: 12

I am now at a loss, any ideas where I have gone wrong?

Thanks

I'm about to setup an Active Directory environment for fout KMS Clients based on Server 2008R2. My KMS host will be also based on 2008R2. But here are my questions:

1. Does the registration key OF THE WINDOWS SERVER HOST matter? I mean i've already installed the server planned foe the kms host and also activated this OS with a mak key. As far as i understand i have to register a kms key with slmgr.vbs ,but i assume that this has nothing to do with the activation of the server where the kms service for the kms host resides ,right?

2. I've seen different "_VLMCS" DNS SRV records on my dns server from different 2008R2 in our AD. I guess this means that these systems activated their Microsoft registration with a KMS key.

This update extends the Key Management Service (KMS) for Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, and Windows Server 2012 to enable the enterprise licensing of Windows 8.1 and Windows Server 2012 R2.

KMS provides support for the following KMS client activations:

• Windows Vista
• Windows Server 2008
• Windows 7
• Windows Server 2008 R2
• Windows 8
• Windows Server 2012
• Windows 8.1
• Windows Server 2012 R2

KMS uses a KMS host key to activate itself on a KMS host and to establish a local activation service in your environment. This update extends support for KMS to provide activation for Windows 8.1 and for Windows Server 2012 R2.

The following files are available for download from the Microsoft Download Center:

Operating system Update All supported x86-based versions of Windows Vista and of Windows Server 2008

Download the package now. All supported x64-based versions of Windows Vista and of Windows Server 2008

Download the package now. All supported IA-64-based versions of Windows Server 2008

Download the package now. All supported x86-based versions of Windows 7

Download the package now. All supported x64-based versions of Windows 7

Download the package now. All supported x64-based versions of Windows Server 2008 R2

Download the package now. All supported IA-64-based versions of WindowsServer2008 R2

Download the package now. All supported x86-based versions of Windows 8

Download the package now. All supported x64-based versions of Windows 8

Download the package now. All supported x64-based versions of Windows Server 2012

Download the package now.

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

To apply this update, you must be running one of the following operating systems:

• Windows Vista Service Pack 2
• Windows Server 2008 Service Pack 2
• Windows 7 Service Pack 1
• Windows Server 2008 R2 Service Pack 1
• Windows 8
• Windows Server 2012

If you have a KMS host that is running Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, or Windows Server 2012, follow these steps to perform an upgrade:

1. Install this update (update 2885698).
2. Restart the computer when you are prompted to do so.
3. To install a new KMS host key for Windows 8.1 activation or for Windows Server 2012 R2 activation, run the following command:
   cscript %windir%\system32\slmgr.vbs /ipk <KMS host key>
   Note In this command, "<KMS host key>" is a placeholder for the new KMS host key for Windows 8.1 activation or for Windows Server 2012 R2 activation.
   
   Important Every KMS host key is associated with a group of Windows editions. Additionally, a KMS host key that is associated with Windows client operating systems cannot be installed on Windows server operating systems, and vice-versa. This is true for all Windows operating systems except for Windows Server 2003. If you install a KMS host key on a Windows operating system that is not associated with that host key, you receive the following error message:
   0xc004f015: The Software Licensing Service reported that the license is not installed.
   SL_E_PRODUCT_SKU_NOT_INSTALLED
   
   For example, you may receive this error message in the following situations:
   • You try to install a Windows 7 KMS host key (CSVLK) on a Windows Server 2008 R2 KMS host.
   • You try to install a Windows 8 KMS host key (CSVLK) on a Windows Server 2008 R2 KMS host or a Windows Server 2012 KMS host.
   • You try to install a Windows 8.1 KMS host key (CSVLK) on a Windows Server 2008 R2 KMS host or a Windows Server 2012 KMS host or a Windows Server 2012R2 KMS host.
4. To activate the new KMS host key on the host computer, run the following command:
   cscript %windir%\system32\slmgr.vbs /ato
5. On an existing Windows Vista or Windows Server 2008 KMS host, restart the service by running the following command:
   net stop slsvc && net start slsvc

Note For information about which operating systems can be activated by a Windows 8.1 or Windows Server 2012 R2 KMS host, see the "Plan for Key Management Services activation" section of the following Microsoft TechNet webpage:

To apply this update, you do not have to make any changes to the registry.

You must restart the computer after you apply this update.

This update does not replace a previously released update.

via >

I am trying to setup a KMS host on a Windows 2008R2 Workgroup server for my Windows 7 clients. This server has already been activated using a MAK key but I am now trying to run the slmgr /ipk xxxxxxxxxxxxxxxx on it but getting Error: 0xC004F015.

Can a server already activated using a MAK key then be made a KMS host using the above command with the newly given KMS key?

Thanks in advance

Pas

I've checked the WAIK and added the oobeSystem|x86_Microsoft-Windows-Shell-Setup_neutral|FirstLogonCommands|SynchronousCommand task that should activate it, but it's just not doing so.

"cscript //b c:\windows\system32\slmgr.vbs /ipk xxxx-xxxx-xxxx-xxxx"

Is it better to use a script that can be run that will activate it via the task sequence instead of WAIK?

Thanks!

Also can 1 KMS host have all these licenses put into it to host out? I see all these guides show how to add one, but most will say if you add another it will erase the first one.

at another location. Is it possible to move the server with the windows key already assigned to that particular box???

I setup a KMS server on a 2003 box for office 2010 which works fine.

I've read through a few guides on windows 7 activations also... So I went ahead and did a

slmgr -ipk [PRODUCTKEY]

but when I do a

slmgr -dlv

It's showing me unlicensed? Could it be the wrong product key ? All the updates are installed and I'm running 1.2 KMS?

Any idea? Would an idea to have a 2nd KMS server running on a 2008 box for windows 7 ?

cscript c:\Windows\System32\slmgr.vbs /ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

Obvioulsy replace xxxxx with your key.

You should see the following:

Microsoft Windows Script Host Version 5.7
Copyright Microsoft Corporation. All rights reserved.
Installed product key xxxxx-xxxxx-xxxxx-xxxxx-xxxxx successfully.

How can I activate via Telephone (offline activation)

If activation for the KMS server is necessary then call Microsoft and follow the instructions.

Open C:\Windows\system32 and execute the following command

slui.exe 4

Then

* Show me other ways to activate
* use the automated phone system

And then call Microsoft and follow the instructions. After successful activation, click on close.

Then do as follows:

net stop slsvcnet start slsvc

You should see the following:

The Software Licensing service is stopping.
The Software Licensing service was stopped successfully.

The Software Licensing service is starting.
The Software Licensing service was started successfully.

Open the Firewall for KMS traffic

In Windows Firewall, click on Exceptions and allow the now listed Key Management Services, failure to do this step will mean that your KMS hosts can not talk to the KMS service and therefore will not activate.

KMS listens on port 1688, to change the port you must do as follows:

SLMgr.vbs /SPrt xxxx

where xxxx = the new port number

After you have entered this command you must restart the SLMgr service using:

net stop slsvc
net start slsvc

Test the KMS server configuration

The KMS server should publish its SRV records in your domain DNS, you should verify that these records exist.

Open C:\Windows\system32 and execute the following command

nslookup -type=srv _vlmcs._tcp

You should see output similar to the following:

C:\Users\Niall>nslookup -type=srv _vlmcs._tcp
Server: ad1.server2008.lab.local
Address: 192.168.3.1

_vlmcs._tcp.server2008.lab.local SRV service location:
priority = 0
weight = 0
port = 1688
svr hostname = kms03.server2008.lab.local
_vlmcs._tcp.server2008.lab.local SRV service location:
priority = 0
weight = 0
port = 1688
svr hostname = kms01server2008..lab.local
kms01.server2008.lab.local internet address = 192.168.3.3
kms02.server2008.lab.local internet address = 192.168.3.4

If not, review the following link for setting up the DNS records or click on this link for troubleshooting KMS activation.

To manually activate a client over the Internet

Any client will automatically try to activate itself every 120 minutes by default, so there is no need to run the acivation command manually. However if you want to test or speed up the process then do as follows.

Open C:\Windows\system32 and execute the following command

cscript C:\Windows\system32\slmgr.vbs /ato

To change the 120 minutes setting, you must do as follows:

SLMgr.vbs /sai x

where x = the new interval in minutes

After you have entered this command you must restart the SLMgr service using:

net stop slsvcnet start slsvc

Query KMS server

To query the KMS server and see its status open a command prompt and execute the following command.

cscript slmgr.vbs /dli

You should see output similar to below:

Microsoft Windows Script Host Version 5.7
Copyright © Microsoft Corporation. All rights reserved.

Name: Windows Server ServerStandard edition
Description: Windows Operating System - Windows Server VOLUME_KMS_B channel
Partial Product Key: xxxxx
License Status: Licensed

Key Management Service is enabled on this machine
Current count: 2
Listening on Port: 1688
DNS publishing enabled
KMS priority: Normal

Key Management Service cumulative requests received from clients
Total requests received: 5
Failed requests received: 0
Requests with License Status Unlicensed: 0
Requests with License Status Licensed: 0
Requests with License Status Initial grace period: 5
Requests with License Status License expired or Hardware out of tolerance: 0

Requests with License Status Non-genuine grace period: 0
Requests with License Status Notification: 0

Microsoft Video showing KMS in action > http://www.microsoft...;DisplayLang=en



License States

A computer can be in one of 5 license states

Initial grace Period
This occurs after the computer is installed and can only last for up to 30 days, this can be reset twice.

Non-Genuine grace Period
This occurs after a computer is found to have a non-genuine or counterfeit Windows operating system installed. This state can last up to 30 days to give you time to reactivate using a genuine copy and License key.

Out-of-tolerance grace period
This can occur when either several hardware changes are made to the computer or when the KMS key has not contacted Microsoft for updates in 180 days. This state can last up to 30 days.

Licensed
This state occurs when everything is ok and the system is activated.

Unlicensed
This state occurs when the activation period has expired and nothing was done about it. The computer will stay in a limited access state until it has been activated.

Activating Workgroup Computers

To activate workgroup computers use the following two lines, replace 192.168.0.1 with the ip address of the KMS server

cscript slmgr.vbs /skms 192.168.0.1
cscript slmgr.vbs /ato

Related Reading:-

Windows 7 Specific KMS info. For Windows 7 and Windows Server 2008 R2 KMS info please refer to this post.

Key Management Services (KMS) explained - http://www.virtuall....s-kms-explained

Which Key do I use, KMS, MAK, VLK ? IF you are unsure about which key to use for activation then take a look at this post on Technet, the list of keys is printed here