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