mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-22 22:03:46 +00:00
author duplicates
This commit is contained in:
Greg Lindsay
@ -1,50 +1,51 @@
|
||||
---
|
||||
title: Activate an Active Directory Forest Online (Windows 10)
|
||||
description: Activate an Active Directory Forest Online
|
||||
ms.assetid: 9b5bc193-799b-4aa5-9d3e-0e495f7195d3
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/25/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Activate an Active Directory Forest Online
|
||||
|
||||
You can use the Volume Activation Management Tool (VAMT) Active Directory-Based Activation (ADBA) function to activate an Active Directory (AD) forest over the Internet. ADBA enables certain products to inherit activation from the domain.
|
||||
|
||||
**Important**
|
||||
ADBA is only applicable to Generic Volume License Keys (GVLKs) and KMS Host keys (CSVLKs). To use ADBA, one or more KMS Host keys (CSVLKs) must be installed on the AD forest, and client keys (GVLKs) must be installed on the client products.
|
||||
|
||||
## Requirements
|
||||
|
||||
Before performing online activation, ensure that the network and the VAMT installation meet the following requirements:
|
||||
- VAMT is installed on a host computer that has Internet access.
|
||||
- VAMT has administrative permissions to the Active Directory domain.
|
||||
- The KMS Host key (CSVLK) you intend to use is added to VAMT in the **Product Keys** node.
|
||||
|
||||
**To perform an online Active Directory forest activation**
|
||||
|
||||
1. Open VAMT.
|
||||
2. In the left-side pane, click the **Active Directory-Based Activation** node.
|
||||
3. In the right-side **Actions** pane, click **Online activate forest** to open the **Install Product Key** dialog box.
|
||||
4. In the **Install Product Key** dialog box, select the KMS Host key (CSVLK) that you want to apply to the AD forest.
|
||||
5. If required, enter a new Active Directory-Based Activation Object name
|
||||
|
||||
**Important**
|
||||
If you want to rename the ADBA object, you must do it now. After you click **Install Key**, the name cannot be changed.
|
||||
|
||||
6. Click **Install Key**.
|
||||
7. VAMT displays the **Activating Active Directory** dialog box until it completes the requested action.
|
||||
|
||||
The activated object and the date that is was created appear in the **Active Directory-Based Activation** node in the center pane.
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Scenario 1: Online Activation](scenario-online-activation-vamt.md)
|
||||
---
|
||||
title: Activate an Active Directory Forest Online (Windows 10)
|
||||
description: Activate an Active Directory Forest Online
|
||||
ms.assetid: 9b5bc193-799b-4aa5-9d3e-0e495f7195d3
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/25/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Activate an Active Directory Forest Online
|
||||
|
||||
You can use the Volume Activation Management Tool (VAMT) Active Directory-Based Activation (ADBA) function to activate an Active Directory (AD) forest over the Internet. ADBA enables certain products to inherit activation from the domain.
|
||||
|
||||
**Important**
|
||||
ADBA is only applicable to Generic Volume License Keys (GVLKs) and KMS Host keys (CSVLKs). To use ADBA, one or more KMS Host keys (CSVLKs) must be installed on the AD forest, and client keys (GVLKs) must be installed on the client products.
|
||||
|
||||
## Requirements
|
||||
|
||||
Before performing online activation, ensure that the network and the VAMT installation meet the following requirements:
|
||||
- VAMT is installed on a host computer that has Internet access.
|
||||
- VAMT has administrative permissions to the Active Directory domain.
|
||||
- The KMS Host key (CSVLK) you intend to use is added to VAMT in the **Product Keys** node.
|
||||
|
||||
**To perform an online Active Directory forest activation**
|
||||
|
||||
1. Open VAMT.
|
||||
2. In the left-side pane, click the **Active Directory-Based Activation** node.
|
||||
3. In the right-side **Actions** pane, click **Online activate forest** to open the **Install Product Key** dialog box.
|
||||
4. In the **Install Product Key** dialog box, select the KMS Host key (CSVLK) that you want to apply to the AD forest.
|
||||
5. If required, enter a new Active Directory-Based Activation Object name
|
||||
|
||||
**Important**
|
||||
If you want to rename the ADBA object, you must do it now. After you click **Install Key**, the name cannot be changed.
|
||||
|
||||
6. Click **Install Key**.
|
||||
7. VAMT displays the **Activating Active Directory** dialog box until it completes the requested action.
|
||||
|
||||
The activated object and the date that is was created appear in the **Active Directory-Based Activation** node in the center pane.
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Scenario 1: Online Activation](scenario-online-activation-vamt.md)
|
||||
- [Add and Remove Computers](add-remove-computers-vamt.md)
|
||||
|
||||
@ -1,127 +1,128 @@
|
||||
---
|
||||
title: Activate clients running Windows 10 (Windows 10)
|
||||
description: After you have configured Key Management Service (KMS) or Active Directory-based activation on your network, activating a client running Windows 10 is easy.
|
||||
ms.assetid: 39446e49-ad7c-48dc-9f18-f85a11ded643
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
keywords: vamt, volume activation, activation, windows activation
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 07/27/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Activate clients running Windows 10
|
||||
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
**Looking for retail activation?**
|
||||
|
||||
- [Get Help Activating Microsoft Windows](https://go.microsoft.com/fwlink/p/?LinkId=618644)
|
||||
|
||||
After you have configured Key Management Service (KMS) or Active Directory-based activation on your network, activating a client running Windows 10 is easy. If the computer has been configured with a Generic Volume License Key (GVLK), neither IT nor the user need take any action. It just works.
|
||||
Enterprise edition images and installation media should already be configured with the GVLK. When the client computer starts, the Licensing service examines the current licensing condition of the computer.
|
||||
If activation or reactivation is required, the following sequence occurs:
|
||||
1. If the computer is a member of a domain, it asks a domain controller for a volume activation object. If Active Directory-based activation is configured, the domain controller returns the object. If the object matches the edition of the software that is installed and the computer has a matching GVLK, the computer is activated (or reactivated), and it will not need to be activated again for 180 days, although the operating system will attempt reactivation at much shorter, regular intervals.
|
||||
2. If the computer is not a member of a domain or if the volume activation object is not available, the computer will issue a DNS query to attempt to locate a KMS server. If a KMS server can be contacted, activation occurs if the KMS has a key that matches the computer’s GVLK.
|
||||
3. The computer tries to activate against Microsoft servers if it is configured with a MAK.
|
||||
|
||||
If the client is not able to activate itself successfully, it will periodically try again. The frequency of the retry attempts depends on the current licensing state and whether the client computer has been successfully activated in the past. For example, if the client computer had been previously activated by Active Directory-based activation, it will periodically try to contact the domain controller at each restart.
|
||||
|
||||
## How Key Management Service works
|
||||
|
||||
KMS uses a client–server topology. KMS client computers can locate KMS host computers by using DNS or a static configuration. KMS clients contact the KMS host by using RPCs carried over TCP/IP.
|
||||
|
||||
### Key Management Service activation thresholds
|
||||
|
||||
You can activate physical computers and virtual machines by contacting a KMS host. To qualify for KMS activation, there must be a minimum number of qualifying computers (called the activation threshold). KMS clients will be activated only after this threshold has been met. Each KMS host counts the number of computers that have requested activation until the threshold is met.
|
||||
|
||||
A KMS host responds to each valid activation request from a KMS client with the count of how many computers have already contacted the KMS host for activation. Client computers that receive a count below the activation threshold are not activated. For example, if the first two computers that contact the KMS host are running Windows 10, the first receives an activation count of 1, and the second receives an activation count of 2. If the next computer is a virtual machine on a computer running Windows 10, it receives an activation count of 3, and so on. None of these computers will be activated, because computers running Windows 10, like other client operating system versions, must receive an activation count of 25 or more.
|
||||
When KMS clients are waiting for the KMS to reach the activation threshold, they will connect to the KMS host every two hours to get the current activation count. They will be activated when the threshold is met.
|
||||
|
||||
In our example, if the next computer that contacts the KMS host is running Windows Server 2012 R2, it receives an activation count of 4, because activation counts are cumulative. If a computer running Windows Server 2012 R2 receives an activation count that is 5 or more, it is activated. If a computer running Windows 10 receives an activation count of 25 or more, it is activated.
|
||||
|
||||
### Activation count cache
|
||||
|
||||
To track the activation threshold, the KMS host keeps a record of the KMS clients that request activation. The KMS host gives each KMS client a client ID designation, and the KMS host saves each client ID in a table. By default, each activation request remains in the table for up to 30 days. When a client renews its activation, the cached client ID is removed from the table, a new record is created, and the 30day period begins again. If a KMS client computer does not renew its activation within 30 days, the KMS host removes the corresponding client ID from the table and reduces the activation count by one.
|
||||
However, the KMS host only caches twice the number of client IDs that are required to meet the activation threshold. Therefore, only the 50 most recent client IDs are kept in the table, and a client ID could be removed much sooner than 30 days.
|
||||
The total size of the cache is set by the type of client computer that is attempting to activate. If a KMS host receives activation requests only from servers, the cache will hold only 10 client IDs (twice the required 5). If a client computer running Windows 10 contacts that KMS host, KMS increases the cache size to 50 to accommodate the higher threshold. KMS never reduces the cache size.
|
||||
|
||||
### Key Management Service connectivity
|
||||
|
||||
KMS activation requires TCP/IP connectivity. By default, KMS hosts and clients use DNS to publish and find the KMS. The default settings can be used, which require little or no administrative action, or KMS hosts and client computers can be manually configured based on network configuration and security requirements.
|
||||
|
||||
### Key Management Service activation renewal
|
||||
|
||||
KMS activations are valid for 180 days (the *activation validity interval*). To remain activated, KMS client computers must renew their activation by connecting to the KMS host at least once every 180 days. By default, KMS client computers attempt to renew their activation every 7 days. If KMS activation fails, the client computer retries every two hours. After a client computer’s activation is renewed, the activation validity interval begins again.
|
||||
|
||||
### Publication of the Key Management Service
|
||||
|
||||
The KMS uses service (SRV) resource records in DNS to store and communicate the locations of KMS hosts. KMS hosts use the DNS dynamic update protocol, if available, to publish the KMS service (SRV) resource records. If dynamic update is not available or the KMS host does not have rights to publish the resource records, the DNS records must be published manually, or you must configure client computers to connect to specific KMS hosts.
|
||||
|
||||
### Client discovery of the Key Management Service
|
||||
|
||||
By default, KMS client computers query DNS for KMS information. The first time a KMS client computer queries DNS for KMS information, it randomly chooses a KMS host from the list of service (SRV) resource records that DNS returns. The address of a DNS server that contains the service (SRV) resource records can be listed as a suffixed entry on KMS client computers, which allows one DNS server to advertise the service (SRV) resource records for KMS, and KMS client computers with other primary DNS servers to find it.
|
||||
Priority and weight parameters can be added to the DnsDomainPublishList registry value for KMS. Establishing KMS host priority groupings and weighting within each group allows you to specify which KMS host the client computers should try first and balances traffic among multiple KMS hosts. Only Windows 10, Windows 8.1, Windows 8, Windows 7, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2 provide these priority and weight parameters.
|
||||
If the KMS host that a client computer selects does not respond, the KMS client computer removes that KMS host from its list of service (SRV) resource records and randomly selects another KMS host from the list. When a KMS host responds, the KMS client computer caches the name of the KMS host and uses it for subsequent activation and renewal attempts. If the cached KMS host does not respond on a subsequent renewal, the KMS client computer discovers a new KMS host by querying DNS for KMS service (SRV) resource records.
|
||||
By default, client computers connect to the KMS host for activation by using anonymous RPCs through TCP port 1688. (You can change the default port.) After establishing a TCP session with the KMS host, the client computer sends a single request packet. The KMS host responds with the activation count. If the count meets or exceeds the activation threshold for that operating system, the client computer is activated and the session is closed. The KMS client computer uses this same process for renewal requests. 250 bytes are used for communication each way.
|
||||
|
||||
### Domain Name System server configuration
|
||||
|
||||
The default KMS automatic publishing feature requires the service (SRV) resource record and support for DNS dynamic update protocol. KMS client computer default behavior and the KMS service (SRV) resource record publishing are supported on a DNS server that is running Microsoft software or any other DNS server that supports service (SRV) resource records (per Internet Engineering Task Force \[IETF\] Request for Comments \[RFC\] 2782) and dynamic updates (per IETF RFC 2136). For example, Berkeley Internet Domain Name versions 8.x and 9.x support service (SRV) resource records and dynamic update.
|
||||
The KMS host must be configured so that it has the credentials needed to create and update the following resource records on the DNS servers: service (SRV), IPv4 host (A), and IPv6 host (AAAA), or the records need to be created manually. The recommended solution for giving the KMS host the needed credentials is to create a security group in AD DS, then add all KMS hosts to that group. On a DNS server that is running Microsoft software, ensure that this security group is given full control over the \_VLMCS.\_TCP record in each DNS domain that will contain the KMS service (SRV) resource records.
|
||||
|
||||
### Activating the first Key Management Service host
|
||||
|
||||
KMS hosts on the network need to install a KMS key, and then be activated with Microsoft. Installation of a KMS key enables the KMS on the KMS host. After installing the KMS key, complete the activation of the KMS host by telephone or online. Beyond this initial activation, a KMS host does not communicate any information to Microsoft. KMS keys are only installed on KMS hosts, never on individual KMS client computers.
|
||||
|
||||
### Activating subsequent Key Management Service hosts
|
||||
|
||||
Each KMS key can be installed on up to six KMS hosts. These hosts can be physical computers or virtual machines. After activating a KMS host, the same host can be reactivated up to nine times with the same key. If the organization needs more than six KMS hosts, you can request additional activations for your organization’s KMS key by calling a Microsoft Volume [Licensing Activation Center](https://go.microsoft.com/fwlink/p/?LinkID=618264) to request an exception.
|
||||
|
||||
## How Multiple Activation Key works
|
||||
|
||||
A MAK is used for one-time activation with Microsoft’s hosted activation services. Each MAK has a predetermined number of allowed activations. This number is based on volume licensing agreements, and it might not match the organization’s exact license count. Each activation that uses a MAK with the Microsoft hosted activation service counts toward the activation limit.
|
||||
|
||||
You can activate computers by using a MAK in two ways:
|
||||
- **MAK independent activation**. Each computer independently connects and is activated with Microsoft over the Internet or by telephone. MAK independent activation is best suited to computers within an organization that do not maintain a connection to the corporate network. MAK independent activation is shown in Figure 16.
|
||||
|
||||
|
||||
|
||||
**Figure 16**. MAK independent activation
|
||||
- **MAK proxy activation**. MAK proxy activation enables a centralized activation request on behalf of multiple computers with one connection to Microsoft. You configure MAK proxy activation by using the VAMT. MAK proxy activation is appropriate for environments in which security concerns restrict direct access to the Internet or the corporate network. It is also suited for development and test labs that lack this connectivity. MAK proxy activation with the VAMT is shown in Figure 17.
|
||||
|
||||
|
||||
|
||||
**Figure 17**. MAK proxy activation with the VAMT
|
||||
|
||||
A MAK is recommended for computers that rarely or never connect to the corporate network and for environments in which the number of computers that require activation does not meet the KMS activation threshold.
|
||||
|
||||
You can use a MAK for individual computers or with an image that can be duplicated or installed by using Microsoft deployment solutions. You can also use a MAK on a computer that was originally configured to use KMS activation. This is useful for moving a computer off the core network to a disconnected environment.
|
||||
|
||||
### Multiple Activation Key architecture and activation
|
||||
|
||||
MAK independent activation installs a MAK product key on a client computer. The key instructs that computer to activate itself with Microsoft servers over the Internet.
|
||||
In MAK proxy activation, the VAMT installs a MAK product key on a client computer, obtains the installation ID from the target computer, sends the installation ID to Microsoft on behalf of the client, and obtains a confirmation ID. The tool then activates the client computer by installing the confirmation ID.
|
||||
|
||||
## Activating as a standard user
|
||||
|
||||
Windows 10, Windows 8.1, Windows 8, Windows 7, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2 do not require administrator privileges for activation, but this change does not allow standard user accounts to remove computers running Windows 7 or Windows Server 2008 R2 from the activated state. An administrator account is still required for other activation- or license-related tasks, such as “rearm.”
|
||||
|
||||
## See also
|
||||
|
||||
- [Volume Activation for Windows 10](volume-activation-windows-10.md)
|
||||
|
||||
---
|
||||
title: Activate clients running Windows 10 (Windows 10)
|
||||
description: After you have configured Key Management Service (KMS) or Active Directory-based activation on your network, activating a client running Windows 10 is easy.
|
||||
ms.assetid: 39446e49-ad7c-48dc-9f18-f85a11ded643
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
keywords: vamt, volume activation, activation, windows activation
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 07/27/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Activate clients running Windows 10
|
||||
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
**Looking for retail activation?**
|
||||
|
||||
- [Get Help Activating Microsoft Windows](https://go.microsoft.com/fwlink/p/?LinkId=618644)
|
||||
|
||||
After you have configured Key Management Service (KMS) or Active Directory-based activation on your network, activating a client running Windows 10 is easy. If the computer has been configured with a Generic Volume License Key (GVLK), neither IT nor the user need take any action. It just works.
|
||||
Enterprise edition images and installation media should already be configured with the GVLK. When the client computer starts, the Licensing service examines the current licensing condition of the computer.
|
||||
If activation or reactivation is required, the following sequence occurs:
|
||||
1. If the computer is a member of a domain, it asks a domain controller for a volume activation object. If Active Directory-based activation is configured, the domain controller returns the object. If the object matches the edition of the software that is installed and the computer has a matching GVLK, the computer is activated (or reactivated), and it will not need to be activated again for 180 days, although the operating system will attempt reactivation at much shorter, regular intervals.
|
||||
2. If the computer is not a member of a domain or if the volume activation object is not available, the computer will issue a DNS query to attempt to locate a KMS server. If a KMS server can be contacted, activation occurs if the KMS has a key that matches the computer’s GVLK.
|
||||
3. The computer tries to activate against Microsoft servers if it is configured with a MAK.
|
||||
|
||||
If the client is not able to activate itself successfully, it will periodically try again. The frequency of the retry attempts depends on the current licensing state and whether the client computer has been successfully activated in the past. For example, if the client computer had been previously activated by Active Directory-based activation, it will periodically try to contact the domain controller at each restart.
|
||||
|
||||
## How Key Management Service works
|
||||
|
||||
KMS uses a client–server topology. KMS client computers can locate KMS host computers by using DNS or a static configuration. KMS clients contact the KMS host by using RPCs carried over TCP/IP.
|
||||
|
||||
### Key Management Service activation thresholds
|
||||
|
||||
You can activate physical computers and virtual machines by contacting a KMS host. To qualify for KMS activation, there must be a minimum number of qualifying computers (called the activation threshold). KMS clients will be activated only after this threshold has been met. Each KMS host counts the number of computers that have requested activation until the threshold is met.
|
||||
|
||||
A KMS host responds to each valid activation request from a KMS client with the count of how many computers have already contacted the KMS host for activation. Client computers that receive a count below the activation threshold are not activated. For example, if the first two computers that contact the KMS host are running Windows 10, the first receives an activation count of 1, and the second receives an activation count of 2. If the next computer is a virtual machine on a computer running Windows 10, it receives an activation count of 3, and so on. None of these computers will be activated, because computers running Windows 10, like other client operating system versions, must receive an activation count of 25 or more.
|
||||
When KMS clients are waiting for the KMS to reach the activation threshold, they will connect to the KMS host every two hours to get the current activation count. They will be activated when the threshold is met.
|
||||
|
||||
In our example, if the next computer that contacts the KMS host is running Windows Server 2012 R2, it receives an activation count of 4, because activation counts are cumulative. If a computer running Windows Server 2012 R2 receives an activation count that is 5 or more, it is activated. If a computer running Windows 10 receives an activation count of 25 or more, it is activated.
|
||||
|
||||
### Activation count cache
|
||||
|
||||
To track the activation threshold, the KMS host keeps a record of the KMS clients that request activation. The KMS host gives each KMS client a client ID designation, and the KMS host saves each client ID in a table. By default, each activation request remains in the table for up to 30 days. When a client renews its activation, the cached client ID is removed from the table, a new record is created, and the 30day period begins again. If a KMS client computer does not renew its activation within 30 days, the KMS host removes the corresponding client ID from the table and reduces the activation count by one.
|
||||
However, the KMS host only caches twice the number of client IDs that are required to meet the activation threshold. Therefore, only the 50 most recent client IDs are kept in the table, and a client ID could be removed much sooner than 30 days.
|
||||
The total size of the cache is set by the type of client computer that is attempting to activate. If a KMS host receives activation requests only from servers, the cache will hold only 10 client IDs (twice the required 5). If a client computer running Windows 10 contacts that KMS host, KMS increases the cache size to 50 to accommodate the higher threshold. KMS never reduces the cache size.
|
||||
|
||||
### Key Management Service connectivity
|
||||
|
||||
KMS activation requires TCP/IP connectivity. By default, KMS hosts and clients use DNS to publish and find the KMS. The default settings can be used, which require little or no administrative action, or KMS hosts and client computers can be manually configured based on network configuration and security requirements.
|
||||
|
||||
### Key Management Service activation renewal
|
||||
|
||||
KMS activations are valid for 180 days (the *activation validity interval*). To remain activated, KMS client computers must renew their activation by connecting to the KMS host at least once every 180 days. By default, KMS client computers attempt to renew their activation every 7 days. If KMS activation fails, the client computer retries every two hours. After a client computer’s activation is renewed, the activation validity interval begins again.
|
||||
|
||||
### Publication of the Key Management Service
|
||||
|
||||
The KMS uses service (SRV) resource records in DNS to store and communicate the locations of KMS hosts. KMS hosts use the DNS dynamic update protocol, if available, to publish the KMS service (SRV) resource records. If dynamic update is not available or the KMS host does not have rights to publish the resource records, the DNS records must be published manually, or you must configure client computers to connect to specific KMS hosts.
|
||||
|
||||
### Client discovery of the Key Management Service
|
||||
|
||||
By default, KMS client computers query DNS for KMS information. The first time a KMS client computer queries DNS for KMS information, it randomly chooses a KMS host from the list of service (SRV) resource records that DNS returns. The address of a DNS server that contains the service (SRV) resource records can be listed as a suffixed entry on KMS client computers, which allows one DNS server to advertise the service (SRV) resource records for KMS, and KMS client computers with other primary DNS servers to find it.
|
||||
Priority and weight parameters can be added to the DnsDomainPublishList registry value for KMS. Establishing KMS host priority groupings and weighting within each group allows you to specify which KMS host the client computers should try first and balances traffic among multiple KMS hosts. Only Windows 10, Windows 8.1, Windows 8, Windows 7, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2 provide these priority and weight parameters.
|
||||
If the KMS host that a client computer selects does not respond, the KMS client computer removes that KMS host from its list of service (SRV) resource records and randomly selects another KMS host from the list. When a KMS host responds, the KMS client computer caches the name of the KMS host and uses it for subsequent activation and renewal attempts. If the cached KMS host does not respond on a subsequent renewal, the KMS client computer discovers a new KMS host by querying DNS for KMS service (SRV) resource records.
|
||||
By default, client computers connect to the KMS host for activation by using anonymous RPCs through TCP port 1688. (You can change the default port.) After establishing a TCP session with the KMS host, the client computer sends a single request packet. The KMS host responds with the activation count. If the count meets or exceeds the activation threshold for that operating system, the client computer is activated and the session is closed. The KMS client computer uses this same process for renewal requests. 250 bytes are used for communication each way.
|
||||
|
||||
### Domain Name System server configuration
|
||||
|
||||
The default KMS automatic publishing feature requires the service (SRV) resource record and support for DNS dynamic update protocol. KMS client computer default behavior and the KMS service (SRV) resource record publishing are supported on a DNS server that is running Microsoft software or any other DNS server that supports service (SRV) resource records (per Internet Engineering Task Force \[IETF\] Request for Comments \[RFC\] 2782) and dynamic updates (per IETF RFC 2136). For example, Berkeley Internet Domain Name versions 8.x and 9.x support service (SRV) resource records and dynamic update.
|
||||
The KMS host must be configured so that it has the credentials needed to create and update the following resource records on the DNS servers: service (SRV), IPv4 host (A), and IPv6 host (AAAA), or the records need to be created manually. The recommended solution for giving the KMS host the needed credentials is to create a security group in AD DS, then add all KMS hosts to that group. On a DNS server that is running Microsoft software, ensure that this security group is given full control over the \_VLMCS.\_TCP record in each DNS domain that will contain the KMS service (SRV) resource records.
|
||||
|
||||
### Activating the first Key Management Service host
|
||||
|
||||
KMS hosts on the network need to install a KMS key, and then be activated with Microsoft. Installation of a KMS key enables the KMS on the KMS host. After installing the KMS key, complete the activation of the KMS host by telephone or online. Beyond this initial activation, a KMS host does not communicate any information to Microsoft. KMS keys are only installed on KMS hosts, never on individual KMS client computers.
|
||||
|
||||
### Activating subsequent Key Management Service hosts
|
||||
|
||||
Each KMS key can be installed on up to six KMS hosts. These hosts can be physical computers or virtual machines. After activating a KMS host, the same host can be reactivated up to nine times with the same key. If the organization needs more than six KMS hosts, you can request additional activations for your organization’s KMS key by calling a Microsoft Volume [Licensing Activation Center](https://go.microsoft.com/fwlink/p/?LinkID=618264) to request an exception.
|
||||
|
||||
## How Multiple Activation Key works
|
||||
|
||||
A MAK is used for one-time activation with Microsoft’s hosted activation services. Each MAK has a predetermined number of allowed activations. This number is based on volume licensing agreements, and it might not match the organization’s exact license count. Each activation that uses a MAK with the Microsoft hosted activation service counts toward the activation limit.
|
||||
|
||||
You can activate computers by using a MAK in two ways:
|
||||
- **MAK independent activation**. Each computer independently connects and is activated with Microsoft over the Internet or by telephone. MAK independent activation is best suited to computers within an organization that do not maintain a connection to the corporate network. MAK independent activation is shown in Figure 16.
|
||||
|
||||
|
||||
|
||||
**Figure 16**. MAK independent activation
|
||||
- **MAK proxy activation**. MAK proxy activation enables a centralized activation request on behalf of multiple computers with one connection to Microsoft. You configure MAK proxy activation by using the VAMT. MAK proxy activation is appropriate for environments in which security concerns restrict direct access to the Internet or the corporate network. It is also suited for development and test labs that lack this connectivity. MAK proxy activation with the VAMT is shown in Figure 17.
|
||||
|
||||
|
||||
|
||||
**Figure 17**. MAK proxy activation with the VAMT
|
||||
|
||||
A MAK is recommended for computers that rarely or never connect to the corporate network and for environments in which the number of computers that require activation does not meet the KMS activation threshold.
|
||||
|
||||
You can use a MAK for individual computers or with an image that can be duplicated or installed by using Microsoft deployment solutions. You can also use a MAK on a computer that was originally configured to use KMS activation. This is useful for moving a computer off the core network to a disconnected environment.
|
||||
|
||||
### Multiple Activation Key architecture and activation
|
||||
|
||||
MAK independent activation installs a MAK product key on a client computer. The key instructs that computer to activate itself with Microsoft servers over the Internet.
|
||||
In MAK proxy activation, the VAMT installs a MAK product key on a client computer, obtains the installation ID from the target computer, sends the installation ID to Microsoft on behalf of the client, and obtains a confirmation ID. The tool then activates the client computer by installing the confirmation ID.
|
||||
|
||||
## Activating as a standard user
|
||||
|
||||
Windows 10, Windows 8.1, Windows 8, Windows 7, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2 do not require administrator privileges for activation, but this change does not allow standard user accounts to remove computers running Windows 7 or Windows Server 2008 R2 from the activated state. An administrator account is still required for other activation- or license-related tasks, such as “rearm.”
|
||||
|
||||
## See also
|
||||
|
||||
- [Volume Activation for Windows 10](volume-activation-windows-10.md)
|
||||
|
||||
|
||||
|
||||
@ -1,39 +1,40 @@
|
||||
---
|
||||
title: Add and Remove a Product Key (Windows 10)
|
||||
description: Add and Remove a Product Key
|
||||
ms.assetid: feac32bb-fb96-4802-81b8-c69220dcfcce
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/25/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Add and Remove a Product Key
|
||||
|
||||
Before you can use a Multiple Activation Key (MAK), retail, or KMS Host key (CSVLK) product key, you must first add it to the Volume Activation Management Tool (VAMT) database.
|
||||
|
||||
## To Add a Product Key
|
||||
|
||||
1. Open VAMT.
|
||||
2. In the left-side pane, right-click the **Product Keys** node to open the **Actions** menu.
|
||||
3. Click **Add product keys** to open the **Add Product Keys** dialog box.
|
||||
4. In the **Add Product Keys** dialog box, select from one of the following methods to add product keys:
|
||||
- To add product keys manually, click **Enter product key(s) separated by line breaks**, enter one or more product keys separated by line breaks, and click **Add Key(s)**.
|
||||
- To import a Comma Separated Values (CSV) file containing a list of product keys, click **Select a product key file to import**, browse to the file location, click **Open** to import the file, and then click **Add Key(s)**.
|
||||
|
||||
**Note**
|
||||
If you are activating a large number of products with a MAK, you should refresh the activation count of the MAK, to ensure that the MAK can support the required number of activations. In the product key list in the center pane, select the MAK and click **Refresh product key data online** in the right-side pane to contact Microsoft and retrieve the number of remaining activations for the MAK. This step requires Internet access. You can only retrieve the remaining activation count for MAKs.
|
||||
|
||||
## Remove a Product Key
|
||||
|
||||
- To remove a product key from the list, simply select the key in the list and click **Delete** on the **Selected Items** menu in the right-side pane. Click **Yes** to confirm deletion of the product key. Removing a product key from the VAMT database will not affect the activation state of any products or computers on the network.
|
||||
|
||||
## Related topics
|
||||
|
||||
---
|
||||
title: Add and Remove a Product Key (Windows 10)
|
||||
description: Add and Remove a Product Key
|
||||
ms.assetid: feac32bb-fb96-4802-81b8-c69220dcfcce
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/25/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Add and Remove a Product Key
|
||||
|
||||
Before you can use a Multiple Activation Key (MAK), retail, or KMS Host key (CSVLK) product key, you must first add it to the Volume Activation Management Tool (VAMT) database.
|
||||
|
||||
## To Add a Product Key
|
||||
|
||||
1. Open VAMT.
|
||||
2. In the left-side pane, right-click the **Product Keys** node to open the **Actions** menu.
|
||||
3. Click **Add product keys** to open the **Add Product Keys** dialog box.
|
||||
4. In the **Add Product Keys** dialog box, select from one of the following methods to add product keys:
|
||||
- To add product keys manually, click **Enter product key(s) separated by line breaks**, enter one or more product keys separated by line breaks, and click **Add Key(s)**.
|
||||
- To import a Comma Separated Values (CSV) file containing a list of product keys, click **Select a product key file to import**, browse to the file location, click **Open** to import the file, and then click **Add Key(s)**.
|
||||
|
||||
**Note**
|
||||
If you are activating a large number of products with a MAK, you should refresh the activation count of the MAK, to ensure that the MAK can support the required number of activations. In the product key list in the center pane, select the MAK and click **Refresh product key data online** in the right-side pane to contact Microsoft and retrieve the number of remaining activations for the MAK. This step requires Internet access. You can only retrieve the remaining activation count for MAKs.
|
||||
|
||||
## Remove a Product Key
|
||||
|
||||
- To remove a product key from the list, simply select the key in the list and click **Delete** on the **Selected Items** menu in the right-side pane. Click **Yes** to confirm deletion of the product key. Removing a product key from the VAMT database will not affect the activation state of any products or computers on the network.
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Manage Product Keys](manage-product-keys-vamt.md)
|
||||
|
||||
@ -1,71 +1,72 @@
|
||||
---
|
||||
title: Appendix Information sent to Microsoft during activation (Windows 10)
|
||||
ms.assetid: 4bfff495-07d0-4385-86e3-7a077cbd64b8
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
description:
|
||||
keywords: vamt, volume activation, activation, windows activation
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 07/27/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Appendix: Information sent to Microsoft during activation
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
**Looking for retail activation?**
|
||||
|
||||
- [Get Help Activating Microsoft Windows](https://go.microsoft.com/fwlink/p/?LinkId=618644)
|
||||
|
||||
When you activate a computer running Windows 10, the following information is sent to Microsoft:
|
||||
|
||||
- The Microsoft product code (a five-digit code that identifies the Windows product you are activating)
|
||||
- A channel ID or site code that identifies how the Windows product was originally obtained
|
||||
|
||||
For example, a channel ID or site code identifies whether the product was originally purchased from a retail store, obtained as an evaluation copy, obtained through a volume licensing program, or preinstalled by a computer manufacturer.
|
||||
|
||||
- The date of installation and whether the installation was successful
|
||||
- Information that helps confirm that your Windows product key has not been altered
|
||||
- Computer make and model
|
||||
- Version information for the operating system and software
|
||||
- Region and language settings
|
||||
- A unique number called a *globally unique identifier*, which is assigned to your computer
|
||||
- Product key (hashed) and product ID
|
||||
- BIOS name, revision number, and revision date
|
||||
- Volume serial number (hashed) of the hard disk drive
|
||||
- The result of the activation check
|
||||
|
||||
This includes error codes and the following information about any activation exploits and related malicious or unauthorized software that was found or disabled:
|
||||
|
||||
- The activation exploit’s identifier
|
||||
- The activation exploit’s current state, such as cleaned or quarantined
|
||||
- Computer manufacturer’s identification
|
||||
- The activation exploit’s file name and hash in addition to a hash of related software components that may indicate the presence of an activation exploit
|
||||
- The name and a hash of the contents of your computer’s startup instructions file
|
||||
- If your Windows license is on a subscription basis, information about how your subscription works
|
||||
|
||||
Standard computer information is also sent, but your computer’s IP address is only retained temporarily.
|
||||
|
||||
## Use of information
|
||||
|
||||
Microsoft uses the information to confirm that you have a licensed copy of the software. Microsoft does not use the information to contact individual consumers.
|
||||
For additional details, see [Windows 10 Privacy Statement](https://go.microsoft.com/fwlink/p/?LinkId=619879).
|
||||
|
||||
## See also
|
||||
|
||||
- [Volume Activation for Windows 10](volume-activation-windows-10.md)
|
||||
|
||||
---
|
||||
title: Appendix Information sent to Microsoft during activation (Windows 10)
|
||||
ms.assetid: 4bfff495-07d0-4385-86e3-7a077cbd64b8
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
description:
|
||||
keywords: vamt, volume activation, activation, windows activation
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 07/27/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Appendix: Information sent to Microsoft during activation
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
**Looking for retail activation?**
|
||||
|
||||
- [Get Help Activating Microsoft Windows](https://go.microsoft.com/fwlink/p/?LinkId=618644)
|
||||
|
||||
When you activate a computer running Windows 10, the following information is sent to Microsoft:
|
||||
|
||||
- The Microsoft product code (a five-digit code that identifies the Windows product you are activating)
|
||||
- A channel ID or site code that identifies how the Windows product was originally obtained
|
||||
|
||||
For example, a channel ID or site code identifies whether the product was originally purchased from a retail store, obtained as an evaluation copy, obtained through a volume licensing program, or preinstalled by a computer manufacturer.
|
||||
|
||||
- The date of installation and whether the installation was successful
|
||||
- Information that helps confirm that your Windows product key has not been altered
|
||||
- Computer make and model
|
||||
- Version information for the operating system and software
|
||||
- Region and language settings
|
||||
- A unique number called a *globally unique identifier*, which is assigned to your computer
|
||||
- Product key (hashed) and product ID
|
||||
- BIOS name, revision number, and revision date
|
||||
- Volume serial number (hashed) of the hard disk drive
|
||||
- The result of the activation check
|
||||
|
||||
This includes error codes and the following information about any activation exploits and related malicious or unauthorized software that was found or disabled:
|
||||
|
||||
- The activation exploit’s identifier
|
||||
- The activation exploit’s current state, such as cleaned or quarantined
|
||||
- Computer manufacturer’s identification
|
||||
- The activation exploit’s file name and hash in addition to a hash of related software components that may indicate the presence of an activation exploit
|
||||
- The name and a hash of the contents of your computer’s startup instructions file
|
||||
- If your Windows license is on a subscription basis, information about how your subscription works
|
||||
|
||||
Standard computer information is also sent, but your computer’s IP address is only retained temporarily.
|
||||
|
||||
## Use of information
|
||||
|
||||
Microsoft uses the information to confirm that you have a licensed copy of the software. Microsoft does not use the information to contact individual consumers.
|
||||
For additional details, see [Windows 10 Privacy Statement](https://go.microsoft.com/fwlink/p/?LinkId=619879).
|
||||
|
||||
## See also
|
||||
|
||||
- [Volume Activation for Windows 10](volume-activation-windows-10.md)
|
||||
|
||||
|
||||
|
||||
@ -1,51 +1,52 @@
|
||||
---
|
||||
title: Import and Export VAMT Data (Windows 10)
|
||||
description: Import and Export VAMT Data
|
||||
ms.assetid: 09a2c595-1a61-4da6-bd46-4ba8763cfd4f
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/25/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Import and Export VAMT Data
|
||||
|
||||
You can use the Volume Activation Management Tool (VAMT) to import product-activation data from a Computer Information List (.cilx or .cil) file into SQL Server, and to export product-activation data into a .cilx file. A .cilx file is an XML file that stores computer and product-activation data.
|
||||
You can import data or export data during the following scenarios:
|
||||
- Import and merge data from previous versions of VAMT.
|
||||
- Export data to use to perform proxy activations.
|
||||
|
||||
**Warning**
|
||||
Editing a .cilx file using an application other than VAMT can corrupt the .cilx file and is not supported.
|
||||
|
||||
## Import VAMT Data
|
||||
|
||||
**To import data into VAMT**
|
||||
1. Open VAMT.
|
||||
2. In the right-side **Actions** pane, click **Import list** to open the **Import List** dialog box.
|
||||
3. In the **Import List** dialog box, navigate to the .cilx file location, select the file, and click **Open**.
|
||||
4. In the **Volume Activation Management Tool** dialog box, click **OK** to begin the import. VAMT displays a progress message while the file is being imported. Click **OK** when a message appears and confirms that the import has completed successfully.
|
||||
|
||||
## Export VAMT Data
|
||||
|
||||
Exporting VAMT data from a non-Internet-connected VAMT host computer is the first step of proxy activation using multiple VAMT hosts. To export product-activation data to a .cilx file:
|
||||
1. In the left-side pane, you can click a product you want to export data for, or click **Products** if the list contains data for all products.
|
||||
2. If you want to export only part of the data in a product list, in the product list view in the center pane select the products you want to export.
|
||||
3. In the right-side **Actions** pane on, click **Export list** to open the **Export List** dialog box.
|
||||
4. In the **Export List** dialog box, click **Browse** to navigate to the .cilx file.
|
||||
5. Under **Export options**, select one of the following data-type options:
|
||||
- Export products and product keys
|
||||
- Export products only
|
||||
- Export proxy activation data only. Selecting this option ensures that the export contains only the licensing information required for the proxy web service to obtain CIDs from Microsoft. No Personally Identifiable Information (PII) is contained in the exported .cilx file when this selection is checked.
|
||||
6. If you have selected products to export, select the **Export selected product rows only** check box.
|
||||
7. Click **Save**. VAMT displays a progress message while the data is being exported. Click **OK** when a message appears and confirms that the export has completed successfully.
|
||||
|
||||
## Related topics
|
||||
|
||||
---
|
||||
title: Import and Export VAMT Data (Windows 10)
|
||||
description: Import and Export VAMT Data
|
||||
ms.assetid: 09a2c595-1a61-4da6-bd46-4ba8763cfd4f
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/25/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Import and Export VAMT Data
|
||||
|
||||
You can use the Volume Activation Management Tool (VAMT) to import product-activation data from a Computer Information List (.cilx or .cil) file into SQL Server, and to export product-activation data into a .cilx file. A .cilx file is an XML file that stores computer and product-activation data.
|
||||
You can import data or export data during the following scenarios:
|
||||
- Import and merge data from previous versions of VAMT.
|
||||
- Export data to use to perform proxy activations.
|
||||
|
||||
**Warning**
|
||||
Editing a .cilx file using an application other than VAMT can corrupt the .cilx file and is not supported.
|
||||
|
||||
## Import VAMT Data
|
||||
|
||||
**To import data into VAMT**
|
||||
1. Open VAMT.
|
||||
2. In the right-side **Actions** pane, click **Import list** to open the **Import List** dialog box.
|
||||
3. In the **Import List** dialog box, navigate to the .cilx file location, select the file, and click **Open**.
|
||||
4. In the **Volume Activation Management Tool** dialog box, click **OK** to begin the import. VAMT displays a progress message while the file is being imported. Click **OK** when a message appears and confirms that the import has completed successfully.
|
||||
|
||||
## Export VAMT Data
|
||||
|
||||
Exporting VAMT data from a non-Internet-connected VAMT host computer is the first step of proxy activation using multiple VAMT hosts. To export product-activation data to a .cilx file:
|
||||
1. In the left-side pane, you can click a product you want to export data for, or click **Products** if the list contains data for all products.
|
||||
2. If you want to export only part of the data in a product list, in the product list view in the center pane select the products you want to export.
|
||||
3. In the right-side **Actions** pane on, click **Export list** to open the **Export List** dialog box.
|
||||
4. In the **Export List** dialog box, click **Browse** to navigate to the .cilx file.
|
||||
5. Under **Export options**, select one of the following data-type options:
|
||||
- Export products and product keys
|
||||
- Export products only
|
||||
- Export proxy activation data only. Selecting this option ensures that the export contains only the licensing information required for the proxy web service to obtain CIDs from Microsoft. No Personally Identifiable Information (PII) is contained in the exported .cilx file when this selection is checked.
|
||||
6. If you have selected products to export, select the **Export selected product rows only** check box.
|
||||
7. Click **Save**. VAMT displays a progress message while the data is being exported. Click **OK** when a message appears and confirms that the export has completed successfully.
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Perform Proxy Activation](proxy-activation-vamt.md)
|
||||
|
||||
@ -1,34 +1,35 @@
|
||||
---
|
||||
title: Install and Configure VAMT (Windows 10)
|
||||
description: Install and Configure VAMT
|
||||
ms.assetid: 5c7ae9b9-0dbc-4277-bc4f-8b3e4ab0bf50
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 07/27/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Install and Configure VAMT
|
||||
|
||||
This section describes how to install and configure the Volume Activation Management Tool (VAMT).
|
||||
|
||||
## In this Section
|
||||
|
||||
|Topic |Description |
|
||||
|------|------------|
|
||||
|[VAMT Requirements](vamt-requirements.md) |Provides system requirements for installing VAMT on a host computer. |
|
||||
|[Install VAMT](install-vamt.md) |Describes how to get and install VAMT. |
|
||||
|[Configure Client Computers](configure-client-computers-vamt.md) |Describes how to configure client computers on your network to work with VAMT. |
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Introduction to VAMT](introduction-vamt.md)
|
||||
|
||||
---
|
||||
title: Install and Configure VAMT (Windows 10)
|
||||
description: Install and Configure VAMT
|
||||
ms.assetid: 5c7ae9b9-0dbc-4277-bc4f-8b3e4ab0bf50
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 07/27/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Install and Configure VAMT
|
||||
|
||||
This section describes how to install and configure the Volume Activation Management Tool (VAMT).
|
||||
|
||||
## In this Section
|
||||
|
||||
|Topic |Description |
|
||||
|------|------------|
|
||||
|[VAMT Requirements](vamt-requirements.md) |Provides system requirements for installing VAMT on a host computer. |
|
||||
|[Install VAMT](install-vamt.md) |Describes how to get and install VAMT. |
|
||||
|[Configure Client Computers](configure-client-computers-vamt.md) |Describes how to configure client computers on your network to work with VAMT. |
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Introduction to VAMT](introduction-vamt.md)
|
||||
|
||||
|
||||
|
||||
@ -1,43 +1,44 @@
|
||||
---
|
||||
title: Install a KMS Client Key (Windows 10)
|
||||
description: Install a KMS Client Key
|
||||
ms.assetid: d234468e-7917-4cf5-b0a8-4968454f7759
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 07/27/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Install a KMS Client Key
|
||||
|
||||
You can use the Volume Activation Management Tool (VAMT) to install Generic Volume License Key (GVLK), or KMS client, product keys. For example, if you are converting a MAK-activated product to KMS activation.
|
||||
|
||||
**Note**
|
||||
By default, volume license editions of Windows Vista, Windows® 7, Windows 8, Windows 10, Windows Server 2008, Windows Server 2008 R2, Windows Server® 2012, and Microsoft® Office 2010 use KMS for activation. GVLKs are already installed in volume license editions of these products.
|
||||
|
||||
**To install a KMS Client key**
|
||||
1. Open VAMT.
|
||||
2. In the left-side pane click **Products** to open the product list view in the center pane.
|
||||
3. In the products list view in the center pane, select the products that need to have GVLKs installed. You can use the **Filter** function to narrow your search for computers by clicking **Filter** in the right-side pane to open the **Filter Products** dialog box.
|
||||
4. In the **Filter Products** dialog box, you can filter the list by computer name, product name, product key type, license status, or by any combination of these options.
|
||||
- To filter the list by computer name, enter a name in the **Computer Name** box.
|
||||
- To filter the list by Product Name, Product Key Type, or License Status, click the list you want to use for the filter and select an option. If necessary, click **clear all filters** to create a new filter.
|
||||
5. Click **Filter**. VAMT displays the filtered list in the center pane.
|
||||
6. Click **Install product key** in the **Selected Items** menu in the right-side pane to display the **Install Product Key** dialog box.
|
||||
7. The **Install Product Key** dialog box displays the keys that are available to be installed.
|
||||
8. Select the **Automatically select an AD or KMS client key** option and then click **Install Key**.
|
||||
|
||||
VAMT displays the **Installing product key** dialog box while it attempts to install the product key for the selected products. When the process is finished, the status appears in the **Action Status** column of the dialog box. Click **Close** to close the dialog box. You can also click the **Automatically close when done** check box when the dialog box appears.
|
||||
|
||||
The same status is shown under the **Status of Last Action** column in the product list view in the center pane.
|
||||
|
||||
## Related topics
|
||||
|
||||
---
|
||||
title: Install a KMS Client Key (Windows 10)
|
||||
description: Install a KMS Client Key
|
||||
ms.assetid: d234468e-7917-4cf5-b0a8-4968454f7759
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 07/27/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Install a KMS Client Key
|
||||
|
||||
You can use the Volume Activation Management Tool (VAMT) to install Generic Volume License Key (GVLK), or KMS client, product keys. For example, if you are converting a MAK-activated product to KMS activation.
|
||||
|
||||
**Note**
|
||||
By default, volume license editions of Windows Vista, Windows® 7, Windows 8, Windows 10, Windows Server 2008, Windows Server 2008 R2, Windows Server® 2012, and Microsoft® Office 2010 use KMS for activation. GVLKs are already installed in volume license editions of these products.
|
||||
|
||||
**To install a KMS Client key**
|
||||
1. Open VAMT.
|
||||
2. In the left-side pane click **Products** to open the product list view in the center pane.
|
||||
3. In the products list view in the center pane, select the products that need to have GVLKs installed. You can use the **Filter** function to narrow your search for computers by clicking **Filter** in the right-side pane to open the **Filter Products** dialog box.
|
||||
4. In the **Filter Products** dialog box, you can filter the list by computer name, product name, product key type, license status, or by any combination of these options.
|
||||
- To filter the list by computer name, enter a name in the **Computer Name** box.
|
||||
- To filter the list by Product Name, Product Key Type, or License Status, click the list you want to use for the filter and select an option. If necessary, click **clear all filters** to create a new filter.
|
||||
5. Click **Filter**. VAMT displays the filtered list in the center pane.
|
||||
6. Click **Install product key** in the **Selected Items** menu in the right-side pane to display the **Install Product Key** dialog box.
|
||||
7. The **Install Product Key** dialog box displays the keys that are available to be installed.
|
||||
8. Select the **Automatically select an AD or KMS client key** option and then click **Install Key**.
|
||||
|
||||
VAMT displays the **Installing product key** dialog box while it attempts to install the product key for the selected products. When the process is finished, the status appears in the **Action Status** column of the dialog box. Click **Close** to close the dialog box. You can also click the **Automatically close when done** check box when the dialog box appears.
|
||||
|
||||
The same status is shown under the **Status of Last Action** column in the product list view in the center pane.
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Perform KMS Activation](kms-activation-vamt.md)
|
||||
|
||||
@ -1,45 +1,46 @@
|
||||
---
|
||||
title: Install a Product Key (Windows 10)
|
||||
description: Install a Product Key
|
||||
ms.assetid: 78812c87-2208-4f8b-9c2c-5a8a18b2d648
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 07/27/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Install a Product Key
|
||||
|
||||
You can use the Volume Activation Management Tool (VAMT) to install retail, Multiple Activation Key (MAK), and KMS Host key (CSVLK).
|
||||
|
||||
**To install a Product key**
|
||||
1. Open VAMT.
|
||||
2. In the left-side pane, click the product that you want to install keys onto.
|
||||
3. You can use the **Filter** function to narrow your search for computers by clicking **Filter** in the right-side pane to open the **Filter Products** dialog box.
|
||||
4. In the **Filter Products** dialog box, you can filter the list by computer name, product name, product key type, license status, or by any combination of these options.
|
||||
- To filter the list by computer name, enter a name in the **Computer Name** box.
|
||||
- To filter the list by Product Name, Product Key Type, or License Status, click the list you want to use for the filter and select an option. If necessary, click **clear all filters** to create a new filter.
|
||||
5. Click **Filter**.
|
||||
6. In the products list view in the center pane, sort the list if needed and then select the products that need to have keys installed. You can use the **CTRL** key or the **SHIFT** key to select more than one product.
|
||||
7. Click **Install product key** in the **Selected Items** menu in the right-side pane to display the **Install Product Key** dialog box.
|
||||
8. The **Select Product Key** dialog box displays the keys that are available to be installed. Under **Recommended MAKs**, VAMT might display one or more recommended MAK based on the selected products. You can select a recommended product key or a product key from the **All Product Keys** list. Use the scroll bar if you need to view the **Description** for each key. When you have selected the product key you want to install, click **Install Key**. Note that only one key can be installed at a time.
|
||||
9. VAMT displays the **Installing product key** dialog box while it attempts to install the product key for the selected products. When the process is finished, the status appears in the **Action Status** column of the dialog box. Click **Close** to close the dialog box. You can also click the **Automatically close when done** check box when the dialog box appears.
|
||||
|
||||
The same status is shown under the **Status of Last Action** column in the product list view in the center pane.
|
||||
|
||||
**Note**
|
||||
Product key installation will fail if VAMT finds mismatched key types or editions. VAMT will display the failure status and will continue the installation for the next product in the list. For more information on choosing the correct MAK or KMS Host key (CSVLK), see [How to Choose the Right
|
||||
Volume License Key for Windows](https://go.microsoft.com/fwlink/p/?linkid=238382).
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Manage Product Keys](manage-product-keys-vamt.md)
|
||||
|
||||
---
|
||||
title: Install a Product Key (Windows 10)
|
||||
description: Install a Product Key
|
||||
ms.assetid: 78812c87-2208-4f8b-9c2c-5a8a18b2d648
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 07/27/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Install a Product Key
|
||||
|
||||
You can use the Volume Activation Management Tool (VAMT) to install retail, Multiple Activation Key (MAK), and KMS Host key (CSVLK).
|
||||
|
||||
**To install a Product key**
|
||||
1. Open VAMT.
|
||||
2. In the left-side pane, click the product that you want to install keys onto.
|
||||
3. You can use the **Filter** function to narrow your search for computers by clicking **Filter** in the right-side pane to open the **Filter Products** dialog box.
|
||||
4. In the **Filter Products** dialog box, you can filter the list by computer name, product name, product key type, license status, or by any combination of these options.
|
||||
- To filter the list by computer name, enter a name in the **Computer Name** box.
|
||||
- To filter the list by Product Name, Product Key Type, or License Status, click the list you want to use for the filter and select an option. If necessary, click **clear all filters** to create a new filter.
|
||||
5. Click **Filter**.
|
||||
6. In the products list view in the center pane, sort the list if needed and then select the products that need to have keys installed. You can use the **CTRL** key or the **SHIFT** key to select more than one product.
|
||||
7. Click **Install product key** in the **Selected Items** menu in the right-side pane to display the **Install Product Key** dialog box.
|
||||
8. The **Select Product Key** dialog box displays the keys that are available to be installed. Under **Recommended MAKs**, VAMT might display one or more recommended MAK based on the selected products. You can select a recommended product key or a product key from the **All Product Keys** list. Use the scroll bar if you need to view the **Description** for each key. When you have selected the product key you want to install, click **Install Key**. Note that only one key can be installed at a time.
|
||||
9. VAMT displays the **Installing product key** dialog box while it attempts to install the product key for the selected products. When the process is finished, the status appears in the **Action Status** column of the dialog box. Click **Close** to close the dialog box. You can also click the **Automatically close when done** check box when the dialog box appears.
|
||||
|
||||
The same status is shown under the **Status of Last Action** column in the product list view in the center pane.
|
||||
|
||||
**Note**
|
||||
Product key installation will fail if VAMT finds mismatched key types or editions. VAMT will display the failure status and will continue the installation for the next product in the list. For more information on choosing the correct MAK or KMS Host key (CSVLK), see [How to Choose the Right
|
||||
Volume License Key for Windows](https://go.microsoft.com/fwlink/p/?linkid=238382).
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Manage Product Keys](manage-product-keys-vamt.md)
|
||||
|
||||
|
||||
|
||||
@ -1,66 +1,67 @@
|
||||
---
|
||||
title: Introduction to VAMT (Windows 10)
|
||||
description: Introduction to VAMT
|
||||
ms.assetid: 0439685e-0bae-4967-b0d4-dd84ca6d7fa7
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/25/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Introduction to VAMT
|
||||
|
||||
The Volume Activation Management Tool (VAMT) enables network administrators and other IT professionals to automate and centrally manage the Windows®, Microsoft® Office®, and select other Microsoft products volume and retail activation process. VAMT can manage volume activation using Multiple Activation Keys (MAKs) or the Windows Key Management Service (KMS). VAMT is a standard Microsoft Management Console (MMC) snap-in and can be installed on any computer that has one of the following Windows operating systems: Windows® 7, Windows 8, Windows 8.1, Windows 10,Windows Server 2008 R2, or Windows Server 2012.
|
||||
|
||||
**Note**
|
||||
VAMT can be installed on, and can manage, physical or virtual instances. VAMT cannot detect whether or not the remote products are virtual. As long as the products can respond to Windows Management Instrumentation (WMI) calls, they will be discovered and activated.
|
||||
|
||||
## In this Topic
|
||||
- [Managing Multiple Activation Key (MAK) and Retail Activation](#bkmk-managingmak)
|
||||
- [Managing Key Management Service (KMS) Activation](#bkmk-managingkms)
|
||||
- [Enterprise Environment](#bkmk-enterpriseenvironment)
|
||||
- [VAMT User Interface](#bkmk-userinterface)
|
||||
|
||||
## <a href="" id="bkmk-managingmak"></a>Managing Multiple Activation Key (MAK) and Retail Activation
|
||||
|
||||
You can use a MAK or a retail product key to activate Windows, Windows Server, or Office on an individual computer or a group of computers. VAMT enables two different activation scenarios:
|
||||
- **Online activation.** Many enterprises maintain a single Windows system image or Office installation package for deployment across the enterprise. Occasionally there is also a need to use retail product keys in special situations. Online activation enables you to activate over the Internet any products installed with MAK, KMS host, or retail product keys on 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 installed on client computers that do not have Internet access. The VAMT host computer distributes a MAK, KMS Host key (CSVLK), or retail product key to one or more client products and collects the installation ID (IID) from each client product. The VAMT host sends the IIDs to Microsoft on behalf of the client products and obtains the corresponding Confirmation IDs (CIDs). The VAMT host then installs the CIDs on the client products to complete the activation. Using this method, only the VAMT host computer needs Internet access. You can also activate products installed on computers in a workgroup that is completely isolated from any larger network, by installing a second instance of VAMT on a computer within the workgroup. Then, use removable media to transfer activation data between this new instance of VAMT and the Internet-connected VAMT host.
|
||||
|
||||
## <a href="" id="bkmk-managingkms"></a>Managing Key Management Service (KMS) Activation
|
||||
|
||||
In addition to MAK or retail activation, you can use VAMT to perform volume activation using the Key Management Service (KMS). VAMT can install and activate GVLK (KMS client) keys on client products. GVLKs are the default product keys used by Volume License editions of Windows Vista, Windows 7, Windows 8, Windows 10, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012 as well as Microsoft Office 2010.
|
||||
VAMT treats a KMS Host key (CSVLK) product key identically to a retail-type product key; therefore, the experience for product key entry and activation management are identical for both these product key types.
|
||||
|
||||
## <a href="" id="bkmk-enterpriseenvironment"></a>Enterprise Environment
|
||||
|
||||
VAMT is commonly implemented in enterprise environments. The following illustrates three common environments—Core Network, Secure Zone, and Isolated Lab.
|
||||
|
||||
|
||||
|
||||
In the Core Network environment, all computers are within a common network managed by Active Directory® Domain Services (AD DS). The Secure Zone represents higher-security Core Network computers that have additional firewall protection.
|
||||
The Isolated Lab environment is a workgroup that is physically separate from the Core Network, and its computers do not have Internet access. The network security policy states that no information that could identify a specific computer or user may be transferred out of the Isolated Lab.
|
||||
|
||||
## <a href="" id="bkmk-userinterface"></a>VAMT User Interface
|
||||
|
||||
The following screenshot shows the VAMT graphical user interface.
|
||||
|
||||
|
||||
|
||||
VAMT provides a single, graphical user interface for managing activations, and for performing other activation-related tasks such as:
|
||||
- **Adding and removing computers.** You can use VAMT to discover computers in the local environment. VAMT can discover computers by querying AD DS, workgroups, by individual computer name or IP address, or via a general LDAP query.
|
||||
- **Discovering products.** You can use VAMT to discover Windows, Windows Server, Office, and select other products installed on the client computers.
|
||||
- **Monitoring activation status.** You can collect activation information about each product, including the last 5 characters of the product key being used, the current license state (such as Licensed, Grace, Unlicensed), and the product edition information.
|
||||
- **Managing product keys.** You can store multiple product keys and use VAMT to install these keys to remote client products. You can also determine the number of activations remaining for MAKs.
|
||||
- **Managing activation data.** VAMT stores activation data in a SQL database. VAMT can export this data to other VAMT hosts or to an archive in XML format.
|
||||
|
||||
## Related topics
|
||||
- [VAMT Step-by-Step Scenarios](vamt-step-by-step.md)
|
||||
|
||||
---
|
||||
title: Introduction to VAMT (Windows 10)
|
||||
description: Introduction to VAMT
|
||||
ms.assetid: 0439685e-0bae-4967-b0d4-dd84ca6d7fa7
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/25/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Introduction to VAMT
|
||||
|
||||
The Volume Activation Management Tool (VAMT) enables network administrators and other IT professionals to automate and centrally manage the Windows®, Microsoft® Office®, and select other Microsoft products volume and retail activation process. VAMT can manage volume activation using Multiple Activation Keys (MAKs) or the Windows Key Management Service (KMS). VAMT is a standard Microsoft Management Console (MMC) snap-in and can be installed on any computer that has one of the following Windows operating systems: Windows® 7, Windows 8, Windows 8.1, Windows 10,Windows Server 2008 R2, or Windows Server 2012.
|
||||
|
||||
**Note**
|
||||
VAMT can be installed on, and can manage, physical or virtual instances. VAMT cannot detect whether or not the remote products are virtual. As long as the products can respond to Windows Management Instrumentation (WMI) calls, they will be discovered and activated.
|
||||
|
||||
## In this Topic
|
||||
- [Managing Multiple Activation Key (MAK) and Retail Activation](#bkmk-managingmak)
|
||||
- [Managing Key Management Service (KMS) Activation](#bkmk-managingkms)
|
||||
- [Enterprise Environment](#bkmk-enterpriseenvironment)
|
||||
- [VAMT User Interface](#bkmk-userinterface)
|
||||
|
||||
## <a href="" id="bkmk-managingmak"></a>Managing Multiple Activation Key (MAK) and Retail Activation
|
||||
|
||||
You can use a MAK or a retail product key to activate Windows, Windows Server, or Office on an individual computer or a group of computers. VAMT enables two different activation scenarios:
|
||||
- **Online activation.** Many enterprises maintain a single Windows system image or Office installation package for deployment across the enterprise. Occasionally there is also a need to use retail product keys in special situations. Online activation enables you to activate over the Internet any products installed with MAK, KMS host, or retail product keys on 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 installed on client computers that do not have Internet access. The VAMT host computer distributes a MAK, KMS Host key (CSVLK), or retail product key to one or more client products and collects the installation ID (IID) from each client product. The VAMT host sends the IIDs to Microsoft on behalf of the client products and obtains the corresponding Confirmation IDs (CIDs). The VAMT host then installs the CIDs on the client products to complete the activation. Using this method, only the VAMT host computer needs Internet access. You can also activate products installed on computers in a workgroup that is completely isolated from any larger network, by installing a second instance of VAMT on a computer within the workgroup. Then, use removable media to transfer activation data between this new instance of VAMT and the Internet-connected VAMT host.
|
||||
|
||||
## <a href="" id="bkmk-managingkms"></a>Managing Key Management Service (KMS) Activation
|
||||
|
||||
In addition to MAK or retail activation, you can use VAMT to perform volume activation using the Key Management Service (KMS). VAMT can install and activate GVLK (KMS client) keys on client products. GVLKs are the default product keys used by Volume License editions of Windows Vista, Windows 7, Windows 8, Windows 10, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012 as well as Microsoft Office 2010.
|
||||
VAMT treats a KMS Host key (CSVLK) product key identically to a retail-type product key; therefore, the experience for product key entry and activation management are identical for both these product key types.
|
||||
|
||||
## <a href="" id="bkmk-enterpriseenvironment"></a>Enterprise Environment
|
||||
|
||||
VAMT is commonly implemented in enterprise environments. The following illustrates three common environments—Core Network, Secure Zone, and Isolated Lab.
|
||||
|
||||
|
||||
|
||||
In the Core Network environment, all computers are within a common network managed by Active Directory® Domain Services (AD DS). The Secure Zone represents higher-security Core Network computers that have additional firewall protection.
|
||||
The Isolated Lab environment is a workgroup that is physically separate from the Core Network, and its computers do not have Internet access. The network security policy states that no information that could identify a specific computer or user may be transferred out of the Isolated Lab.
|
||||
|
||||
## <a href="" id="bkmk-userinterface"></a>VAMT User Interface
|
||||
|
||||
The following screenshot shows the VAMT graphical user interface.
|
||||
|
||||
|
||||
|
||||
VAMT provides a single, graphical user interface for managing activations, and for performing other activation-related tasks such as:
|
||||
- **Adding and removing computers.** You can use VAMT to discover computers in the local environment. VAMT can discover computers by querying AD DS, workgroups, by individual computer name or IP address, or via a general LDAP query.
|
||||
- **Discovering products.** You can use VAMT to discover Windows, Windows Server, Office, and select other products installed on the client computers.
|
||||
- **Monitoring activation status.** You can collect activation information about each product, including the last 5 characters of the product key being used, the current license state (such as Licensed, Grace, Unlicensed), and the product edition information.
|
||||
- **Managing product keys.** You can store multiple product keys and use VAMT to install these keys to remote client products. You can also determine the number of activations remaining for MAKs.
|
||||
- **Managing activation data.** VAMT stores activation data in a SQL database. VAMT can export this data to other VAMT hosts or to an archive in XML format.
|
||||
|
||||
## Related topics
|
||||
- [VAMT Step-by-Step Scenarios](vamt-step-by-step.md)
|
||||
|
||||
|
||||
|
||||
@ -1,33 +1,34 @@
|
||||
---
|
||||
title: Manage Activations (Windows 10)
|
||||
description: Manage Activations
|
||||
ms.assetid: 53bad9ed-9430-4f64-a8de-80613870862c
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/25/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Manage Activations
|
||||
|
||||
This section describes how to activate a client computer, by using a variety of activation methods.
|
||||
|
||||
## In this Section
|
||||
|
||||
|Topic |Description |
|
||||
|------|------------|
|
||||
|[Perform Online Activation](online-activation-vamt.md) |Describes how to activate a client computer over the Internet. |
|
||||
|[Perform Proxy Activation](proxy-activation-vamt.md) |Describes how to perform volume activation for client products that do not have Internet access. |
|
||||
|[Perform KMS Activation](kms-activation-vamt.md) |Describes how perform volume activation using the Key Management Service (KMS). |
|
||||
|[Perform Local Reactivation](local-reactivation-vamt.md) |Describes how to reactivate an operating system or Office program that was reinstalled. |
|
||||
|[Activate an Active Directory Forest Online](activate-forest-vamt.md) |Describes how to use Active Directory-Based Activation to online activate an Active Directory forest. |
|
||||
|[Activate by Proxy an Active Directory Forest](activate-forest-by-proxy-vamt.md) |Describes how to use Active Directory-Based Activation to proxy activate an Active Directory forest that is not connected to the Internet. |
|
||||
|
||||
|
||||
---
|
||||
title: Manage Activations (Windows 10)
|
||||
description: Manage Activations
|
||||
ms.assetid: 53bad9ed-9430-4f64-a8de-80613870862c
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/25/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Manage Activations
|
||||
|
||||
This section describes how to activate a client computer, by using a variety of activation methods.
|
||||
|
||||
## In this Section
|
||||
|
||||
|Topic |Description |
|
||||
|------|------------|
|
||||
|[Perform Online Activation](online-activation-vamt.md) |Describes how to activate a client computer over the Internet. |
|
||||
|[Perform Proxy Activation](proxy-activation-vamt.md) |Describes how to perform volume activation for client products that do not have Internet access. |
|
||||
|[Perform KMS Activation](kms-activation-vamt.md) |Describes how perform volume activation using the Key Management Service (KMS). |
|
||||
|[Perform Local Reactivation](local-reactivation-vamt.md) |Describes how to reactivate an operating system or Office program that was reinstalled. |
|
||||
|[Activate an Active Directory Forest Online](activate-forest-vamt.md) |Describes how to use Active Directory-Based Activation to online activate an Active Directory forest. |
|
||||
|[Activate by Proxy an Active Directory Forest](activate-forest-by-proxy-vamt.md) |Describes how to use Active Directory-Based Activation to proxy activate an Active Directory forest that is not connected to the Internet. |
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,29 +1,30 @@
|
||||
---
|
||||
title: Manage Product Keys (Windows 10)
|
||||
description: Manage Product Keys
|
||||
ms.assetid: 4c6c4216-b4b7-437c-904e-4cb257f913cd
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/25/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Manage Product Keys
|
||||
|
||||
This section describes how to add and remove a product key from the Volume Activation Management Tool (VAMT). After you add a product key to VAMT, you can install that product key on a product or products you select in the VAMT database.
|
||||
## In this Section
|
||||
|
||||
|Topic |Description |
|
||||
|------|------------|
|
||||
|[Add and Remove a Product Key](add-remove-product-key-vamt.md) |Describes how to add a product key to the VAMT database. |
|
||||
|[Install a Product Key](install-product-key-vamt.md) |Describes how to install a product key for specific product. |
|
||||
|[Install a KMS Client Key](install-kms-client-key-vamt.md) |Describes how to install a GVLK (KMS client) key. |
|
||||
|
||||
|
||||
---
|
||||
title: Manage Product Keys (Windows 10)
|
||||
description: Manage Product Keys
|
||||
ms.assetid: 4c6c4216-b4b7-437c-904e-4cb257f913cd
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/25/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Manage Product Keys
|
||||
|
||||
This section describes how to add and remove a product key from the Volume Activation Management Tool (VAMT). After you add a product key to VAMT, you can install that product key on a product or products you select in the VAMT database.
|
||||
## In this Section
|
||||
|
||||
|Topic |Description |
|
||||
|------|------------|
|
||||
|[Add and Remove a Product Key](add-remove-product-key-vamt.md) |Describes how to add a product key to the VAMT database. |
|
||||
|[Install a Product Key](install-product-key-vamt.md) |Describes how to install a product key for specific product. |
|
||||
|[Install a KMS Client Key](install-kms-client-key-vamt.md) |Describes how to install a GVLK (KMS client) key. |
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,25 +1,26 @@
|
||||
---
|
||||
title: Manage VAMT Data (Windows 10)
|
||||
description: Manage VAMT Data
|
||||
ms.assetid: 233eefa4-3125-4965-a12d-297a67079dc4
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/25/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Manage VAMT Data
|
||||
|
||||
This section describes how to save, import, export, and merge a Computer Information List (CILX) file using the Volume Activation Management Tool (VAMT).
|
||||
|
||||
## In this Section
|
||||
|Topic |Description |
|
||||
|------|------------|
|
||||
|[Import and Export VAMT Data](import-export-vamt-data.md) |Describes how to import and export VAMT data. |
|
||||
---
|
||||
title: Manage VAMT Data (Windows 10)
|
||||
description: Manage VAMT Data
|
||||
ms.assetid: 233eefa4-3125-4965-a12d-297a67079dc4
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/25/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Manage VAMT Data
|
||||
|
||||
This section describes how to save, import, export, and merge a Computer Information List (CILX) file using the Volume Activation Management Tool (VAMT).
|
||||
|
||||
## In this Section
|
||||
|Topic |Description |
|
||||
|------|------------|
|
||||
|[Import and Export VAMT Data](import-export-vamt-data.md) |Describes how to import and export VAMT data. |
|
||||
|[Use VAMT in Windows PowerShell](use-vamt-in-windows-powershell.md) |Describes how to access Windows PowerShell and how to import the VAMT PowerShell module. |
|
||||
|
||||
@ -1,44 +1,45 @@
|
||||
---
|
||||
title: Monitor activation (Windows 10)
|
||||
ms.assetid: 264a3e86-c880-4be4-8828-bf4c839dfa26
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
description:
|
||||
keywords: vamt, volume activation, activation, windows activation
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Monitor activation
|
||||
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
**Looking for retail activation?**
|
||||
|
||||
- [Get Help Activating Microsoft Windows](https://go.microsoft.com/fwlink/p/?LinkId=618644)
|
||||
|
||||
You can monitor the success of the activation process for a computer running Windows in several ways. The most popular methods include:
|
||||
- Using the Volume Licensing Service Center website to track use of MAK keys.
|
||||
- Using the **Slmgr /dlv** command on a client computer or on the KMS host. (For a full list of options, see [Slmgr.vbs Options](https://technet.microsoft.com/library/ff793433.aspx).)
|
||||
- Viewing the licensing status, which is exposed through Windows Management Instrumentation (WMI); therefore, it is available to non-Microsoft or custom tools that can access WMI. (Windows PowerShell can also access WMI information.)
|
||||
- Most licensing actions and events are recorded in the Event log (ex: Application Log events 12288-12290).
|
||||
- Microsoft System Center Operations Manager and the KMS Management Pack can provide insight and information to users of System Center Operations Manager.
|
||||
- See [Troubleshooting activation error codes](https://docs.microsoft.com/windows-server/get-started/activation-error-codes) for information about troubleshooting procedures for Multiple Activation Key (MAK) or the Key Management Service (KMS).
|
||||
- The VAMT provides a single site from which to manage and monitor volume activations. This is explained in the next section.
|
||||
|
||||
## See also
|
||||
|
||||
---
|
||||
title: Monitor activation (Windows 10)
|
||||
ms.assetid: 264a3e86-c880-4be4-8828-bf4c839dfa26
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
description:
|
||||
keywords: vamt, volume activation, activation, windows activation
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Monitor activation
|
||||
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
**Looking for retail activation?**
|
||||
|
||||
- [Get Help Activating Microsoft Windows](https://go.microsoft.com/fwlink/p/?LinkId=618644)
|
||||
|
||||
You can monitor the success of the activation process for a computer running Windows in several ways. The most popular methods include:
|
||||
- Using the Volume Licensing Service Center website to track use of MAK keys.
|
||||
- Using the **Slmgr /dlv** command on a client computer or on the KMS host. (For a full list of options, see [Slmgr.vbs Options](https://technet.microsoft.com/library/ff793433.aspx).)
|
||||
- Viewing the licensing status, which is exposed through Windows Management Instrumentation (WMI); therefore, it is available to non-Microsoft or custom tools that can access WMI. (Windows PowerShell can also access WMI information.)
|
||||
- Most licensing actions and events are recorded in the Event log (ex: Application Log events 12288-12290).
|
||||
- Microsoft System Center Operations Manager and the KMS Management Pack can provide insight and information to users of System Center Operations Manager.
|
||||
- See [Troubleshooting activation error codes](https://docs.microsoft.com/windows-server/get-started/activation-error-codes) for information about troubleshooting procedures for Multiple Activation Key (MAK) or the Key Management Service (KMS).
|
||||
- The VAMT provides a single site from which to manage and monitor volume activations. This is explained in the next section.
|
||||
|
||||
## See also
|
||||
|
||||
[Volume Activation for Windows 10](volume-activation-windows-10.md)
|
||||
|
||||
@ -1,55 +1,56 @@
|
||||
---
|
||||
title: Perform Online Activation (Windows 10)
|
||||
description: Perform Online Activation
|
||||
ms.assetid: 8381792b-a454-4e66-9b4c-e6e4c9303823
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/25/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Perform Online Activation
|
||||
|
||||
You can use the Volume Activation Management Tool (VAMT) to enable client products to be activated over the Internet. You can install the client products with any kind of product key that is eligible for online activation—Multiple Activation Key (MAK), retail, and Windows Key Management Services (KMS) host key.
|
||||
|
||||
## Requirements
|
||||
|
||||
Before performing online activation, ensure that the network and the VAMT installation meet the following requirements:
|
||||
- VAMT is installed on a central computer that has network access to all client computers.
|
||||
- Both the VAMT host and client computers have Internet access.
|
||||
- The products that you want to activate are added to VAMT.
|
||||
- VAMT has administrative permissions on all computers that you intend to activate, and that Windows Management Instrumentation (WMI) can be accessed through the Windows firewall. For more information, see [Configure Client Computers](configure-client-computers-vamt.md).
|
||||
|
||||
The product keys that are installed on the client products must have a sufficient number of remaining activations. If you are activating a MAK key, you can retrieve the remaining number of activations for that key by selecting the MAK in the product key list in the center pane and then clicking
|
||||
**Refresh product key data online** in the right-side pane. This retrieves the number of remaining activations for the MAK from Microsoft. Note that this step requires Internet access and that the remaining activation count can only be retrieved for MAKs.
|
||||
|
||||
## To Perform an Online Activation
|
||||
|
||||
**To perform an online activation**
|
||||
1. Open VAMT.
|
||||
2. In the products list view in the center pane, sort the list if necessary. You can use the **Filter** function to narrow your search for computers by clicking **Filter** in the right-side pane to open the **Filter Products** dialog box.
|
||||
3. In the **Filter Products** dialog box, you can filter the list by computer name, product name, product key type, license status, or by any combination of these options.
|
||||
- To filter the list by computer name, enter a name in the **Computer Name** box.
|
||||
- To filter the list by Product Name, Product Key Type, or License Status, click the list you want to use for the filter and select an option. If necessary, click **clear all filters** to create a new filter.
|
||||
4. Click **Filter**. VAMT displays the filtered list in the center pane.
|
||||
5. Select the products that you want to activate. You can use the **CTRL** key or the **SHIFT** key to select more than one product.
|
||||
6. Click **Activate** in the **Selected Items** menu in the right-side **Actions** pane and then point to **Activate**. If the **Actions** pane is not displayed, click the Show/Hide Action Pane button, which is located on the toolbar to the right of the Help button.
|
||||
7. Point to **Online activate**, and then select the appropriate credential option. If you click the **Alternate Credentials** option, you will be prompted to enter an alternate user name and password.
|
||||
8. VAMT displays the **Activating products** dialog box until it completes the requested action. When activation is complete, the status appears in the **Action Status** column of the dialog box. Click **Close** to close the dialog box. You can also click the **Automatically close when done** check box when the dialog box appears.
|
||||
|
||||
The same status is shown under the **Status of Last Action** column in the products list view in the center pane.
|
||||
|
||||
**Note**
|
||||
Online activation does not enable you to save the Confirmation IDs (CIDs). As a result, you cannot perform local reactivation.
|
||||
|
||||
**Note**
|
||||
You can use online activation to select products that have different key types and activate the products at the same time.
|
||||
|
||||
## Related topics
|
||||
---
|
||||
title: Perform Online Activation (Windows 10)
|
||||
description: Perform Online Activation
|
||||
ms.assetid: 8381792b-a454-4e66-9b4c-e6e4c9303823
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/25/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Perform Online Activation
|
||||
|
||||
You can use the Volume Activation Management Tool (VAMT) to enable client products to be activated over the Internet. You can install the client products with any kind of product key that is eligible for online activation—Multiple Activation Key (MAK), retail, and Windows Key Management Services (KMS) host key.
|
||||
|
||||
## Requirements
|
||||
|
||||
Before performing online activation, ensure that the network and the VAMT installation meet the following requirements:
|
||||
- VAMT is installed on a central computer that has network access to all client computers.
|
||||
- Both the VAMT host and client computers have Internet access.
|
||||
- The products that you want to activate are added to VAMT.
|
||||
- VAMT has administrative permissions on all computers that you intend to activate, and that Windows Management Instrumentation (WMI) can be accessed through the Windows firewall. For more information, see [Configure Client Computers](configure-client-computers-vamt.md).
|
||||
|
||||
The product keys that are installed on the client products must have a sufficient number of remaining activations. If you are activating a MAK key, you can retrieve the remaining number of activations for that key by selecting the MAK in the product key list in the center pane and then clicking
|
||||
**Refresh product key data online** in the right-side pane. This retrieves the number of remaining activations for the MAK from Microsoft. Note that this step requires Internet access and that the remaining activation count can only be retrieved for MAKs.
|
||||
|
||||
## To Perform an Online Activation
|
||||
|
||||
**To perform an online activation**
|
||||
1. Open VAMT.
|
||||
2. In the products list view in the center pane, sort the list if necessary. You can use the **Filter** function to narrow your search for computers by clicking **Filter** in the right-side pane to open the **Filter Products** dialog box.
|
||||
3. In the **Filter Products** dialog box, you can filter the list by computer name, product name, product key type, license status, or by any combination of these options.
|
||||
- To filter the list by computer name, enter a name in the **Computer Name** box.
|
||||
- To filter the list by Product Name, Product Key Type, or License Status, click the list you want to use for the filter and select an option. If necessary, click **clear all filters** to create a new filter.
|
||||
4. Click **Filter**. VAMT displays the filtered list in the center pane.
|
||||
5. Select the products that you want to activate. You can use the **CTRL** key or the **SHIFT** key to select more than one product.
|
||||
6. Click **Activate** in the **Selected Items** menu in the right-side **Actions** pane and then point to **Activate**. If the **Actions** pane is not displayed, click the Show/Hide Action Pane button, which is located on the toolbar to the right of the Help button.
|
||||
7. Point to **Online activate**, and then select the appropriate credential option. If you click the **Alternate Credentials** option, you will be prompted to enter an alternate user name and password.
|
||||
8. VAMT displays the **Activating products** dialog box until it completes the requested action. When activation is complete, the status appears in the **Action Status** column of the dialog box. Click **Close** to close the dialog box. You can also click the **Automatically close when done** check box when the dialog box appears.
|
||||
|
||||
The same status is shown under the **Status of Last Action** column in the products list view in the center pane.
|
||||
|
||||
**Note**
|
||||
Online activation does not enable you to save the Confirmation IDs (CIDs). As a result, you cannot perform local reactivation.
|
||||
|
||||
**Note**
|
||||
You can use online activation to select products that have different key types and activate the products at the same time.
|
||||
|
||||
## Related topics
|
||||
- [Manage Activations](manage-activations-vamt.md)
|
||||
|
||||
@ -1,35 +1,36 @@
|
||||
---
|
||||
title: Remove Products (Windows 10)
|
||||
description: Remove Products
|
||||
ms.assetid: 4d44379e-dda1-4a8f-8ebf-395b6c0dad8e
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/25/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Remove Products
|
||||
|
||||
To remove one or more products from the Volume Activation Management Tool (VAMT), you can delete them from the product list view in the center pane.
|
||||
|
||||
**To delete one or more products**
|
||||
1. Click a product node in the left-side pane.
|
||||
2. You can use the **Filter** function to narrow your search for computers by clicking **Filter** in the right-side pane to open the **Filter Products** dialog box.
|
||||
3. In the **Filter Products** dialog box, you can filter the list by computer name, product name, product key type, license status, or by any combination of these options.
|
||||
- To filter the list by computer name, enter a name in the **Computer Name** box.
|
||||
- To filter the list by Product Name, Product Key Type, or License Status, click the list you want to use for the filter and select an option. If necessary, click **clear all filters** to create a new filter.
|
||||
4. Click **Filter**. VAMT displays the filtered list in the center pane.
|
||||
5. Select the products you want to delete.
|
||||
6. Click **Delete** in the **Selected Items** menu in the right-side pane.
|
||||
7. On the **Confirm Delete Selected Products** dialog box, click **OK**.
|
||||
|
||||
## Related topics
|
||||
- [Add and Manage Products](add-manage-products-vamt.md)
|
||||
|
||||
---
|
||||
title: Remove Products (Windows 10)
|
||||
description: Remove Products
|
||||
ms.assetid: 4d44379e-dda1-4a8f-8ebf-395b6c0dad8e
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/25/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Remove Products
|
||||
|
||||
To remove one or more products from the Volume Activation Management Tool (VAMT), you can delete them from the product list view in the center pane.
|
||||
|
||||
**To delete one or more products**
|
||||
1. Click a product node in the left-side pane.
|
||||
2. You can use the **Filter** function to narrow your search for computers by clicking **Filter** in the right-side pane to open the **Filter Products** dialog box.
|
||||
3. In the **Filter Products** dialog box, you can filter the list by computer name, product name, product key type, license status, or by any combination of these options.
|
||||
- To filter the list by computer name, enter a name in the **Computer Name** box.
|
||||
- To filter the list by Product Name, Product Key Type, or License Status, click the list you want to use for the filter and select an option. If necessary, click **clear all filters** to create a new filter.
|
||||
4. Click **Filter**. VAMT displays the filtered list in the center pane.
|
||||
5. Select the products you want to delete.
|
||||
6. Click **Delete** in the **Selected Items** menu in the right-side pane.
|
||||
7. On the **Confirm Delete Selected Products** dialog box, click **OK**.
|
||||
|
||||
## Related topics
|
||||
- [Add and Manage Products](add-manage-products-vamt.md)
|
||||
|
||||
|
||||
|
||||
@ -1,48 +1,49 @@
|
||||
---
|
||||
title: Scenario 3 KMS Client Activation (Windows 10)
|
||||
description: Scenario 3 KMS Client Activation
|
||||
ms.assetid: 72b04e8f-cd35-490c-91ab-27ea799b05d0
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/25/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Scenario 3: KMS Client Activation
|
||||
|
||||
In this scenario, you use the Volume Activation Management Tool (VAMT) to activate Key Management Service (KMS) client keys or Generic Volume License Keys (GVLKs). This can be performed on either Core Network or Isolated Lab computers. By default, volume license editions of Windows Vista, Windows® 7, Windows 8, Windows 10, Windows Server 2008, Windows Server 2008 R2, Windows Server® 2012, and Microsoft® Office 2010 use KMS for activation. GVLKs are already installed in volume license editions of these products. You do not have to enter a key to activate a product as a GVLK, unless you are converting a MAK-activated product to a KMS activation. For more information, see [Install a KMS Client Key](install-kms-client-key-vamt.md).
|
||||
|
||||
The procedure that is described below assumes the following:
|
||||
- The KMS Service is enabled and available to all KMS clients.
|
||||
- VAMT has been installed and computers have been added to the VAMT database. See Parts 1 through 4 in either [Scenario 1: Online Activation](scenario-online-activation-vamt.md) or [Scenario 2: Proxy Activation](scenario-proxy-activation-vamt.md) for more information.
|
||||
|
||||
## Activate KMS Clients
|
||||
|
||||
1. Open VAMT.
|
||||
2. To set the KMS activation options, on the menu bar click **View**. Then click **Preferences** to open the **Volume Activation Management Tool Preferences** dialog box.
|
||||
3. In the **Volume Activation Management Tool Preferences** dialog box, under **KMS Management Services host selection** select from the following options:
|
||||
- **Find a KMS host automatically using DNS**. This is the default setting. VAMT will instruct the computer to query the Domain Name Service (DNS) to locate a KMS host and perform activation. If the client contains a registry key with a valid KMS host, that value will be used instead.
|
||||
- **Find a KMS host using DNS in this domain for supported products**. Select this option if you use a specific domain, and enter the name of the domain.
|
||||
- **Use specific KMS host**. Select this option for environments which do not use DNS for KMS host identification, and manually enter the KMS host name and select the KMS host port. VAMT will set the specified KMS host name and KMS host port on the target computer, and then instruct the computer to perform activation with the specific KMS host.
|
||||
4. In the left-side pane, in the **Products** node, click the product that you want to activate.
|
||||
5. In the products list view in the center pane, sort the list if necessary. You can use the **Filter** function to narrow your search for computers by clicking **Filter** in the right-side pane to open the **Filter Products** dialog box.
|
||||
6. In the **Filter Products** dialog box, you can filter the list by computer name, product name, product key type, license status, or by any combination of these options.
|
||||
- To filter the list by computer name, enter a name in the **Computer Name** box.
|
||||
- To filter the list by Product Name, Product Key Type, or License Status, click the list you want to use for the filter and select an option. If necessary, click **clear all filters** to create a new filter.
|
||||
7. Click **Filter**. VAMT displays the filtered list in the center pane.
|
||||
8. Select the products that you want to activate.
|
||||
9. Click **Activate** in the **Selected Items** menu in the right-side **Actions** pane, click **Activate**, point to **Volume activate**, and then click the appropriate credential option. If you click the **Alternate Credentials** option, you will be prompted to enter an alternate user name and password.
|
||||
10. VAMT displays the **Activating products** dialog box until it completes the requested action. When activation is complete, the status appears in the **Action Status** column of the dialog box. Click **Close** to close the dialog box. You can also click the **Automatically close when done** check box when the dialog box appears.
|
||||
|
||||
The same status is shown under the **Status of Last Action** column in the products list view in the center pane.
|
||||
|
||||
## Related topics
|
||||
- [VAMT Step-by-Step Scenarios](vamt-step-by-step.md)
|
||||
|
||||
---
|
||||
title: Scenario 3 KMS Client Activation (Windows 10)
|
||||
description: Scenario 3 KMS Client Activation
|
||||
ms.assetid: 72b04e8f-cd35-490c-91ab-27ea799b05d0
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/25/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Scenario 3: KMS Client Activation
|
||||
|
||||
In this scenario, you use the Volume Activation Management Tool (VAMT) to activate Key Management Service (KMS) client keys or Generic Volume License Keys (GVLKs). This can be performed on either Core Network or Isolated Lab computers. By default, volume license editions of Windows Vista, Windows® 7, Windows 8, Windows 10, Windows Server 2008, Windows Server 2008 R2, Windows Server® 2012, and Microsoft® Office 2010 use KMS for activation. GVLKs are already installed in volume license editions of these products. You do not have to enter a key to activate a product as a GVLK, unless you are converting a MAK-activated product to a KMS activation. For more information, see [Install a KMS Client Key](install-kms-client-key-vamt.md).
|
||||
|
||||
The procedure that is described below assumes the following:
|
||||
- The KMS Service is enabled and available to all KMS clients.
|
||||
- VAMT has been installed and computers have been added to the VAMT database. See Parts 1 through 4 in either [Scenario 1: Online Activation](scenario-online-activation-vamt.md) or [Scenario 2: Proxy Activation](scenario-proxy-activation-vamt.md) for more information.
|
||||
|
||||
## Activate KMS Clients
|
||||
|
||||
1. Open VAMT.
|
||||
2. To set the KMS activation options, on the menu bar click **View**. Then click **Preferences** to open the **Volume Activation Management Tool Preferences** dialog box.
|
||||
3. In the **Volume Activation Management Tool Preferences** dialog box, under **KMS Management Services host selection** select from the following options:
|
||||
- **Find a KMS host automatically using DNS**. This is the default setting. VAMT will instruct the computer to query the Domain Name Service (DNS) to locate a KMS host and perform activation. If the client contains a registry key with a valid KMS host, that value will be used instead.
|
||||
- **Find a KMS host using DNS in this domain for supported products**. Select this option if you use a specific domain, and enter the name of the domain.
|
||||
- **Use specific KMS host**. Select this option for environments which do not use DNS for KMS host identification, and manually enter the KMS host name and select the KMS host port. VAMT will set the specified KMS host name and KMS host port on the target computer, and then instruct the computer to perform activation with the specific KMS host.
|
||||
4. In the left-side pane, in the **Products** node, click the product that you want to activate.
|
||||
5. In the products list view in the center pane, sort the list if necessary. You can use the **Filter** function to narrow your search for computers by clicking **Filter** in the right-side pane to open the **Filter Products** dialog box.
|
||||
6. In the **Filter Products** dialog box, you can filter the list by computer name, product name, product key type, license status, or by any combination of these options.
|
||||
- To filter the list by computer name, enter a name in the **Computer Name** box.
|
||||
- To filter the list by Product Name, Product Key Type, or License Status, click the list you want to use for the filter and select an option. If necessary, click **clear all filters** to create a new filter.
|
||||
7. Click **Filter**. VAMT displays the filtered list in the center pane.
|
||||
8. Select the products that you want to activate.
|
||||
9. Click **Activate** in the **Selected Items** menu in the right-side **Actions** pane, click **Activate**, point to **Volume activate**, and then click the appropriate credential option. If you click the **Alternate Credentials** option, you will be prompted to enter an alternate user name and password.
|
||||
10. VAMT displays the **Activating products** dialog box until it completes the requested action. When activation is complete, the status appears in the **Action Status** column of the dialog box. Click **Close** to close the dialog box. You can also click the **Automatically close when done** check box when the dialog box appears.
|
||||
|
||||
The same status is shown under the **Status of Last Action** column in the products list view in the center pane.
|
||||
|
||||
## Related topics
|
||||
- [VAMT Step-by-Step Scenarios](vamt-step-by-step.md)
|
||||
|
||||
|
||||
|
||||
@ -1,38 +1,39 @@
|
||||
---
|
||||
title: Update Product Status (Windows 10)
|
||||
description: Update Product Status
|
||||
ms.assetid: 39d4abd4-801a-4e8f-9b8c-425a24a96764
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/25/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Update Product Status
|
||||
|
||||
After you add computers to the VAMT database, you need to use the **Update license status** function to add the products that are installed on the computers. You can also use the **Update license status** at any time to retrieve the most current license status for any products in the VAMT database.
|
||||
To retrieve license status, VAMT must have administrative permissions on all selected computers and Windows Management Instrumentation (WMI) must be accessible through the Windows Firewall. In addition, for workgroup computers, a registry key must be created to enable remote administrative actions under User Account Control (UAC). For more information, see [Configure Client Computers](configure-client-computers-vamt.md).
|
||||
|
||||
**Note**
|
||||
The license-status query requires a valid computer name for each system queried. If the VAMT database contains computers that were added without Personally Identifiable Information, computer names will not be available for those computers, and the status for these computers will not be updated.
|
||||
|
||||
## Update the license status of a product
|
||||
|
||||
1. Open VAMT.
|
||||
2. In the **Products** list, select one or more products that need to have their status updated.
|
||||
3. In the right-side **Actions** pane, click **Update license status** and then click a credential option. Choose **Alternate Credentials** only if you are updating products that require administrator credentials different from the ones you used to log into the computer.
|
||||
4. If you are supplying alternate credentials, in the **Windows Security** dialog box type the appropriate user name and password and click **OK**.
|
||||
|
||||
VAMT displays the **Collecting product information** dialog box while it collects the status of all selected products. When the process is finished, the updated licensing status of each product will appear in the product list view in the center pane.
|
||||
|
||||
**Note**
|
||||
If a previously discovered Microsoft Office 2010 product has been uninstalled from the remote computer, updating its licensing status will cause the entry to be deleted from the **Office** product list view, and, consequently, the total number of discovered products will be smaller. However, the Windows installation of the same computer will not be deleted and will always be shown in the **Windows** products list view.
|
||||
|
||||
## Related topics
|
||||
---
|
||||
title: Update Product Status (Windows 10)
|
||||
description: Update Product Status
|
||||
ms.assetid: 39d4abd4-801a-4e8f-9b8c-425a24a96764
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/25/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Update Product Status
|
||||
|
||||
After you add computers to the VAMT database, you need to use the **Update license status** function to add the products that are installed on the computers. You can also use the **Update license status** at any time to retrieve the most current license status for any products in the VAMT database.
|
||||
To retrieve license status, VAMT must have administrative permissions on all selected computers and Windows Management Instrumentation (WMI) must be accessible through the Windows Firewall. In addition, for workgroup computers, a registry key must be created to enable remote administrative actions under User Account Control (UAC). For more information, see [Configure Client Computers](configure-client-computers-vamt.md).
|
||||
|
||||
**Note**
|
||||
The license-status query requires a valid computer name for each system queried. If the VAMT database contains computers that were added without Personally Identifiable Information, computer names will not be available for those computers, and the status for these computers will not be updated.
|
||||
|
||||
## Update the license status of a product
|
||||
|
||||
1. Open VAMT.
|
||||
2. In the **Products** list, select one or more products that need to have their status updated.
|
||||
3. In the right-side **Actions** pane, click **Update license status** and then click a credential option. Choose **Alternate Credentials** only if you are updating products that require administrator credentials different from the ones you used to log into the computer.
|
||||
4. If you are supplying alternate credentials, in the **Windows Security** dialog box type the appropriate user name and password and click **OK**.
|
||||
|
||||
VAMT displays the **Collecting product information** dialog box while it collects the status of all selected products. When the process is finished, the updated licensing status of each product will appear in the product list view in the center pane.
|
||||
|
||||
**Note**
|
||||
If a previously discovered Microsoft Office 2010 product has been uninstalled from the remote computer, updating its licensing status will cause the entry to be deleted from the **Office** product list view, and, consequently, the total number of discovered products will be smaller. However, the Windows installation of the same computer will not be deleted and will always be shown in the **Windows** products list view.
|
||||
|
||||
## Related topics
|
||||
- [Add and Manage Products](add-manage-products-vamt.md)
|
||||
|
||||
@ -1,46 +1,47 @@
|
||||
---
|
||||
title: VAMT Requirements (Windows 10)
|
||||
description: VAMT Requirements
|
||||
ms.assetid: d14d152b-ab8a-43cb-a8fd-2279364007b9
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/25/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# VAMT Requirements
|
||||
|
||||
This topic includes info about the product key and system requirements for VAMT.
|
||||
|
||||
## Product Key Requirements
|
||||
|
||||
The Volume Activation Management Tool (VAMT) can be used to perform activations using any of the following types of product keys.
|
||||
|
||||
|Product key type |Where to obtain |
|
||||
|-----------------|----------------|
|
||||
|<ul><li>Multiple Activation Key (MAK)</li><li>Key Management Service (KMS) host key (CSVLK)</li><li>KMS client setup keys (GVLK)</li></ul> |Volume licensing keys can only be obtained with a signed contract from Microsoft. For more info, see the [Microsoft Volume Licensing portal](https://go.microsoft.com/fwlink/p/?LinkId=227282). |
|
||||
|Retail product keys |Obtained at time of product purchase. |
|
||||
|
||||
## System Requirements
|
||||
|
||||
The following table lists the system requirements for the VAMT host computer.
|
||||
|
||||
| Item | Minimum system requirement |
|
||||
| ---- | ---------------------------|
|
||||
| Computer and Processor | 1 GHz x86 or x64 processor |
|
||||
| Memory | 1 GB RAM for x86 or 2 GB RAM for x64 |
|
||||
| Hard Disk | 16 GB available hard disk space for x86 or 20 GB for x64 |
|
||||
| External Drive | Removable media (Optional) |
|
||||
| Display | 1024x768 or higher resolution monitor |
|
||||
| Network | Connectivity to remote computers via Windows Management Instrumentation (TCP/IP) and Microsoft Activation Web Service on the Internet via HTTPS |
|
||||
| Operating System | Windows 7, Windows 8, Windows 8.1, Windows 10, Windows Server 2008 R2, Windows Server 2012, or later. |
|
||||
| Additional Requirements | <ul><li>Connection to a SQL Server database. For more info, see [Install VAMT](install-vamt.md).</li><li>PowerShell 3.0: For Windows 8, Windows 8.1, Windows 10, and Windows Server 2012, PowerShell is included in the installation. For previous versions of Windows and Windows Server, you must download PowerShell 3.0. To download PowerShell, go to [Download Windows PowerShell 3.0](https://go.microsoft.com/fwlink/p/?LinkId=218356).</li><li>If installing on Windows Server 2008 R2, you must also install .NET Framework 3.51.</li></ul> |
|
||||
|
||||
## Related topics
|
||||
---
|
||||
title: VAMT Requirements (Windows 10)
|
||||
description: VAMT Requirements
|
||||
ms.assetid: d14d152b-ab8a-43cb-a8fd-2279364007b9
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/25/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# VAMT Requirements
|
||||
|
||||
This topic includes info about the product key and system requirements for VAMT.
|
||||
|
||||
## Product Key Requirements
|
||||
|
||||
The Volume Activation Management Tool (VAMT) can be used to perform activations using any of the following types of product keys.
|
||||
|
||||
|Product key type |Where to obtain |
|
||||
|-----------------|----------------|
|
||||
|<ul><li>Multiple Activation Key (MAK)</li><li>Key Management Service (KMS) host key (CSVLK)</li><li>KMS client setup keys (GVLK)</li></ul> |Volume licensing keys can only be obtained with a signed contract from Microsoft. For more info, see the [Microsoft Volume Licensing portal](https://go.microsoft.com/fwlink/p/?LinkId=227282). |
|
||||
|Retail product keys |Obtained at time of product purchase. |
|
||||
|
||||
## System Requirements
|
||||
|
||||
The following table lists the system requirements for the VAMT host computer.
|
||||
|
||||
| Item | Minimum system requirement |
|
||||
| ---- | ---------------------------|
|
||||
| Computer and Processor | 1 GHz x86 or x64 processor |
|
||||
| Memory | 1 GB RAM for x86 or 2 GB RAM for x64 |
|
||||
| Hard Disk | 16 GB available hard disk space for x86 or 20 GB for x64 |
|
||||
| External Drive | Removable media (Optional) |
|
||||
| Display | 1024x768 or higher resolution monitor |
|
||||
| Network | Connectivity to remote computers via Windows Management Instrumentation (TCP/IP) and Microsoft Activation Web Service on the Internet via HTTPS |
|
||||
| Operating System | Windows 7, Windows 8, Windows 8.1, Windows 10, Windows Server 2008 R2, Windows Server 2012, or later. |
|
||||
| Additional Requirements | <ul><li>Connection to a SQL Server database. For more info, see [Install VAMT](install-vamt.md).</li><li>PowerShell 3.0: For Windows 8, Windows 8.1, Windows 10, and Windows Server 2012, PowerShell is included in the installation. For previous versions of Windows and Windows Server, you must download PowerShell 3.0. To download PowerShell, go to [Download Windows PowerShell 3.0](https://go.microsoft.com/fwlink/p/?LinkId=218356).</li><li>If installing on Windows Server 2008 R2, you must also install .NET Framework 3.51.</li></ul> |
|
||||
|
||||
## Related topics
|
||||
- [Install and Configure VAMT](install-configure-vamt.md)
|
||||
|
||||
@ -1,32 +1,33 @@
|
||||
---
|
||||
title: VAMT Step-by-Step Scenarios (Windows 10)
|
||||
description: VAMT Step-by-Step Scenarios
|
||||
ms.assetid: 455c542c-4860-4b57-a1f0-7e2d28e11a10
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/25/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# VAMT Step-by-Step Scenarios
|
||||
|
||||
This section provides step-by-step instructions on implementing the Volume Activation Management Tool (VAMT) in typical environments. VAMT supports many common scenarios; the scenarios in this section describe some of the most common to get you started.
|
||||
|
||||
## In this Section
|
||||
|
||||
|Topic |Description |
|
||||
|------|------------|
|
||||
|[Scenario 1: Online Activation](scenario-online-activation-vamt.md) |Describes how to distribute Multiple Activation Keys (MAKs) to products installed on one or more connected computers within a network, and how to instruct these products to contact Microsoft over the Internet for activation. |
|
||||
|[Scenario 2: Proxy Activation](scenario-proxy-activation-vamt.md) |Describes how to use two VAMT host computers — the first one with Internet access and a second computer within an isolated workgroup — as proxies to perform MAK volume activation for workgroup computers that do not have Internet access. |
|
||||
|[Scenario 3: KMS Client Activation](scenario-kms-activation-vamt.md) |Describes how to use VAMT to configure client products for Key Management Service (KMS) activation. By default, volume license editions of Windows 10, Windows Vista, Windows® 7, Windows 8, Windows Server 2008, Windows Server 2008 R2, or Windows Server® 2012, and Microsoft® Office 2010 use KMS for activation. |
|
||||
|
||||
## Related topics
|
||||
- [Introduction to VAMT](introduction-vamt.md)
|
||||
|
||||
---
|
||||
title: VAMT Step-by-Step Scenarios (Windows 10)
|
||||
description: VAMT Step-by-Step Scenarios
|
||||
ms.assetid: 455c542c-4860-4b57-a1f0-7e2d28e11a10
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/25/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# VAMT Step-by-Step Scenarios
|
||||
|
||||
This section provides step-by-step instructions on implementing the Volume Activation Management Tool (VAMT) in typical environments. VAMT supports many common scenarios; the scenarios in this section describe some of the most common to get you started.
|
||||
|
||||
## In this Section
|
||||
|
||||
|Topic |Description |
|
||||
|------|------------|
|
||||
|[Scenario 1: Online Activation](scenario-online-activation-vamt.md) |Describes how to distribute Multiple Activation Keys (MAKs) to products installed on one or more connected computers within a network, and how to instruct these products to contact Microsoft over the Internet for activation. |
|
||||
|[Scenario 2: Proxy Activation](scenario-proxy-activation-vamt.md) |Describes how to use two VAMT host computers — the first one with Internet access and a second computer within an isolated workgroup — as proxies to perform MAK volume activation for workgroup computers that do not have Internet access. |
|
||||
|[Scenario 3: KMS Client Activation](scenario-kms-activation-vamt.md) |Describes how to use VAMT to configure client products for Key Management Service (KMS) activation. By default, volume license editions of Windows 10, Windows Vista, Windows® 7, Windows 8, Windows Server 2008, Windows Server 2008 R2, or Windows Server® 2012, and Microsoft® Office 2010 use KMS for activation. |
|
||||
|
||||
## Related topics
|
||||
- [Introduction to VAMT](introduction-vamt.md)
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user