Solved

KMS Server

Posted on 2014-01-22
4
399 Views
Last Modified: 2014-01-23
We have a lot of dekstops computers and we initially installed a MAK Key with the desktops. Now we have a KMS server we would like to use, and I was reading about the thresholds before for the KMS server will active desktops. Is there a way for force all desktops and servers to check the KMS server to for key authentication. slmgr.vbs /ato is going to be a problem to run on all the computers. can this be scripted or is there a different way?
0
Comment
Question by:timgreen7077
[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
  • 2
  • 2
4 Comments
 
LVL 2

Accepted Solution

by:
CubeOver earned 500 total points
ID: 39802023
Yes you shall need to script the following:

start slmgr.vbs -ipk <KMS client key>

Then the clients will try to reactivate automatically.
List of KMS client keys here
http://technet.microsoft.com/en-us/library/jj612867.aspx

Alternatively have a look at VAMT, this requires client and yourself to be online in order to change key. Appropriate firewall ports must also be open between VAMT and clients. Multiple selections are possible, so you can run key replacement en masse.
http://technet.microsoft.com/en-us/library/hh825141.aspx
0
 
LVL 4

Expert Comment

by:peter_field
ID: 39802054
If I understand you, you're trying to get clients to check in to push you over the activation limits. Really, the load placed on the KMS host by a client activating is minimal, and the limits are low. I'd manually activate the 10 or so clients that you need to get over the limit. This isn't something you need to do on an ongoing basis.
0
 
LVL 2

Expert Comment

by:CubeOver
ID: 39802069
Peter, I think the Author wants to move away from MAKs to KMS activation, but the clients that are already MAK-activated are needed to form quota of 25 Windows 7 machines required for  KMS host activation. E.g. he has less than 25 un-activated machines, but with those that are already MAK-activated, he will get over the threshold.

Hence he needs to install his unique KMS host key on one of domain members that have Internet access, publish it in DNS, and then remove specific MAK keys from clients and replace them with generic ones. I do not think the /ato command is necessary as the client will try to activate automatically anyway. Moreover, /ato on clients will do no good unless KMS host has reached the threshold, contacted MS clearinghouse and grabbed specific tokens for each of the machines. This all will happen in due time, no need to rush.

The only issue may be that MAK clients are already past the 30 day grace period.
This is why activation requires proper planning. Or just stick to the MAK keys, there is no drama unless people take machines away from the company and use them at home like after being parted with. MAK activations are typically have very high maximum count, like 5000 per key (at least on our Enterprise Select).
0
 
LVL 4

Expert Comment

by:peter_field
ID: 39802095
Thanks CubeOver.. that makes sense.

The KMS host does not request specific tokens for clients, it simply needs to check in with Microsoft with your KMS host key, and once that is ok, then clients can start attempting to activate, but will fail until the threshold is met.

Install your KMS host, activate it against Microsoft and then switch your clients over to KMS.

To switch the clients over to KMS use:
cscript c:\windows\system32\slmgr.vbs /ipk <ProductKey>

Open in new window

where the product ID is from http://technet.microsoft.com/en-us/library/jj612867.aspx. If you need to do this for all your clients, I would script it.

You can manually run /ato to quickly get your KMS host over the threshold, but as CubeOver points out, after they are converted to KMS clients, they will check in by themselves given time.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

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

A safe way to clean winsxs folder from your windows server 2008 R2 editions
I was prompted to write this article after the recent World-Wide Ransomware outbreak. For years now, System Administrators around the world have used the excuse of "Waiting a Bit" before applying Security Patch Updates. This type of reasoning to me …
To efficiently enable the rotation of USB drives for backups, storage pools need to be created. This way no matter which USB drive is installed, the backups will successfully write without any administrative intervention. Multiple USB devices need t…
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…

726 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