mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-16 02:43:43 +00:00
resolving conflicts
This commit is contained in:
Dani Halfin
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Activate by Proxy an Active Directory Forest (Windows 10)
|
||||
description: Learn how to use the active directory-based activation function of the volume activation management tool to activate an active directory (AD) forest by proxy.
|
||||
ms.custom: seo-marvel-apr2020
|
||||
description: Learn how to use the Volume Activation Management Tool (VAMT) Active Directory-Based Activation (ADBA) function to activate by proxy an Active Directory (AD) forest.
|
||||
ms.assetid: 6475fc87-a6f7-4fa8-b0aa-de19f2dea7e5
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Activate an Active Directory Forest Online (Windows 10)
|
||||
description: Learn how to use the active directory-based activation function of the volume activation management tool to activate an active directory (AD) forest online.
|
||||
ms.custom: seo-marvel-apr2020
|
||||
description: Use the Volume Activation Management Tool (VAMT) Active Directory-Based Activation (ADBA) function to activate an Active Directory (AD) forest online.
|
||||
ms.assetid: 9b5bc193-799b-4aa5-9d3e-0e495f7195d3
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -4,7 +4,7 @@ ms.assetid: f2417bfe-7d25-4e82-bc07-de316caa8dac
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
description: Learn about the three possible scenarios for volume activation of Windows 10 or Windows Server 2012 R2 by using a Key Management Service (KMS) host.
|
||||
description: How to activate using Key Management Service in Windows 10.
|
||||
keywords: vamt, volume activation, activation, windows activation
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -15,28 +15,30 @@ author: greg-lindsay
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 10/16/2017
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-mar2020
|
||||
---
|
||||
|
||||
# Activate using Key Management Service
|
||||
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
- 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)
|
||||
- [Get Help Activating Microsoft Windows 10](https://support.microsoft.com/help/12440/)
|
||||
- [Get Help Activating Microsoft Windows 7 or Windows 8.1 ](https://go.microsoft.com/fwlink/p/?LinkId=618644)
|
||||
|
||||
There are three possible scenarios for volume activation of Windows 10 or Windows Server 2012 R2 by using a Key Management Service (KMS) host:
|
||||
- Host KMS on a computer running Windows 10
|
||||
- Host KMS on a computer running Windows Server 2012 R2
|
||||
- Host KMS on a computer running an earlier version of Windows
|
||||
|
||||
- Host KMS on a computer running Windows 10
|
||||
- Host KMS on a computer running Windows Server 2012 R2
|
||||
- Host KMS on a computer running an earlier version of Windows
|
||||
|
||||
Check out [Windows 10 Volume Activation Tips](https://blogs.technet.microsoft.com/askcore/2015/09/15/windows-10-volume-activation-tips/).
|
||||
|
||||
@ -44,65 +46,68 @@ Check out [Windows 10 Volume Activation Tips](https://blogs.technet.microsoft.co
|
||||
|
||||
Installing a KMS host key on a computer running Windows 10 allows you to activate other computers running Windows 10 against this KMS host and earlier versions of the client operating system, such as Windows 8.1 or Windows 7.
|
||||
Clients locate the KMS server by using resource records in DNS, so some configuration of DNS may be required. This scenario can be beneficial if your organization uses volume activation for clients and MAK-based activation for a smaller number of servers.
|
||||
To enable KMS functionality, a KMS key is installed on a KMS host; then, the host is activated over the Internet or by phone using Microsoft's activation services.
|
||||
To enable KMS functionality, a KMS key is installed on a KMS host; then, the host is activated over the Internet or by phone using Microsoft activation services.
|
||||
|
||||
**Configure KMS in Windows 10**
|
||||
### Configure KMS in Windows 10
|
||||
|
||||
1. Open an elevated command prompt.
|
||||
2. Enter one of the following commands.
|
||||
- To install a KMS key, type **slmgr.vbs /ipk <KmsKey>**.
|
||||
- To activate online, type **slmgr.vbs /ato**.
|
||||
- To activate by using the telephone, type **slui.exe 4**.
|
||||
3. After activating the KMS key, restart the Software Protection Service.
|
||||
To activate, use the slmgr.vbs command. Open an elevated command prompt and run one of the following commands:
|
||||
|
||||
- To install the KMS key, type `slmgr.vbs /ipk <KmsKey>`.
|
||||
- To activate online, type `slmgr.vbs /ato`.
|
||||
- To activate by telephone, follow these steps:
|
||||
1. Run `slmgr.vbs /dti` and confirm the installation ID.
|
||||
2. Call [Microsoft Licensing Activation Centers worldwide telephone numbers](https://www.microsoft.com/licensing/existing-customer/activation-centers) and follow the voice prompts to enter the installation ID that you obtained in step 1 on your telephone.
|
||||
3. Follow the voice prompts and write down the responded 48-digit confirmation ID for OS activation.
|
||||
4. Run `slmgr.vbs /atp \<confirmation ID\>`.
|
||||
|
||||
For more information, see the information for Windows 7 in [Deploy KMS Activation](https://go.microsoft.com/fwlink/p/?LinkId=717032).
|
||||
|
||||
## Key Management Service in Windows Server 2012 R2
|
||||
|
||||
Installing a KMS host key on a computer running Windows Server allows you to activate computers running Windows Server 2012 R2, Windows Server 2008 R2, Windows Server 2008, Windows 10, Windows 8.1, Windows 7, and Windows Vista.
|
||||
|
||||
**Note**
|
||||
You cannot install a client KMS key into the KMS in Windows Server.
|
||||
> [!NOTE]
|
||||
> You cannot install a client KMS key into the KMS in Windows Server.
|
||||
|
||||
This scenario is commonly used in larger organizations that do not find the overhead of using a server a burden.
|
||||
|
||||
**Note**
|
||||
> [!NOTE]
|
||||
> If you receive error 0xC004F015 when trying to activate Windows 10 Enterprise, see [KB 3086418](https://go.microsoft.com/fwlink/p/?LinkId=620687).
|
||||
|
||||
If you receive error 0xC004F015 when trying to activate Windows 10 Enterprise, see [KB 3086418](https://go.microsoft.com/fwlink/p/?LinkId=620687).
|
||||
|
||||
**Configure KMS in Windows Server 2012 R2**
|
||||
### Configure KMS in Windows Server 2012 R2
|
||||
|
||||
1. Sign in to a computer running Windows Server 2012 R2 with an account that has local administrative credentials.
|
||||
2. Launch Server Manager.
|
||||
3. Add the Volume Activation Services role, as shown in Figure 4.
|
||||
|
||||
|
||||
|
||||
**Figure 4**. Adding the Volume Activation Services role in Server Manager\
|
||||
|
||||
|
||||
**Figure 4**. Adding the Volume Activation Services role in Server Manager
|
||||
|
||||
4. When the role installation is complete, click the link to launch the Volume Activation Tools (Figure 5).
|
||||
|
||||
|
||||
|
||||
|
||||
**Figure 5**. Launching the Volume Activation Tools
|
||||
|
||||
5. Select the **Key Management Service (KMS)** option, and specify the computer that will act as the KMS host (Figure 6).
|
||||
5. Select the **Key Management Service (KMS)** option, and specify the computer that will act as the KMS host (Figure 6).
|
||||
This can be the same computer on which you installed the role or another computer. For example, it can be a client computer running Windows 10.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
**Figure 6**. Configuring the computer as a KMS host
|
||||
|
||||
5. Install your KMS host key by typing it in the text box, and then click **Commit** (Figure 7).
|
||||
|
||||
6. Install your KMS host key by typing it in the text box, and then click **Commit** (Figure 7).
|
||||
|
||||
|
||||
|
||||
|
||||
**Figure 7**. Installing your KMS host key
|
||||
|
||||
6. If asked to confirm replacement of an existing key, click **Yes**.
|
||||
7. After the product key is installed, you must activate it. Click **Next** (Figure 8).
|
||||
|
||||
7. If asked to confirm replacement of an existing key, click **Yes**.
|
||||
8. After the product key is installed, you must activate it. Click **Next** (Figure 8).
|
||||
|
||||
|
||||
|
||||
|
||||
**Figure 8**. Activating the software
|
||||
|
||||
The KMS key can be activated online or by phone. See Figure 9.
|
||||
@ -116,31 +121,33 @@ Now that the KMS host is configured, it will begin to listen for activation requ
|
||||
## Verifying the configuration of Key Management Service
|
||||
|
||||
You can verify KMS volume activation from the KMS host server or from the client computer. KMS volume activation requires a minimum threshold of 25 computers before activation requests will be processed. The verification process described here will increment the activation count each time a client computer contacts the KMS host, but unless the activation threshold is reached, the verification will take the form of an error message rather than a confirmation message.
|
||||
**Note**
|
||||
|
||||
If you configured Active Directory-based activation before configuring KMS activation, you must use a client computer that will not first try to activate itself by using Active Directory-based activation. You could use a workgroup computer that is not joined to a domain or a computer running Windows 7 or Windows Server 2008 R2.
|
||||
> [!NOTE]
|
||||
> If you configured Active Directory-based activation before configuring KMS activation, you must use a client computer that will not first try to activate itself by using Active Directory-based activation. You could use a workgroup computer that is not joined to a domain or a computer running Windows 7 or Windows Server 2008 R2.
|
||||
|
||||
To verify that KMS volume activation works, complete the following steps:
|
||||
|
||||
1. On the KMS host, open the event log and confirm that DNS publishing is successful.
|
||||
2. On a client computer, open a Command Prompt window, type **Slmgr.vbs /ato**, and then press ENTER.<p>
|
||||
The **/ato** command causes the operating system to attempt activation by using whichever key has been installed in the operating system. The response should show the license state and detailed Windows version information.
|
||||
3. On a client computer or the KMS host, open an elevated Command Prompt window, type **Slmgr /dlv**, and then press ENTER.<p>
|
||||
1. On the KMS host, open the event log and confirm that DNS publishing is successful.
|
||||
2. On a client computer, open a Command Prompt window, type **Slmgr.vbs /ato**, and then press ENTER.
|
||||
|
||||
The **/dlv** command displays the detailed licensing information. The response should return an error that states that the KMS activation count is too low. This confirms that KMS is functioning correctly, even though the client has not been activated.
|
||||
The **/ato** command causes the operating system to attempt activation by using whichever key has been installed in the operating system. The response should show the license state and detailed Windows version information.
|
||||
3. On a client computer or the KMS host, open an elevated Command Prompt window, type **Slmgr.vbs /dlv**, and then press ENTER.
|
||||
|
||||
For more information about the use and syntax of slmgr.vbs, see [Slmgr.vbs Options](https://go.microsoft.com/fwlink/p/?LinkId=733639).
|
||||
The **/dlv** command displays the detailed licensing information. The response should return an error that states that the KMS activation count is too low. This confirms that KMS is functioning correctly, even though the client has not been activated.
|
||||
|
||||
For more information about the use and syntax of slmgr.vbs, see [Slmgr.vbs Options](https://docs.microsoft.com/windows-server/get-started/activation-slmgr-vbs-options).
|
||||
|
||||
## Key Management Service in earlier versions of Windows
|
||||
|
||||
If you have already established a KMS infrastructure in your organization for an earlier version of Windows, you may want to continue using that infrastructure to activate computers running Windows 10 or Windows Server 2012 R2. Your existing KMS host must be running Windows 7 or later. To upgrade your KMS host, complete the following steps:
|
||||
|
||||
1. Download and install the correct update for your current KMS host operating system. Restart the computer as directed.
|
||||
2. Request a new KMS host key from the Volume Licensing Service Center.
|
||||
3. Install the new KMS host key on your KMS host.
|
||||
4. Activate the new KMS host key by running the slmgr.vbs script.
|
||||
1. Download and install the correct update for your current KMS host operating system. Restart the computer as directed.
|
||||
2. Request a new KMS host key from the Volume Licensing Service Center.
|
||||
3. Install the new KMS host key on your KMS host.
|
||||
4. Activate the new KMS host key by running the slmgr.vbs script.
|
||||
|
||||
For detailed instructions, see [Update that enables Windows 8.1 and Windows 8 KMS hosts to activate a later version of Windows](https://go.microsoft.com/fwlink/p/?LinkId=618265) and [Update that enables Windows 7 and Windows Server 2008 R2 KMS hosts to activate Windows 10](https://go.microsoft.com/fwlink/p/?LinkId=626590).
|
||||
|
||||
## See also
|
||||
- [Volume Activation for Windows 10](volume-activation-windows-10.md)
|
||||
|
||||
- [Volume Activation for Windows 10](volume-activation-windows-10.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,6 +1,6 @@
|
||||
---
|
||||
title: Active Directory-Based Activation Overview (Windows 10)
|
||||
description: Active Directory-Based Activation Overview
|
||||
description: Enable your enterprise to activate its computers through a connection to their domain using Active Directory-Based Activation (ADBA).
|
||||
ms.assetid: c1dac3bd-6a86-4c45-83dd-421e63a398c0
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Add and Manage Products (Windows 10)
|
||||
description: This article contains a list of topics to help you learn how to manage client computers and products in the Volume Activation Management Tool (VAMT).
|
||||
ms.custom: seo-marvel-apr2020
|
||||
description: Add client computers into the Volume Activation Management Tool (VAMT). After you add the computers, you can manage the products that are installed on your network.
|
||||
ms.assetid: a48fbc23-917d-40f7-985c-e49702c05e51
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
@ -20,7 +19,7 @@ ms.topic: article
|
||||
|
||||
This section describes how to add client computers into the Volume Activation Management Tool (VAMT). After the computers are added, you can manage the products that are installed on your network.
|
||||
|
||||
## In this section
|
||||
## In this Section
|
||||
|
||||
|Topic |Description |
|
||||
|------|------------|
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Add and Remove Computers (Windows 10)
|
||||
description: In this article, you will learn about how to manage computers in the Volume Activation Management Tool (VAMT).
|
||||
ms.custom: seo-marvel-apr2020
|
||||
description: The Discover products function on the Volume Activation Management Tool (VAMT) allows you to search the Active Directory domain or a general LDAP query.
|
||||
ms.assetid: cb6f3a78-ece0-4dc7-b086-cb003d82cd52
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Add and Remove a Product Key (Windows 10)
|
||||
description: In this article, you will learn about how to manage a product key in the Volume Activation Management Tool (VAMT).
|
||||
ms.custom: seo-marvel-apr2020
|
||||
description: Add a product key to the Volume Activation Management Tool (VAMT) database. Also, learn how to remove the key from the database.
|
||||
ms.assetid: feac32bb-fb96-4802-81b8-c69220dcfcce
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -4,7 +4,7 @@ ms.assetid: 4bfff495-07d0-4385-86e3-7a077cbd64b8
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
description: Learn about the information that is sent to Microsoft when you activate a computer running Windows 10.
|
||||
description:
|
||||
keywords: vamt, volume activation, activation, windows activation
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -15,7 +15,6 @@ author: greg-lindsay
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 07/27/2017
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Appendix: Information sent to Microsoft during activation
|
||||
@ -52,21 +51,21 @@ When you activate a computer running Windows 10, the following information is s
|
||||
|
||||
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
|
||||
- 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.
|
||||
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).
|
||||
|
||||
## Related topics
|
||||
## See also
|
||||
|
||||
- [Volume Activation for Windows 10](volume-activation-windows-10.md)
|
||||
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Configure Client Computers (Windows 10)
|
||||
description: In this article, you will learn how to configure client computers to enable Volume Activation Management Tool (VAMT) to function correctly.
|
||||
ms.custom: seo-marvel-apr2020
|
||||
description: Learn how to configure client computers to enable the Volume Activation Management Tool (VAMT) to function correctly.
|
||||
ms.assetid: a48176c9-b05c-4dd5-a9ef-83073e2370fc
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
@ -25,8 +24,8 @@ To enable the Volume Activation Management Tool (VAMT) to function correctly, ce
|
||||
|
||||
Organizations where the VAMT will be widely used may benefit from making these changes inside the master image for Windows.
|
||||
|
||||
> [IMPORTANT]
|
||||
> This procedure only applies to clients running Windows Vista or later. For clients running Windows XP Service Pack 1, see [Connecting Through Windows Firewall](https://docs.microsoft.com/windows/win32/wmisdk/connecting-to-wmi-remotely-with-vbscript).
|
||||
> [IMPORTANT]
|
||||
> This procedure only applies to clients running Windows Vista or later. For clients running Windows XP Service Pack 1, see [Connecting Through Windows Firewall](https://docs.microsoft.com/windows/win32/wmisdk/connecting-to-wmi-remotely-with-vbscript).
|
||||
|
||||
## Configuring the Windows Firewall to allow VAMT access
|
||||
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Import and Export VAMT Data (Windows 10)
|
||||
description: In this article, you'll learn how to import and export data using the Volume Activation Management Tool (VAMT).
|
||||
ms.custom: seo-marvel-apr2020
|
||||
description: Learn how to use the Volume Activation Management Tool (VAMT) to import product-activation data from a .cilx or .cil file into SQL Server.
|
||||
ms.assetid: 09a2c595-1a61-4da6-bd46-4ba8763cfd4f
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Install and Configure VAMT (Windows 10)
|
||||
description: In this article, you'll learn how to install and configure the Volume Activation Management Tool (VAMT).
|
||||
ms.custom: seo-marvel-apr2020
|
||||
description: Learn how to install and configure the Volume Activation Management Tool (VAMT), and learn where to find information about the process.
|
||||
ms.assetid: 5c7ae9b9-0dbc-4277-bc4f-8b3e4ab0bf50
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
@ -21,7 +20,7 @@ ms.topic: article
|
||||
|
||||
This section describes how to install and configure the Volume Activation Management Tool (VAMT).
|
||||
|
||||
## In this section
|
||||
## In this Section
|
||||
|
||||
|Topic |Description |
|
||||
|------|------------|
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Install a KMS Client Key (Windows 10)
|
||||
description: Learn how to use the Volume Activation Management Tool (VAMT) to install Generic Volume License Key (GVLK), or KMS client, product keys.
|
||||
ms.custom: seo-marvel-apr2020
|
||||
description: Learn to use the Volume Activation Management Tool (VAMT) to install Generic Volume License Key (GVLK), or KMS client, product keys.
|
||||
ms.assetid: d234468e-7917-4cf5-b0a8-4968454f7759
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Install a Product Key (Windows 10)
|
||||
description: Learn how to use the Volume Activation Management Tool (VAMT) to install retail, Multiple Activation Key (MAK), and KMS Host key (CSVLK).
|
||||
ms.custom: seo-marvel-apr2020
|
||||
description: Learn to use the Volume Activation Management Tool (VAMT) to install retail, Multiple Activation Key (MAK), and KMS Host key (CSVLK).
|
||||
ms.assetid: 78812c87-2208-4f8b-9c2c-5a8a18b2d648
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Install VAMT (Windows 10)
|
||||
description: Install VAMT
|
||||
description: Learn how to install Volume Activation Management Tool (VAMT) as part of the Windows Assessment and Deployment Kit (ADK) for Windows 10.
|
||||
ms.assetid: 2eabd3e2-0a68-43a5-8189-2947e46482fc
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Introduction to VAMT (Windows 10)
|
||||
description: Learn about VAMT that enables network administrators & other IT professionals to automate and manage the volume & retail activation process for windows & other Microsoft products.
|
||||
ms.custom: seo-marvel-apr2020
|
||||
description: VAMT enables administrators to automate and centrally manage the Windows, Microsoft Office, and select other Microsoft products volume and retail activation process.
|
||||
ms.assetid: 0439685e-0bae-4967-b0d4-dd84ca6d7fa7
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
@ -18,26 +17,28 @@ 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.
|
||||
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.
|
||||
> [!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)
|
||||
## 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.
|
||||
|
||||
- **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.
|
||||
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
|
||||
@ -46,7 +47,7 @@ VAMT is commonly implemented in enterprise environments. The following illustrat
|
||||
|
||||
|
||||
|
||||
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.
|
||||
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
|
||||
@ -56,13 +57,13 @@ 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.
|
||||
|
||||
- **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,7 +1,6 @@
|
||||
---
|
||||
title: Perform KMS Activation (Windows 10)
|
||||
description: In this article, you will learn how to configure devices to perform volume activation using the Key Management Service (KMS).
|
||||
ms.custom: seo-marvel-apr2020
|
||||
description: The Volume Activation Management Tool (VAMT) can be used to perform volume activation using the Key Management Service (KMS).
|
||||
ms.assetid: 5a3ae8e6-083e-4153-837e-ab0a225c1d10
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Perform Local Reactivation (Windows 10)
|
||||
description: In this article, you will learn how to perform local reactivation using the Volume Activation Management Tool (VAMT).
|
||||
ms.custom: seo-marvel-apr2020
|
||||
description: An initially activated a computer using scenarios like MAK, retail, or CSLVK (KMS host), can be reactivated with Volume Activation Management Tool (VAMT).
|
||||
ms.assetid: aacd5ded-da11-4d27-a866-3f57332f5dec
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Manage Activations (Windows 10)
|
||||
description: This article contains a list of topics that can help you with activating a client computer, by using a variety of activation methods.
|
||||
ms.custom: seo-marvel-apr2020
|
||||
description: Learn how to manage activations and how to activate a client computer by using a variety of activation methods.
|
||||
ms.assetid: 53bad9ed-9430-4f64-a8de-80613870862c
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
@ -20,7 +19,7 @@ ms.topic: article
|
||||
|
||||
This section describes how to activate a client computer, by using a variety of activation methods.
|
||||
|
||||
## In this section
|
||||
## In this Section
|
||||
|
||||
|Topic |Description |
|
||||
|------|------------|
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Manage Product Keys (Windows 10)
|
||||
description: In this article, you will learn how to manage product keys from the Volume Activation Management Tool (VAMT).
|
||||
ms.custom: seo-marvel-apr2020
|
||||
description: In this article, learn how to add and remove a product key from the Volume Activation Management Tool (VAMT).
|
||||
ms.assetid: 4c6c4216-b4b7-437c-904e-4cb257f913cd
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
@ -19,7 +18,7 @@ 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
|
||||
## In this Section
|
||||
|
||||
|Topic |Description |
|
||||
|------|------------|
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Manage VAMT Data (Windows 10)
|
||||
description: This article contains a list of topics that can help you with managing data in the Volume Activation Management Tool (VAMT).
|
||||
ms.custom: seo-marvel-apr2020
|
||||
description: Learn how to save, import, export, and merge a Computer Information List (CILX) file using the Volume Activation Management Tool (VAMT).
|
||||
ms.assetid: 233eefa4-3125-4965-a12d-297a67079dc4
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
@ -20,7 +19,7 @@ ms.topic: article
|
||||
|
||||
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
|
||||
## In this Section
|
||||
|Topic |Description |
|
||||
|------|------------|
|
||||
|[Import and Export VAMT Data](import-export-vamt-data.md) |Describes how to import and export VAMT data. |
|
||||
|
||||
@ -4,7 +4,7 @@ ms.assetid: 264a3e86-c880-4be4-8828-bf4c839dfa26
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
description: Learn several ways to monitor the success of the activation process for a computer running Microsoft Windows 10.
|
||||
description:
|
||||
keywords: vamt, volume activation, activation, windows activation
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -14,7 +14,6 @@ audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Monitor activation
|
||||
@ -41,6 +40,6 @@ You can monitor the success of the activation process for a computer running Win
|
||||
- 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.
|
||||
|
||||
## Related topics
|
||||
## See also
|
||||
|
||||
[Volume Activation for Windows 10](volume-activation-windows-10.md)
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Perform Online Activation (Windows 10)
|
||||
description: In this article, you will learn how to perform online activation of the client products using the Volume Activation Management Tool (VAMT).
|
||||
ms.custom: seo-marvel-apr2020
|
||||
description: Learn how to use the Volume Activation Management Tool (VAMT) to enable client products to be activated online.
|
||||
ms.assetid: 8381792b-a454-4e66-9b4c-e6e4c9303823
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Perform Proxy Activation (Windows 10)
|
||||
description: In this article, you will learn how to use VAMT to perform proxy activation of the client products that do not have internet access.
|
||||
ms.custom: seo-marvel-apr2020
|
||||
description: Perform proxy activation by using the Volume Activation Management Tool (VAMT) to activate client computers that do not have Internet access.
|
||||
ms.assetid: 35a919ed-f1cc-4d10-9c88-9bd634549dc3
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Remove Products (Windows 10)
|
||||
description: In this article, you will learn how to remove products from the Volume Activation Management Tool (VAMT).
|
||||
ms.custom: seo-marvel-apr2020
|
||||
description: Learn how you must delete products from the product list view so you can remove products from the Volume Activation Management Tool (VAMT).
|
||||
ms.assetid: 4d44379e-dda1-4a8f-8ebf-395b6c0dad8e
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Scenario 3 KMS Client Activation (Windows 10)
|
||||
description: Learn how to use the Volume Activation Management Tool (VAMT) to activate Key Management Service (KMS) client keys or Generic Volume License Keys (GVLKs).
|
||||
ms.custom: seo-marvel-apr2020
|
||||
ms.assetid: 72b04e8f-cd35-490c-91ab-27ea799b05d0
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Scenario 1 Online Activation (Windows 10)
|
||||
description: This article presents a scenario on how to use Volume Activation Management Tool (VAMT) to perform online activation for multiple activation keys.
|
||||
ms.custom: seo-marvel-apr2020
|
||||
description: Achieve network access by deploying the Volume Activation Management Tool (VAMT) in a Core Network environment.
|
||||
ms.assetid: 94dba40e-383a-41e4-b74b-9e884facdfd3
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
@ -28,7 +27,7 @@ The Secure Zone represents higher-security Core Network computers that have addi
|
||||
|
||||
|
||||
|
||||
## In this topic
|
||||
## In This Topic
|
||||
- [Install and start VAMT on a networked host computer](#bkmk-partone)
|
||||
- [Configure the Windows Management Instrumentation firewall exception on target computers](#bkmk-parttwo)
|
||||
- [Connect to VAMT database](#bkmk-partthree)
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Scenario 2 Proxy Activation (Windows 10)
|
||||
description: This article presents a scenario on how to use VAMT to activate products that are installed on workgroup computers in an isolated lab environment.
|
||||
ms.custom: seo-marvel-apr2020
|
||||
description: Use the Volume Activation Management Tool (VAMT) to activate products that are installed on workgroup computers in an isolated lab environment.
|
||||
ms.assetid: ed5a8a56-d9aa-4895-918f-dd1898cb2c1a
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Update Product Status (Windows 10)
|
||||
description: "In this article, you will learn how to use Volume Activation Management Tool (VAMT) to update product status for products installed on computers."
|
||||
ms.custom: seo-marvel-apr2020
|
||||
description: Learn how to use the Update license status function to add the products that are installed on the computers.
|
||||
ms.assetid: 39d4abd4-801a-4e8f-9b8c-425a24a96764
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Use VAMT in Windows PowerShell (Windows 10)
|
||||
description: In this article, you will learn how to use Volume Activation Management Tool (VAMT) in Windows PowerShell.
|
||||
ms.custom: seo-marvel-apr2020
|
||||
description: Learn how to use Volume Activation Management Tool (VAMT) PowerShell cmdlets to perform the same functions as the Vamt.exe command-line tool.
|
||||
ms.assetid: 13e0ceec-d827-4681-a5c3-8704349e3ba9
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: VAMT known issues (Windows 10)
|
||||
description: In this article, you will learn about the known issues with the Volume Activation Management Tool (VAMT).
|
||||
ms.custom: seo-marvel-apr2020
|
||||
description: Find out the current known issues with the Volume Activation Management Tool (VAMT), versions 3.0. and 3.1.
|
||||
ms.assetid: 8992f1f3-830a-4ce7-a248-f3a6377ab77f
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
@ -49,13 +48,13 @@ On the KMS host computer, perform the following steps:
|
||||
|
||||
1. To extract the contents of the update, run the following command:
|
||||
|
||||
```cmd
|
||||
```console
|
||||
expand c:\KB3058168\Windows8.1-KB3058168-x64.msu -f:* C:\KB3058168\
|
||||
```
|
||||
|
||||
1. To extract the contents of Windows8.1-KB3058168-x64.cab, run the following command:
|
||||
|
||||
```cmd
|
||||
```console
|
||||
expand c:\KB3058168\Windows8.1-KB3058168-x64.cab -f:pkeyconfig-csvlk.xrm-ms c:\KB3058168
|
||||
```
|
||||
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: VAMT Requirements (Windows 10)
|
||||
description: This article includes information about the product key and system requirements for Volume Activation Management Tool (VAMT).
|
||||
ms.custom: seo-marvel-apr2020
|
||||
description: In this article, learn about the product key and system requierements for Volume Activation Management Tool (VAMT).
|
||||
ms.assetid: d14d152b-ab8a-43cb-a8fd-2279364007b9
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: VAMT Step-by-Step Scenarios (Windows 10)
|
||||
description: This article contains a list of topics that provide you with step-by-step instructions on implementing VAMT in typical environments.
|
||||
ms.custom: seo-marvel-apr2020
|
||||
description: Learn step-by-step instructions on implementing the Volume Activation Management Tool (VAMT) in typical environments.
|
||||
ms.assetid: 455c542c-4860-4b57-a1f0-7e2d28e11a10
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
@ -20,13 +19,13 @@ ms.topic: article
|
||||
|
||||
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
|
||||
## 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. |
|
||||
|[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