Difference between MAK, KMS and ADBA activation

Last years I did multiple blogposts about activation based on MAK and KMS. Recently I did mention the ADBA license Pack too. This time some pros and cons beween these activation tools.

Multiple Activation Key (MAK) usage:
- For workgroup-joined systems (when no domain is used)
- Systems which are used outside the domain, and not connected in 180 days or more. Otherwise activation will be expired.

Key Management Service (KMS) usage:
- CMD-line based & domain wide, therefore a KMS host is need for every (child) domain.
- A minimum of 25 devices and/or 5 servers for activation
- Valid for 180 days, where every 7 days a check is done
- Windows 7 & Server 2008 support or later

AD-Based Activation (ADBA) usage:
- GUI based & forest wide, so no need to have a KMS host for every (child) domain
- No minimum on devices and/or servers (!)
- Activated during domain-join immediately, and removed when domain-join is undone or 180 days has passed.
- Windows 8 & Server 2012 support or later
- No TCP 1688 (KMS) is used, but default LDAP instead

Hope it's clear that ADBA is the way to go. Less servers needed and easier in communication and activation. Hope you like it too :-)

A setup guide can be found here: Installing Volume Activation Services Role in Windows Server 2012 to Configure ADBA

More blogposts about activation tools:
Update KMS hosts for Windows 10 activation
Usage of Microsoft Office 2016 KMS Host or ADBA License Pack
And many, many more...

Update KMS hosts for Windows 10 activation

Last month I did a blogpost on Usage of Microsoft Office 2016 KMS Host or ADBA License Pack. This time I want to show you what's needed to update existing KMS hosts for Windows 10 activation.

When KMS is installed on Windows Server 2008 R2 a hotfix is needed. It can be found here: Microsoft

After that a special key is needed. It's called Windows Srv 2012R2 DataCtr/Std KMS for Windows 10. You can find it on the following location:

On the Volume License Servicing Center go to Licenses > Relationship Summary, instead of going to 'Downloads and Keys' where you can find it normally. Navigate to the License ID and open the details of it, then select Product Keys. In that you find the key needed for Windows 10 activation mentioned earlier.

Just use the commands Slmgr -ipk <product key> and Slmgr -ato on your KMS host to update it for Windows 10 activation, and you will be fine! This also on Windows Server 2008 R2 :-)

Sources:
Activating Windows 10 on Windows Server 2008 R2, Windows Server 2012 and 2012 R2 KMS hosts
Windows 10 KMS Requirements (outdated)
Find and Update Your KMS Service Host Key To Activate Windows 10

Usage of Microsoft Office 2016 KMS Host or ADBA License Pack

Another blogpost about licensing. Before this 4 other blogposts where available, just have a look at that one also:
Key Management Services (KMS) explained
Using KMS Client Setup Keys during deployment
Usage of Microsoft Office 2010 KMS Host License Pack
Usage of Microsoft Office 2013 KMS Host License Pack

The Microsoft Office 2016 KMS Host License Pack must be installed before importing the KMS key. It can be downloaded at this location: Download Center. During installation the Office 2016 KMS key can be imported successfully.

Volume license editions of Office 2016 client products require activation. This download enables IT administrators to set up a Key Management Service (KMS) or configure a domain for Active Directory-Based activation (ADBA). Either of these volume activation methods can locally activate all Office 2016 clients connected to an organization’s network.

Just make sure your KMS host is running on Windows 7/8.x/10 or Windows Server 2008R2/2012/2012R2.

Active Directory-Based activation (ADBA)
For environments in which all computers are running Windows 8.x/10 or Windows Server 2012/2012R2, and they are joined to a domain, ADBA is the best option for activating all client computers and servers, and you may be able to remove any KMS hosts from your environment.

If you are using both KMS and ADBA, it may be difficult to see whether a client computer has been activated by KMS or by ADBA. Consider disabling KMS during the test, or make sure that you are using a client that has not already been activated by KMS. The slmrg.vbs /dlv command also indicates whether KMS has been used.

For future scenarios, ADBA is the way to go!

