Solved

2008 R2 KMS server and how to activate 2012 R2 and 8 8.1 Clients

Posted on 2014-12-23
6
329 Views
Last Modified: 2014-12-31
We are currently running a server 2008 R2 KMS server that is being used to activate our Windows 7 and Server 2008/2008 R2 devices.

We are beginning to deploy more 2012 R2 servers and would like to use KMS to activate these as well. I have been doing a little bit of research online and it looks like we need to install a hotfix so 2008 R2 can activate new OS's.

http://support.microsoft.com/kb/2885698

After I install the hotfix is it as simple a task as running the

SLMGR.VBS /ipk {new 2012 R2 datacenter KMS host key}

From what I have seen it looks like the new KMS keys will work to activate down level clients. I just want to make sure this is the case before I replace the current key and mess up 2500 laptops and servers.

Thanks
0
Comment
Question by:Joseph Daly
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 2
6 Comments
 
LVL 58

Expert Comment

by:Cliff Galiher
ID: 40515314
Keep in mind that KMS has minimum counts before it'll activate machines. 8 clients is below that 25 minimum. If you are introducing 2012 R2 as a DC, I'd recommend using AD activation instead. AD activation doesn't activate older servers and clients, but your existing KMS server can continue to do that, and AD activation will handle the new servers and clients. It doesn't require an activation service like KMS, and doesn't have minimum counts before it'll activate either. This is the preferred activation method from Microsoft moving forward. In fact, you won't normally even see KMS keys in VLSC anymore. That requires sending a special request to get them.
0
 
LVL 35

Author Comment

by:Joseph Daly
ID: 40519753
We are still on 2008 r2 Dcs so as activation probably isn't an option until further down the line.

Still looking for the proper steps to upgrade kms for 2012.
0
 
LVL 58

Assisted Solution

by:Cliff Galiher
Cliff Galiher earned 500 total points
ID: 40519848
Install this update on your KMS server then follow the usual guidance to install and activate a new KMS key for 2012.

https://support.microsoft.com/kb/2691586
0
Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

 
LVL 58

Expert Comment

by:Cliff Galiher
ID: 40519852
As always, have a backup. I'd also use VAMT periodically for a month or two (weekly or so) to audit existing machines and make sure they are activating against the new server.
0
 
LVL 35

Author Comment

by:Joseph Daly
ID: 40522642
How would I go about using VAMT to verify this? Cant I just run slmgr.vbs /dlv and see the KMS information at the bottom of the popup box?

Ive never used VAMT before so curious to hear.

Thanks
0
 
LVL 58

Accepted Solution

by:
Cliff Galiher earned 500 total points
ID: 40522706
slmgr on the server will give you counts but not machine specifics. And running it on each client would work, but would be time consuming.  VAMT has a GUI tool that lets you scan the network and it can remotely query every machine to get its status. It'll report if it is activated, in a grace period, or out of compliance. Very handy. Since KMS clients re-activate periodically, you'll want to run that query regularly to watch for machines switching from an activated status (which they'll be in from the old KMS service) to a grace period status (if there is a problem contacting the KMS service after the change.)  Since not all machines will attempt to reactivate at the same time, and their existing activation doesn't necessarily expire at the same time you are making the change, there is a window of time where problems could go unnoticed.  Hence the reason to query regularly.  

The upshot is that even if a machine falls from activated to the grace-period window, the users will not notice an issue. It is only if the grace period is also allowed to expire that users will experience an issue. So running VAMT regularly for a month or two will let you spot problems before they impact users.  Of course ideally no problems will occur. But better safe than sorry.

While you've never used VAMT before, it is a very straightforward GUI. I don't think you'll have any issues figuring it out. Even with a large number of clients, sorting by status is simple, and the data is exportable for further refining in Excel or similar if desired. For any volume activation of size, it is a worthwhile investment in knowledge to have.
0

Featured Post

How our DevOps Teams Maximize Uptime

Our Dev teams are like yours. They’re continually cranking out code for new features/bugs fixes, testing, deploying, responding to production monitoring events and more. It’s complex. So, we thought you’d like to see what’s working for us. Read the use case whitepaper.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

What to do when Windows Update is not working correctly? What tools can I use to detect the cause of the malfunction problem? What does this numeric error code mean? These and other questions that you have been asking in the past are answered here (…
Sometimes drives fill up and we don't know why.  If you don't understand the best way to use the tools available, you may end up being stumped as to why your drive says it's not full when you have no space left!  Here's how you can find out...
This tutorial will walk an individual through the process of installing of Data Protection Manager on a server running Windows Server 2012 R2, including the prerequisites. Microsoft .Net 3.5 is required. To install this feature, go to Server Manager…
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…

730 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question