MAK activation works by assigning a predetermined number of allowed activations to a single key, based on the organization's volume licensing agreement. There are two primary methods for deploying a MAK:
To maximize the value of a MAK and ensure compliance, organizations should implement the following strategies:
Unlike a Retail Key, which is typically restricted to a single device, a MAK is associated with a specific number of allowed activations determined by the volume licensing agreement purchased by the company. For example, an organization purchasing 500 licenses may receive a single MAK that allows for 500 activations. multiple activation key
Instead of tracking hundreds of unique alphanumeric keys, administrators only need to manage and secure one string. This simplifies imaging and deployment scripts.
In a deployment task sequence, either use KMS or use a MAK with pre‑activation (sysprep with /generalize and skip re‑entering the key). Otherwise, each deployed image uses a fresh activation. MAK activation works by assigning a predetermined number
Once a device is activated via MAK, it remains activated permanently unless there are significant hardware changes. No regular "check-ins" with Microsoft are required. MAK vs. KMS: Key Differences
Once the activation count reaches zero, the MAK stops working. You can request an increase from Microsoft (subject to your volume license agreement). Instead of tracking hundreds of unique alphanumeric keys,
In environments with strict internet security policies or air-gapped networks, devices may not be able to connect directly to the vendor's servers. In these cases, a tool like the can be used. VAMT collects activation requests from internal devices and acts as a proxy, sending a single bulk request to the vendor’s server on behalf of the devices.