More on KMS activation: HERE
More on AD-based activation: HERE

MDT 2013 - Deploy Multiple Windows versions with a single Deploymentshare

When deploying an Windows image in MDT 2013 you can add rules in CustomSettings.ini to offer a product key during deployment (for example). Settings in this ini file are used to create the unattend file, which is needed during mini-setup. Just add the following rules for skipping the product key:
-SkipProductKey=YES
-ProductKey=AAAAA-BBBBB-CCCCC-DDDDD-EEEEE

When using multiple Windows versions however, this will not do the job. In that case add the product key in the deployment task sequence(s). Just add it at start in the task sequence, beneath the Initialization phase. Just name the variable ProductKey and enter a KMS Client Setup Key (for example). It's just that simple ;)

When looking for KMS Client Setup Keys have a look here: http://technet.microsoft.com/en-us/library/jj612867.aspx

Just love MDT because of simplicity and functionality!

How to setup a MS Office 2013 KMS Host on Windows Server 2012

Last month I did a blogpost about "Usage of Microsoft Office 2013 KMS Host License Pack". This one is needed to activate Microsoft Office 2013 through KMS. When using the License Pack things can still go wrong. Let's have a look how to setup Microsoft Office 2013 KMS Host on Windows Server 2012 first.

The KMS activation process for MS Office 2013 is the same as what it was for MS Office 2010. However, the interface to setup the KMS host for MS Office 2013 on a Windows Server 2012 has been updated to use the Volume Activation Tools.

1: Download the Microsoft Office 2013 Volume License Pack from the Microsoft Download Center (MSDL) site;
2: Double-click the downloaded EXE to run it;
3: Once the EXE finishes running, the Volume Activation Tools wizard will appear;
4: On the next screen, choose Key Management Service (KMS) and browse to, or specify the name of, the system running Key Management Service. Typically, this would be the system you are running the Volume Activation Tools on;
5. Next, enter the KMS host (CSVLK) key;
6. Choose activation method, online or phone;
7. Activation Succeeded (or not);

When the activation fails because of STATUS_SUCCESS error, change the KMS listening port from 0 to 1688. Then it will be fine after all!

Configuration succeeded! Yeah!!

To trigger activation manually on the KMS client, run ospp.vbs /act at the command prompt. cscript "%installdir%\Program Files\Microsoft Office\Office15\ospp.vbs" /act

Source (partly): How to setup Microsoft Office 2013 KMS Host on Windows Server 2012

How to update an existing KMS Host (based on Windows Server 2008)

Last week it was needed to update an existing KMS host. This because new Operating Systems based on Windows 8.1 and Windows Server 2012 R2 (both Windows 6.3) must be activated. Because an error message is displayed on Windows Server 2008, an hotfix must be installed first before importing the key. Let's have a look.

KMS (Key Management Service) activates computers on a local network, eliminating the need for individual computers to connect to Microsoft. To do this, KMS uses a client–server topology. Commands for setting up a KMS host can be found here: Key Management Services (KMS) explained. When using Windows Server 2008, an update is needed to activate Windows 6.3 systems.

This update extends KMS for Windows Vista, for Windows Server 2008, for Windows 7, and for Windows Server 2008 R2 to enable the enterprise licensing of Windows 8 / 8.1 and of Windows Server 2012 / R2. The update can be found here: Microsoft Support. After installing the update it's possible to update the KMS host finally.

Other blogposts about KMS available:
Using KMS Client Setup Keys during deployment  
Usage of Microsoft Office 2010 KMS Host License Pack
Usage of Microsoft Office 2013 KMS Host License Pack

Usage of Microsoft Office 2013 KMS Host License Pack

Another blogpost about KMS again. Before this 3 other blogposts where available, just have a look at that one also:
Key Management Services (KMS) explained
Using KMS Client Setup Keys during deployment  
Usage of Microsoft Office 2010 KMS Host License Pack

The Microsoft Office 2013 KMS Host License Pack must be installed before importing the KMS key. It can be downloaded at this location: Download Center. During installation the Office 2013 KMS key can be imported successfully.

