Tag Info

Hot answers tagged

22

Assuming that you are in an Active Directory domain environment with at least 25 computers on-site (or on your reliable, mission-critical WAN or VPN) running any combination of Server 2008, Server 2008 R2, Windows Vista, and Windows 7, you will want to use KMS. Detailed pros/cons: MAK: Pro: When you activate a product with a MAK key, it is activated ...


5

As it turns out, the version of the KMS software included with Server 2008 is version 1.1. In order to use Windows 7 and Server 2008 R2 KMS keys, you need to be running KMS 1.2. KMS 1.2 is included as part of Windows 7 and Server 2008 R2, but requires a separate download to run on Server 2008 (non-R2) or Server 2003. I found the answer and more info on ...


5

Well, lets jsut say ignoring documentation is never wise, and you did so. Your images should be sysprepped and thus geneate unique identities. as they obvfiously are not - you are in trouble.


4

Self-answer: I needed to download http://www.microsoft.com/downloads/details.aspx?FamilyID=97b7b710-6831-4ce5-9ff5-fdc21fe8d965&displayLang=en - the Office 2010 KMS Host License Pack. This modifies KMS to also activate Office, as the stock KMS is not able to ;)


3

First of all, it is necessary to install KB2757817 in order to activate a Server 2012 KMS key on Windows Server 2008 R2. Second, you need to clarify whether you actually have a Server 2012 KMS key. You will not be able to install a Windows 8 KMS key on a server, period. However, server KMS keys typically can activate client operating systems. For example: ...


3

http://blogs.technet.com/b/odsupport/archive/2013/10/17/unable-to-kms-activate-office-running-on-windows-8-1-or-windows-server-2012-r2.aspx Installing the Hotfix from KB2885698 worked for me. Do give it a try.


3

KMS is by design stateless. The documents stated pretty clearly that there is no reporting capabilities, which means you're on your own for making one. You're already doing everything you can. The next step is to make a long term archive of event-logs so you can get longer timescales beyond what the server running KMS keeps.


3

It's not a big deal. Licensing is such a tiny application, and the attack surface is a single port on a service I've never seen a vulnerability for (though you may want to double-check on that). If you can, go ahead and make sure it's 2008 R2 so that Office 2010 KMS/volume licensing is supported.


3

The Volume Activation Management Tool v3.1 has been released and it now includes several reports including how many clients of each type (MAK, KMS) have been activated. You can read an overview of the tool on TechNet at http://technet.microsoft.com/en-us/library/hh824953.aspx


2

You say the CMIDs should be fine, but you haven't actually verified them. You need to find out whether all of the machines really do have unique CMIDs or not. The KB article tells you to run slmgr.vbs -dli on the clients. And you say the output wasn't displaying the CMID. Did you actually run the command on the client workstations? Or did you ...


2

My wish is for 1 server to handle all the KMS licenses, is it possible? Yes, but remember to backup/plan for replacing it. KMS is a separate download (e.g. here for Server 2008). The download pages contain technet links (and technet search gives a lot of links as well).


2

Computers activated with a KMS must check-in with the KMS once ever 180 days. If the computer isn't going to be able to communicate with the KMS (if it's, say, an off-site employee w/ no access to the LAN) then a KMS activation probably isn't the way to go. After a MAK activation, no further communication with Microsoft is required. This makes it work well ...


2

Honestly, KMS is the most convenient way to license large number of computer, but the buck stops right there. You can pull statistics from it using cscript slmgr.vbs /dli; but the licensed count will never exceed twice the minimum to activate a particular license (ie Win 7 takes 25 to activate, so the count will never go over 50). It doesn't keep track of ...


2

I would check for : -if there is a connection over to KMS server (1688 TCP ) -if the computer sees the network as a domain . -if you have a logged atempt to activate that 2013 Office . If that doesn't help I would take a look at http://technet.microsoft.com/en-us/library/ee939272.aspx - KMS troubleshooting .


2

Looking at your screen shot shows the line "Windows Server(R), VOLUME_KMSCLIENT channel" which seems to indicate your 2008 R2 KMS host was activated using a KMS client or MAK key. This means you cannot use this host to activate windows 7 clients. Find your 2008 R2 KMS key from the microsoft licensing site and remove the current key and use the 2008 R2 KMS ...


