How to Use Multiple Activation Key (MAK) Activation with Automatic Updates

  • CTX129105
  • Created onMar 26, 2014
  • Updated onMar 27, 2014
Article Topic Configuration, Licensing


This article describes how to use Multiple Activation Key (MAK) Activation with Automatic Updates.

Note: For Provisioning Server 6.x environment, using vDisk versioning is another alternative to update MAK-enabled image.


  • Knowledge of Provisioning Services and Microsoft Licensing

  • Knowledge of Automatic Updates

  • Volume Activation Management Tool (VAMT) 2.0 Tool


  • Ensure that MAK activation is successful for multiple target devices. (Login to Target Devices > Properties > check Windows Activation).

  • Restart these devices and ensure that reactivation is successful.

  • Assuming that the vDisk is set to standard image mode at this time.


Complete the following set of procedures:

Preparing vDisk

  1. In the vDisks properties, navigate to the Auto Update tab.

  2. Select Enable automatic updates for this vDisk.

  3. Select Apply vDisk updates as soon as they are detected by the server. This allows the user to update on demand. The other option allows the user to schedule the update.

  4. Enter the Class and type the same unique string. This string should be identical to the class properties in the device properties of all the target devices that are getting the updated vDisk.

Copying vDisk

  1. On the Provisioning Services (PVS) server, open Windows Explorer.

  2. Navigate to the directory where the vDisks are stored.

  3. Copy both vDisk (.vhd) and Properties file (.pvp) files and paste where the original vDisk is located.

  4. Rename these two files with appropriate name.

Note: vDisk and .pvp file names have to be identical.

Adding Copied vDisk to Provisioning Services Database

  1. In the PVS console, right-click Store and choose Add Existing vDisk.

  2. Click Search and select the copied vDisk.

  3. Click Add to add the vDisk to the PVS database.

Switching Copied vDisk to Private Mode

  1. Open vDisk properties of the copied vDisk.

  2. In the General tab, change the access mode to Private Image.

  3. In the Auto Update tab, update increment Major #, Minor #, or Build # to signify that copied vDisk is the updated vDisk.

Updating the Copied vDisk

  1. Create a new Virtual Machine (VM) to be used for updating the vDisk.

  2. Create a new device record from PVS console with a unique name.

  3. Type the MAC address of the VM and set it to start from vDisk.

  4. In the vDisks tab of new device, add the copied vDisk.

  5. Start the VM and update the copied vDisk.

  6. Shutdown the device after completing the update.

  7. Change the copied vDisk properties to Standard Image mode. Change the cache type to the cache type of original vDisk.

Running Auto Update

  1. Open PVS console > Servers > PVS server.

  2. Right-click and select Check for Automatic Updates.

  3. Access the device location where all the target devices are located.

  4. Right-click and select Refresh.

  5. For Target devices, which are started from the original vDisk, take the updated vDisk from next restart.

  6. For Target devices, which are down, replace the updated vDisk with original vDisk.

Verifying MAK Reactivation

  1. Start the target devices.

  2. Right-click My Computer and select Properties.

  3. Activate Windows in the Windows Activation section.

If Windows is not activated, the following message is displayed:

"3 days until automatic activation. Activate Windows now."

That is, Windows has received all the necessary information required for activation, but Windows is delaying activation.

Force Windows to activate immediately by completing the following procedure:

  1. Open a command prompt with elevated administrator privilege.

  2. Run the command slmgr –ato with no quotes.

  3. When the command is successfully executed, right-click My Computer and select Properties.

  4. Verify that Windows is activated by checking Windows activation, which displays that Windows is activated.

Automatic translation

Important: This article was translated by an automatic translation system (also referred to as Machine Translation, or MT) and has not been translated or reviewed by people. Citrix offers a machine translated version of this article to allow for greater access to the support content. However, automatic translation is not always perfect and may contain errors of vocabulary, syntax or grammar. Citrix is not responsible for inconsistencies, errors or damage incurred as a result of the use of MT articles from our customers.Thank you.
Click here to see the English version of this article.
Was this helpful?
Thank you for your feedback

Share your comments or find out more about this topic

Citrix Forums