Volume license editions of Office 2013 client products require activation. This download enables IT administrators to set up a Key Management Service (KMS) or configure a domain for Active Directory-Based activation. Either of these volume activation methods can locally activate all Office 2013 clients connected to an organization’s network.

Just make sure your KMS host is running on Windows 7, Windows 8, Windows Server 2008 R2 or Windows Server 2012.

Usage of Microsoft Office 2010 KMS Host License Pack

Another blogpost about KMS again. Before this 2 other blogposts where available, just have a look at that one also:
Key Management Services (KMS) explained
Using KMS Client Setup Keys during deployment  

When setting up KMS a Windows Server KMS key can be installed at first try. When using a Office (2010) key afterwards an error message is displayed.
Error: 0xC004F050 The software licensing service reported that the product key is invalid

This because the Microsoft Office 2010 KMS Host License Pack must be installed first. It can be downloaded at this location: Download Center. During installation the Office 2010 KMS key can be imported succesfully.

More information can be found on Microsoft TechNet also.

Using KMS Client Setup Keys during deployment

Last month I did a new ConfigMgr 2012 SP1 installation. When deploying the Windows 7 image, which was created by ConfigMgr Capture media, no activation by KMS (Key Management Service) was done. This because MAK (Multiple Activation Key) was used in the image during installation. When deploying the same image afterwards, no KMS activation can be done anymore. There is a solution however; just use the applicable KMS client setup keys below.

KMS Client Setup Keys

Operating System Edition	Product Key
Windows 7
Windows 7 Professional	FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4
Windows 7 Professional N	MRPKT-YTG23-K7D7T-X2JMM-QY7MG
Windows 7 Enterprise	33PXH-7Y6KF-2VJC9-XBBR8-HVTHH
Windows 7 Enterprise N	YDRBP-3D83W-TY26F-D46B2-XCKRJ
Windows 7 Enterprise E	C29WB-22CC8-VJ326-GHFJW-H9DH4
Windows Server 2008 R2
Windows Server 2008 R2 HPC Edition	FKJQ8-TMCVP-FRMR7-4WR42-3JCD7
Windows Server 2008 R2 Datacenter	74YFP-3QFB3-KQT8W-PMXWJ-7M648
Windows Server 2008 R2 Enterprise	489J6-VHDMP-X63PK-3K798-CPX3Y
Windows Server 2008 R2 for Itanium-Based Systems	GT63C-RJFQ3-4GMB6-BRFB9-CB83V
Windows Server 2008 R2 Standard	YC6KT-GKW9T-YTKYR-T4X34-R7VHC
Windows Web Server 2008 R2	6TPJF-RBVHG-WBW2R-86QPH-6RTM4

After using above keys in the Apply Windows Settings step in your task sequence, MAK registration is replaced with KMS. Then activation can be done by the KMS host again. It's still needed however to buy a KMS host key for doing the actual activation, but it will work this way!

When seeing this, activation can be done!

For more information about KMS read this blogpost
For more KMS Client Setup Keys read this thread

Key Management Services (KMS) explained

When installing Windows Server 2008 (R2) or Windows Vista / 7 in your network you must think about volume activation. With volume activation there are two (2) different models for completing this. These are Key Management Service (KMS) and Multiple Activation Key (MAK). Both are working and has there own benefits.

• Key Management Service (KMS) – KMS activates operating systems on the local network, so individual computers doesn't has to connect to Microsoft. KMS clients connects with a KMS host for activation.
• Multiple Activation Key (MAK) - MAK requires computers to connect one time to a Microsoft activation server. Once computers are activated, no further communication with Microsoft is required.

Have a look at this page for more information about Volume License Keys:
http://www.microsoft.com/licensing/existing-customers/product-activation-faq.aspx

Because KMS becomes more and more implemented in projects I will explain it in detail. I will no further explain MAK in this blogpost, because it's known by most people.

KMS requires a minimum number of either physical or virtual computers in a network environment to become functional. These minimums, called activation thresholds, are set so that they are easily met by enterprise customers. For computers running:

