mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
Updated -description meta field to adhere to SEO standards
This commit is contained in:
parent
15d3f0f87b
commit
915996ff61
@ -2,7 +2,7 @@
|
|||||||
title: Windows 10 - Apps
|
title: Windows 10 - Apps
|
||||||
ms.reviewer:
|
ms.reviewer:
|
||||||
manager: dansimp
|
manager: dansimp
|
||||||
description: What are Windows, UWP, and Win32 apps
|
description: Use this article to understand the different types of apps that run on Windows 10, such as UWP and Win32 apps.
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: deploy
|
ms.mktglfcycl: deploy
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
|
@ -1,6 +1,6 @@
|
|||||||
---
|
---
|
||||||
title: DevInfo CSP
|
title: DevInfo CSP
|
||||||
description: DevInfo CSP
|
description: Learn now the DevInfo configuration service provider handles the managed object which provides device information to the OMA DM server.
|
||||||
ms.assetid: d3eb70db-1ce9-4c72-a13d-651137c1713c
|
ms.assetid: d3eb70db-1ce9-4c72-a13d-651137c1713c
|
||||||
ms.reviewer:
|
ms.reviewer:
|
||||||
manager: dansimp
|
manager: dansimp
|
||||||
|
@ -1,6 +1,6 @@
|
|||||||
---
|
---
|
||||||
title: Firewall CSP
|
title: Firewall CSP
|
||||||
description: Firewall CSP
|
description: The Firewall configuration service provider (CSP) allows the mobile device management (MDM) server to configure the Windows Defender Firewall global settings.
|
||||||
ms.author: dansimp
|
ms.author: dansimp
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
|
@ -1,6 +1,6 @@
|
|||||||
---
|
---
|
||||||
title: WMI providers supported in Windows 10
|
title: WMI providers supported in Windows 10
|
||||||
description: WMI providers supported in Windows 10
|
description: Manage settings and applications on devices that subscribe to the Mobile Device Management (MDM) service with Windows Management Infrastructure (WMI).
|
||||||
MS-HAID:
|
MS-HAID:
|
||||||
- 'p\_phdevicemgmt.wmi\_providers\_supported\_in\_windows\_10\_technical\_preview'
|
- 'p\_phdevicemgmt.wmi\_providers\_supported\_in\_windows\_10\_technical\_preview'
|
||||||
- 'p\_phDeviceMgmt.wmi\_providers\_supported\_in\_windows'
|
- 'p\_phDeviceMgmt.wmi\_providers\_supported\_in\_windows'
|
||||||
|
@ -1,6 +1,6 @@
|
|||||||
---
|
---
|
||||||
title: Hard-Link Migration Store (Windows 10)
|
title: Hard-Link Migration Store (Windows 10)
|
||||||
description: Hard-Link Migration Store
|
description: Use of a hard-link migration store for a computer-refresh scenario drastically improves migration performance and significantly reduces hard-disk utilization.
|
||||||
ms.assetid: b0598418-4607-4952-bfa3-b6e4aaa2c574
|
ms.assetid: b0598418-4607-4952-bfa3-b6e4aaa2c574
|
||||||
ms.reviewer:
|
ms.reviewer:
|
||||||
manager: laurawi
|
manager: laurawi
|
||||||
|
@ -1,78 +1,79 @@
|
|||||||
---
|
---
|
||||||
title: USMT XML Reference (Windows 10)
|
title: USMT XML Reference (Windows 10)
|
||||||
description: USMT XML Reference
|
description: Work with and customize the migration XML files using USMT XML Reference for Windows 10.
|
||||||
ms.assetid: fb946975-0fee-4ec0-b3ef-7c34945ee96f
|
ms.assetid: fb946975-0fee-4ec0-b3ef-7c34945ee96f
|
||||||
ms.reviewer:
|
ms.reviewer:
|
||||||
manager: laurawi
|
manager: laurawi
|
||||||
ms.author: greglin
|
ms.author: greglin
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: deploy
|
ms.mktglfcycl: deploy
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
audience: itpro
author: greg-lindsay
|
audience: itpro
|
||||||
ms.date: 04/19/2017
|
author: greg-lindsay
|
||||||
ms.topic: article
|
ms.date: 04/19/2017
|
||||||
---
|
ms.topic: article
|
||||||
|
---
|
||||||
# USMT XML Reference
|
|
||||||
|
# USMT XML Reference
|
||||||
|
|
||||||
This section contains topics that you can use to work with and to customize the migration XML files.
|
|
||||||
|
This section contains topics that you can use to work with and to customize the migration XML files.
|
||||||
## In This Section
|
|
||||||
|
## In This Section
|
||||||
|
|
||||||
<table>
|
|
||||||
<colgroup>
|
<table>
|
||||||
<col width="50%" />
|
<colgroup>
|
||||||
<col width="50%" />
|
<col width="50%" />
|
||||||
</colgroup>
|
<col width="50%" />
|
||||||
<tbody>
|
</colgroup>
|
||||||
<tr class="odd">
|
<tbody>
|
||||||
<td align="left"><p><a href="understanding-migration-xml-files.md" data-raw-source="[Understanding Migration XML Files](understanding-migration-xml-files.md)">Understanding Migration XML Files</a></p></td>
|
<tr class="odd">
|
||||||
<td align="left"><p>Provides an overview of the default and custom migration XML files and includes guidelines for creating and editing a customized version of the MigDocs.xml file.</p></td>
|
<td align="left"><p><a href="understanding-migration-xml-files.md" data-raw-source="[Understanding Migration XML Files](understanding-migration-xml-files.md)">Understanding Migration XML Files</a></p></td>
|
||||||
</tr>
|
<td align="left"><p>Provides an overview of the default and custom migration XML files and includes guidelines for creating and editing a customized version of the MigDocs.xml file.</p></td>
|
||||||
<tr class="even">
|
</tr>
|
||||||
<td align="left"><p><a href="usmt-configxml-file.md" data-raw-source="[Config.xml File](usmt-configxml-file.md)">Config.xml File</a></p></td>
|
<tr class="even">
|
||||||
<td align="left"><p>Describes the Config.xml file and policies concerning its configuration.</p></td>
|
<td align="left"><p><a href="usmt-configxml-file.md" data-raw-source="[Config.xml File](usmt-configxml-file.md)">Config.xml File</a></p></td>
|
||||||
</tr>
|
<td align="left"><p>Describes the Config.xml file and policies concerning its configuration.</p></td>
|
||||||
<tr class="odd">
|
</tr>
|
||||||
<td align="left"><p><a href="usmt-customize-xml-files.md" data-raw-source="[Customize USMT XML Files](usmt-customize-xml-files.md)">Customize USMT XML Files</a></p></td>
|
<tr class="odd">
|
||||||
<td align="left"><p>Describes how to customize USMT XML files.</p></td>
|
<td align="left"><p><a href="usmt-customize-xml-files.md" data-raw-source="[Customize USMT XML Files](usmt-customize-xml-files.md)">Customize USMT XML Files</a></p></td>
|
||||||
</tr>
|
<td align="left"><p>Describes how to customize USMT XML files.</p></td>
|
||||||
<tr class="even">
|
</tr>
|
||||||
<td align="left"><p><a href="usmt-custom-xml-examples.md" data-raw-source="[Custom XML Examples](usmt-custom-xml-examples.md)">Custom XML Examples</a></p></td>
|
<tr class="even">
|
||||||
<td align="left"><p>Gives examples of XML files for various migration scenarios.</p></td>
|
<td align="left"><p><a href="usmt-custom-xml-examples.md" data-raw-source="[Custom XML Examples](usmt-custom-xml-examples.md)">Custom XML Examples</a></p></td>
|
||||||
</tr>
|
<td align="left"><p>Gives examples of XML files for various migration scenarios.</p></td>
|
||||||
<tr class="odd">
|
</tr>
|
||||||
<td align="left"><p><a href="usmt-conflicts-and-precedence.md" data-raw-source="[Conflicts and Precedence](usmt-conflicts-and-precedence.md)">Conflicts and Precedence</a></p></td>
|
<tr class="odd">
|
||||||
<td align="left"><p>Describes the precedence of migration rules and how conflicts are handled.</p></td>
|
<td align="left"><p><a href="usmt-conflicts-and-precedence.md" data-raw-source="[Conflicts and Precedence](usmt-conflicts-and-precedence.md)">Conflicts and Precedence</a></p></td>
|
||||||
</tr>
|
<td align="left"><p>Describes the precedence of migration rules and how conflicts are handled.</p></td>
|
||||||
<tr class="even">
|
</tr>
|
||||||
<td align="left"><p><a href="usmt-general-conventions.md" data-raw-source="[General Conventions](usmt-general-conventions.md)">General Conventions</a></p></td>
|
<tr class="even">
|
||||||
<td align="left"><p>Describes the XML helper functions.</p></td>
|
<td align="left"><p><a href="usmt-general-conventions.md" data-raw-source="[General Conventions](usmt-general-conventions.md)">General Conventions</a></p></td>
|
||||||
</tr>
|
<td align="left"><p>Describes the XML helper functions.</p></td>
|
||||||
<tr class="odd">
|
</tr>
|
||||||
<td align="left"><p><a href="xml-file-requirements.md" data-raw-source="[XML File Requirements](xml-file-requirements.md)">XML File Requirements</a></p></td>
|
<tr class="odd">
|
||||||
<td align="left"><p>Describes the requirements for custom XML files.</p></td>
|
<td align="left"><p><a href="xml-file-requirements.md" data-raw-source="[XML File Requirements](xml-file-requirements.md)">XML File Requirements</a></p></td>
|
||||||
</tr>
|
<td align="left"><p>Describes the requirements for custom XML files.</p></td>
|
||||||
<tr class="even">
|
</tr>
|
||||||
<td align="left"><p><a href="usmt-recognized-environment-variables.md" data-raw-source="[Recognized Environment Variables](usmt-recognized-environment-variables.md)">Recognized Environment Variables</a></p></td>
|
<tr class="even">
|
||||||
<td align="left"><p>Describes environment variables recognized by USMT.</p></td>
|
<td align="left"><p><a href="usmt-recognized-environment-variables.md" data-raw-source="[Recognized Environment Variables](usmt-recognized-environment-variables.md)">Recognized Environment Variables</a></p></td>
|
||||||
</tr>
|
<td align="left"><p>Describes environment variables recognized by USMT.</p></td>
|
||||||
<tr class="odd">
|
</tr>
|
||||||
<td align="left"><p><a href="usmt-xml-elements-library.md" data-raw-source="[XML Elements Library](usmt-xml-elements-library.md)">XML Elements Library</a></p></td>
|
<tr class="odd">
|
||||||
<td align="left"><p>Describes the XML elements and helper functions for authoring migration XML files to use with USMT.</p></td>
|
<td align="left"><p><a href="usmt-xml-elements-library.md" data-raw-source="[XML Elements Library](usmt-xml-elements-library.md)">XML Elements Library</a></p></td>
|
||||||
</tr>
|
<td align="left"><p>Describes the XML elements and helper functions for authoring migration XML files to use with USMT.</p></td>
|
||||||
</tbody>
|
</tr>
|
||||||
</table>
|
</tbody>
|
||||||
|
</table>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
@ -1,49 +1,50 @@
|
|||||||
---
|
---
|
||||||
title: Perform KMS Activation (Windows 10)
|
title: Perform KMS Activation (Windows 10)
|
||||||
description: Perform KMS Activation
|
description: The Volume Activation Management Tool (VAMT) can be used to perform volume activation using the Key Management Service (KMS).
|
||||||
ms.assetid: 5a3ae8e6-083e-4153-837e-ab0a225c1d10
|
ms.assetid: 5a3ae8e6-083e-4153-837e-ab0a225c1d10
|
||||||
ms.reviewer:
|
ms.reviewer:
|
||||||
manager: laurawi
|
manager: laurawi
|
||||||
ms.author: greglin
|
ms.author: greglin
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: deploy
|
ms.mktglfcycl: deploy
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
ms.pagetype: activation
|
ms.pagetype: activation
|
||||||
audience: itpro
author: greg-lindsay
|
audience: itpro
|
||||||
ms.date: 04/25/2017
|
author: greg-lindsay
|
||||||
ms.topic: article
|
ms.date: 04/25/2017
|
||||||
---
|
ms.topic: article
|
||||||
|
---
|
||||||
# Perform KMS Activation
|
|
||||||
|
# Perform KMS Activation
|
||||||
The Volume Activation Management Tool (VAMT) can be used to perform volume activation using the Key Management Service (KMS). You can use VAMT to activate Generic Volume Licensing Keys, or KMS client keys, on products accessible to VAMT. GVLKs are the default product keys used by the volume-license editions of Windows Vista, Windows 7, Windows 8, Windows 10, Windows Server 2008, Windows Server 2008 R2, Windows Server® 2012, and Microsoft Office 2010. GVLKs are already installed in volume-license editions of these products.
|
|
||||||
|
The Volume Activation Management Tool (VAMT) can be used to perform volume activation using the Key Management Service (KMS). You can use VAMT to activate Generic Volume Licensing Keys, or KMS client keys, on products accessible to VAMT. GVLKs are the default product keys used by the volume-license editions of Windows Vista, Windows 7, Windows 8, Windows 10, Windows Server 2008, Windows Server 2008 R2, Windows Server® 2012, and Microsoft Office 2010. GVLKs are already installed in volume-license editions of these products.
|
||||||
## Requirements
|
|
||||||
|
## Requirements
|
||||||
Before configuring KMS activation, ensure that your network and VAMT installation meet the following requirements:
|
|
||||||
- KMS host is set up and enabled.
|
Before configuring KMS activation, ensure that your network and VAMT installation meet the following requirements:
|
||||||
- KMS clients can access the KMS host.
|
- KMS host is set up and enabled.
|
||||||
- VAMT is installed on a central computer with network access to all client computers.
|
- KMS clients can access the KMS host.
|
||||||
- The products to be activated have been added to VAMT. For more information on adding product keys, see [Install a KMS Client Key](install-kms-client-key-vamt.md).
|
- VAMT is installed on a central computer with network access to all client computers.
|
||||||
- VAMT has administrative permissions on all computers to be activated, and Windows Management Instrumentation (WMI) is accessible through the Windows Firewall. For more information, see [Configure Client Computers](configure-client-computers-vamt.md).
|
- The products to be activated have been added to VAMT. For more information on adding product keys, see [Install a KMS Client Key](install-kms-client-key-vamt.md).
|
||||||
|
- VAMT has administrative permissions on all computers to be activated, and Windows Management Instrumentation (WMI) is accessible through the Windows Firewall. For more information, see [Configure Client Computers](configure-client-computers-vamt.md).
|
||||||
## To configure devices for KMS activation
|
|
||||||
|
## To configure devices for KMS activation
|
||||||
**To configure devices for KMS activation**
|
|
||||||
1. Open VAMT.
|
**To configure devices for KMS activation**
|
||||||
2. If necessary, set up the KMS activation preferences. If you don’t need to set up the preferences, skip to step 6 in this procedure. Otherwise, continue to step 2.
|
1. Open VAMT.
|
||||||
3. To set up the preferences, on the menu bar click **View**, then click **Preferences** to open the **Volume Activation Management Tool Preferences** dialog box.
|
2. If necessary, set up the KMS activation preferences. If you don’t need to set up the preferences, skip to step 6 in this procedure. Otherwise, continue to step 2.
|
||||||
4. Under **Key Management Services host selection**, select one of the following options:
|
3. To set up the preferences, on the menu bar click **View**, then click **Preferences** to open the **Volume Activation Management Tool Preferences** dialog box.
|
||||||
- **Find a KMS host automatically using DNS (default)**. If you choose this option, VAMT first clears any previously configured KMS host on the target computer and instructs the computer to query the Domain Name Service (DNS) to locate a KMS host and attempt activation.
|
4. Under **Key Management Services host selection**, select one of the following options:
|
||||||
- **Find a KMS host using DNS in this domain for supported products**. Enter the domain name. If you choose this option, VAMT first clears any previously configured KMS host on the target computer and instructs the computer to query the DNS in the specified domain to locate a KMS host and attempt activation.
|
- **Find a KMS host automatically using DNS (default)**. If you choose this option, VAMT first clears any previously configured KMS host on the target computer and instructs the computer to query the Domain Name Service (DNS) to locate a KMS host and attempt activation.
|
||||||
- **Use specific KMS host**. Enter the KMS host name and KMS host port. For environments which do not use DNS for KMS host identification, VAMT sets the specified KMS host name and KMS host port on the target computer, and then instructs the computer to attempt activation with the specific KMS host.
|
- **Find a KMS host using DNS in this domain for supported products**. Enter the domain name. If you choose this option, VAMT first clears any previously configured KMS host on the target computer and instructs the computer to query the DNS in the specified domain to locate a KMS host and attempt activation.
|
||||||
5. Click **Apply**, and then click **OK** to close the **Volume Activation Management Tool Preferences** dialog box.
|
- **Use specific KMS host**. Enter the KMS host name and KMS host port. For environments which do not use DNS for KMS host identification, VAMT sets the specified KMS host name and KMS host port on the target computer, and then instructs the computer to attempt activation with the specific KMS host.
|
||||||
6. Select the products to be activated by selecting individual products in the product list view in the center pane. You can use the **Filter** function to narrow your search for computers by clicking **Filter** in the right-side pane to open the **Filter Products** dialog box.In the **Filter Products** dialog box, you can filter the list by computer name, product name, product key type, license status, or by any combination of these options.
|
5. Click **Apply**, and then click **OK** to close the **Volume Activation Management Tool Preferences** dialog box.
|
||||||
- To filter the list by computer name, enter a name in the **Computer Name** box.
|
6. Select the products to be activated by selecting individual products in the product list view in the center pane. You can use the **Filter** function to narrow your search for computers by clicking **Filter** in the right-side pane to open the **Filter Products** dialog box.In the **Filter Products** dialog box, you can filter the list by computer name, product name, product key type, license status, or by any combination of these options.
|
||||||
- To filter the list by Product Name, Product Key Type, or License Status, click the list you want to use for the filter and select an option. If necessary, click **clear all filters** to create a new filter.
|
- To filter the list by computer name, enter a name in the **Computer Name** box.
|
||||||
7. Click **Filter**. VAMT displays the filtered list in the center pane.
|
- To filter the list by Product Name, Product Key Type, or License Status, click the list you want to use for the filter and select an option. If necessary, click **clear all filters** to create a new filter.
|
||||||
8. In the right-side pane, click **Activate** in the **Selected Items** menu, and then click **Volume activate**.
|
7. Click **Filter**. VAMT displays the filtered list in the center pane.
|
||||||
9. Click a credential option. Choose **Alternate credentials** only if you are activating products that require administrator credentials different from the ones you are currently using.
|
8. In the right-side pane, click **Activate** in the **Selected Items** menu, and then click **Volume activate**.
|
||||||
10. If you are supplying alternate credentials, at the prompt, type the appropriate user name and password and click **OK**.
|
9. Click a credential option. Choose **Alternate credentials** only if you are activating products that require administrator credentials different from the ones you are currently using.
|
||||||
VAMT displays the **Volume Activation** dialog box until it completes the requested action. When the process is finished, the updated activation status of each product appears in the product list view in the center pane.
|
10. If you are supplying alternate credentials, at the prompt, type the appropriate user name and password and click **OK**.
|
||||||
|
VAMT displays the **Volume Activation** dialog box until it completes the requested action. When the process is finished, the updated activation status of each product appears in the product list view in the center pane.
|
||||||
|
|
||||||
|
@ -1,6 +1,6 @@
|
|||||||
---
|
---
|
||||||
title: Get machines security states collection API
|
title: Get machines security states collection API
|
||||||
description: Retrieves a collection of machines security states.
|
description: Retrieve a collection of machine security states using Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP.
|
||||||
keywords: apis, graph api, supported apis, get, machine, security, state
|
keywords: apis, graph api, supported apis, get, machine, security, state
|
||||||
search.product: eADQiWindows 10XVcnh
|
search.product: eADQiWindows 10XVcnh
|
||||||
search.appverid: met150
|
search.appverid: met150
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
---
|
---
|
||||||
title: Microsoft Defender Security Center time zone settings
|
title: Microsoft Defender Security Center time zone settings
|
||||||
description: Use the menu to configure the time zone and view license information.
|
description: Use the menu to configure the Microsoft Defender Security Center time zone settings and view license information.
|
||||||
keywords: settings, Windows Defender, cybersecurity threat intelligence, advanced threat protection, time zone, utc, local time, license
|
keywords: settings, Microsoft Defender, cybersecurity threat intelligence, advanced threat protection, time zone, utc, local time, license
|
||||||
search.product: eADQiWindows 10XVcnh
|
search.product: eADQiWindows 10XVcnh
|
||||||
search.appverid: met150
|
search.appverid: met150
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
|
@ -1,6 +1,6 @@
|
|||||||
---
|
---
|
||||||
title: Checklist Configuring Basic Firewall Settings (Windows 10)
|
title: Checklist Configuring Basic Firewall Settings (Windows 10)
|
||||||
description: Checklist Configuring Basic Firewall Settings
|
description: Configure Windows Firewall to set inbound and outbound behavior, display notifications, record log files and more of the necessary function for Firewall.
|
||||||
ms.assetid: 0d10cdae-da3d-4a33-b8a4-6b6656b6d1f9
|
ms.assetid: 0d10cdae-da3d-4a33-b8a4-6b6656b6d1f9
|
||||||
ms.reviewer:
|
ms.reviewer:
|
||||||
ms.author: dansimp
|
ms.author: dansimp
|
||||||
|
Loading…
x
Reference in New Issue
Block a user