Ravenfield for mac. What are KMS and MAKs? With a Volume License Agreement with Microsoft, you are normally given two types of keys: Multiple Activation Key (MAK) and Key Management Services (KMS). The MAK will normally have an activation count, while the KMS does not. Simply put, MAK is a key that registers direct back to Microsoft with a certain amount of. Aug 01, 2007 The KMS key is used only to set up the KMS box; once that is done (and at least 25 real (not virtual) Vista boxes have asked for activation) the KMS will activate any volume licensed copy that hasn't had a MAK key entered.
Jul31
Tags
Oct 04, 2016 This will force you to use the Windows Srv 2012R2 DataCtr/Std KMS for Windows 10 key from the Volume licensing site. This key is good for Windows 10 and Windows Server 2012R2. Because of this, it will likely result in meeting the minimum requirement for this key, as you probably already have 5 Windows Server 2012 R2. When this process is complete, the MAK keys for each product will be listed along with the rest of the organization's existing keys in the Volume Licensing Service Center. Product Groups for MAK and KMS Keys. Product keys for both KMS and MAK apply to product key groups rather than to individual operating system editions.
Related Posts
Share This
Microsoft licensing is one of the things that puts fear into most people who have dipped their toes into it. Understanding how to be compliant with Microsoft – and how to make sure the company’s money is being spent properly – can be daunting. From an admin’s side, this is often not a concern as it’s not a part of their job – but at least understanding the implications of installing 10 different SQL servers in the environment is a necessity. Google drive stuck uploading. One of the more fundamental models Microsoft now uses with Windows Server, Windows Client (e.g. Windows 7) and Office is using a key to register the products. So, how do you do it if you’re on a Volume Licensing Agreement?
Microsoft Licensing Kms Vs Mak
What are KMS and MAKs?
![Volume License Kms Vs Mak Key Volume License Kms Vs Mak Key](https://4sysops.com/wp-content/uploads/2014/01/Configuring-Active-Directory-Based-Activation.png)
With a Volume License Agreement with Microsoft, you are normally given two types of keys: Multiple Activation Key (MAK) and Key Management Services (KMS). The MAK will normally have an activation count, while the KMS does not. Simply put, MAK is a key that registers direct back to Microsoft with a certain amount of allowed activations. KMS on the other hand, lets all your clients use a generic key to talk back to a KMS Server on premise, and that centralised server talks back to Microsoft. The MAK side of things is pretty straight forward: you put a different key in per client, it will phone home and then either activate or fail. This works, but isn’t the way you should do things in a large environment. KMS gives you that automation.
KMS sounds great, how do I set that up?
I’ve written about this before on How To Enable Office 2013 KMS Host and How to add your KMS keys for Windows 8 and Server 2012, so I’ll just clarify how the process works. There are two types of KMS keys – client and server. The client key is normally the default key installed when using a volume license version of software, and the keys are publicly available. Here’s a list on Technet of keys. The KMS server needs to be configured as per my “How to” articles. Having a KMS Client key registered on your client will make it go through a different process of phoning home and check DNS records. The KMS server on premise gets the request, approves and activates the client. Technet as per usual has great documentation covering all of this, available here.
Microsoft Mak Vs Kms
I’ve set it up and it’s not working – help! 100 000 pyramid game app.
OK, don’t get too worried here. First, you need to have enough clients trying to register on your KMS server before it will activate any of them. For Windows Client operating systems, you’ll need 25. Yes, that’s a lot. For Windows Servers and Microsoft Office, you’ll only need 5.
For an example, let’s say you’ve installed Microsoft Visio 2013 and it’s not registered (if you’re unsure if it’s registered or not, in Visio go to File > Account. On the right hand side it will tell you if the product is activated or not). Icom programming software for mac. Start by checking that you have a correct KMS key entered – you can re-enter it in the product.
You can force the activation of Office 2013 by going to the folder where it’s installed (by default it’s C:Program Files (x86)Microsoft OfficeOffice15) and running the command:
cscript OSPP.VBS /act
This will either tell you that you’ve successfully activated your product, or give an error. One of the most common errors is:
ERROR CODE: 0xC004F038
ERROR DESCRIPTION: The Software Licensing Service reported that the product could not be activated. The count reported by your Key Management Service (KMS) is insufficient. Please contact your system administrator.
ERROR DESCRIPTION: The Software Licensing Service reported that the product could not be activated. The count reported by your Key Management Service (KMS) is insufficient. Please contact your system administrator.
Nice description. So, next up you’ll need to check your count reported on the KMS server. Forgot what server your KMS server is? You might be able to find out by using the command:
slmgr /dlv
which will give you an informative window telling you the KMS machine name from DNS. Or you can check your DNS for the entry from the DNS console under DNS Server > Forward Lookup Zones > internal domain name > _tcp > _VLMCS record.
On your KMS server, you can display the client count so far, to see if it’s hit the magic 5 with this command:
Free casino slots online for fun. cscript slmgr.vbs /dlv 2E28138A-847F-42BC-9752-61B03FFF33CD
The string on the end is the Office 2013 Activation ID. For Office 2010 it’s “bfe7a195-4f8f-4f0b-a622-cf13c7d16864”.You’ll see a lot of information, but the important part is this:
Key Management Service is enabled on this machine
Current count: 5
Listening on Port: 1688
DNS publishing enabled
KMS priority: Normal
Current count: 5
Listening on Port: 1688
DNS publishing enabled
KMS priority: Normal
In this example, I’ve just hit the 5 so clients will now activate. If it was less than 5, I’d still be getting the previous error on the clients I had.
If you generally want to see what licenses you have on the KMS server, you can run the ‘Volume Activation Management Tool’ which is available as part of the Windows Assessment and Deployment Kit (ADK). Install instructions from Technet are available here. This tool will visually show you what products you have licensed, but won’t go into great detail. It’s good to have just as an overview.
There are other scenarios and issues that can happen with KMS activation. On the KMS server, you can check the KMS event logs in Event Viewer under Applications and Service Logs > Key Management Service. On the client, there are a huge amount of switches you can use with the slmgr.vbs script – you can run it without any switches to see them all.
- Review: Lumia 830 vs Lumia 930 showdown- December 13, 2014
- Western Digital Make Backup Devices?- September 14, 2014
- Review: Nokia Lumia 930- September 4, 2014
- KMS and MAK Licensing- July 31, 2014
- Review: Samsung Gear 2 Neo- June 18, 2014
- Storage that’s nearly INVINCIBLE- June 2, 2014
- Coping with infinite email- May 30, 2014
- TechEd North America – The Closing Line- May 18, 2014
- TechEd North America – Half Way Mark- May 15, 2014
- Windows Phone 8.1 Is Out!- April 21, 2014
![Kms and mak Kms and mak](https://content.spiceworksstatic.com/service.community/p/post_images/0000004231/53063523/attached_image/1.png)
Cornell's site license for Microsoft Windows and Microsoft Office Professional Plus provides unlimited licensing via our Key Management Service (KMS). This page provides instructions for technical support providers (TSPs) to switch a computer from the earlier Multiple Activation Key (MAK) system to the preferred KMS system.
Switching a machine from MAK to KMS requires use of the Windows command line. You will need to issue Visual Basic commands to replace the existing MAK product key with a Generic Volume License Key (GVLK). If your network is not set up for autodiscovery, you will also need to issue additional commands to tell the machine the URL of the KMS server, and to start the automated activation process.
KMS activation can be blocked by a firewall. Please be sure that any firewalls between the client machine and the KMS server are open to incoming and outgoing traffic on TCP port 1688.
This page is intended for technical support providers and network administrators. If you're not one of those, you should talk to your TSP or net admin before proceeding.
Covered Products
Cornell's KMS activation service will automatically activate the following Microsoft products if they had been installed from the Cornell site license version of the installers.
- Windows 7 (Enterprise or Professional)
- Windows 8 (Enterprise or Professional)
- Windows 10 (Education, Enterprise, Enterprise 2015 LTSB, or Professional)
- Windows Server (2008, 2008R2, and 2012)
- Microsoft Office (2016, 2013, and 2010)
Our KMS service will not activate versions of the above software that were installed from OEM or retail versions of the installers.
Switch Activation from MAK to KMS
Updating an installation of Windows of Office entails entering commands at a command prompt. The commands you enter depend on whether your local area network has been configured to allow KMS autodiscovery. Networks administered by CIT are already configured for KMS. More information about autodiscovery can be found on our main KMS page.
If you aren't sure whether your local area network has already been configured for KMS, you can use the KMS manual configuration instructions.
From a Network with KMS Autodiscovery
Windows and Windows Server (all supported versions)
- Open another browser window, and go to our Generic Volume License Key (GVLK) page to find the appropriate GVLK for your version of Windows.
- Open an Elevated Command Prompt window. For instructions, please see How To Open an Elevated Command Prompt.
- In the Command Prompt window, verify that the current directory is C:WindowsSystem32. If it is not, type
CD WindowsSystem32
and press . - Type the following command to set the key.
cscript slmgr.vbs /ipk GVLK-from-Step-1
replacing GVLK-from-Step-1 with the actual key you found in step 1,
then press .
(Note: There is a space between ipk and the product key. ) - Type the following command:
cscript slmgr.vbs /ato
and press .
(There is a space after vbs in the command above.) - Close the command prompt window.
Windows should now be in an activated state on this computer.
Office 2016, 2013, and 2010
- Open up an Elevated Command Prompt window. For instructions, please see How To Open an Elevated Command Prompt.
- In the elevated Command Prompt window, type a command that corresponds to your version of Office:
- Office 2016
CD Program FilesMicrosoft OfficeOffice16
Note: If this is the 32-bit version of Office installed onto a machine running the 64-bit version of Windows, use the following command instead:
CD Program Files (x86)Microsoft OfficeOffice16 - Office 2013
CD Program FilesMicrosoft OfficeOffice15
Note: If this is the 32-bit version of Office installed onto a machine running the 64-bit version of Windows, use the following command instead:
CD Program Files (x86)Microsoft OfficeOffice15 - Office 2010
CD Program FilesMicrosoft OfficeOffice14
Note: If this is the 32-bit version of Office installed onto a machine running the 64-bit version of Windows, use the following command instead:
CD Program Files (x86)Microsoft OfficeOffice14
- Office 2016
- Press .
- Type the following command that corresponds to your version of Office:
- Office 2016
cscript ospp.vbs /inpkey:XQNVK-8JYDB-WJ9W3-YJ8YR-WFG99 - Office 2013
cscript ospp.vbs /inpkey:YC7DK-G2NP3-2QQC3-J6H88-GVGXT - Office 2010
cscript ospp.vbs /inpkey:VYBBJ-TRJPB-QFQRF-QFT4D-H3GVB
- Office 2016
- Press . (There is a colon between inpkey and the product key.)
- Type cscript ospp.vbs /act then Press .
- Close the command prompt window.
Office should now be in an activated state on this computer.
From a Network Without KMS Autodiscovery (manual configuration)
Windows (all supported versions)
- Open up a new browser window and go to our Generic Volume License Key (GVLK) page to find the GVLK that is appropriate to your version of Windows.
- Open an Elevated Command Prompt window. For instruction, please see How To Open an Elevated Command Prompt.
- In the elevated Command Prompt window, verify that the current directory is C:WindowsSystem32. If it is not, type
CD WindowsSystem32
and press . - Type the following command to set the key:
cscript slmgr.vbs /ipk GVLK-from-Step-1
replacing GVLK-from-Step-1 with the actual key you found in step 1,
then press .
(There is a space between ipk and the product key.) - Type the following command:
cscript slmgr.vbs /skms kms01.cit.cornell.edu
and press .
(Note: There is a space between skms and the url.
The url in the command above begins with kay-emm-ess-zero-one.) - Type the following command:
cscript slmgr.vbs /ato
and press .
(There is a space after vbs in the command above.) - Close the elevated Command Prompt window.
Windows should now be in an activated state on this computer.
Office 2016, 2013, and 2010
- Open up an Elevated Command Prompt. For instructions, please see How To Open an Elevated Command Prompt.
- In the command prompt window, type the following command that corresponds to your version of Office:
- Office 2016
CD Program FilesMicrosoft OfficeOffice16
Note: If this is the 32-bit version of Office installed onto a machine running the 64-bit version of Windows, use the following command instead:
CD Program Files (x86)Microsoft OfficeOffice16 - Office 2013:
CD Program FilesMicrosoft OfficeOffice15
Note: If this is the 32-bit version of Office installed onto a machine running the 64-bit version of Windows, use the following command instead:
CD Program Files (x86)Microsoft OfficeOffice15 - Office 2010
CD Program FilesMicrosoft OfficeOffice14
Note: If this is the 32-bit version of Office installed onto a machine running the 64-bit version of Windows, use the following command instead:
CD Program Files (x86)Microsoft OfficeOffice14
- Office 2016
- Press.
- Type the following command that corresponds to your version of Office:
- Office 2016
cscript ospp.vbs /inpkey:XQNVK-8JYDB-WJ9W3-YJ8YR-WFG99 - Office 2013
cscript ospp.vbs /inpkey:YC7DK-G2NP3-2QQC3-J6H88-GVGXT - Office 2010
cscript ospp.vbs /inpkey:VYBBJ-TRJPB-QFQRF-QFT4D-H3GVB
- Office 2016
- .
- Note: There is a colon betweeninpkeyand the product key.
- Type the following command:
- cscript ospp.vbs /sethst:kms01.cit.cornell.edu
- Press.
- Note: There is a colon betweensethstand the url.
Note: The url in the command above begins with 'kay-emm-ess-zero-one.' - Type the following command:
- cscript ospp.vbs /act
- Press.
- Note: There is a space aftervbsin the command above.
- Close the command prompt window.
Office should now be in an activated state on this computer.