• Windows Server 2008 and Windows Server 2008 R2 you must have at least five (5) computers to activate.
• Windows Vista or Windows 7 you must have at least twenty-five (25) computers to activate. These thresholds can be a mix of server and client machines to make up the threshold number.
• Office 2010, Project 2010 and Visio 2010 you must have at least five (5) computers to activate. If you have deployed Microsoft Office 2010 products, including Project 2010 and Visio 2010, you must have at least five (5) computers running Office 2010, Project 2010 or Visio 2010.

The KMS service can be installed on a (existing) server or client!, and will place an record in DNS for recognition. The following commands are available to use in combination with a KMS host: 

When using Windows Server 2008 (R1) or Windows Vista systems an hotfix is needed. This will extend support for KMS to provide activation for Windows 7 and Windows Server 2008 R2. The KMS host will be upgraded from version 1.1 to 1.2 with this hotfix.

• Update for Windows Server 2008 for Itanium-based Systems (KB968912)
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=7cd70df9-e154-434a-828a-ef2af7df2ecd
• Update for Windows Vista for x64-based Systems (KB968912) http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=2c80091b-818f-422d-9231-baa18a18338b
• Update for Windows Vista (KB968912)
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=927b7f08-a969-4035-b677-4e325d37145d
• Update for Windows Server 2008 (KB968912) http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=8a9ba611-d138-4526-b3fd-873c9c28b60c
• Update for Windows Server 2008 x64 Edition (KB968912)
  http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=d284f030-642f-443b-85ce-74ef449d5ab4

The command for installing KMS with a product key or updating an existing one is "cscript %windir%\system32\slmgr.vbs /ipk {product key}". After that restarting of the KMS service is needed. This can be done with the following commands: "net stop slsvc" and "net start slsvc". When it's functional it can be tested with the "slmgr.vbs /dli" (basic information) and "slmgr.vbs /dlv" (detailed information) commands.

Have a look at this TechNet post for more information about this: http://social.technet.microsoft.com/Forums/en/winservergen/thread/8edd0ece-7786-42d4-9a23-48e2c271b17d

It's possible to query the DNS server for License keys also. This can be done with the Nslookup –type=all _vlmcs._tcp command. With the "slmgr.vbs /ato" command it's also possible to force a activation renewal. That way it's easier to get the minum required systems activated. When no DNS record is created automatically, you must create one yourself. This can be done with the following guide: Manually Create SRV Records in DNS

During installation it's possible that the following error message is displayed:
Error: 0xC004F015. This can be solved with installing the KMS 1.2 patch or use the correct product key. Have a look at this TechNet post for more information about this: http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/0ce4f1aa-94db-46e0-8d2c-1fb37961a873

On the client (when KMS is active already) it's possible that the following error is displayed: 0xC004F038. This can be solved with activating enough computers. When this is done (at least 5 servers and/or 25 computers) the error message will be gone. Then activation for all systems will be available!

One last note: When creating or deploying a Windows 7 image don't use a build-in product key. Otherwise there's the risk that every Windows 7 client behaves like a KMS host. No product key at all is needed on the Windows 7 client. Just activate them by the KMS host which resides on the Windows Server 2008 (R2) server or on a Windows Vista / 7 host.

Have a look at this TechNet post for more information about this:
http://social.technet.microsoft.com/Forums/en/mdt/thread/c9691329-702e-42e1-9593-c8c06618ff0f

For default KMS Client Setup Keys have a look at this TechNet post:
http://technet.microsoft.com/en-us/library/ff793421.aspx

Update 18-11-2011: On Windows Server 2008 R2 and/or Windows 7 the commands to restart the KMS service are now: "net stop sppsvc" and "net start sppsvc".

Just to clarify things:

The Software Licensing Service existed in Windows Vista, but was replaced in Windows 7. The service that handles the licensing is now called the Software Protection Service (SPPSVC). All of the same procedures and commands still work the same as they did in Windows Vista.

Also, the associated SL UI Notification Service (SLUINotify) in Vista was changed to the SPP Notification Service (SPPUINotify) in Windows 7. (SPP means Software Protection Platform)

TechNet source: Windows 7 Activation Issues