2

Well according to Microsoft this is completely normal and the machines will end up in "Licensed" when the Grace period of 30 days is up. Got to say I'm a little suspicious about that, but I have to take their word for it. I'll update this post again in a few weeks if that does not turn out to be the case. UPDATE: I can now confirm that the machines have ...


2

If my Google-fu is correct, it unfortunately looks like you can't do this. Paraphrasing the TechNet post: You can't install the Windows 8 KMS host Product Key for Windows on Windows Server 2008 R2. You can only install the Windows 8 KMS host Product Key on a Windows client operating system (i.e., Windows 7 or Windows 8). If your KMS host is a ...


2

My understanding is that you're way off. KMS keys are not 'linked' to a MAK key; they do not have an 'activation total'. Any KMS server key will activate any number of clients, given the normal minimum requirements are met to trigger KMS to start activating client requests. All you should need to do is switch your clients from MAK keys to the default KMS ...


1

When the grace period expires, Windows typically will reboot every hour until activated. The grace period it would seem is 30 days (which can be re-armed). See below. There is an article here: http://technet.microsoft.com/en-us/library/hh831612.aspx but it doesn't explicitly say what will happen, just says "The computers running Windows Server 2012 must ...


1

You can use KMS on a Server 2008 (non-R2) server to license up-level versions, you just need to update the KMS server. (And also update your OS from SP1 to SP2.) Here is the update: http://support.microsoft.com/kb/2757817/en-us This update extends the Key Management Service (KMS) for Windows Vista, for Windows Server 2008, for Windows 7, and for ...


1

The CMID of the workstation needs to be unique. As TomTom pointed out, sysprep is the way to go and is a requirement regardless of your imaging process, otherwise the operating system is unsupported by Microsoft. Sysprep does way more than just change your sid or cmid. Scott McArthur who is a Senior Support Escalation Engineer at Microsoft wrote a blog that ...


1

http://social.technet.microsoft.com/Forums/en-IE/winservergen/thread/476639f4-b8ac-44fa-bc8c-f8adea542bf8 Looks like you won't activating Windows 8 or Windows Server 2012 against a 2003 KMS host.


1

KMS activation is the default for non-retail versions of Windows 7. It will be searching DNS for a KMS server and not finding anything, hence the error. If you have a MAK key, you have two options: Manually enter the MAK on each machine that you want to activate (use the 'Change Product key' link in the System Properties page. Download the VAMT and host ...


1

Am I wrong ? yes and no. You need a 2008 R2 KMS key to activate KMS, but what KMS can activate depends on the class of the key. http://www.itechtalk.com/thread439.html There is a KMS key that allows KMS to ONLY activate Windows 7 and no other WIndows Servers.


1

The KMs service activates anybody that asks for activation from vista on up. In order for your server to activate computers, you must have at least 5 Servers checked in for server activation to occur or 25 Windows 7 or Vista machines checked in for client activation to occur.


1

I've done exactly this. As Hyppy said, it's a very low impact application as all it is doing is passing data through. Do be careful of KMS versions, though as there is some variation. I ended up running one on 2003 and another on 2008R2 because of what they each were able to license.


1

You REALLY need to read the documentation. The thing I can't find clearly explained is whether or not I should be adding Win 7 licenses to the KMS server in some way? Your key is a Windows Server 2008 Std/Ent KMS B key, which means it will activate everything that is livenced with a KMS B key. Check ...


1

You are correct in that you need 25 machines before the KMS server will work. But this 25 includes Windows 2008 and Windows 2008 R2 servers as well. You can use your MAK key, but after a certain number of activations (it will show you how many on the licensing site) it won't activate automatically any more and you'll have to call in to activate those ...


1

According to the Office 2010 Resource Kit documentation (link) it is supposed to be 180 days as well: All KMS clients must connect to the KMS host at least one time every 180 days to reactivate.


1

You can also pull your KMS logs on the KMS host, comma delimited parse them, and sort by CMID. If you see a bunch of servers with the same CMID then you will know if your install/setup is going correctly.



Only top voted, non community-wiki answers of a minimum length are eligible