mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-13 05:47:23 +00:00
Cleaning up after conversion
This commit is contained in:
LizRoss
parent
c5eaa43ee9
commit
e873a58245
@ -10,8 +10,6 @@ author: CFaw
|
||||
---
|
||||
|
||||
# Activate using Active Directory-based activation
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
@ -44,7 +42,7 @@ The process proceeds as follows:
|
||||
|
||||
3. Client computers are activated by receiving the activation object from a domain controller during startup.
|
||||
|
||||
|
||||
|
||||
|
||||
**Figure 10**. The Active Directory-based activation flow
|
||||
|
||||
@ -57,14 +55,10 @@ Clients that are activated with Active Directory-based activation will maintain
|
||||
When a reactivation event occurs, the client queries AD DS for the activation object. Client computers examine the activation object and compare it to the local edition as defined by the GVLK. If the object and GVLK match, reactivation occurs. If the AD DS object cannot be retrieved, client computers use KMS activation. If the computer is removed from the domain, when the computer or the Software Protection service is restarted, the operating system will change the status from activated to not activated, and the computer will try to activate with KMS.
|
||||
|
||||
## Step-by-step configuration: Active Directory-based activation
|
||||
|
||||
|
||||
**Note**
|
||||
You must be a member of the local Administrators group on all computers mentioned in these steps. You also need to be a member of the Enterprise Administrators group, because setting up Active Directory-based activation changes forest-wide settings.
|
||||
|
||||
|
||||
|
||||
To configure Active Directory-based activation on Windows Server 2012 R2, complete the following steps:
|
||||
**To configure Active Directory-based activation on Windows Server 2012 R2, complete the following steps:**
|
||||
|
||||
1. Use an account with Domain Administrator and Enterprise Administrator credentials to sign in to a domain controller.
|
||||
|
||||
@ -72,39 +66,37 @@ To configure Active Directory-based activation on Windows Server 2012 R2, comp
|
||||
|
||||
3. Add the Volume Activation Services role, as shown in Figure 11.
|
||||
|
||||
|
||||
|
||||
|
||||
**Figure 11**. Adding the Volume Activation Services role
|
||||
|
||||
4. Click the link to launch the Volume Activation Tools (Figure 12).
|
||||
|
||||
|
||||
|
||||
|
||||
**Figure 12**. Launching the Volume Activation Tools
|
||||
|
||||
5. Select the **Active Directory-Based Activation** option (Figure 13).
|
||||
|
||||
|
||||
|
||||
|
||||
**Figure 13**. Selecting Active Directory-Based Activation
|
||||
|
||||
6. Enter your KMS host key and (optionally) a display name (Figure 14).
|
||||
|
||||
|
||||
|
||||
|
||||
**Figure 14**. Entering your KMS host key
|
||||
|
||||
7. Activate your KMS host key by phone or online (Figure 15).
|
||||
|
||||
|
||||
|
||||
|
||||
**Figure 15**. Choosing how to activate your product
|
||||
|
||||
8. After activating the key, click **Commit**, and then click **Close**.
|
||||
|
||||
## Verifying the configuration of Active Directory-based activation
|
||||
|
||||
|
||||
To verify your Active Directory-based activation configuration, complete the following steps:
|
||||
|
||||
1. After you configure Active Directory-based activation, start a computer that is running an edition of Windows that is configured by volume licensing.
|
||||
@ -119,21 +111,8 @@ To verify your Active Directory-based activation configuration, complete the fol
|
||||
|
||||
6. Scroll down to the **Windows activation** section, and verify that this client has been activated.
|
||||
|
||||
**Note**
|
||||
**Note**<br>
|
||||
If you are using both KMS and Active Directory-based activation, it may be difficult to see whether a client has been activated by KMS or by Active Directory-based activation. Consider disabling KMS during the test, or make sure that you are using a client computer that has not already been activated by KMS. The **slmrg.vbs /dlv** command also indicates whether KMS has been used.
|
||||
|
||||
|
||||
|
||||
## See also
|
||||
|
||||
|
||||
- [Volume Activation for Windows 10](volume-activation-windows-10.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -10,8 +10,6 @@ author: CFaw
|
||||
---
|
||||
|
||||
# Activate clients running Windows 10
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
@ -28,7 +26,9 @@ author: CFaw
|
||||
|
||||
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:
|
||||
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.
|
||||
|
||||
@ -39,12 +39,9 @@ Enterprise edition images and installation media should already be configured wi
|
||||
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.
|
||||
@ -54,7 +51,6 @@ When KMS clients are waiting for the KMS to reach the activation threshold, they
|
||||
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.
|
||||
@ -62,19 +58,15 @@ However, the KMS host only caches twice the number of client IDs that are requir
|
||||
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.
|
||||
@ -84,35 +76,30 @@ If the KMS host that a client computer selects does not respond, the KMS client
|
||||
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](http://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
|
||||
|
||||
@ -121,19 +108,14 @@ A MAK is recommended for computers that rarely or never connect to the corporate
|
||||
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)
|
||||
|
||||
|
||||
|
||||
@ -9,13 +9,9 @@ author: CFaw
|
||||
---
|
||||
|
||||
# Active Directory-Based Activation Overview
|
||||
|
||||
|
||||
Active Directory-Based Activation (ADBA) enables enterprises to activate computers through a connection to their domain. Many companies have computers at offsite locations that use products that are registered to the company. Previously these computers needed to either use a retail key or a Multiple Activation Key (MAK), or physically connect to the network in order to activate their products by using Key Management Services (KMS). ADBA provides a way to activate these products if the computers can join the company’s domain. When the user joins their computer to the domain, the ADBA object automatically activates Windows installed on their computer, as long as the computer has a Generic Volume License Key (GVLK) installed. No single physical computer is required to act as the activation object, because it is distributed throughout the domain.
|
||||
|
||||
## Active Directory-Based Activation Scenarios
|
||||
|
||||
|
||||
VAMT enables IT Professionals to manage and activate the Active Directory-Based Activation object. Activation can be performed by using a scenario such as the following:
|
||||
|
||||
- Online activation: To activate an ADBA forest online, the user selects the **Online activate forest** function, selects a KMS Host key (CSVLK) to use, and gives the Active Directory-Based Activation Object a name.
|
||||
@ -23,11 +19,8 @@ VAMT enables IT Professionals to manage and activate the Active Directory-Based
|
||||
- Proxy activation: For a proxy activation, the user first selects the **Proxy activate forest** function, selects a KMS Host key (CSVLK) to use, gives the Active Directory-Based Activation Object a name, and provides a file name to save the CILx file that contains the Installation ID. Next, the user takes that file to a computer that is running VAMT with an Internet connection and then selects the **Acquire confirmation IDs for CILX** function on the VAMT landing page, and provides the original CILx file. When VAMT has loaded the Confirmation IDs into the original CILx file, the user takes this file back to the original VAMT instance, where the user completes the proxy activation process by selecting the **Apply confirmation ID to Active Directory domain** function.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[How to Activate an Active Directory Forest Online](http://go.microsoft.com/fwlink/p/?LinkId=246565)
|
||||
|
||||
[How to Proxy Activate an Active Directory Forest](http://go.microsoft.com/fwlink/p/?LinkId=246566)
|
||||
- [How to Activate an Active Directory Forest Online](http://go.microsoft.com/fwlink/p/?LinkId=246565)
|
||||
- [How to Proxy Activate an Active Directory Forest](http://go.microsoft.com/fwlink/p/?LinkId=246566)
|
||||
|
||||
|
||||
|
||||
|
||||
@ -10,8 +10,6 @@ author: CFaw
|
||||
---
|
||||
|
||||
# Appendix: Information sent to Microsoft during activation
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
@ -71,15 +69,11 @@ When you activate a computer running Windows 10, the following information is s
|
||||
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](http://go.microsoft.com/fwlink/p/?LinkId=619879).
|
||||
|
||||
## See also
|
||||
|
||||
|
||||
- [Volume Activation for Windows 10](volume-activation-windows-10.md)
|
||||
|
||||
|
||||
|
||||
@ -9,18 +9,12 @@ author: CFaw
|
||||
---
|
||||
|
||||
# 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)
|
||||
@ -29,39 +23,31 @@ VAMT can be installed on, and can manage, physical or virtual instances. VAMT ca
|
||||
|
||||
- [VAMT User Interface](#bkmk-userinterface)
|
||||
|
||||
## <a href="" id="bkmk-managingmak"></a>Managing Multiple Activation Key (MAK) and Retail Activation
|
||||
|
||||
|
||||
## 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
|
||||
|
||||
|
||||
## 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
|
||||
|
||||
|
||||
## 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
|
||||
|
||||
|
||||
## 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:
|
||||
|
||||
@ -76,9 +62,7 @@ VAMT provides a single, graphical user interface for managing activations, and f
|
||||
- **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)
|
||||
- [VAMT Step-by-Step Scenarios](vamt-step-by-step.md)
|
||||
|
||||
|
||||
|
||||
|
||||
@ -10,8 +10,6 @@ author: CFaw
|
||||
---
|
||||
|
||||
# Monitor activation
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
@ -41,8 +39,6 @@ You can monitor the success of the activation process for a computer running Win
|
||||
- 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)
|
||||
|
||||
|
||||
|
||||
@ -10,8 +10,6 @@ author: CFaw
|
||||
---
|
||||
|
||||
# Use the Volume Activation Management Tool
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
@ -35,8 +33,6 @@ The VAMT is distributed as part of the Windows Assessment and Deployment Kit (Wi
|
||||
In Windows Server 2012 R2, you can install the VAMT directly from Server Manager without downloading the Windows ADK by selecting the Volume Activation Services role or the Remote Server Administration Tools/Role Administration Tools/Volume Activation Tools feature.
|
||||
|
||||
## Activating with the Volume Activation Management Tool
|
||||
|
||||
|
||||
You can use the VAMT to complete the activation process in products by using MAK and retail keys, and you can work with computers individually or in groups. The VAMT enables two activation scenarios:
|
||||
|
||||
- **Online activation**. Online activation enables you to activate over the Internet any products that are installed with MAK, KMS host, or retail product keys. You can activate one or more connected computers within a network. This process requires that each product communicate activation information directly to Microsoft.
|
||||
@ -46,26 +42,20 @@ You can use the VAMT to complete the activation process in products by using MAK
|
||||
By using this method, only the VAMT host computer requires Internet access. Proxy activation by using the VAMT is beneficial for isolated network segments and for cases where your organization has a mix of retail, MAK, and KMS-based activations.
|
||||
|
||||
## Tracking products and computers with the Volume Activation Management Tool
|
||||
|
||||
|
||||
The VAMT provides an overview of the activation and licensing status of computers across your network, as shown in Figure 18. Several prebuilt reports are also available to help you proactively manage licensing.
|
||||
|
||||
|
||||
|
||||
|
||||
**Figure 18**. The VAMT showing the licensing status of multiple computers
|
||||
|
||||
## Tracking key usage with the Volume Activation Management Tool
|
||||
|
||||
|
||||
The VAMT makes it easier to track the various keys that are issued to your organization. You can enter each key into VAMT, and then the VAMT can use those keys for online or proxy activation of clients. The tool can also describe what type of key it is and to which product group it belongs. The VAMT is the most convenient way to quickly determine how many activations remain on a MAK. Figure 19 shows an example of key types and usage.
|
||||
|
||||
|
||||
|
||||
|
||||
**Figure 19**. The VAMT showing key types and usage
|
||||
|
||||
## Other Volume Activation Management Tool features
|
||||
|
||||
|
||||
The VAMT stores information in a Microsoft SQL Server database for performance and flexibility, and it provides a single graphical user interface for managing activations and performing other activation-related tasks, such as:
|
||||
|
||||
- **Adding and removing computers**. You can use the VAMT to discover computers in the local environment. The VAMT can discover computers by querying AD DS, workgroups, or individual computer names or IP addresses, or through a general LDAP query.
|
||||
@ -81,8 +71,6 @@ For more information, see:
|
||||
- [VAMT Step-by-Step Scenarios](http://go.microsoft.com/fwlink/p/?LinkId=618267)
|
||||
|
||||
## See also
|
||||
|
||||
|
||||
- [Volume Activation for Windows 10](volume-activation-windows-10.md)
|
||||
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user