mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
Update metadata descriptions 3_30 3
This commit is contained in:
1justingilmore
parent
3af4347ddb
commit
77d7f40264
@ -4,7 +4,7 @@ ms.assetid: 386e6713-5c20-4d2a-a220-a38d94671a38
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
description:
|
||||
description: Learn how to configure your environment for BitLocker, the disk volume encryption built into Windows 10 Enterprise and Windows 10 Pro, using MDT.
|
||||
keywords: disk, encryption, TPM, configure, secure, script
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -14,6 +14,7 @@ ms.pagetype: mdt
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-mar2020
|
||||
---
|
||||
|
||||
# Set up MDT for BitLocker
|
||||
|
||||
@ -4,7 +4,7 @@ ms.assetid: 0ce05f66-9009-4739-a789-60f3ce380e76
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
description:
|
||||
description: The Compatibility Administrator tool helps you resolve potential application-compatibility issues before deploying a new version of Windows.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: plan
|
||||
ms.pagetype: appcompat
|
||||
@ -12,6 +12,7 @@ ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-mar2020
|
||||
---
|
||||
|
||||
# Compatibility Administrator User's Guide
|
||||
|
||||
@ -4,7 +4,7 @@ ms.assetid: fdfbf02f-c4c4-4739-a400-782204fd3c6c
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
description:
|
||||
description: Learn about deploying your compatibility fixes as part of an application-installation package or through a centralized compatibility-fix database.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: plan
|
||||
ms.pagetype: appcompat
|
||||
@ -13,6 +13,7 @@ audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-mar2020
|
||||
---
|
||||
|
||||
# Compatibility Fix Database Management Strategies and Deployment
|
||||
@ -88,7 +89,7 @@ This approach tends to work best for organizations that have a well-developed de
|
||||
|
||||
### Merging Centralized Compatibility-Fix Databases
|
||||
|
||||
If you decide to use the centralized compatibility-fix database deployment strategy, you can merge any of your individual compatibility-fix databases. This enables you to create a single custom compatibility-fix database that can be used to search for and determine whether Windows® should apply a fix to a specific executable (.exe) file. We recommend merging your databases based on the following process.
|
||||
If you decide to use the centralized compatibility-fix database deployment strategy, you can merge any of your individual compatibility-fix databases. This enables you to create a single custom compatibility-fix database that can be used to search for and determine whether Windows® should apply a fix to a specific executable (.exe) file. We recommend merging your databases based on the following process.
|
||||
|
||||
**To merge your custom-compatibility databases**
|
||||
|
||||
@ -113,7 +114,7 @@ If you decide to use the centralized compatibility-fix database deployment strat
|
||||
|
||||
Deploying your custom compatibility-fix database into your organization requires you to perform the following actions:
|
||||
|
||||
1. Store your custom compatibility-fix database (.sdb file) in a location that is accessible to all of your organization’s computers.
|
||||
1. Store your custom compatibility-fix database (.sdb file) in a location that is accessible to all of your organization's computers.
|
||||
|
||||
2. Use the Sdbinst.exe command-line tool to install the custom compatibility-fix database locally.
|
||||
|
||||
@ -124,7 +125,7 @@ In order to meet the two requirements above, we recommend that you use one of th
|
||||
You can package your .sdb file and a custom deployment script into an .msi file, and then deploy the .msi file into your organization.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> You must ensure that you mark your custom script so that it does not impersonate the calling user. For example, if you use Microsoft® Visual Basic® Scripting Edition (VBScript), the custom action type would be:
|
||||
> You must ensure that you mark your custom script so that it does not impersonate the calling user. For example, if you use Microsoft® Visual Basic® Scripting Edition (VBScript), the custom action type would be:
|
||||
>`msidbCustomActionTypeVBScript + msidbCustomActionTypeInScript + msidbCustomActionTypeNoImpersonate = 0x0006 + 0x0400 + 0x0800 = 0x0C06 = 3078 decimal)`
|
||||
|
||||
|
||||
|
||||
@ -11,6 +11,8 @@ ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.localizationpriority: high
|
||||
ms.topic: article
|
||||
description: Read news articles about Windows as a service, including Windows 10, Windows 10 Enterprise, Windows 10 Pro.
|
||||
ms.custom: seo-marvel-mar2020
|
||||
---
|
||||
# Windows as a service - More news
|
||||
|
||||
@ -19,8 +21,8 @@ Here's more news about [Windows as a service](windows-as-a-service.md):
|
||||
<ul>
|
||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-10-Enterprise-vs-Windows-10-Pro-Modern-management/ba-p/720445">Windows 10 Enterprise vs. Windows 10 Pro: Modern management considerations for your organization </a> - June 25, 2019</li>
|
||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Updating-Windows-10-version-1903-using-Configuration-Manager-or/ba-p/639100">Updating Windows 10, version 1903 using Configuration Manager or WSUS</a> - May 23, 2019</li>
|
||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/What-s-new-in-Windows-Update-for-Business-in-Windows-10-version/ba-p/622064">What’s new in Windows Update for Business in Windows 10, version 1903</a> - May 21, 2019</li>
|
||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/What-s-new-for-IT-pros-in-Windows-10-version-1903/ba-p/622024">What’s new for IT pros in Windows 10, version 1903</a> - May 21, 2019</li>
|
||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/What-s-new-in-Windows-Update-for-Business-in-Windows-10-version/ba-p/622064">What's new in Windows Update for Business in Windows 10, version 1903</a> - May 21, 2019</li>
|
||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/What-s-new-for-IT-pros-in-Windows-10-version-1903/ba-p/622024">What's new for IT pros in Windows 10, version 1903</a> - May 21, 2019</li>
|
||||
<li><a href="https://blogs.windows.com/windowsexperience/2019/05/21/how-to-get-the-windows-10-may-2019-update">How to get the Windows 10 May 2019 Update</a> - May 21, 2019</li>
|
||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/The-benefits-of-Windows-10-Dynamic-Update/ba-p/467847">The benefits of Windows 10 Dynamic Update</a> - April 17, 2019</li>
|
||||
<li><a href="https://blogs.windows.com/windowsexperience/2019/04/04/improving-the-windows-10-update-experience-with-control-quality-and-transparency">Improving the Windows 10 update experience with control, quality and transparency</a> - April 4, 2019</li>
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Log files - Windows IT Pro
|
||||
title: Log files and resolving upgrade errors
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Log Files (Windows 10)
|
||||
title: Log files for User State Migration Tool (USMT)
|
||||
description: Log Files
|
||||
ms.assetid: 28185ebd-630a-4bbd-94f4-8c48aad05649
|
||||
ms.reviewer:
|
||||
@ -251,7 +251,7 @@ The following examples describe common scenarios in which you can use the diagno
|
||||
|
||||
**Why is this file not migrating when I authored an "include" rule for it?**
|
||||
|
||||
Let’s imagine that we have the following directory structure and that we want the “data” directory to be included in the migration along with the “New Text Document.txt” file in the “New Folder.” The directory of **C:\\data** contains:
|
||||
Let's imagine that we have the following directory structure and that we want the "data" directory to be included in the migration along with the "New Text Document.txt" file in the "New Folder." The directory of **C:\\data** contains:
|
||||
|
||||
```
|
||||
01/21/2009 10:08 PM <DIR> .
|
||||
@ -293,7 +293,7 @@ To migrate these files you author the following migration XML:
|
||||
</migration>
|
||||
```
|
||||
|
||||
However, upon testing the migration you notice that the “New Text Document.txt” file isn’t included in the migration. To troubleshoot this failure, the migration can be repeated with the environment variable MIG\_ENABLE\_DIAG set such that the diagnostic log is generated. Upon searching the diagnostic log for the component “DATA1”, the following XML section is discovered:
|
||||
However, upon testing the migration you notice that the "New Text Document.txt" file isn't included in the migration. To troubleshoot this failure, the migration can be repeated with the environment variable MIG\_ENABLE\_DIAG set such that the diagnostic log is generated. Upon searching the diagnostic log for the component "DATA1", the following XML section is discovered:
|
||||
|
||||
``` xml
|
||||
<MigUnitList>
|
||||
@ -312,7 +312,7 @@ However, upon testing the migration you notice that the “New Text Document.txt
|
||||
</Perform>
|
||||
```
|
||||
|
||||
Analysis of this XML section reveals the migunit that was created when the migration rule was processed. The <Perform> section details the actual files that were scheduled for gathering and the result of the gathering operation. The “New Text Document.txt” file doesn’t appear in this section, which confirms that the migration rule was not correctly authored.
|
||||
Analysis of this XML section reveals the migunit that was created when the migration rule was processed. The <Perform> section details the actual files that were scheduled for gathering and the result of the gathering operation. The "New Text Document.txt" file doesn't appear in this section, which confirms that the migration rule was not correctly authored.
|
||||
|
||||
An analysis of the XML elements reference topic reveals that the <pattern> tag needs to be modified as follows:
|
||||
|
||||
@ -345,7 +345,7 @@ This diagnostic log confirms that the modified <pattern> value enables the
|
||||
|
||||
**Why is this file migrating when I authored an exclude rule excluding it?**
|
||||
|
||||
In this scenario, you have the following directory structure and you want all files in the “data” directory to migrate, except for text files. The **C:\\Data** folder contains:
|
||||
In this scenario, you have the following directory structure and you want all files in the "data" directory to migrate, except for text files. The **C:\\Data** folder contains:
|
||||
|
||||
```
|
||||
Directory of C:\Data
|
||||
@ -395,7 +395,7 @@ You author the following migration XML:
|
||||
</component>
|
||||
```
|
||||
|
||||
However, upon testing the migration you notice that all the text files are still included in the migration. In order to troubleshoot this issue, the migration can be performed with the environment variable MIG\_ENABLE\_DIAG set so that the diagnostic log is generated. Upon searching the diagnostic log for the component “DATA1”, the following XML section is discovered:
|
||||
However, upon testing the migration you notice that all the text files are still included in the migration. In order to troubleshoot this issue, the migration can be performed with the environment variable MIG\_ENABLE\_DIAG set so that the diagnostic log is generated. Upon searching the diagnostic log for the component "DATA1", the following XML section is discovered:
|
||||
|
||||
``` xml
|
||||
<MigUnitList>
|
||||
|
||||
@ -1,144 +1,146 @@
|
||||
---
|
||||
title: Activate using Key Management Service (Windows 10)
|
||||
ms.assetid: f2417bfe-7d25-4e82-bc07-de316caa8dac
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
description:
|
||||
keywords: vamt, volume activation, activation, windows activation
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
author: greg-lindsay
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 10/16/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# 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
|
||||
|
||||
**Looking for retail activation?**
|
||||
|
||||
- [Get Help Activating Microsoft Windows](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
|
||||
|
||||
Check out [Windows 10 Volume Activation Tips](https://blogs.technet.microsoft.com/askcore/2015/09/15/windows-10-volume-activation-tips/).
|
||||
|
||||
## Key Management Service in Windows 10
|
||||
|
||||
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.
|
||||
|
||||
**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.
|
||||
|
||||
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.
|
||||
|
||||
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).
|
||||
|
||||
**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\
|
||||
|
||||
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
|
||||
|
||||
5. 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).
|
||||
|
||||
|
||||
|
||||
**Figure 8**. Activating the software
|
||||
|
||||
The KMS key can be activated online or by phone. See Figure 9.
|
||||
|
||||
|
||||
|
||||
**Figure 9**. Choosing to activate online
|
||||
|
||||
Now that the KMS host is configured, it will begin to listen for activation requests. However, it will not activate clients successfully until the activation threshold is met.
|
||||
|
||||
## 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.
|
||||
|
||||
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>
|
||||
|
||||
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://go.microsoft.com/fwlink/p/?LinkId=733639).
|
||||
|
||||
## 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.
|
||||
|
||||
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)
|
||||
---
|
||||
title: Activate using Key Management Service (Windows 10)
|
||||
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.
|
||||
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: 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
|
||||
|
||||
**Looking for retail activation?**
|
||||
|
||||
- [Get Help Activating Microsoft Windows](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
|
||||
|
||||
Check out [Windows 10 Volume Activation Tips](https://blogs.technet.microsoft.com/askcore/2015/09/15/windows-10-volume-activation-tips/).
|
||||
|
||||
## Key Management Service in Windows 10
|
||||
|
||||
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.
|
||||
|
||||
**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.
|
||||
|
||||
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.
|
||||
|
||||
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).
|
||||
|
||||
**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\
|
||||
|
||||
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
|
||||
|
||||
5. 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).
|
||||
|
||||
|
||||
|
||||
**Figure 8**. Activating the software
|
||||
|
||||
The KMS key can be activated online or by phone. See Figure 9.
|
||||
|
||||
|
||||
|
||||
**Figure 9**. Choosing to activate online
|
||||
|
||||
Now that the KMS host is configured, it will begin to listen for activation requests. However, it will not activate clients successfully until the activation threshold is met.
|
||||
|
||||
## 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.
|
||||
|
||||
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>
|
||||
|
||||
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://go.microsoft.com/fwlink/p/?LinkId=733639).
|
||||
|
||||
## 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.
|
||||
|
||||
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)
|
||||
|
||||
@ -1,71 +1,73 @@
|
||||
---
|
||||
title: Appendix Information sent to Microsoft during activation (Windows 10)
|
||||
ms.assetid: 4bfff495-07d0-4385-86e3-7a077cbd64b8
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
description:
|
||||
keywords: vamt, volume activation, activation, windows activation
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
author: greg-lindsay
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 07/27/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Appendix: Information sent to Microsoft during activation
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
**Looking for retail activation?**
|
||||
|
||||
- [Get Help Activating Microsoft Windows](https://go.microsoft.com/fwlink/p/?LinkId=618644)
|
||||
|
||||
When you activate a computer running Windows 10, the following information is sent to Microsoft:
|
||||
|
||||
- The Microsoft product code (a five-digit code that identifies the Windows product you are activating)
|
||||
- A channel ID or site code that identifies how the Windows product was originally obtained
|
||||
|
||||
For example, a channel ID or site code identifies whether the product was originally purchased from a retail store, obtained as an evaluation copy, obtained through a volume licensing program, or preinstalled by a computer manufacturer.
|
||||
|
||||
- The date of installation and whether the installation was successful
|
||||
- Information that helps confirm that your Windows product key has not been altered
|
||||
- Computer make and model
|
||||
- Version information for the operating system and software
|
||||
- Region and language settings
|
||||
- A unique number called a *globally unique identifier*, which is assigned to your computer
|
||||
- Product key (hashed) and product ID
|
||||
- BIOS name, revision number, and revision date
|
||||
- Volume serial number (hashed) of the hard disk drive
|
||||
- The result of the activation check
|
||||
|
||||
This includes error codes and the following information about any activation exploits and related malicious or unauthorized software that was found or disabled:
|
||||
|
||||
- The activation exploit’s identifier
|
||||
- The activation exploit’s current state, such as cleaned or quarantined
|
||||
- Computer manufacturer’s identification
|
||||
- The activation exploit’s file name and hash in addition to a hash of related software components that may indicate the presence of an activation exploit
|
||||
- The name and a hash of the contents of your computer’s startup instructions file
|
||||
- If your Windows license is on a subscription basis, information about how your subscription works
|
||||
|
||||
Standard computer information is also sent, but your computer’s IP address is only retained temporarily.
|
||||
|
||||
## Use of information
|
||||
|
||||
Microsoft uses the information to confirm that you have a licensed copy of the software. Microsoft does not use the information to contact individual consumers.
|
||||
For additional details, see [Windows 10 Privacy Statement](https://go.microsoft.com/fwlink/p/?LinkId=619879).
|
||||
|
||||
## See also
|
||||
|
||||
- [Volume Activation for Windows 10](volume-activation-windows-10.md)
|
||||
|
||||
|
||||
---
|
||||
title: Appendix Information sent to Microsoft during activation (Windows 10)
|
||||
ms.assetid: 4bfff495-07d0-4385-86e3-7a077cbd64b8
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
description: Learn about the information that is sent to Microsoft when you activate a computer running Windows 10.
|
||||
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
|
||||
ms.custom: seo-marvel-mar2020
|
||||
---
|
||||
|
||||
# Appendix: Information sent to Microsoft during activation
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
**Looking for retail activation?**
|
||||
|
||||
- [Get Help Activating Microsoft Windows](https://go.microsoft.com/fwlink/p/?LinkId=618644)
|
||||
|
||||
When you activate a computer running Windows 10, the following information is sent to Microsoft:
|
||||
|
||||
- The Microsoft product code (a five-digit code that identifies the Windows product you are activating)
|
||||
- A channel ID or site code that identifies how the Windows product was originally obtained
|
||||
|
||||
For example, a channel ID or site code identifies whether the product was originally purchased from a retail store, obtained as an evaluation copy, obtained through a volume licensing program, or preinstalled by a computer manufacturer.
|
||||
|
||||
- The date of installation and whether the installation was successful
|
||||
- Information that helps confirm that your Windows product key has not been altered
|
||||
- Computer make and model
|
||||
- Version information for the operating system and software
|
||||
- Region and language settings
|
||||
- A unique number called a *globally unique identifier*, which is assigned to your computer
|
||||
- Product key (hashed) and product ID
|
||||
- BIOS name, revision number, and revision date
|
||||
- Volume serial number (hashed) of the hard disk drive
|
||||
- The result of the activation check
|
||||
|
||||
This includes error codes and the following information about any activation exploits and related malicious or unauthorized software that was found or disabled:
|
||||
|
||||
- The activation exploit's identifier
|
||||
- The activation exploit's current state, such as cleaned or quarantined
|
||||
- Computer manufacturer's identification
|
||||
- The activation exploit's file name and hash in addition to a hash of related software components that may indicate the presence of an activation exploit
|
||||
- The name and a hash of the contents of your computer's startup instructions file
|
||||
- If your Windows license is on a subscription basis, information about how your subscription works
|
||||
|
||||
Standard computer information is also sent, but your computer's IP address is only retained temporarily.
|
||||
|
||||
## Use of information
|
||||
|
||||
Microsoft uses the information to confirm that you have a licensed copy of the software. Microsoft does not use the information to contact individual consumers.
|
||||
For additional details, see [Windows 10 Privacy Statement](https://go.microsoft.com/fwlink/p/?LinkId=619879).
|
||||
|
||||
## See also
|
||||
|
||||
- [Volume Activation for Windows 10](volume-activation-windows-10.md)
|
||||
|
||||
|
||||
|
||||
@ -1,44 +1,46 @@
|
||||
---
|
||||
title: Monitor activation (Windows 10)
|
||||
ms.assetid: 264a3e86-c880-4be4-8828-bf4c839dfa26
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
description:
|
||||
keywords: vamt, volume activation, activation, windows activation
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
author: greg-lindsay
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Monitor activation
|
||||
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
**Looking for retail activation?**
|
||||
|
||||
- [Get Help Activating Microsoft Windows](https://go.microsoft.com/fwlink/p/?LinkId=618644)
|
||||
|
||||
You can monitor the success of the activation process for a computer running Windows in several ways. The most popular methods include:
|
||||
- Using the Volume Licensing Service Center website to track use of MAK keys.
|
||||
- Using the **Slmgr /dlv** command on a client computer or on the KMS host. (For a full list of options, see [Slmgr.vbs Options](https://technet.microsoft.com/library/ff793433.aspx).)
|
||||
- Viewing the licensing status, which is exposed through Windows Management Instrumentation (WMI); therefore, it is available to non-Microsoft or custom tools that can access WMI. (Windows PowerShell can also access WMI information.)
|
||||
- Most licensing actions and events are recorded in the Event log (ex: Application Log events 12288-12290).
|
||||
- Microsoft System Center Operations Manager and the KMS Management Pack can provide insight and information to users of System Center Operations Manager.
|
||||
- See [Troubleshooting activation error codes](https://docs.microsoft.com/windows-server/get-started/activation-error-codes) for information about troubleshooting procedures for Multiple Activation Key (MAK) or the Key Management Service (KMS).
|
||||
- The VAMT provides a single site from which to manage and monitor volume activations. This is explained in the next section.
|
||||
|
||||
## See also
|
||||
|
||||
[Volume Activation for Windows 10](volume-activation-windows-10.md)
|
||||
---
|
||||
title: Monitor activation (Windows 10)
|
||||
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.
|
||||
keywords: vamt, volume activation, activation, windows activation
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-mar2020
|
||||
---
|
||||
|
||||
# Monitor activation
|
||||
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
**Looking for retail activation?**
|
||||
|
||||
- [Get Help Activating Microsoft Windows](https://go.microsoft.com/fwlink/p/?LinkId=618644)
|
||||
|
||||
You can monitor the success of the activation process for a computer running Windows in several ways. The most popular methods include:
|
||||
- Using the Volume Licensing Service Center website to track use of MAK keys.
|
||||
- Using the **Slmgr /dlv** command on a client computer or on the KMS host. (For a full list of options, see [Slmgr.vbs Options](https://technet.microsoft.com/library/ff793433.aspx).)
|
||||
- Viewing the licensing status, which is exposed through Windows Management Instrumentation (WMI); therefore, it is available to non-Microsoft or custom tools that can access WMI. (Windows PowerShell can also access WMI information.)
|
||||
- Most licensing actions and events are recorded in the Event log (ex: Application Log events 12288-12290).
|
||||
- Microsoft System Center Operations Manager and the KMS Management Pack can provide insight and information to users of System Center Operations Manager.
|
||||
- See [Troubleshooting activation error codes](https://docs.microsoft.com/windows-server/get-started/activation-error-codes) for information about troubleshooting procedures for Multiple Activation Key (MAK) or the Key Management Service (KMS).
|
||||
- The VAMT provides a single site from which to manage and monitor volume activations. This is explained in the next section.
|
||||
|
||||
## See also
|
||||
|
||||
[Volume Activation for Windows 10](volume-activation-windows-10.md)
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Windows 10 deployment tools reference
|
||||
title: Windows 10 deployment tools
|
||||
description: Learn about the tools available to deploy Windows 10.
|
||||
ms.assetid: 5C4B0AE3-B2D0-4628-9E73-606F3FAA17BB
|
||||
ms.reviewer:
|
||||
@ -26,5 +26,5 @@ Learn about the tools available to deploy Windows 10.
|
||||
|[Configure a PXE server to load Windows PE](configure-a-pxe-server-to-load-windows-pe.md) |This guide describes how to configure a PXE server to load Windows PE by booting a client computer from the network. |
|
||||
|[Windows ADK for Windows 10 scenarios for IT Pros](windows-adk-scenarios-for-it-pros.md) |The Windows Assessment and Deployment Kit (Windows ADK) contains tools that can be used by IT Pros to deploy Windows. |
|
||||
|[Deploy Windows To Go in your organization](deploy-windows-to-go.md) |This topic helps you to deploy Windows To Go in your organization. Before you begin deployment, make sure that you have reviewed the topics [Windows To Go: feature overview](planning/windows-to-go-overview.md) and [Prepare your organization for Windows To Go](planning/prepare-your-organization-for-windows-to-go.md) to ensure that you have the correct hardware and are prepared to complete the deployment. You can then use the steps in this topic to start your Windows To Go deployment. |
|
||||
|[Volume Activation Management Tool (VAMT) Technical Reference](volume-activation/volume-activation-management-tool.md) |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. |
|
||||
|[Volume Activation Management Tool (VAMT) Technical Reference](volume-activation/volume-activation-management-tool.md) |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. |
|
||||
|[User State Migration Tool (USMT) Technical Reference](usmt/usmt-technical-reference.md) |The User State Migration Tool (USMT) 10.0 is included with the Windows Assessment and Deployment Kit (Windows ADK) for Windows 10. USMT provides a highly customizable user-profile migration experience for IT professionals |
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Windows 10 deployment tools
|
||||
title: Learn about Windows 10 deployment tools
|
||||
description: Browse through documentation describing Windows 10 deployment tools. Learn how to use these these tools to successfully deploy Windows 10 to your organization.
|
||||
ms.assetid: 5C4B0AE3-B2D0-4628-9E73-606F3FAA17BB
|
||||
ms.reviewer:
|
||||
@ -26,5 +26,5 @@ Learn about the tools available to deploy Windows 10.
|
||||
|[Configure a PXE server to load Windows PE](configure-a-pxe-server-to-load-windows-pe.md) |This guide describes how to configure a PXE server to load Windows PE by booting a client computer from the network. |
|
||||
|[Windows ADK for Windows 10 scenarios for IT Pros](windows-adk-scenarios-for-it-pros.md) |The Windows Assessment and Deployment Kit (Windows ADK) contains tools that can be used by IT Pros to deploy Windows. |
|
||||
|[Deploy Windows To Go in your organization](deploy-windows-to-go.md) |This topic helps you to deploy Windows To Go in your organization. Before you begin deployment, make sure that you have reviewed the topics [Windows To Go: feature overview](planning/windows-to-go-overview.md) and [Prepare your organization for Windows To Go](planning/prepare-your-organization-for-windows-to-go.md) to ensure that you have the correct hardware and are prepared to complete the deployment. You can then use the steps in this topic to start your Windows To Go deployment. |
|
||||
|[Volume Activation Management Tool (VAMT) Technical Reference](volume-activation/volume-activation-management-tool.md) |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. |
|
||||
|[Volume Activation Management Tool (VAMT) Technical Reference](volume-activation/volume-activation-management-tool.md) |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. |
|
||||
|[User State Migration Tool (USMT) Technical Reference](usmt/usmt-technical-reference.md) |The User State Migration Tool (USMT) 10.0 is included with the Windows Assessment and Deployment Kit (Windows ADK) for Windows 10. USMT provides a highly customizable user-profile migration experience for IT professionals |
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user