mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-20 21:03:42 +00:00
Add periods to alt text
No other changes
This commit is contained in:
Gary Moore
@ -55,7 +55,7 @@ The process proceeds as follows:
|
||||
3. Client computers are activated by receiving the activation object from a domain controller during startup.
|
||||
|
||||
> [!div class="mx-imgBorder"]
|
||||
> 
|
||||
> 
|
||||
|
||||
**Figure 10**. The Active Directory-based activation flow
|
||||
|
||||
@ -80,31 +80,31 @@ When a reactivation event occurs, the client queries AD DS for the activation o
|
||||
|
||||
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
|
||||
|
||||
|
||||
@ -80,39 +80,39 @@ This scenario is commonly used in larger organizations that do not find the over
|
||||
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
|
||||
|
||||
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).
|
||||
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
|
||||
|
||||
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
|
||||
|
||||
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.
|
||||
|
||||
|
||||
|
||||
|
||||
**Figure 9**. Choosing to activate online
|
||||
|
||||
|
||||
@ -99,12 +99,12 @@ A MAK is used for one-time activation with Microsoft’s hosted activation servi
|
||||
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
|
||||
|
||||
|
||||
@ -34,7 +34,7 @@ Before adding computers, ensure that the Windows Management Instrumentation (WMI
|
||||
5. VAMT searches for the specified computers and adds them to the VAMT database. During the search, VAMT displays the **Finding computers** message shown below.
|
||||
To cancel the search, click **Cancel**. When the search is complete the names of the newly-discovered computers appear in the product list view in the center pane.
|
||||
|
||||
|
||||
|
||||
|
||||
**Important**
|
||||
This step adds only the computers to the VAMT database, and not the products that are installed on the computers. To add the products, you need to run the **Update license status** function.
|
||||
|
||||
@ -45,7 +45,7 @@ Enable the VAMT to access client computers using the **Windows Firewall** Contro
|
||||
|
||||
Enable the VAMT to access client computers across multiple subnets using the **Windows Firewall with Advanced Security** Control Panel:
|
||||
|
||||
|
||||
|
||||
|
||||
1. Open the Control Panel and double-click **Administrative Tools**.
|
||||
2. Click **Windows Firewall with Advanced Security**.
|
||||
|
||||
@ -49,7 +49,7 @@ You install VAMT as part of the Windows Assessment and Deployment Kit (ADK) for
|
||||
|
||||
5. On the completion page, note the instance name for your installation, select **Close**, and then select **Yes**.
|
||||
|
||||
|
||||
|
||||
|
||||
### Install VAMT using the ADK
|
||||
|
||||
@ -73,7 +73,7 @@ You install VAMT as part of the Windows Assessment and Deployment Kit (ADK) for
|
||||
|
||||
2. Enter the server instance name (for a remote SQL use the FQDN) and a name for the database, select **Connect**, and then select **Yes** to create the database. See the following image for an example for SQL.
|
||||
|
||||
|
||||
|
||||
|
||||
For remote SQL Server, use `servername.yourdomain.com`.
|
||||
|
||||
|
||||
@ -45,7 +45,7 @@ VAMT treats a KMS Host key (CSVLK) product key identically to a retail-type prod
|
||||
|
||||
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.
|
||||
@ -54,7 +54,7 @@ The Isolated Lab environment is a workgroup that is physically separate from the
|
||||
|
||||
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:
|
||||
|
||||
|
||||
@ -120,7 +120,7 @@ In the core network, a centralized KMS solution is recommended. You can also use
|
||||
|
||||
A typical core network that includes a KMS host is shown in Figure 1.
|
||||
|
||||
|
||||
|
||||
|
||||
**Figure 1**. Typical core network
|
||||
|
||||
@ -140,7 +140,7 @@ If the isolated network cannot communicate with the core network’s KMS server,
|
||||
|
||||
If the network is fully isolated, MAK-independent activation would be the recommended choice, perhaps using the telephone option. But VAMT proxy activation may also be possible. You can also use MAKs to activate new computers during setup, before they are placed in the isolated network.
|
||||
|
||||
|
||||
|
||||
|
||||
**Figure 2**. New KMS host in an isolated network
|
||||
|
||||
@ -222,7 +222,7 @@ The flow of KMS activation is shown in Figure 3, and it follows this sequence:
|
||||
7. If the KMS host has a KMS host key that matches the products in the GVLK, the KMS host sends a single packet back to the client. This packet contains a count of the number of computers that have requested activation from this KMS host.
|
||||
8. If the count exceeds the activation threshold for the product that is being activated, the client is activated. If the activation threshold has not yet been met, the client will try again.
|
||||
|
||||
|
||||
|
||||
|
||||
**Figure 3**. KMS activation flow
|
||||
|
||||
|
||||
@ -25,7 +25,7 @@ In this scenario, the Volume Activation Management Tool (VAMT) is deployed in th
|
||||
- Retail
|
||||
The Secure Zone represents higher-security Core Network computers that have additional firewall protection.
|
||||
|
||||
|
||||
|
||||
|
||||
## In This Topic
|
||||
- [Install and start VAMT on a networked host computer](#bkmk-partone)
|
||||
|
||||
@ -19,7 +19,7 @@ ms.topic: article
|
||||
|
||||
In this scenario, the Volume Activation Management Tool (VAMT) is used to activate products that are installed on workgroup computers in an isolated lab environment. For workgroups which are isolated from the larger network, you can perform proxy activation of Multiple Activation Keys (MAKs), KMS Host keys (CSVLKs), Generic Volume License Keys (GVLKs) (or KMS client keys), or retail keys. Proxy activation is performed by installing a second instance of VAMT on a computer in the isolated workgroup. You can then use removable media to transfer VAMT Computer Information Lists (CILXs) between the instance of VAMT in the isolated workgroup and another VAMT host that has Internet access. The following diagram shows a Multiple Activation Key (MAK) proxy activation scenario:
|
||||
|
||||
|
||||
|
||||
|
||||
## Step 1: Install VAMT on a Workgroup Computer in the Isolated Lab
|
||||
|
||||
|
||||
@ -51,7 +51,7 @@ You can use the VAMT to complete the activation process in products by using MAK
|
||||
|
||||
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
|
||||
|
||||
@ -59,7 +59,7 @@ The VAMT provides an overview of the activation and licensing status of computer
|
||||
|
||||
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
|
||||
|
||||
|
||||
@ -30,7 +30,7 @@ The current known issues with the Volume Activation Management Tool (VAMT), vers
|
||||
|
||||
Another known issue is that when you try to add a Windows 10 Key Management Service (KMS) Host key (CSVLK) or a Windows Server 2012 R2 for Windows 10 CSVLK into VAMT 3.1 (version 10.0.10240.0), you receive the error message shown here.
|
||||
|
||||
|
||||
|
||||
|
||||
This issue occurs because VAMT 3.1 does not contain the correct Pkconfig files to recognize this kind of key. To work around this issue, use one of the following methods.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user