VAMT 3.0 Adding licenses and manage host (part 2)

In my previous post we installed VAMT 3.0 and created the database.

In this post we will add MAK and KMS keys and we will add some host to monitor the servers/clients to see if the activation is successful. Because you need at least 5 Servers or 25 Clients before KMS keys will work we are using MAK keys in this post.

When you opened VAMT and are connected to the database you will see the following screen.

VAMT 3.0 Overview

As you can see there are now products discovered or License keys installed.

To install the license keys “Right click” on the “Product keys” and select “Add product keys..“, then add the license keys into the box and click on “Add Key(s)” when you like to add multiple keys use a separate line for the different keys.

After the key is verified it will show up in the product keys overview.

VAMT Add Key


VAMT 3.0 Installation (part 1)

In this series I’m writing a 2 part article about how to install and configure VAMT.

When you want to manage your MAK or KMS licenses activation within your organization you can use Microsoft Volume Activation Management Tool (VAMT) version 3.0. Whit VAMT 3.0 you can add licenses, view activations and more. VAMT is part of the Windows Assessment and Deployment Kit (ADK) for Windows® 8. 

Before you can use VAMT you have to download it first at the following location:

VAMT can be installed in the following Operating Systems:

  • Windows® 8
  • Windows® 7
  • Windows Server® 2012
  • Windows Server® 2008 R2
  • Windows Vista®
  • Windows Server® 2008

When using VAMT 3.0 you need an SQL server, when you don’t have an SQL server you can select the SQL 2012 Express to be installed on your system. The user who is installing VAMT needs DbCreator rights on the SQL server which you like to use. All other users which want to connect to the database need to be db_owner of the database used to install VAMT.

When installing ADK you need to specify the location the files are stored, in the screenshot below you can select to install or just download to install it on a separate computer, we will choose to install.

ADK Specify location to install

Change vDisk from MAK to KMS

When using MAK on a provisioned vDisk with multiple versions and you need to change the activation to KMS, it’s important to first create a Merge of the version to a now Base image. This has to be done because you need to change the Microsoft Volume Licensing option within the vDisk properties and dis can only be done on al the versions and only when the vDisk isn’t locked.

Important: you need at least 25 Windows 7 clients or 5 Windows 2008 R2 host using KMS to get it work.

After creating a Merge base, copy the VHD and PVP file and rename them to a appropriate name, in this example the new name is “XenAppKMS”, after renaming import the vDisk into the Provisioning Services Console and add it to a test or maintenance device.

 Imported XenAppKMS