mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-20 21:03:42 +00:00
Links: Windows (2021-03)
This commit is contained in:
David Coulter
@ -134,9 +134,9 @@ To verify your Active Directory-based activation configuration, complete the fol
|
||||
> [!NOTE]
|
||||
> 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 **slmgr.vbs /dlv** command also indicates whether KMS has been used.
|
||||
>
|
||||
> To manage individual activations or apply multiple (mass) activations, please consider using the [VAMT](https://docs.microsoft.com/windows/deployment/volume-activation/volume-activation-management-tool).
|
||||
> To manage individual activations or apply multiple (mass) activations, please consider using the [VAMT](./volume-activation-management-tool.md).
|
||||
|
||||
|
||||
## See also
|
||||
|
||||
- [Volume Activation for Windows 10](volume-activation-windows-10.md)
|
||||
- [Volume Activation for Windows 10](volume-activation-windows-10.md)
|
||||
@ -40,7 +40,7 @@ There are three possible scenarios for volume activation of Windows 10 or Windo
|
||||
- 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/).
|
||||
Check out [Windows 10 Volume Activation Tips](/archive/blogs/askcore/windows-10-volume-activation-tips).
|
||||
|
||||
## Key Management Service in Windows 10
|
||||
|
||||
@ -60,7 +60,7 @@ To activate, use the slmgr.vbs command. Open an elevated command prompt and run
|
||||
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).
|
||||
For more information, see the information for Windows 7 in [Deploy KMS Activation](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn502531(v=ws.11)).
|
||||
|
||||
## Key Management Service in Windows Server 2012 R2
|
||||
|
||||
@ -72,7 +72,7 @@ Installing a KMS host key on a computer running Windows Server allows you to act
|
||||
This scenario is commonly used in larger organizations that do not find the overhead of using a server a burden.
|
||||
|
||||
> [!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](/troubleshoot/windows-server/deployment/error-0xc004f015-activate-windows-10).
|
||||
|
||||
### Configure KMS in Windows Server 2012 R2
|
||||
|
||||
@ -135,7 +135,7 @@ To verify that KMS volume activation works, complete the following steps:
|
||||
|
||||
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).
|
||||
For more information about the use and syntax of slmgr.vbs, see [Slmgr.vbs Options](/windows-server/get-started/activation-slmgr-vbs-options).
|
||||
|
||||
## Key Management Service in earlier versions of Windows
|
||||
|
||||
@ -150,4 +150,4 @@ For detailed instructions, see [Update that enables Windows 8.1 and Windows 8 KM
|
||||
|
||||
## See also
|
||||
|
||||
- [Volume Activation for Windows 10](volume-activation-windows-10.md)
|
||||
- [Volume Activation for Windows 10](volume-activation-windows-10.md)
|
||||
@ -38,7 +38,7 @@ VAMT enables IT Professionals to manage and activate the ADBA object. Activation
|
||||
|
||||
## Related topics
|
||||
|
||||
- [How to Activate an Active Directory Forest Online](https://docs.microsoft.com/windows/deployment/volume-activation/activate-forest-vamt)
|
||||
- [How to Proxy Activate an Active Directory Forest](https://docs.microsoft.com/windows/deployment/volume-activation/activate-forest-by-proxy-vamt)
|
||||
|
||||
- [How to Activate an Active Directory Forest Online](./activate-forest-vamt.md)
|
||||
- [How to Proxy Activate an Active Directory Forest](./activate-forest-by-proxy-vamt.md)
|
||||
|
||||
|
||||
@ -25,7 +25,7 @@ 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).
|
||||
> This procedure only applies to clients running Windows Vista or later. For clients running Windows XP Service Pack 1, see [Connecting Through Windows Firewall](/windows/win32/wmisdk/connecting-to-wmi-remotely-with-vbscript).
|
||||
|
||||
## Configuring the Windows Firewall to allow VAMT access
|
||||
|
||||
@ -97,4 +97,4 @@ The above configurations will open an additional port through the Windows Firewa
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Install and Configure VAMT](install-configure-vamt.md)
|
||||
- [Install and Configure VAMT](install-configure-vamt.md)
|
||||
@ -37,10 +37,9 @@ You can use the Volume Activation Management Tool (VAMT) to install retail, Mult
|
||||
|
||||
**Note**
|
||||
Product key installation will fail if VAMT finds mismatched key types or editions. VAMT will display the failure status and will continue the installation for the next product in the list. For more information on choosing the correct MAK or KMS Host key (CSVLK), see [How to Choose the Right
|
||||
Volume License Key for Windows](https://go.microsoft.com/fwlink/p/?linkid=238382).
|
||||
Volume License Key for Windows](/previous-versions/tn-archive/ee939271(v=technet.10)).
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Manage Product Keys](manage-product-keys-vamt.md)
|
||||
|
||||
|
||||
|
||||
@ -32,8 +32,8 @@ You install VAMT as part of the Windows Assessment and Deployment Kit (ADK) for
|
||||
|
||||
### Requirements
|
||||
|
||||
- [Windows Server with Desktop Experience](https://docs.microsoft.com/windows-server/get-started/getting-started-with-server-with-desktop-experience), with internet access (for the main VAMT console) and all updates applied
|
||||
- Latest version of the [Windows 10 ADK](https://docs.microsoft.com/windows-hardware/get-started/adk-install)
|
||||
- [Windows Server with Desktop Experience](/windows-server/get-started/getting-started-with-server-with-desktop-experience), with internet access (for the main VAMT console) and all updates applied
|
||||
- Latest version of the [Windows 10 ADK](/windows-hardware/get-started/adk-install)
|
||||
- Any supported [SQL Server Express](https://www.microsoft.com/sql-server/sql-server-editions-express) version, the latest is recommended
|
||||
- Alternatively, any supported **full** SQL instance
|
||||
|
||||
@ -53,7 +53,7 @@ You install VAMT as part of the Windows Assessment and Deployment Kit (ADK) for
|
||||
|
||||
### Install VAMT using the ADK
|
||||
|
||||
1. Download the latest version of [Windows 10 ADK](https://docs.microsoft.com/windows-hardware/get-started/adk-install).
|
||||
1. Download the latest version of [Windows 10 ADK](/windows-hardware/get-started/adk-install).
|
||||
|
||||
If an older version is already installed, it is recommended to uninstall the older ADK and install the latest version. Existing VAMT data is maintained in the VAMT database.
|
||||
|
||||
@ -89,4 +89,3 @@ To uninstall VAMT using the **Programs and Features** Control Panel:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -33,13 +33,13 @@ ms.topic: article
|
||||
|
||||
You can monitor the success of the activation process for a computer running Windows in several ways. The most popular methods include:
|
||||
- Using the Volume Licensing Service Center website to track use of MAK keys.
|
||||
- Using the **Slmgr /dlv** command on a client computer or on the KMS host. (For a full list of options, see [Slmgr.vbs Options](https://technet.microsoft.com/library/ff793433.aspx).)
|
||||
- Using the **Slmgr /dlv** command on a client computer or on the KMS host. (For a full list of options, see [Slmgr.vbs Options](/previous-versions//ff793433(v=technet.10)).)
|
||||
- Viewing the licensing status, which is exposed through Windows Management Instrumentation (WMI); therefore, it is available to non-Microsoft or custom tools that can access WMI. (Windows PowerShell can also access WMI information.)
|
||||
- Most licensing actions and events are recorded in the Event log (ex: Application Log events 12288-12290).
|
||||
- Microsoft System Center Operations Manager and the KMS Management Pack can provide insight and information to users of System Center Operations Manager.
|
||||
- See [Troubleshooting activation error codes](https://docs.microsoft.com/windows-server/get-started/activation-error-codes) for information about troubleshooting procedures for Multiple Activation Key (MAK) or the Key Management Service (KMS).
|
||||
- See [Troubleshooting activation error codes](/windows-server/get-started/activation-error-codes) for information about troubleshooting procedures for Multiple Activation Key (MAK) or the Key Management Service (KMS).
|
||||
- The VAMT provides a single site from which to manage and monitor volume activations. This is explained in the next section.
|
||||
|
||||
## See also
|
||||
|
||||
[Volume Activation for Windows 10](volume-activation-windows-10.md)
|
||||
[Volume Activation for Windows 10](volume-activation-windows-10.md)
|
||||
@ -199,7 +199,7 @@ When you create installation media or images for client computers that will be a
|
||||
|
||||
Installation media from Microsoft for Enterprise editions of the Windows operating system may already contain the GVLK. One GVLK is available for each type of installation. The GLVK will not activate the software against Microsoft activation servers, but rather against a KMS or Active Directory-based activation object. In other words, the GVLK does not work unless a valid KMS host key can be found. GVLKs are the only product keys that do not need to be kept confidential.
|
||||
|
||||
Typically, you will not need to manually enter a GVLK unless a computer has been activated with a MAK or a retail key and it is being converted to a KMS activation or to Active Directory-based activation. If you need to locate the GVLK for a particular client edition, see [Appendix A: KMS Client Setup Keys](https://technet.microsoft.com/library/jj612867.aspx).
|
||||
Typically, you will not need to manually enter a GVLK unless a computer has been activated with a MAK or a retail key and it is being converted to a KMS activation or to Active Directory-based activation. If you need to locate the GVLK for a particular client edition, see [Appendix A: KMS Client Setup Keys](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj612867(v=ws.11)).
|
||||
|
||||
### Multiple activation keys
|
||||
|
||||
@ -229,4 +229,3 @@ The flow of KMS activation is shown in Figure 3, and it follows this sequence:
|
||||
## See also
|
||||
- [Volume Activation for Windows 10](volume-activation-windows-10.md)
|
||||
|
||||
|
||||
|
||||
@ -116,7 +116,7 @@ To collect the status from select computers in the database, you can select comp
|
||||
The same status appears under the **Status of Last Action** column in the product list view in the center pane.
|
||||
**Note**
|
||||
|
||||
Product key installation will fail if VAMT finds mismatched key types or editions. VAMT will display the failure status and will continue the installation for the next product in the list. For more information on choosing the correct product key, see [How to Choose the Right Volume License Key for Windows.](https://go.microsoft.com/fwlink/p/?linkid=238382)
|
||||
Product key installation will fail if VAMT finds mismatched key types or editions. VAMT will display the failure status and will continue the installation for the next product in the list. For more information on choosing the correct product key, see [How to Choose the Right Volume License Key for Windows.](/previous-versions/tn-archive/ee939271(v=technet.10))
|
||||
|
||||
## <a href="" id="bkmk-partnine"></a>Step 9: Activate the client products
|
||||
|
||||
@ -134,4 +134,3 @@ To collect the status from select computers in the database, you can select comp
|
||||
## Related topics
|
||||
- [VAMT Step-by-Step Scenarios](vamt-step-by-step.md)
|
||||
|
||||
|
||||
|
||||
@ -99,7 +99,7 @@ To collect the status from select computers in the database, you can select comp
|
||||
The same status appears under the **Status of Last Action** column in the product list view in the center pane.
|
||||
|
||||
**Note**
|
||||
Product key installation will fail if VAMT finds mismatched key types or editions. VAMT displays the failure status and continues the installation for the next product in the list. For more information on choosing the correct product key, see [How to Choose the Right Volume License Key for Windows.](https://go.microsoft.com/fwlink/p/?linkid=238382)
|
||||
Product key installation will fail if VAMT finds mismatched key types or editions. VAMT displays the failure status and continues the installation for the next product in the list. For more information on choosing the correct product key, see [How to Choose the Right Volume License Key for Windows.](/previous-versions/tn-archive/ee939271(v=technet.10))
|
||||
|
||||
**Note**
|
||||
Installing a MAK and overwriting the GVLK on client products must be done with care. If the RTM version of Windows Vista has been installed on the computer for more than 30 days, then its initial grace period has expired. As a result, it will enter Reduced Functionality Mode (RFM) if online activation is not completed successfully before the next logon attempt. However, you can use online activation to recover properly configured computers from RFM, as long as the computers are available on the network. RFM only applies to the RTM version of Windows Vista or the retail editions of Microsoft Office 2010. Windows Vista with SP1 or later, Windows 7, Windows 8, Windows 10, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012, and volume editions of Office 2010 will not enter RFM.
|
||||
@ -168,4 +168,3 @@ If you have captured new images of the computers in the isolated lab, but the un
|
||||
## Related topics
|
||||
- [VAMT Step-by-Step Scenarios](vamt-step-by-step.md)
|
||||
|
||||
|
||||
|
||||
@ -71,10 +71,10 @@ The VAMT stores information in a Microsoft SQL Server database for performance
|
||||
- **Managing activation data**. The VAMT stores activation data in a SQL Server database. The tool can export this data in XML format to other VAMT hosts or to an archive.
|
||||
|
||||
For more information, see:
|
||||
- [Volume Activation Management Tool (VAMT) Overview](https://go.microsoft.com/fwlink/p/?LinkId=618266)
|
||||
- [VAMT Step-by-Step Scenarios](https://go.microsoft.com/fwlink/p/?LinkId=618267)
|
||||
- [Volume Activation Management Tool (VAMT) Overview](./volume-activation-management-tool.md)
|
||||
- [VAMT Step-by-Step Scenarios](./vamt-step-by-step.md)
|
||||
|
||||
## See also
|
||||
- [Volume Activation for Windows 10](volume-activation-windows-10.md)
|
||||
|
||||
|
||||
|
||||
@ -20,7 +20,7 @@ ms.topic: article
|
||||
The Volume Activation Management Tool (VAMT) PowerShell cmdlets can be used to perform the same functions as the Vamt.exe command-line tool.
|
||||
|
||||
**To install PowerShell 3.0**
|
||||
- VAMT PowerShell cmdlets require Windows PowerShell, which is included in Windows 10, Windows 8 and Windows Server® 2012. You can download PowerShell for Windows 7 or other operating systems from the [Microsoft Download Center](https://go.microsoft.com/fwlink/p/?LinkId=218356).
|
||||
- VAMT PowerShell cmdlets require Windows PowerShell, which is included in Windows 10, Windows 8 and Windows Server® 2012. You can download PowerShell for Windows 7 or other operating systems from the [Microsoft Download Center](/powershell/scripting/install/installing-powershell).
|
||||
|
||||
**To install the Windows Assessment and Deployment Kit**
|
||||
- In addition to PowerShell, you must import the VAMT PowerShell module. The module is included in the VAMT 3.0 folder after you install the Windows Assessment and Deployment Kit (Windows ADK).
|
||||
@ -57,7 +57,7 @@ get-help get-VamtProduct -all
|
||||
```
|
||||
|
||||
**Warning**
|
||||
The update-help cmdlet is not supported for VAMT PowerShell cmdlets. To view online help for VAMT cmdlets, you can use the -online option with the get-help cmdlet. For more information, see [Volume Activation Management Tool (VAMT) Cmdlets in Windows PowerShell](https://docs.microsoft.com/powershell/module/vamt).
|
||||
The update-help cmdlet is not supported for VAMT PowerShell cmdlets. To view online help for VAMT cmdlets, you can use the -online option with the get-help cmdlet. For more information, see [Volume Activation Management Tool (VAMT) Cmdlets in Windows PowerShell](/powershell/module/vamt).
|
||||
|
||||
**To view VAMT PowerShell Help sections**
|
||||
|
||||
@ -76,4 +76,4 @@ The update-help cmdlet is not supported for VAMT PowerShell cmdlets. To view onl
|
||||
For example, type:
|
||||
``` powershell
|
||||
get-help get-VamtProduct -examples
|
||||
```
|
||||
```
|
||||
@ -36,7 +36,7 @@ This issue occurs because VAMT 3.1 does not contain the correct Pkconfig files t
|
||||
|
||||
### Method 1
|
||||
|
||||
Do not add the CSVLK to the VAMT 3.1 tool. Instead, use the **slmgr.vbs /ipk \<*CSVLK*>** command to install a CSVLK on a KMS host. In this command, \<*CSVLK*> represents the specific key that you want to install. For more information about how to use the Slmgr.vbs tool, see [Slmgr.vbs options for obtaining volume activation information](https://docs.microsoft.com/windows-server/get-started/activation-slmgr-vbs-options).
|
||||
Do not add the CSVLK to the VAMT 3.1 tool. Instead, use the **slmgr.vbs /ipk \<*CSVLK*>** command to install a CSVLK on a KMS host. In this command, \<*CSVLK*> represents the specific key that you want to install. For more information about how to use the Slmgr.vbs tool, see [Slmgr.vbs options for obtaining volume activation information](/windows-server/get-started/activation-slmgr-vbs-options).
|
||||
|
||||
### Method 2
|
||||
|
||||
@ -60,4 +60,4 @@ On the KMS host computer, perform the following steps:
|
||||
|
||||
1. In the C:\KB3058168\x86_microsoft-windows-s..nent-sku-csvlk-pack_31bf3856ad364e35_6.3.9600.17815_none_bd26b4f34d049716 folder, copy the pkeyconfig-csvlk.xrm-ms file. Paste this file into the C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\VAMT3\pkconfig folder.
|
||||
|
||||
1. Restart VAMT.
|
||||
1. Restart VAMT.
|
||||
@ -41,7 +41,7 @@ The following table lists the system requirements for the VAMT host computer.
|
||||
| Display | 1024x768 or higher resolution monitor |
|
||||
| Network | Connectivity to remote computers via Windows Management Instrumentation (TCP/IP) and Microsoft Activation Web Service on the Internet via HTTPS |
|
||||
| Operating System | Windows 7, Windows 8, Windows 8.1, Windows 10, Windows Server 2008 R2, Windows Server 2012, or later. |
|
||||
| Additional Requirements | <ul><li>Connection to a SQL Server database. For more info, see [Install VAMT](install-vamt.md).</li><li>PowerShell 3.0: For Windows 8, Windows 8.1, Windows 10, and Windows Server 2012, PowerShell is included in the installation. For previous versions of Windows and Windows Server, you must download PowerShell 3.0. To download PowerShell, go to [Download Windows PowerShell 3.0](https://go.microsoft.com/fwlink/p/?LinkId=218356).</li><li>If installing on Windows Server 2008 R2, you must also install .NET Framework 3.51.</li></ul> |
|
||||
| Additional Requirements | <ul><li>Connection to a SQL Server database. For more info, see [Install VAMT](install-vamt.md).</li><li>PowerShell 3.0: For Windows 8, Windows 8.1, Windows 10, and Windows Server 2012, PowerShell is included in the installation. For previous versions of Windows and Windows Server, you must download PowerShell 3.0. To download PowerShell, go to [Download Windows PowerShell 3.0](/powershell/scripting/install/installing-powershell).</li><li>If installing on Windows Server 2008 R2, you must also install .NET Framework 3.51.</li></ul> |
|
||||
|
||||
## Related topics
|
||||
- [Install and Configure VAMT](install-configure-vamt.md)
|
||||
- [Install and Configure VAMT](install-configure-vamt.md)
|
||||
@ -45,9 +45,9 @@ This guide provides information and step-by-step guidance to help you choose a v
|
||||
|
||||
Because most organizations will not immediately switch all computers to Windows 10, practical volume activation strategies must also take in to account how to work with the Windows 8.1, Windows 7, Windows Server 2012, and Windows Server 2008 R2 operating systems. This guide discusses how the new volume activation tools can support earlier operating systems, but it does not discuss the tools that are provided with earlier operating system versions.
|
||||
|
||||
Volume activation -and the need for activation itself- is not new, and this guide does not review all of its concepts and history. You can find additional background in the appendices of this guide. For more information, see [Volume Activation Overview](https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831612(v=ws.11)).
|
||||
Volume activation -and the need for activation itself- is not new, and this guide does not review all of its concepts and history. You can find additional background in the appendices of this guide. For more information, see [Volume Activation Overview](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831612(v=ws.11)).
|
||||
|
||||
If you would like additional information about planning a volume activation deployment specifically for Windows 7 and Windows Server 2008 R2, please see the [Volume Activation Planning Guide for Windows 7](https://go.microsoft.com/fwlink/p/?LinkId=618210).
|
||||
If you would like additional information about planning a volume activation deployment specifically for Windows 7 and Windows Server 2008 R2, please see the [Volume Activation Planning Guide for Windows 7](/previous-versions/tn-archive/dd878528(v=technet.10)).
|
||||
|
||||
To successfully plan and implement a volume activation strategy, you must:
|
||||
|
||||
@ -69,4 +69,4 @@ Keep in mind that the method of activation does not change an organization’s r
|
||||
- [Activate clients running Windows 10](activate-windows-10-clients-vamt.md)
|
||||
- [Monitor activation](monitor-activation-client.md)
|
||||
- [Use the Volume Activation Management Tool](use-the-volume-activation-management-tool-client.md)
|
||||
- [Appendix: Information sent to Microsoft during activation](appendix-information-sent-to-microsoft-during-activation-client.md)
|
||||
- [Appendix: Information sent to Microsoft during activation](appendix-information-sent-to-microsoft-during-activation-client.md)
|
||||
Reference in New Issue
Block a user