VAMT 2.0 uses the Microsoft Management Console (MMC) 3. The main difference to the interface of VAMT 1.2 is that there now is a third pane in the middle where the managed computers are displayed. In VAMT 1.2, you had to create a folder before you could add computers. In VAMT 2.0, these folders can't be added anymore.
Download the CDS Manual. OD Weight / Wall Grade Connection Design Option Drift Type Min.
Windows ADK 10 for Volume Activation Management Tool (VAMT) – Version 3.1 SQL server 2008 or later required (SQL Server Express supported) Locate your KMS Server. It is most probably been a long time since you’ve played around your KMS server. To find which server is acting as your KMS.

-->

Applies to

When you try to create a database by using Volume Activation Management Tool (VAMT) 3.0 on a computer that is running Windows 8 or Windows Server 2012, you receive.

Windows 10
Windows 8.1
Windows 8
Windows 7
Windows Server 2012 R2
Windows Server 2012
Windows Server 2008 R2

Looking for retail activation?

The Volume Activation Management Tool (VAMT) provides several useful features, including the ability to perform VAMT proxy activation and to track and monitor several types of product keys.

By using the VAMT, you can automate and centrally manage the volume, retail, and MAK activation process for Windows, Office, and select other Microsoft products. The VAMT can manage volume activation by using MAKs or KMS. It is a standard Microsoft Management Console snap-in, and it can beinstalled on any computer running Windows 10, Windows 8.1, Windows 8, Windows 7, Windows Server 2012 R2, Windows Server 2012, or Windows Server 2008 R2.

The VAMT is distributed as part of the Windows Assessment and Deployment Kit (Windows ADK), which is a free download available from Microsoft Download Center. For more information, see Windows Assessment and Deployment Kit (Windows ADK) for Windows 10.

In Windows Server 2012 R2, you can install the VAMT directly from Server Manager without downloading the Windows ADK by selecting the Volume Activation Services role or the Remote Server Administration Tools/Role Administration Tools/Volume Activation Tools feature.

Activating with the Volume Activation Management Tool

You can use the VAMT to complete the activation process in products by using MAK and retail keys, and you can work with computers individually or in groups. The VAMT enables two activation scenarios:

Online activation. Online activation enables you to activate over the Internet any products that are installed with MAK, KMS host, or retail product keys. You can activate one or more connected computers within a network. This process requires that each product communicate activation information directly to Microsoft.
Proxy activation. This activation method enables you to perform volume activation for products that are installed on client computers that do not have Internet access. The VAMT host computer distributes a MAK, KMS host key, or retail product key to one or more client products and collects the installation ID from each client product. The VAMT host sends the installation IDs to Microsoft on behalf of the client products and obtains the corresponding confirmation IDs. The VAMT host then installs the confirmation IDs on the client products to complete their activation.By using this method, only the VAMT host computer requires Internet access. Proxy activation by using the VAMT is beneficial for isolated network segments and for cases where your organization has a mix of retail, MAK, and KMS-based activations.

Tracking products and computers with the Volume Activation Management Tool

The VAMT provides an overview of the activation and licensing status of computers across your network, as shown in Figure 18. Several prebuilt reports are also available to help you proactively manage licensing.

Figure 18. The VAMT showing the licensing status of multiple computers

Tracking key usage with the Volume Activation Management Tool

The VAMT makes it easier to track the various keys that are issued to your organization. You can enter each key into VAMT, and then the VAMT can use those keys for online or proxy activation of clients. The tool can also describe what type of key it is and to which product group it belongs. The VAMT is the most convenient way to quickly determine how many activations remain on a MAK. Figure 19 shows an example of key types and usage.

Figure 19. The VAMT showing key types and usage

Other Volume Activation Management Tool features

The VAMT stores information in a Microsoft SQL Server database for performance and flexibility, and it provides a single graphical user interface for managing activations and performing other activation-related tasks, such as:

Adding and removing computers. You can use the VAMT to discover computers in the local environment. The VAMT can discover computers by querying AD DS, workgroups, or individual computer names or IP addresses, or through a general LDAP query.
Discovering products. You can use the VAMT to discover Windows, Windows Server, Office, and select other products that are installed on the client computers.
Managing activation data. The VAMT stores activation data in a SQL Server database. The tool can export this data in XML format to other VAMT hosts or to an archive.

For more information, see:

Today, we are continuing our journey into the Extended Security Updates (ESU) program that would provide additional support to Windows 7 and Windows 2008/R2 (and SQL 2008 R2) products that have reached end of life beginning of 2020. When we started writing about ESU, we thought that one or two posts maximum would be enough to provide the necessary information. However, based on the questions, feedback and problems encountered by customers, we are already writing part IV of this serie.

So far, we have seen how to prepare the infrastructure and which patches needs to be deployed in order to benefit from the ESU program. We have then see how to install the VAMT tool which is the Microsoft recommended tool to install, distribute and activate ESU MAK Key through the network. We have also covered how to connect the VAMT Tool to the backend infrastructure which can be a SQL Express co-hosted with VAMT or a remote SQL Database server.

At this stage, you would think that you are ready to deploy your ESU MAK Key. However, it seems that the VAMT tool will not recognize the ESU MAK Key as a valid key if you do not deploy a required patch for the VAMT Tool. In this post, we will describe what’s needs to be done to deploy and install this small patch….

Let’s proceed…. !

To obtain more information and follow up with this series about ESU Program, please have a look at

You have installed all the necessary prerequisites within your infrastructure in order to get extended support for your legacy operating system such Windows 7 and Windows 2008 R2. You have installed the VAMT Tool completed and you are ready to deploy your ESU MAK key that you have paid and obtained. You think that you are ready to start using the VAMT tool and deploy the ESU MAK and start downloading and installing available critical or security hotfixes for Windows 7 and Windows 2008 R2.

At this stage, you fire up the VAMT tool console and you expand the nodes. You right click on the product key node and the following dialog box is displayed in front of you.

Click on Picture for Better Resolution

You enter your newly received ESU MAK Key and you press the Add keys button. Immediately after, you will receive a message that your keys are not valid or not recognized.

Click on Picture for Better Resolution

If you read carefully the warning message above, it states that a possible update might be available. Do not click on the link as it will check for an updated version of adk and not updated version of files needed by VAMT to validate the product keys…

Updating VAMT Software

As shown

Activating with the Volume Activation Management Tool

Tracking products and computers with the Volume Activation Management Tool

Tracking key usage with the Volume Activation Management Tool

Other Volume Activation Management Tool features

See also

Updating VAMT Software

Vamt Download 3.1