**(default)** | 0 | 0 | No additional message displays. |  | +| Disabled or not configured
**(default)** | 0 | 0 | No additional message displays. |  | | Enabled | 1 | 1 | Show an additional message stating that a site has opened in IE11. | | | Enabled | 2 | 2 | Show an additional message with a *Keep going in Microsoft Edge* link to allow users to open the site in Microsoft Edge. | | diff --git a/browsers/includes/import-into-the-enterprise-mode-site-list-mgr-include.md b/browsers/includes/import-into-the-enterprise-mode-site-list-mgr-include.md index 4f722ff9f5..9116168ca3 100644 --- a/browsers/includes/import-into-the-enterprise-mode-site-list-mgr-include.md +++ b/browsers/includes/import-into-the-enterprise-mode-site-list-mgr-include.md @@ -10,7 +10,7 @@ ms:topic: include If you need to replace your entire site list because of errors, or simply because it’s out of date, you can import your exported Enterprise Mode site list using the Enterprise Mode Site List Manager. ->[!IMPORTANT] +>[!IMPORTANT] >Importing your file overwrites everything that’s currently in the tool, so make sure it’s what want to do. 1. In the Enterprise Mode Site List Manager, click **File \> Import**. diff --git a/devices/hololens/hololens-install-localized.md b/devices/hololens/hololens-install-localized.md index 44e729c92f..0d3b2aecfb 100644 --- a/devices/hololens/hololens-install-localized.md +++ b/devices/hololens/hololens-install-localized.md @@ -17,7 +17,7 @@ manager: dansimp In order to switch to the Chinese or Japanese version of HoloLens, you’ll need to download the build for the language on a PC and then install it on your HoloLens using the Windows Device Recovery Tool (WDRT). ->[!IMPORTANT] +>[!IMPORTANT] >Installing the Chinese or Japanese builds of HoloLens using WDRT will delete existing data, like personal files and settings, from your HoloLens. diff --git a/devices/surface-hub/admin-group-management-for-surface-hub.md b/devices/surface-hub/admin-group-management-for-surface-hub.md index f3e0e2e1ba..8125113887 100644 --- a/devices/surface-hub/admin-group-management-for-surface-hub.md +++ b/devices/surface-hub/admin-group-management-for-surface-hub.md @@ -37,7 +37,7 @@ Note that the local admin account information is not backed by any directory ser ### Domain join the device to Active Directory (AD) -You can domain join the Surface Hub to your AD domain to allow users from a specified security group to configure settings. During first run, choose to use [Active Directory Domain Services](first-run-program-surface-hub.md#a-href-iduse-active-directoryause-active-directory-domain-services). You'll need to provide credentials that are capable of joining the domain of your choice, and the name of an existing security group. Anyone who is a member of that security group can enter their credentials and unlock Settings. +You can domain join the Surface Hub to your AD domain to allow users from a specified security group to configure settings. During first run, choose to use [Active Directory Domain Services](first-run-program-surface-hub.md#use-active-directory-domain-services). You'll need to provide credentials that are capable of joining the domain of your choice, and the name of an existing security group. Anyone who is a member of that security group can enter their credentials and unlock Settings. #### What happens when you domain join your Surface Hub? Surface Hubs use domain join to: @@ -53,7 +53,7 @@ Surface Hub does not support applying group policies or certificates from the do ### Azure Active Directory (Azure AD) join the device -You can Azure AD join the Surface Hub to allow IT pros from your Azure AD tenant to configure settings. During first run, choose to use [Microsoft Azure Active Directory](first-run-program-surface-hub.md#a-href-iduse-microsoft-azureause-microsoft-azure-active-directory). You will need to provide credentials that are capable of joining the Azure AD tenant of your choice. After you successfully Azure AD join, the appropriate people will be granted admin rights on the device. +You can Azure AD join the Surface Hub to allow IT pros from your Azure AD tenant to configure settings. During first run, choose to use [Microsoft Azure Active Directory](first-run-program-surface-hub.md#use-microsoft-azure-active-directory). You will need to provide credentials that are capable of joining the Azure AD tenant of your choice. After you successfully Azure AD join, the appropriate people will be granted admin rights on the device. By default, all **global administrators** will be given admin rights on an Azure AD joined Surface Hub. With **Azure AD Premium** or **Enterprise Mobility Suite (EMS)**, you can add additional administrators: 1. In the [Azure classic portal](https://manage.windowsazure.com/), click **Active Directory**, and then click the name of your organization's directory. diff --git a/devices/surface/surface-enterprise-management-mode.md b/devices/surface/surface-enterprise-management-mode.md index 5dfb51b75b..9244515eb1 100644 --- a/devices/surface/surface-enterprise-management-mode.md +++ b/devices/surface/surface-enterprise-management-mode.md @@ -29,7 +29,7 @@ There are two administrative options you can use to manage SEMM and enrolled Sur The primary workspace of SEMM is Microsoft Surface UEFI Configurator, as shown in Figure 1. Microsoft Surface UEFI Configurator is a tool that is used to create Windows Installer (.msi) packages or WinPE images that are used to enroll, configure, and unenroll SEMM on a Surface device. These packages contain a configuration file where the settings for UEFI are specified. SEMM packages also contain a certificate that is installed and stored in firmware and used to verify the signature of configuration files before UEFI settings are applied. - + *Figure 1. Microsoft Surface UEFI Configurator* @@ -51,7 +51,7 @@ You can download Microsoft Surface UEFI Configurator from the [Surface Tools for Surface UEFI configuration packages are the primary mechanism to implement and manage SEMM on Surface devices. These packages contain a configuration file of UEFI settings specified during creation of the package in Microsoft Surface UEFI Configurator and a certificate file, as shown in Figure 2. When a configuration package is run for the first time on a Surface device that is not already enrolled in SEMM, it provisions the certificate file in the device’s firmware and enrolls the device in SEMM. When enrolling a device in SEMM, you will be prompted to confirm the operation by providing the last two digits of the SEMM certificate thumbprint before the certificate file is stored and the enrollment can complete. This confirmation requires that a user be present at the device at the time of enrollment to perform the confirmation. - + *Figure 2. Secure a SEMM configuration package with a certificate* @@ -64,11 +64,11 @@ After a device is enrolled in SEMM, the configuration file is read and the setti You can use Surface UEFI settings to enable or disable the operation of individual components, such as cameras, wireless communication, or docking USB port (as shown in Figure 3), and configure advanced settings (as shown in Figure 4). - + *Figure 3. Enable or disable devices in Surface UEFI with SEMM* - + *Figure 4. Configure advanced settings with SEMM* @@ -102,13 +102,13 @@ You can configure the following advanced settings with SEMM: >[!NOTE] >When you create a SEMM configuration package, two characters are shown on the **Successful** page, as shown in Figure 5. - + *Figure 5. Display of the last two characters of the certificate thumbprint on the Successful page* These characters are the last two characters of the certificate thumbprint and should be written down or recorded. The characters are required to confirm enrollment in SEMM on a Surface device, as shown in Figure 6. - + *Figure 6. Enrollment confirmation in SEMM with the SEMM certificate thumbprint* @@ -134,7 +134,7 @@ A Surface UEFI reset package is used to perform only one task — to unenroll a In some scenarios, it may be impossible to use a Surface UEFI reset package. (For example, if Windows becomes unusable on the Surface device.) In these scenarios you can unenroll the Surface device from SEMM through the **Enterprise Management** page of Surface UEFI (shown in Figure 7) with a Recovery Request operation. - + *Figure 7. Initiate a SEMM recovery request on the Enterprise Management page* diff --git a/education/windows/autopilot-reset.md b/education/windows/autopilot-reset.md index 92f671930d..2c11c122c4 100644 --- a/education/windows/autopilot-reset.md +++ b/education/windows/autopilot-reset.md @@ -77,7 +77,7 @@ Autopilot Reset is a two-step process: trigger it and then authenticate. Once yo 2. Sign in with the admin account credentials. If you created a provisioning package, plug in the USB drive and trigger Autopilot Reset. ->[!IMPORTANT] +>[!IMPORTANT] >To reestablish Wi-Fi connectivity after reset, make sure the **Connect automatically** box is checked for the device's wireless network connection. Once Autopilot Reset is triggered, the reset process starts. diff --git a/education/windows/set-up-students-pcs-to-join-domain.md b/education/windows/set-up-students-pcs-to-join-domain.md index 22ee5f98f0..3842e9d435 100644 --- a/education/windows/set-up-students-pcs-to-join-domain.md +++ b/education/windows/set-up-students-pcs-to-join-domain.md @@ -28,7 +28,7 @@ Follow the steps in [Provision PCs with common settings for initial deployment ( 1. In the **Account Management** step: - > [!WARNING] + > [!WARNING] > If you don't create a local administrator account and the device fails to enroll in Active Directory for any reason, you will have to reimage the device and start over. As a best practice, we recommend: > - Use a least-privileged domain account to join the device to the domain. > - Create a temporary administrator account to use for debugging or reprovisioning if the device fails to enroll successfully. diff --git a/mdop/appv-v4/about-app-v-package-accelerators--app-v-46-sp1-.md b/mdop/appv-v4/about-app-v-package-accelerators--app-v-46-sp1-.md index 44b77a218d..1b90836822 100644 --- a/mdop/appv-v4/about-app-v-package-accelerators--app-v-46-sp1-.md +++ b/mdop/appv-v4/about-app-v-package-accelerators--app-v-46-sp1-.md @@ -1,11 +1,11 @@ --- title: About App-V Package Accelerators (App-V 4.6 SP1) description: About App-V Package Accelerators (App-V 4.6 SP1) -author: dansimp +author: manikadhiman ms.assetid: fc2d2375-8f17-4a6d-b374-771cb947cb8c ms.reviewer: manager: dansimp -ms.author: dansimp +ms.author: manikadhiman ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/g b/mdop/appv-v4/g new file mode 100644 index 0000000000..e69de29bb2 diff --git a/mdop/appv-v4/i b/mdop/appv-v4/i new file mode 100644 index 0000000000..e69de29bb2 diff --git a/mdop/appv-v4/sftmime--command-reference.md b/mdop/appv-v4/sftmime--command-reference.md index e8e258091f..1f2d7d6407 100644 --- a/mdop/appv-v4/sftmime--command-reference.md +++ b/mdop/appv-v4/sftmime--command-reference.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: a4a69228-9dd3-4623-b773-899d03c0cf10 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/sfttray-command-reference.md b/mdop/appv-v4/sfttray-command-reference.md index 8140bf0b25..0b72c8c94c 100644 --- a/mdop/appv-v4/sfttray-command-reference.md +++ b/mdop/appv-v4/sfttray-command-reference.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 6fa3a939-b047-4d6c-bd1d-dfb93e065eb2 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/side-by-side-privatization-failed-dialog-box--app-v-46-sp1-.md b/mdop/appv-v4/side-by-side-privatization-failed-dialog-box--app-v-46-sp1-.md index 0dcc776014..2148e9742b 100644 --- a/mdop/appv-v4/side-by-side-privatization-failed-dialog-box--app-v-46-sp1-.md +++ b/mdop/appv-v4/side-by-side-privatization-failed-dialog-box--app-v-46-sp1-.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: bcdb9b82-b53d-4a36-9f5d-71c021d4be28 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/software-audit-reportserver.md b/mdop/appv-v4/software-audit-reportserver.md index 6aff452589..4d147072ea 100644 --- a/mdop/appv-v4/software-audit-reportserver.md +++ b/mdop/appv-v4/software-audit-reportserver.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 55a49ed2-f331-40d3-add6-8e5fcd6816fd ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/stand-alone-delivery-scenario-for-application-virtualization-clients.md b/mdop/appv-v4/stand-alone-delivery-scenario-for-application-virtualization-clients.md index 9032d28833..ca951538f7 100644 --- a/mdop/appv-v4/stand-alone-delivery-scenario-for-application-virtualization-clients.md +++ b/mdop/appv-v4/stand-alone-delivery-scenario-for-application-virtualization-clients.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 7545b468-f58a-4504-a6d5-3c2d303731c4 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/stand-alone-delivery-scenario-overview.md b/mdop/appv-v4/stand-alone-delivery-scenario-overview.md index b575c0fb1c..7ac815d680 100644 --- a/mdop/appv-v4/stand-alone-delivery-scenario-overview.md +++ b/mdop/appv-v4/stand-alone-delivery-scenario-overview.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: b109f309-f3c1-43af-996f-2a9b138dd171 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/streaming-page-learn-more.md b/mdop/appv-v4/streaming-page-learn-more.md index b0c5184b1e..690d651a6b 100644 --- a/mdop/appv-v4/streaming-page-learn-more.md +++ b/mdop/appv-v4/streaming-page-learn-more.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: a69a57a0-1bbe-4604-840d-bfa87ec463e1 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/support-for-client-reporting-over-http.md b/mdop/appv-v4/support-for-client-reporting-over-http.md index b925ec73f6..85014b79b4 100644 --- a/mdop/appv-v4/support-for-client-reporting-over-http.md +++ b/mdop/appv-v4/support-for-client-reporting-over-http.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 4a26ac80-1fb5-4c05-83de-4d06793f7bf2 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/sxs-conflict-detected-dialog-box--app-v-46-sp1-.md b/mdop/appv-v4/sxs-conflict-detected-dialog-box--app-v-46-sp1-.md index 8f93271c15..03fc10a7d3 100644 --- a/mdop/appv-v4/sxs-conflict-detected-dialog-box--app-v-46-sp1-.md +++ b/mdop/appv-v4/sxs-conflict-detected-dialog-box--app-v-46-sp1-.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 7cbb67ba-cc11-4f10-b903-4a6af233eacb ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/system-error-reportserver.md b/mdop/appv-v4/system-error-reportserver.md index 237d59c2c4..a981fa9bd2 100644 --- a/mdop/appv-v4/system-error-reportserver.md +++ b/mdop/appv-v4/system-error-reportserver.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 4081db2f-92a6-4928-a26b-757048159094 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/system-utilization-reportserver.md b/mdop/appv-v4/system-utilization-reportserver.md index 1ec3d0ca07..7251ff513b 100644 --- a/mdop/appv-v4/system-utilization-reportserver.md +++ b/mdop/appv-v4/system-utilization-reportserver.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 4d490d15-2d1f-4f2c-99bb-0685447c0672 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/target-os-page-learn-more.md b/mdop/appv-v4/target-os-page-learn-more.md index ebff477c32..ef9fb2aa79 100644 --- a/mdop/appv-v4/target-os-page-learn-more.md +++ b/mdop/appv-v4/target-os-page-learn-more.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 003fd992-0a7e-494e-9e75-4dd5e0927e15 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/tasks-for-the-application-virtualization-sequencer--app-v-46-sp1-.md b/mdop/appv-v4/tasks-for-the-application-virtualization-sequencer--app-v-46-sp1-.md index 1a10986fb0..d7a550ba6b 100644 --- a/mdop/appv-v4/tasks-for-the-application-virtualization-sequencer--app-v-46-sp1-.md +++ b/mdop/appv-v4/tasks-for-the-application-virtualization-sequencer--app-v-46-sp1-.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 58597af9-6a62-4588-ab41-dbf6b7026267 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/tasks-for-the-application-virtualization-sequencer.md b/mdop/appv-v4/tasks-for-the-application-virtualization-sequencer.md index 80409aa31a..736d4abb06 100644 --- a/mdop/appv-v4/tasks-for-the-application-virtualization-sequencer.md +++ b/mdop/appv-v4/tasks-for-the-application-virtualization-sequencer.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 398018f4-297a-440d-b614-23f0ab03e7bd ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/troubleshooting-application-virtualization-sequencer-issues.md b/mdop/appv-v4/troubleshooting-application-virtualization-sequencer-issues.md index a3ddde9f65..d518b6dd1c 100644 --- a/mdop/appv-v4/troubleshooting-application-virtualization-sequencer-issues.md +++ b/mdop/appv-v4/troubleshooting-application-virtualization-sequencer-issues.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 2712094b-a0bc-4643-aced-5415535f3fec ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/troubleshooting-certificate-permission-issues.md b/mdop/appv-v4/troubleshooting-certificate-permission-issues.md index 16fc79d00d..62d5a6e274 100644 --- a/mdop/appv-v4/troubleshooting-certificate-permission-issues.md +++ b/mdop/appv-v4/troubleshooting-certificate-permission-issues.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 06b8cbbc-93fd-44aa-af39-2d780792d3c3 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/troubleshooting-information-for-the-application-virtualization-client.md b/mdop/appv-v4/troubleshooting-information-for-the-application-virtualization-client.md index 22e79957d1..37f2f88e78 100644 --- a/mdop/appv-v4/troubleshooting-information-for-the-application-virtualization-client.md +++ b/mdop/appv-v4/troubleshooting-information-for-the-application-virtualization-client.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 260a8dad-847f-4ec0-b7dd-6e6bc52017ed ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/troubleshooting-information-for-the-application-virtualization-server.md b/mdop/appv-v4/troubleshooting-information-for-the-application-virtualization-server.md index e96e8c89c6..80485a8023 100644 --- a/mdop/appv-v4/troubleshooting-information-for-the-application-virtualization-server.md +++ b/mdop/appv-v4/troubleshooting-information-for-the-application-virtualization-server.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: e9d43d9b-84f2-4d1b-bb90-a13740151e0c ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/troubleshooting-the-application-virtualization-sequencer.md b/mdop/appv-v4/troubleshooting-the-application-virtualization-sequencer.md index 499919914a..de5af9194f 100644 --- a/mdop/appv-v4/troubleshooting-the-application-virtualization-sequencer.md +++ b/mdop/appv-v4/troubleshooting-the-application-virtualization-sequencer.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 12ea8367-0b84-44e1-a885-e0539486556b ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/type-of-application-page--learn-more-.md b/mdop/appv-v4/type-of-application-page--learn-more-.md index 43e10916ae..72e6772aa9 100644 --- a/mdop/appv-v4/type-of-application-page--learn-more-.md +++ b/mdop/appv-v4/type-of-application-page--learn-more-.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: d1262d16-7b14-441e-8500-7974bf68d196 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/unload-app.md b/mdop/appv-v4/unload-app.md index f1fc716403..a2748ee100 100644 --- a/mdop/appv-v4/unload-app.md +++ b/mdop/appv-v4/unload-app.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: f0d729ae-8772-498b-be11-1a4b35499c53 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/unload-package.md b/mdop/appv-v4/unload-package.md index d6b99df94d..03039cbbfe 100644 --- a/mdop/appv-v4/unload-package.md +++ b/mdop/appv-v4/unload-package.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: a076eb5a-ce3d-49e4-ac7a-4d4df10e3477 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/unlock-app.md b/mdop/appv-v4/unlock-app.md index a3baef0cc3..8d20a7f7a3 100644 --- a/mdop/appv-v4/unlock-app.md +++ b/mdop/appv-v4/unlock-app.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 91fc8ceb-b4f5-4a06-8193-05189f830943 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/unpublish-package.md b/mdop/appv-v4/unpublish-package.md index b330633056..4111a75383 100644 --- a/mdop/appv-v4/unpublish-package.md +++ b/mdop/appv-v4/unpublish-package.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 1651427c-72a5-4701-bb57-71e14a7a3803 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/user-access-permissions-in-application-virtualization-client.md b/mdop/appv-v4/user-access-permissions-in-application-virtualization-client.md index 9b63a8f574..37f72f87ed 100644 --- a/mdop/appv-v4/user-access-permissions-in-application-virtualization-client.md +++ b/mdop/appv-v4/user-access-permissions-in-application-virtualization-client.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 7459374c-810c-45e3-b205-fdd1f8514f80 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/using-application-virtualization-servers-as-a-package-management-solution.md b/mdop/appv-v4/using-application-virtualization-servers-as-a-package-management-solution.md index cddeb89a38..11a9533a37 100644 --- a/mdop/appv-v4/using-application-virtualization-servers-as-a-package-management-solution.md +++ b/mdop/appv-v4/using-application-virtualization-servers-as-a-package-management-solution.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 41597355-e7bb-45e2-b300-7b1724419975 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/using-electronic-software-distribution-as-a-package-management-solution.md b/mdop/appv-v4/using-electronic-software-distribution-as-a-package-management-solution.md index d18552112d..6f8e379deb 100644 --- a/mdop/appv-v4/using-electronic-software-distribution-as-a-package-management-solution.md +++ b/mdop/appv-v4/using-electronic-software-distribution-as-a-package-management-solution.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 7d96ea70-3e7e-49fa-89cc-586804a10657 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/verify-applications-page--package-accelerators-.md b/mdop/appv-v4/verify-applications-page--package-accelerators-.md index e7872c65f7..6cb0bdd47e 100644 --- a/mdop/appv-v4/verify-applications-page--package-accelerators-.md +++ b/mdop/appv-v4/verify-applications-page--package-accelerators-.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: e58a37db-d042-453f-aa0d-2f324600a35b ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/virtual-application-package-additional-components.md b/mdop/appv-v4/virtual-application-package-additional-components.md index 93bc8cb78a..e44d919586 100644 --- a/mdop/appv-v4/virtual-application-package-additional-components.md +++ b/mdop/appv-v4/virtual-application-package-additional-components.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 476b0f40-ebd6-4296-92fa-61fa9495c03c ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/virtual-file-system-tab-keep.md b/mdop/appv-v4/virtual-file-system-tab-keep.md index 4539cb830f..9d50f3a15c 100644 --- a/mdop/appv-v4/virtual-file-system-tab-keep.md +++ b/mdop/appv-v4/virtual-file-system-tab-keep.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 9d084e2a-720d-4a25-9cd5-d0d70868b413 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/virtual-registry-tab-keep.md b/mdop/appv-v4/virtual-registry-tab-keep.md index a5fc398729..ab7b437cfd 100644 --- a/mdop/appv-v4/virtual-registry-tab-keep.md +++ b/mdop/appv-v4/virtual-registry-tab-keep.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 25833383-24c4-40a1-b34c-73b2bd3f11e1 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/virtual-services-tab-keep.md b/mdop/appv-v4/virtual-services-tab-keep.md index cc04c66c9e..2314727dbd 100644 --- a/mdop/appv-v4/virtual-services-tab-keep.md +++ b/mdop/appv-v4/virtual-services-tab-keep.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 9fc4679d-ccb5-4df7-99de-dd7d3a367ecc ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v4/wizard-pages--appv-46-sp1-.md b/mdop/appv-v4/wizard-pages--appv-46-sp1-.md index f0c3601dc1..8ea9090de2 100644 --- a/mdop/appv-v4/wizard-pages--appv-46-sp1-.md +++ b/mdop/appv-v4/wizard-pages--appv-46-sp1-.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: dadab8cf-fe6d-4cff-8f6c-e9676f244872 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/about-app-v-50-dynamic-configuration.md b/mdop/appv-v5/about-app-v-50-dynamic-configuration.md index 1bf73e3068..103b44d92c 100644 --- a/mdop/appv-v5/about-app-v-50-dynamic-configuration.md +++ b/mdop/appv-v5/about-app-v-50-dynamic-configuration.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 88afaca1-68c5-45c4-a074-9371c56b5804 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/about-app-v-50-reporting.md b/mdop/appv-v5/about-app-v-50-reporting.md index ccee39c432..a050c4a164 100644 --- a/mdop/appv-v5/about-app-v-50-reporting.md +++ b/mdop/appv-v5/about-app-v-50-reporting.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 27c33dda-f017-41e3-8a78-1b681543ec4f ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/about-app-v-50-sp1.md b/mdop/appv-v5/about-app-v-50-sp1.md index 451b009c6a..d77515d490 100644 --- a/mdop/appv-v5/about-app-v-50-sp1.md +++ b/mdop/appv-v5/about-app-v-50-sp1.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 2848a51b-452e-4c70-b465-f6717cfa667f ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/about-app-v-50-sp2.md b/mdop/appv-v5/about-app-v-50-sp2.md index 6b5b3c4422..9da2057ae1 100644 --- a/mdop/appv-v5/about-app-v-50-sp2.md +++ b/mdop/appv-v5/about-app-v-50-sp2.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 16ca8452-cef2-464e-b4b5-c10d4630fa6a ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/about-app-v-50-sp3.md b/mdop/appv-v5/about-app-v-50-sp3.md index 63df66e88a..c7b6ad9dc3 100644 --- a/mdop/appv-v5/about-app-v-50-sp3.md +++ b/mdop/appv-v5/about-app-v-50-sp3.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 67b5268b-edc1-4027-98b0-b3937dd70a6b ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/about-app-v-50.md b/mdop/appv-v5/about-app-v-50.md index fb3495e25e..76b86ac82d 100644 --- a/mdop/appv-v5/about-app-v-50.md +++ b/mdop/appv-v5/about-app-v-50.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 5799141b-44bc-4033-afcc-212235e15f00 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/about-app-v-51-dynamic-configuration.md b/mdop/appv-v5/about-app-v-51-dynamic-configuration.md index f177c5c927..b66bfce583 100644 --- a/mdop/appv-v5/about-app-v-51-dynamic-configuration.md +++ b/mdop/appv-v5/about-app-v-51-dynamic-configuration.md @@ -10,7 +10,7 @@ ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 ms.date: 08/28/2018 -ms.author: v-madhi +ms.author: dansimp --- # About App-V 5.1 dynamic configuration diff --git a/mdop/appv-v5/about-app-v-51-reporting.md b/mdop/appv-v5/about-app-v-51-reporting.md index 437bf0fac0..05c85668ea 100644 --- a/mdop/appv-v5/about-app-v-51-reporting.md +++ b/mdop/appv-v5/about-app-v-51-reporting.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 385dca00-7178-4e35-8d86-c58867ebd65c ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/about-app-v-51.md b/mdop/appv-v5/about-app-v-51.md index ce9936dd0f..199fc19259 100644 --- a/mdop/appv-v5/about-app-v-51.md +++ b/mdop/appv-v5/about-app-v-51.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 35bc9908-d502-4a9c-873f-8ee17b6d9d74 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/about-client-configuration-settings.md b/mdop/appv-v5/about-client-configuration-settings.md index 95a612993f..ab80cd454a 100644 --- a/mdop/appv-v5/about-client-configuration-settings.md +++ b/mdop/appv-v5/about-client-configuration-settings.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: cc7ae28c-b2ac-4f68-b992-5ccdbd5316a4 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/about-client-configuration-settings51.md b/mdop/appv-v5/about-client-configuration-settings51.md index 5fd93bfbda..608b86b707 100644 --- a/mdop/appv-v5/about-client-configuration-settings51.md +++ b/mdop/appv-v5/about-client-configuration-settings51.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 18bb307a-7eda-4dd6-a83e-6afaefd99470 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/about-the-connection-group-file.md b/mdop/appv-v5/about-the-connection-group-file.md index 761c226be9..a46bdbf5ea 100644 --- a/mdop/appv-v5/about-the-connection-group-file.md +++ b/mdop/appv-v5/about-the-connection-group-file.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: bfeb6013-a7ca-4e36-9fe3-229702e83f0d ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/about-the-connection-group-file51.md b/mdop/appv-v5/about-the-connection-group-file51.md index 349025a234..f8949ce649 100644 --- a/mdop/appv-v5/about-the-connection-group-file51.md +++ b/mdop/appv-v5/about-the-connection-group-file51.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 1f4df515-f5f6-4b58-91a8-c71598cb3ea4 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/about-the-connection-group-virtual-environment.md b/mdop/appv-v5/about-the-connection-group-virtual-environment.md index 75100634cb..34358bc9b5 100644 --- a/mdop/appv-v5/about-the-connection-group-virtual-environment.md +++ b/mdop/appv-v5/about-the-connection-group-virtual-environment.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 535fa640-cbd9-425e-8437-94650a70c264 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/about-the-connection-group-virtual-environment51.md b/mdop/appv-v5/about-the-connection-group-virtual-environment51.md index 32499187a5..4e889a147b 100644 --- a/mdop/appv-v5/about-the-connection-group-virtual-environment51.md +++ b/mdop/appv-v5/about-the-connection-group-virtual-environment51.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: b7bb0e3d-8cd5-45a9-b84e-c9ab4196a18c ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/accessibility-for-app-v-50.md b/mdop/appv-v5/accessibility-for-app-v-50.md index a20dd8d230..1f11859823 100644 --- a/mdop/appv-v5/accessibility-for-app-v-50.md +++ b/mdop/appv-v5/accessibility-for-app-v-50.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 56696523-6332-4bbe-8ddf-32b1dfe38131 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/accessibility-for-app-v-51.md b/mdop/appv-v5/accessibility-for-app-v-51.md index 0cf9055fe5..bae1242c01 100644 --- a/mdop/appv-v5/accessibility-for-app-v-51.md +++ b/mdop/appv-v5/accessibility-for-app-v-51.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: ef3f7742-f2e9-4748-ad60-74e0961b1bd9 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/administering-app-v-50-virtual-applications-by-using-the-management-console.md b/mdop/appv-v5/administering-app-v-50-virtual-applications-by-using-the-management-console.md index 7b05fe95fd..cb135d1d39 100644 --- a/mdop/appv-v5/administering-app-v-50-virtual-applications-by-using-the-management-console.md +++ b/mdop/appv-v5/administering-app-v-50-virtual-applications-by-using-the-management-console.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: e9280dbd-782b-493a-b495-daab25247795 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/administering-app-v-51-by-using-powershell.md b/mdop/appv-v5/administering-app-v-51-by-using-powershell.md index 96bacd5ed2..877702cf37 100644 --- a/mdop/appv-v5/administering-app-v-51-by-using-powershell.md +++ b/mdop/appv-v5/administering-app-v-51-by-using-powershell.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 9e10ff07-2cd9-4dc1-9e99-582f90c36081 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/administering-app-v-51-virtual-applications-by-using-the-management-console.md b/mdop/appv-v5/administering-app-v-51-virtual-applications-by-using-the-management-console.md index 0b60feb13f..72a7e81f82 100644 --- a/mdop/appv-v5/administering-app-v-51-virtual-applications-by-using-the-management-console.md +++ b/mdop/appv-v5/administering-app-v-51-virtual-applications-by-using-the-management-console.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: a4d078aa-ec54-4fa4-9463-bfb3b971d724 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/administering-app-v-by-using-powershell.md b/mdop/appv-v5/administering-app-v-by-using-powershell.md index b790e0a1b9..42d3dcaa27 100644 --- a/mdop/appv-v5/administering-app-v-by-using-powershell.md +++ b/mdop/appv-v5/administering-app-v-by-using-powershell.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 1ff4686a-1e19-4eff-b648-ada091281094 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/app-v-50-capacity-planning.md b/mdop/appv-v5/app-v-50-capacity-planning.md index 0da70f5f48..457f754602 100644 --- a/mdop/appv-v5/app-v-50-capacity-planning.md +++ b/mdop/appv-v5/app-v-50-capacity-planning.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 56f48b00-cd91-4280-9481-5372a0e2e792 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/app-v-50-deployment-checklist.md b/mdop/appv-v5/app-v-50-deployment-checklist.md index e89ddbd7da..811e99527d 100644 --- a/mdop/appv-v5/app-v-50-deployment-checklist.md +++ b/mdop/appv-v5/app-v-50-deployment-checklist.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: d6d93152-82b4-4b02-8b11-ed21d3331f00 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/app-v-50-planning-checklist.md b/mdop/appv-v5/app-v-50-planning-checklist.md index b6d777753f..4dbf695034 100644 --- a/mdop/appv-v5/app-v-50-planning-checklist.md +++ b/mdop/appv-v5/app-v-50-planning-checklist.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 81d3fa62-3c9e-4de7-a9da-cd13112b0862 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/app-v-50-prerequisites.md b/mdop/appv-v5/app-v-50-prerequisites.md index 0302114997..2ecd8abb24 100644 --- a/mdop/appv-v5/app-v-50-prerequisites.md +++ b/mdop/appv-v5/app-v-50-prerequisites.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 9756b571-c785-4ce6-a95c-d4e134e89429 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/app-v-50-security-considerations.md b/mdop/appv-v5/app-v-50-security-considerations.md index bf8f5d21ce..3359e49b81 100644 --- a/mdop/appv-v5/app-v-50-security-considerations.md +++ b/mdop/appv-v5/app-v-50-security-considerations.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 1e7292a0-7972-4b4f-85a9-eaf33f6c563a ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/app-v-50-sp3-prerequisites.md b/mdop/appv-v5/app-v-50-sp3-prerequisites.md index 2602520d15..fb281d9f9f 100644 --- a/mdop/appv-v5/app-v-50-sp3-prerequisites.md +++ b/mdop/appv-v5/app-v-50-sp3-prerequisites.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: fa8d5578-3a53-4e8a-95c7-e7a5f6e4a31c ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/app-v-50-sp3-supported-configurations.md b/mdop/appv-v5/app-v-50-sp3-supported-configurations.md index 358dab67f7..ce1e2700d6 100644 --- a/mdop/appv-v5/app-v-50-sp3-supported-configurations.md +++ b/mdop/appv-v5/app-v-50-sp3-supported-configurations.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 08ced79a-0ed3-43c3-82e7-de01c1f33e81 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/app-v-50-supported-configurations.md b/mdop/appv-v5/app-v-50-supported-configurations.md index 7e15af526e..d8aebe5e0d 100644 --- a/mdop/appv-v5/app-v-50-supported-configurations.md +++ b/mdop/appv-v5/app-v-50-supported-configurations.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 3787ff63-7ce7-45a8-8f01-81b4b6dced34 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/app-v-51-capacity-planning.md b/mdop/appv-v5/app-v-51-capacity-planning.md index 0857fe051a..81fe9f8d6c 100644 --- a/mdop/appv-v5/app-v-51-capacity-planning.md +++ b/mdop/appv-v5/app-v-51-capacity-planning.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 7a98062f-5a60-49d6-ab40-dc6057e1dd5a ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/app-v-51-deployment-checklist.md b/mdop/appv-v5/app-v-51-deployment-checklist.md index 6c7e928ab7..59236f1c84 100644 --- a/mdop/appv-v5/app-v-51-deployment-checklist.md +++ b/mdop/appv-v5/app-v-51-deployment-checklist.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 44bed85a-e4f5-49d7-a308-a2b681f76372 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/app-v-51-planning-checklist.md b/mdop/appv-v5/app-v-51-planning-checklist.md index bdbfdc5fdf..c662fbb94c 100644 --- a/mdop/appv-v5/app-v-51-planning-checklist.md +++ b/mdop/appv-v5/app-v-51-planning-checklist.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 1e26a861-0612-43a6-972f-375a40a8dcbc ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/app-v-51-prerequisites.md b/mdop/appv-v5/app-v-51-prerequisites.md index 6fba020f4b..037f317f8d 100644 --- a/mdop/appv-v5/app-v-51-prerequisites.md +++ b/mdop/appv-v5/app-v-51-prerequisites.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 1bfa03c1-a4ae-45ec-8a2b-b10c2b94bfb0 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/app-v-51-security-considerations.md b/mdop/appv-v5/app-v-51-security-considerations.md index b54278c951..dac917b699 100644 --- a/mdop/appv-v5/app-v-51-security-considerations.md +++ b/mdop/appv-v5/app-v-51-security-considerations.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 6bc6c1fc-f813-47d4-b763-06fd4faf6a72 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/app-v-51-supported-configurations.md b/mdop/appv-v5/app-v-51-supported-configurations.md index 3a0148212e..8b83ac6fad 100644 --- a/mdop/appv-v5/app-v-51-supported-configurations.md +++ b/mdop/appv-v5/app-v-51-supported-configurations.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 8b8db63b-f71c-4ae9-80e7-a6752334e1f6 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/application-publishing-and-client-interaction.md b/mdop/appv-v5/application-publishing-and-client-interaction.md index 019bd67909..17dee15c45 100644 --- a/mdop/appv-v5/application-publishing-and-client-interaction.md +++ b/mdop/appv-v5/application-publishing-and-client-interaction.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: c69a724a-85d1-4e2d-94a2-7ffe0b47d971 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/application-publishing-and-client-interaction51.md b/mdop/appv-v5/application-publishing-and-client-interaction51.md index d0d7b36135..66b1ace5e5 100644 --- a/mdop/appv-v5/application-publishing-and-client-interaction51.md +++ b/mdop/appv-v5/application-publishing-and-client-interaction51.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 36a4bf6f-a917-41a6-9856-6248686df352 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/check-reg-key-svr.md b/mdop/appv-v5/check-reg-key-svr.md index 89361828ee..84fc0d654a 100644 --- a/mdop/appv-v5/check-reg-key-svr.md +++ b/mdop/appv-v5/check-reg-key-svr.md @@ -9,7 +9,7 @@ ms.prod: w10 ms.date: 06/16/2016 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp --- diff --git a/mdop/appv-v5/creating-and-managing-app-v-50-virtualized-applications.md b/mdop/appv-v5/creating-and-managing-app-v-50-virtualized-applications.md index 98c65e2e5a..89f4fc49d7 100644 --- a/mdop/appv-v5/creating-and-managing-app-v-50-virtualized-applications.md +++ b/mdop/appv-v5/creating-and-managing-app-v-50-virtualized-applications.md @@ -5,7 +5,7 @@ author: manikadhiman ms.assetid: 66bab403-d7e0-4e7b-bc8f-a29a98a7160a ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library diff --git a/mdop/appv-v5/how-to-deploy-the-app-v-50-server-using-a-script.md b/mdop/appv-v5/how-to-deploy-the-app-v-50-server-using-a-script.md index fdaab43d4a..3132a01373 100644 --- a/mdop/appv-v5/how-to-deploy-the-app-v-50-server-using-a-script.md +++ b/mdop/appv-v5/how-to-deploy-the-app-v-50-server-using-a-script.md @@ -21,8 +21,8 @@ In order to complete the **appv\_server\_setup.exe** Server setup successfully u Use the following tables for more information about installing the App-V 5.0 server using the command line. ->[!NOTE] ->The information in the following tables can also be accessed using the command line by typing the following command: +>[!NOTE] +> The information in the following tables can also be accessed using the command line by typing the following command: >``` > appv\_server\_setup.exe /? >``` diff --git a/mdop/appv-v5/how-to-sequence-a-new-application-with-app-v-51-beta-gb18030.md b/mdop/appv-v5/how-to-sequence-a-new-application-with-app-v-51-beta-gb18030.md index d836a5126f..5143059379 100644 --- a/mdop/appv-v5/how-to-sequence-a-new-application-with-app-v-51-beta-gb18030.md +++ b/mdop/appv-v5/how-to-sequence-a-new-application-with-app-v-51-beta-gb18030.md @@ -71,7 +71,7 @@ ms.date: 06/16/2016 3. On the **Prepare Computer** page, review the issues that could cause the package creation to fail or could cause the package to contain unnecessary data. You should resolve all potential issues before you continue. After making any corrections, click **Refresh** to display the updated information. After you have resolved all potential issues, click **Next**. - > [!IMPORTANT] + > [!IMPORTANT] > If you are required to disable virus scanning software, you should first scan the computer that runs the sequencer in order to ensure that no unwanted or malicious files could be added to the package. @@ -102,7 +102,7 @@ If the application does not have an associated installer file and you plan to ru 7. On the **Installation** page, when the sequencer and application installer are ready you can proceed to install the application so that the sequencer can monitor the installation process. - > [!IMPORTANT] + > [!IMPORTANT] > You should always install applications to a secure location and make sure no other users are logged on to the computer running the sequencer during monitoring. @@ -143,7 +143,7 @@ Click **Next**. 13. On the **Target OS** page, specify the operating systems that can run this package. To allow all supported operating systems in your environment to run this package, select **Allow this package to run on any operating system**. To configure this package to run only on specific operating systems, select **Allow this package to run only on the following operating systems** and select the operating systems that can run this package. Click **Next**. - > [!IMPORTANT] + > [!IMPORTANT] > Make sure that the operating systems you specify here are supported by the application you are sequencing. @@ -152,7 +152,7 @@ Click **Next**. To save the package immediately, select **Save the package now** (default). Add optional **Comments** to be associated with the package. Comments are useful for identifying the program version and other information about the package. - > [!IMPORTANT] + > [!IMPORTANT] > The system does not support non-printable characters in **Comments** and **Descriptions**. @@ -165,7 +165,7 @@ The default **Save Location** is also displayed on this page. To change the defa The package is now available in the sequencer. - > [!IMPORTANT] + > [!IMPORTANT] > After you have successfully created a virtual application package, you cannot run the virtual application package on the computer that is running the sequencer. @@ -187,7 +187,7 @@ On the computer that runs the sequencer, click **All Programs**, and then Click 3. On the **Prepare Computer** page, review the issues that might cause the package creation to fail or could cause the package to contain unnecessary data. You should resolve all potential issues before you continue. After making any corrections, click **Refresh** to display the updated information. After you have resolved all potential issues, click **Next**. - > [!IMPORTANT] + > [!IMPORTANT] > If you are required to disable virus scanning software, you should first scan the computer that runs the sequencer in order to ensure that no unwanted or malicious files could be added to the package. @@ -229,7 +229,7 @@ On the computer that runs the sequencer, click **All Programs**, and then Click To save the package immediately, select **Save the package now**. Optionally, add a **Description** that will be associated with the package. Descriptions are useful for identifying the version and other information about the package. - > [!IMPORTANT] + > [!IMPORTANT] > The system does not support non-printable characters in Comments and Descriptions. @@ -246,7 +246,7 @@ The default **Save Location** is also displayed on this page. To change the defa 3. On the **Prepare Computer** page, review the issues that could cause the package creation to fail or could cause the package to contain unnecessary data. You should resolve all potential issues before you continue. After making any corrections, click **Refresh** to display the updated information. After you have resolved all potential issues, click **Next**. - > [!IMPORTANT] + > [!IMPORTANT] > If you are required to disable virus scanning software, you should first scan the computer that runs the App-V 5.0 Sequencer in order to ensure that no unwanted or malicious files can be added to the package. @@ -271,7 +271,7 @@ The default **Save Location** is also displayed on this page. To change the defa To save the package immediately, select **Save the package now**. Optionally, add a **Description** to be associated with the package. Descriptions are useful for identifying the program version and other information about the package. - > [!IMPORTANT] + > [!IMPORTANT] > The system does not support non-printable characters in Comments and Descriptions. @@ -284,7 +284,7 @@ The default **Save Location** is also displayed on this page. To change the defa The package is now available in the sequencer. To edit the package properties, click **Edit \[Package Name\]**. - > [!IMPORTANT] + > [!IMPORTANT] > After you have successfully created a virtual application package, you cannot run the virtual application package on the computer that is running the sequencer. diff --git a/mdop/dart-v10/getting-started-with-dart-10.md b/mdop/dart-v10/getting-started-with-dart-10.md index 0fc0d27b12..634c9a9c74 100644 --- a/mdop/dart-v10/getting-started-with-dart-10.md +++ b/mdop/dart-v10/getting-started-with-dart-10.md @@ -19,8 +19,8 @@ ms.date: 08/30/2016 Microsoft Diagnostics and Recovery Toolset (DaRT) 10 requires thorough planning before you deploy it or use its features. If you are new to this product, we recommend that you read the documentation carefully. Before you deploy the product to a production environment, we also recommend that you validate your deployment plan in a test network environment. You might also consider taking a class about relevant technologies. ->[!NOTE] ->A downloadable version of this administrator’s guide is not available. However, you can click **Download PDF** at the bottom of the Table of Contents pane to get a PDF version of this guide. +>[!NOTE] +> A downloadable version of this administrator’s guide is not available. However, you can click **Download PDF** at the bottom of the Table of Contents pane to get a PDF version of this guide. > >Additional information about this product can also be found on the [Diagnostics and Recovery Toolset documentation download page.](https://www.microsoft.com/download/details.aspx?id=27754) diff --git a/smb/cloud-mode-business-setup.md b/smb/cloud-mode-business-setup.md index c2d50ddd02..e85552bb33 100644 --- a/smb/cloud-mode-business-setup.md +++ b/smb/cloud-mode-business-setup.md @@ -252,7 +252,7 @@ Now that you have Azure AD Premium and have it properly configured, you can conf You can read this blog post to learn how you can combine login, Azure AD Join, and Intune MDM enrollment into an easy step so that you can bring your devices into a managed state that complies with the policies for your organization. We will use this blog post as our guide for this part of the walkthrough. -> [!IMPORTANT] +> [!IMPORTANT] > We will use the classic Azure portal instead of the new portal to configure automatic MDM enrollment with Intune. **To enable automatic MDM enrollment** diff --git a/windows/application-management/app-v/appv-about-appv.md b/windows/application-management/app-v/appv-about-appv.md index f52c78ba07..91926ff30c 100644 --- a/windows/application-management/app-v/appv-about-appv.md +++ b/windows/application-management/app-v/appv-about-appv.md @@ -51,7 +51,7 @@ The changes in App-V for Windows 10, version 1607 impact existing implementation * The App-V client is installed on user devices automatically with Windows 10, version 1607, and no longer has to be deployed separately. Performing an in-place upgrade to Windows 10, version 1607, on user devices automatically installs the App-V client. * In previous releases of App-V, the application sequencer was included in the Microsoft Desktop Optimization Pack. Although you’ll need to use the new application sequencer to create new virtualized applications, existing virtualized applications will continue to work. The App-V application sequencer is available from the [Windows 10 Assessment and Deployment Kit (ADK)](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit). - >[!NOTE] + > [!NOTE] >If you're already using App-V 5.x, you don't need to redeploy the App-V server components, as they haven't changed since App-V 5.0's release. For more information about how to configure an existing App-V installation after upgrading user devices to Windows 10, see [Upgrading to App-V for Windows 10 from an existing installation](../app-v/appv-upgrading-to-app-v-for-windows-10-from-an-existing-installation.md) and [Migrating to App-V for Windows 10 from a previous version](../app-v/appv-migrating-to-appv-from-a-previous-version.md). diff --git a/windows/application-management/app-v/appv-application-publishing-and-client-interaction.md b/windows/application-management/app-v/appv-application-publishing-and-client-interaction.md index f852b68c53..45588fbda9 100644 --- a/windows/application-management/app-v/appv-application-publishing-and-client-interaction.md +++ b/windows/application-management/app-v/appv-application-publishing-and-client-interaction.md @@ -411,14 +411,14 @@ The process then configures the client for package or connection group additions 5. Remove objects that are not published to the target (user or machine). - >[!NOTE] + > [!NOTE] >This will not perform a package deletion but rather remove integration points for the specific target (user or machine) and remove user catalog files (machine catalog files for globally published). 6. Invoke background load mounting based on client configuration. 7. Packages that already have publishing information for the machine or user are immediately restored. - >[!NOTE] + > [!NOTE] >This condition occurs as a product of removal without unpublishing with background addition of the package. This completes an App-V package add for the publishing refresh process. The next step is publishing the package to a specific target (machine or user). @@ -447,7 +447,7 @@ During the Publishing Refresh operation, the specific publishing operation, **Pu 2. Store backup information in the user’s registry and roaming profile (Shortcut Backups). - >[!NOTE] + > [!NOTE] >This enables restore extension points if the package is unpublished. 3. Run scripts targeted for publishing timing. diff --git a/windows/application-management/app-v/appv-configure-access-to-packages-with-the-management-console.md b/windows/application-management/app-v/appv-configure-access-to-packages-with-the-management-console.md index 318d7bb572..a4d1d3bb4f 100644 --- a/windows/application-management/app-v/appv-configure-access-to-packages-with-the-management-console.md +++ b/windows/application-management/app-v/appv-configure-access-to-packages-with-the-management-console.md @@ -34,8 +34,8 @@ Use the following procedure to configure access to virtualized packages. 1. Using the format **mydomain** \\ **groupname**, enter the name or part of the name of an Active Directory group object, then select **Check**. - >[!NOTE] - >Ensure that you provide an associated domain name for the group that you are searching for. + > [!NOTE] + > Ensure that you provide an associated domain name for the group that you are searching for. 3. Grant access to the package by first selecting the desired group, then selecting **Grant Access**. The newly added group is displayed in the **AD entities with access** pane. diff --git a/windows/application-management/app-v/appv-connection-group-file.md b/windows/application-management/app-v/appv-connection-group-file.md index 11bb4e3d26..16d0bd518e 100644 --- a/windows/application-management/app-v/appv-connection-group-file.md +++ b/windows/application-management/app-v/appv-connection-group-file.md @@ -93,7 +93,7 @@ You can use the connection group file to configure each connection group by usin - Specify runtime priorities for connection groups. To edit priority by using the App-V Management Console, select the connection group and then select **Edit**. - >[!NOTE] + > [!NOTE] >A package only requires priority if it's associated with more than one connection group. - Specify package precedence within the connection group. diff --git a/windows/application-management/app-v/appv-convert-a-package-created-in-a-previous-version-of-appv.md b/windows/application-management/app-v/appv-convert-a-package-created-in-a-previous-version-of-appv.md index 27efb333f1..b6228dd6cd 100644 --- a/windows/application-management/app-v/appv-convert-a-package-created-in-a-previous-version-of-appv.md +++ b/windows/application-management/app-v/appv-convert-a-package-created-in-a-previous-version-of-appv.md @@ -18,7 +18,7 @@ ms.topic: article You can use the package converter utility to upgrade virtual application packages created by previous versions of App-V. This section will tell you how to convert existing virtual application packages for upgrade. ->[!NOTE] +>[!NOTE] >If you are running a computer with a 64-bit architecture, you must use the x86 version of Windows PowerShell. The package converter can only directly convert packages created by an App-V sequencer version 4.5 or later. Packages created with an App-V version earlier than 4.5 must be upgraded to at least App-V 4.5 before conversion. @@ -54,8 +54,8 @@ The App-V package converter will save the App-V 4.6 installation root folder and Additionally, the package converter optimizes performance of packages in App-V for Windows 10 by setting the package to stream fault the App-V package. This is more performant than the primary feature block and fully downloading the package. The flag **DownloadFullPackageOnFirstLaunch** allows you to convert the package and set the package to be fully downloaded by default. - >[!NOTE] - >Before you specify the output directory, you must create the output directory. +> [!NOTE] + >Before you specify the output directory, you must create the output directory. ### Advanced Conversion Tips diff --git a/windows/application-management/app-v/appv-create-a-custom-configuration-file-with-the-management-console.md b/windows/application-management/app-v/appv-create-a-custom-configuration-file-with-the-management-console.md index fe5b518593..098316aee4 100644 --- a/windows/application-management/app-v/appv-create-a-custom-configuration-file-with-the-management-console.md +++ b/windows/application-management/app-v/appv-create-a-custom-configuration-file-with-the-management-console.md @@ -30,11 +30,8 @@ You can create a dynamic user configuration file with the App-V Management Conso 4. Select **Advanced**, and then select **Export Configuration**. Enter a file name and select **Save**. Now you can edit the file to configure a package for a user. - >[!NOTE] - >If you want to export a configuration while running on Windows Server, make sure to disable the IE Enhanced Security Configuration setting. If this setting is enabled and set to block downloads, you won't be able to download anything from the App-V Server. - - - + > [!NOTE] + > If you want to export a configuration while running on Windows Server, make sure to disable the IE Enhanced Security Configuration setting. If this setting is enalbed and set to block downloads, you won't be able to download anything from the App-V Server. ## Related topics diff --git a/windows/application-management/app-v/appv-create-a-package-accelerator.md b/windows/application-management/app-v/appv-create-a-package-accelerator.md index edd86cbce5..e16200acad 100644 --- a/windows/application-management/app-v/appv-create-a-package-accelerator.md +++ b/windows/application-management/app-v/appv-create-a-package-accelerator.md @@ -53,7 +53,7 @@ Use the following procedure to create a package accelerator. 6. On the **Gathering Information** page, review the files that you couldn't find in the location specified by the **Installation Files** page. If the files displayed are not required, select **Remove these files**, then select **Next**. If the files are required, select **Previous** and copy the required files to the directory specified on the **Installation Files** page. - >[!NOTE] + > [!NOTE] >You must either remove the unrequired files or select **Previous** and locate the required files to advance to the next page of this wizard. 7. On the **Select Files** page, carefully review the detected files. Clear any file the package accelerator doesn't need to run successfully and select only the files that the application requires. When you're done, select **Next**. diff --git a/windows/application-management/app-v/appv-create-a-virtual-application-package-package-accelerator.md b/windows/application-management/app-v/appv-create-a-virtual-application-package-package-accelerator.md index 9d287e1b55..936ec0bf29 100644 --- a/windows/application-management/app-v/appv-create-a-virtual-application-package-package-accelerator.md +++ b/windows/application-management/app-v/appv-create-a-virtual-application-package-package-accelerator.md @@ -40,7 +40,7 @@ Use the following procedure to create a virtual application package with the App Alternatively, if you have already copied the installation files to a directory on this computer, select **Make New Folder**, browse to the folder that contains the installation files, then select **Next**. - >[!NOTE] + > [!NOTE] >You can specify the following types of supported installation files: > - Windows Installer files (**.msi**) > - Cabinet files (.cab) diff --git a/windows/application-management/app-v/appv-create-and-use-a-project-template.md b/windows/application-management/app-v/appv-create-and-use-a-project-template.md index 92d3b64795..5e2bef4061 100644 --- a/windows/application-management/app-v/appv-create-and-use-a-project-template.md +++ b/windows/application-management/app-v/appv-create-and-use-a-project-template.md @@ -27,7 +27,7 @@ You must first create and save a project template, including a virtual app packa 1. On the device running the App-V Sequencer, select **Start**, select **All Programs**, select **Microsoft Application Virtualization**, and then select **Microsoft Application Virtualization Sequencer**. - >[!NOTE] + > [!NOTE] >If the virtual app package is currently open in the App-V Sequencer console, skip to Step 3 of this procedure. 2. On the **File** menu, select **Open**, select **Edit Package**, browse for the virtual app package that includes the settings you want to save with the App-V Project Template, and then select **Edit** to change any of the settings or info included in the file. diff --git a/windows/application-management/app-v/appv-creating-and-managing-virtualized-applications.md b/windows/application-management/app-v/appv-creating-and-managing-virtualized-applications.md index b80b894483..66e540afb8 100644 --- a/windows/application-management/app-v/appv-creating-and-managing-virtualized-applications.md +++ b/windows/application-management/app-v/appv-creating-and-managing-virtualized-applications.md @@ -31,7 +31,7 @@ You can use the App-V Sequencer to perform the following tasks: - Upgrade existing packages. You can expand an existing package onto the computer running the sequencer and then upgrade the application to create a newer version. - Edit configuration information associated with an existing package. For example, you can add a shortcut or modify a file type association. - >[!NOTE] + > [!NOTE] >You must create shortcuts and save them to an available network location to allow roaming. If a shortcut is created and saved in a private location, the package must be published locally to the computer running the App-V client. - Convert existing virtual packages. diff --git a/windows/application-management/app-v/appv-deploy-the-appv-server.md b/windows/application-management/app-v/appv-deploy-the-appv-server.md index 9f1b448fb1..79a0d77597 100644 --- a/windows/application-management/app-v/appv-deploy-the-appv-server.md +++ b/windows/application-management/app-v/appv-deploy-the-appv-server.md @@ -54,7 +54,7 @@ ms.topic: article | You are using a custom database name. | Select **Custom configuration** and type the database name.
The database name must be unique, or the installation will fail.| 8. On the **Configure** page, accept the default value, **Use this local computer**. - >[!NOTE] + > [!NOTE] >If you're installing the Management server and Management database side-by-side, the appropriate options are selected by default and cannot be changed. 9. On the initial **Create New Reporting Database** page, configure the **Microsoft SQL Server instance** and **Reporting Server database** by selecting the appropriate option below. @@ -64,7 +64,7 @@ ms.topic: article | You are using a custom database name. | Select **Custom configuration** and type the database name.
The database name must be unique, or the installation will fail.| 10. On the **Configure** page, accept the default value: **Use this local computer**. - >[!NOTE] + > [!NOTE] >If you're installing the Management server and Management database side-by-side, the appropriate options are selected by default and cannot be changed. 11. On the **Configure** (Management Server Configuration) page, specify the following: diff --git a/windows/application-management/app-v/appv-deploying-microsoft-office-2013-with-appv.md b/windows/application-management/app-v/appv-deploying-microsoft-office-2013-with-appv.md index 44920d8d72..ea9f0906f7 100644 --- a/windows/application-management/app-v/appv-deploying-microsoft-office-2013-with-appv.md +++ b/windows/application-management/app-v/appv-deploying-microsoft-office-2013-with-appv.md @@ -110,7 +110,7 @@ The XML file included in the Office Deployment Tool specifies the product detail ``` - >[!NOTE] + > [!NOTE] >The configuration XML is a sample XML file. This file includes lines that are commented out. You can “uncomment” these lines to customize additional settings with the file. The previous example of an XML configuration file specifies that Office 2013 ProPlus 32-bit edition, including Visio ProPlus, will be downloaded in English to the \\\\server\\Office 2013, which is the location where Office applications will be saved to. Note that the Product ID of the applications will not affect the final licensing of Office. Office 2013 App-V packages with various licensing can be created from the same applications by specifying licensing in a later stage. For more information, see [Customizable attributes and elements of the XML file](#customizable-attributes-and-elements-of-the-xml-file), later in this topic. @@ -206,7 +206,7 @@ After you download the Office 2013 applications through the Office Deployment To An example of when to use this parameter is if you create different packages for different users. For example, you can create a package with just Office 2013 for some users, and create another package with Office 2013 and Visio 2013 for another set of users. - >[!NOTE] + > [!NOTE] >Even if you use unique package IDs, you can still deploy only one App-V package to a single device. 2. Use the **/packager** command to convert the Office applications to an Office 2013 App-V package. @@ -231,7 +231,7 @@ After you download the Office 2013 applications through the Office Deployment To * **App-V Packages**, which contains an Office 2013 App-V package and two deployment configuration files.
* **WorkingDir** - >[!NOTE] + > [!NOTE] >To troubleshoot any issues, see the log files in the %temp% directory (default). 3. Verify that the Office 2013 App-V package works correctly: diff --git a/windows/application-management/app-v/appv-deploying-microsoft-office-2016-with-appv.md b/windows/application-management/app-v/appv-deploying-microsoft-office-2016-with-appv.md index d38f80fbd5..74b0b27728 100644 --- a/windows/application-management/app-v/appv-deploying-microsoft-office-2016-with-appv.md +++ b/windows/application-management/app-v/appv-deploying-microsoft-office-2016-with-appv.md @@ -111,7 +111,7 @@ The XML file included in the Office Deployment Tool specifies the product detail ``` - >[!NOTE] + > [!NOTE] >The configuration XML is a sample XML file. The file includes lines that are commented out. You can “uncomment” these lines to customize additional settings with the file. To uncomment these lines, remove the `````` from the end of the line. The previous example of an XML configuration file specifies that Office 2016 ProPlus 32-bit edition, including Visio ProPlus, will be downloaded in English to the \\\\server\\Office2016 location where Office applications will be saved. Note that the Product ID of the applications will not affect Office's final licensing. You can create Office 2016 App-V packages with various licensing from the same applications by specifying licensing in a later stage. The following table summarizes the XML file's customizable attributes and elements: @@ -190,7 +190,7 @@ After you download the Office 2016 applications through the Office Deployment To An example of when to use this parameter is if you create different packages for different users. For example, you can create a package with just Office 2016 for some users, and create another package with Office 2016 and Visio 2016 for another set of users. - >[!NOTE] + > [!NOTE] >Even if you use unique package IDs, you can still deploy only one App-V package to a single device. 2. Use the /packager command to convert the Office applications to an Office 2016 App-V package. @@ -215,7 +215,7 @@ After you download the Office 2016 applications through the Office Deployment To * **App-V Packages**—contains an Office 2016 App-V package and two deployment configuration files. * **WorkingDir** - >[!NOTE] + > [!NOTE] >To troubleshoot any issues, see the log files in the %temp% directory (default). 3. Verify that the Office 2016 App-V package works correctly: @@ -359,7 +359,7 @@ To upgrade an Office 2016 package, use the Office Deployment Tool. To upgrade a 1. Create a new Office 2016 package through the Office Deployment Tool that uses the most recent Office 2016 application software. The most recent Office 2016 bits can always be obtained through the download stage of creating an Office 2016 App-V Package. The newly created Office 2016 package will have the most recent updates and a new Version ID. All packages created using the Office Deployment Tool have the same lineage. - >[!NOTE] + > [!NOTE] >Office App-V packages have two Version IDs: >* An Office 2016 App-V Package Version ID that is unique across all packages created using the Office Deployment Tool. >* A second App-V Package Version ID, formatted as X.X.X.X, in the AppX manifest that will only change if there is a new version of Office itself. For example, if a new Office 2016 release with upgrades is available, and a package is created through the Office Deployment Tool to incorporate these upgrades, the X.X.X.X version ID will change to reflect the new version of Office. The App-V server will use the X.X.X.X version ID to differentiate this package and recognize that it contains new upgrades to the previously published package, and as a result, publish it as an upgrade to the existing Office 2016 package. diff --git a/windows/application-management/app-v/appv-deploying-the-appv-server.md b/windows/application-management/app-v/appv-deploying-the-appv-server.md index 0827190013..ae16a7025e 100644 --- a/windows/application-management/app-v/appv-deploying-the-appv-server.md +++ b/windows/application-management/app-v/appv-deploying-the-appv-server.md @@ -35,7 +35,7 @@ App-V offers the following five server components, each of which serves a specif * **Management server.** Use the App-V management server and console to manage your App-V infrastructure. See [Administering App-V with the management console](appv-administering-virtual-applications-with-the-management-console.md) for more information about the management server. - >[!NOTE] + > [!NOTE] >If you are using App-V with your electronic software distribution solution, you don’t need to use the management server and console. However, you may want to take advantage of the reporting and streaming capabilities in App-V. * **Management database.** Use the App-V management database to facilitate database pre-deployments for App-V management. For more information about the management database, see [How to deploy the App-V server](appv-deploy-the-appv-server.md). * **Publishing server.** Use the App-V publishing server to host and stream virtual applications. The publishing server supports the HTTP and HTTPS protocols and does not require a database connection. To learn how to configure the publishing server, see [How to install the App-V publishing server](appv-install-the-publishing-server-on-a-remote-computer.md). diff --git a/windows/application-management/app-v/appv-dynamic-configuration.md b/windows/application-management/app-v/appv-dynamic-configuration.md index a06eec8e98..61c8be02a4 100644 --- a/windows/application-management/app-v/appv-dynamic-configuration.md +++ b/windows/application-management/app-v/appv-dynamic-configuration.md @@ -428,7 +428,7 @@ The body of the deployment configuration file includes two sections: ``` -User Configuration: see [Dynamic User Configuration File](appv-dynamic-configuration.md#dynamic-user-configuration-file) for more information about this section. +User Configuration: see [Dynamic User Configuration](#dynamic-user-configuration-file) for more information about this section. Machine Configuration: The Machine Configuration section of the Deployment Configuration File configures information that can only be set for an entire machine, not a specific user on the computer, like the HKEY\_LOCAL\_MACHINE registry keys in the Virtual Registry. This element can have the following four subsections. diff --git a/windows/application-management/app-v/appv-install-the-management-and-reporting-databases-on-separate-computers.md b/windows/application-management/app-v/appv-install-the-management-and-reporting-databases-on-separate-computers.md index ab69c602ad..30f57f3cb7 100644 --- a/windows/application-management/app-v/appv-install-the-management-and-reporting-databases-on-separate-computers.md +++ b/windows/application-management/app-v/appv-install-the-management-and-reporting-databases-on-separate-computers.md @@ -33,7 +33,7 @@ Use the following procedure to install the database server and management server * If you are using a custom database name, select **Custom configuration** and enter the database name. 7. On the next **Create new management server database** page, select **Use a remote computer**, then enter the remote machine account using the following format: ```Domain\MachineAccount```. - >[!NOTE] + > [!NOTE] >If you plan to deploy the management server on the same computer you must select **Use this local computer**. Specify the user name for the management server **Install Administrator** using the following format: ```Domain\AdministratorLoginName```. After that, select **Next**. 8. To start the installation, select **Install**. @@ -49,7 +49,7 @@ Use the following procedure to install the database server and management server * If you're using a custom database name, select **Custom configuration** and enter the database name. 7. On the next **Create new management server database** page, select **Use a remote computer**, and enter the remote machine account using the following format: ```Domain\MachineAccount```. - >[!NOTE] + > [!NOTE] >If you plan to deploy the reporting server on the same computer you must select **Use this local computer**. Specify the user name for the reporting server **Install Administrator** using the following format: Domain\\AdministratorLoginName. After that, select **Next**. 8. To start the installation, select **Install**. @@ -68,7 +68,7 @@ Use the following procedure to install the database server and management server * The App-V Reporting Database scripts and instructions readme are located in the following folder: **InstallationExtractionLocation** \\ **Database Scripts** \\ **Reporting Database**. 4. For each database, copy the scripts to a share and modify them following the instructions in the readme file. - >[!NOTE] + > [!NOTE] >For more information about modifying the required SIDs contained in the scripts see, [How to Install the App-V Databases and Convert the Associated Security Identifiers by Using Windows PowerShell](appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md). 5. Run the scripts on the computer running Microsoft SQL Server. diff --git a/windows/application-management/app-v/appv-install-the-management-server-on-a-standalone-computer.md b/windows/application-management/app-v/appv-install-the-management-server-on-a-standalone-computer.md index a1a2580c13..314545131f 100644 --- a/windows/application-management/app-v/appv-install-the-management-server-on-a-standalone-computer.md +++ b/windows/application-management/app-v/appv-install-the-management-server-on-a-standalone-computer.md @@ -25,7 +25,7 @@ To install the management server on a standalone computer and connect it to the 5. On the **Installation Location** page, accept the default location, then select **Next**. 6. On the **Configure Existing Management Database** page, select **Use a remote SQL Server**, then enter the computer running Microsoft SQL's machine name, such as ```SqlServerMachine```. - >[!NOTE] + > [!NOTE] >If the Microsoft SQL Server is deployed on the same server, select **Use local SQL Server**. For the SQL Server Instance, select **Use the default instance**. If you are using a custom Microsoft SQL Server instance, you must select **Use a custom instance**, then enter the instance's name. Specify the **SQL Server Database name** that this management server will use, such as ```AppvManagement```. 7. On the **Configure management server configuration** page, specify the following items: * The AD group or account that will connect to the management console for administrative purposes for example **MyDomain\\MyUser** or **MyDomain\\AdminGroup**. The account or AD group you specify will be enabled to manage the server through the management console. You can add additional users or groups using the management console after installation diff --git a/windows/application-management/app-v/appv-install-the-reporting-server-on-a-standalone-computer.md b/windows/application-management/app-v/appv-install-the-reporting-server-on-a-standalone-computer.md index 66ae70f8bd..a0a7912e96 100644 --- a/windows/application-management/app-v/appv-install-the-reporting-server-on-a-standalone-computer.md +++ b/windows/application-management/app-v/appv-install-the-reporting-server-on-a-standalone-computer.md @@ -30,7 +30,7 @@ Use the following procedure to install the reporting server on a standalone comp 5. On the **Installation location** page, accept the default location and select **Next**. 6. On the **Configure existing reporting database** page, select **Use a remote SQL Server**, then enter the machine name of the computer running Microsoft SQL Server. For example, you can name your computer **SqlServerMachine**. - >[!NOTE] + > [!NOTE] >If the Microsoft SQL Server is deployed on the same server, select **Use local SQL Server**. For the SQL Server instance, select **Use the default instance**. If you're using a custom Microsoft SQL Server instance, select **Use a custom instance**, then enter the name of your custom instance. Specify the **SQL Server Database name** that this reporting server will use; for example, you can name the server **AppvReporting**. 7. On the **Configure reporting server configuration** page. diff --git a/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md b/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md index 2e1a1e5f64..f0f0b0ad03 100644 --- a/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md +++ b/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md @@ -32,8 +32,8 @@ Get-AppvClientPackage –Name "ContosoApplication" -Version 2 Use the **Add-AppvClientPackage** cmdlet to add a package to a computer. ->[!IMPORTANT] ->This example only adds a package. It does not publish the package to the user or the computer. +> [!IMPORTANT] +> This example only adds a package. It does not publish the package to the user or the computer. For example: @@ -59,8 +59,8 @@ Publish-AppvClientPackage "ContosoApplication" -Global ## Publish a package to a specific user ->[!NOTE] ->You must use App-V 5.0 SP2 Hotfix Package 5 or later to use this parameter. +> [!NOTE] +> You must use App-V 5.0 SP2 Hotfix Package 5 or later to use this parameter. An administrator can publish a package to a specific user by specifying the optional *–UserSID* parameter with the **Publish-AppvClientPackage** cmdlet, where *-UserSID* represents the end user’s security identifier (SID). @@ -99,8 +99,8 @@ Unpublish-AppvClientPackage "ContosoApplication" ## Unpublish a package for a specific user ->[!NOTE] ->You must use App-V 5.0 SP2 Hotfix Package 5 or later to use this parameter. +> [!NOTE] +> You must use App-V 5.0 SP2 Hotfix Package 5 or later to use this parameter. An administrator can unpublish a package for a specific user by using the optional *-UserSID* parameter with the **Unpublish-AppvClientPackage** cmdlet, where *-UserSID* represents the end user’s security identifier (SID). @@ -127,8 +127,8 @@ For example: Remove-AppvClientPackage "ContosoApplication" ``` ->[!NOTE] ->App-V cmdlets have been assigned to variables for the previous examples for clarity only; assignment is not a requirement. Most cmdlets can be combined as displayed in [Add and publish a package](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#add-and-publish-a-package). For a detailed tutorial, see [App-V 5.0 Client PowerShell Deep Dive](https://blogs.technet.microsoft.com/appv/2012/12/03/app-v-5-0-client-powershell-deep-dive/). +> [!NOTE] +> App-V cmdlets have been assigned to variables for the previous examples for clarity only; assignment is not a requirement. Most cmdlets can be combined as displayed in [Add and publish a package](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#add-and-publish-a-package). For a detailed tutorial, see [App-V 5.0 Client PowerShell Deep Dive](https://blogs.technet.microsoft.com/appv/2012/12/03/app-v-5-0-client-powershell-deep-dive/). ## Enable only administrators to publish or unpublish packages diff --git a/windows/application-management/app-v/appv-planning-for-high-availability-with-appv.md b/windows/application-management/app-v/appv-planning-for-high-availability-with-appv.md index 178c952b5a..e6167f8707 100644 --- a/windows/application-management/app-v/appv-planning-for-high-availability-with-appv.md +++ b/windows/application-management/app-v/appv-planning-for-high-availability-with-appv.md @@ -87,7 +87,7 @@ Use the following steps to modify the connection string to include ```failover p 2. Navigate to **HKEY\_LOCAL\_MACHINE** \\ **Software** \\ **Microsoft** \\ **AppV** \\ **Server** \\ **ManagementService**. 3. Modify the **MANAGEMENT\_SQL\_CONNECTION\_STRING** value with the ```failover partner =
This setting allows you to configure the algorithm and cipher strength used by BitLocker Drive Encryption. This setting is applied when you turn on BitLocker. Changing the encryption method has no effect if the drive is already encrypted, or if encryption is in progress.
@@ -193,7 +193,7 @@ The following diagram shows the BitLocker configuration service provider in tree - 6 = XTS-AES 128 - 7 = XTS-AES 256 -> [!Note] +> [!NOTE] > When you enable EncryptionMethodByDriveType, you must specify values for all three drives (operating system, fixed data, and removable data), otherwise it will fail (500 return status). For example, if you only set the encrytion method for the OS and removable drives, you will get a 500 return status.If you want to disable this policy use the following SyncML:
@@ -245,26 +245,26 @@ The following diagram shows the BitLocker configuration service provider in treeThis setting allows you to configure whether BitLocker requires additional authentication each time the computer starts and whether you are using BitLocker with or without a Trusted Platform Module (TPM). This setting is applied when you turn on BitLocker.
-> [!Note] +> [!NOTE] > Only one of the additional authentication options can be required at startup, otherwise an error occurs.If you want to use BitLocker on a computer without a TPM, set the "ConfigureNonTPMStartupKeyUsage_Name" data. In this mode either a password or a USB drive is required for start-up. When using a startup key, the key information used to encrypt the drive is stored on the USB drive, creating a USB key. When the USB key is inserted the access to the drive is authenticated and the drive is accessible. If the USB key is lost or unavailable or if you have forgotten the password then you will need to use one of the BitLocker recovery options to access the drive.
On a computer with a compatible TPM, four types of authentication methods can be used at startup to provide added protection for encrypted data. When the computer starts, it can use only the TPM for authentication, or it can also require insertion of a USB flash drive containing a startup key, the entry of a 6-digit to 20-digit personal identification number (PIN), or both.
-> [!Note] +> [!NOTE] > In Windows 10, version 1703 release B, you can use a minimum PIN of 4 digits. SystemDrivesMinimumPINLength policy must be set to allow PINs shorter than 6 digits.If you enable this policy setting, users can configure advanced startup options in the BitLocker setup wizard.
If you disable or do not configure this setting, users can configure only basic options on computers with a TPM.
-> [!Note] +> [!NOTE] > If you want to require the use of a startup PIN and a USB flash drive, you must configure BitLocker settings using the command-line tool manage-bde instead of the BitLocker Drive Encryption setup wizard.Sample value for this node to enable this policy is:
@@ -342,12 +342,12 @@ The following diagram shows the BitLocker configuration service provider in treeThis setting allows you to configure a minimum length for a Trusted Platform Module (TPM) startup PIN. This setting is applied when you turn on BitLocker. The startup PIN must have a minimum length of 6 digits and can have a maximum length of 20 digits.
-> [!Note] +> [!NOTE] > In Windows 10, version 1703 release B, you can use a minimum PIN length of 4 digits. > >In TPM 2.0 if minimum PIN length is set below 6 digits, Windows will attempt to update the TPM lockout period to be greater than the default when a PIN is changed. If successful, Windows will only reset the TPM lockout period back to default if the TPM is reset. This does not apply to TPM 1.2. @@ -411,7 +411,7 @@ The following diagram shows the BitLocker configuration service provider in treeThis setting lets you configure the entire recovery message or replace the existing URL that are displayed on the pre-boot key recovery screen when the OS drive is locked. @@ -437,7 +437,7 @@ The following diagram shows the BitLocker configuration service provider in tree - 'yy' = string of max length 900. - 'zz' = string of max length 500. -> [!Note] +> [!NOTE] > When you enable SystemDrivesRecoveryMessage, you must specify values for all three settings (pre-boot recovery screen, recovery message, and recovery URL), otherwise it will fail (500 return status). For example, if you only specify values for message and URL, you will get a 500 return status.
Disabling the policy will let the system choose the default behaviors. If you want to disable this policy use the following SyncML:
@@ -457,7 +457,7 @@ The following diagram shows the BitLocker configuration service provider in tree ``` -> [!Note] +> [!NOTE] > Not all characters and languages are supported in pre-boot. It is strongly recommended that you test that the characters you use for the custom message or URL appear correctly on the pre-boot recovery screen.Data type is string. Supported operations are Add, Get, Replace, and Delete.
@@ -492,7 +492,7 @@ The following diagram shows the BitLocker configuration service provider in treeThis setting allows you to control how BitLocker-protected operating system drives are recovered in the absence of the required startup key information. This setting is applied when you turn on BitLocker.
@@ -589,7 +589,7 @@ The following diagram shows the BitLocker configuration service provider in treeThis setting allows you to control how BitLocker-protected fixed data drives are recovered in the absence of the required credentials. This setting is applied when you turn on BitLocker.
@@ -687,7 +687,7 @@ The following diagram shows the BitLocker configuration service provider in treeThis setting determines whether BitLocker protection is required for fixed data drives to be writable on a computer.
@@ -749,7 +749,7 @@ The following diagram shows the BitLocker configuration service provider in treeThis setting configures whether BitLocker protection is required for a computer to be able to write data to a removable data drive.
@@ -795,7 +795,7 @@ The following diagram shows the BitLocker configuration service provider in treeAllows the admin to disable the warning prompt for other disk encryption on the user machines that are targeted when the RequireDeviceEncryption policy is also set to 1.
-> [!Important] +> [!IMPORTANT] > Starting in Windows 10, version 1803, the value 0 can only be set for Azure Active Directory joined devices. When RequireDeviceEncryption is set to 1 and AllowWarningForOtherDiskEncryption is set to 0, Windows will attempt to silently enable [BitLocker](https://docs.microsoft.com/windows/device-security/bitlocker/bitlocker-overview). > [!Warning] @@ -842,7 +842,7 @@ The following diagram shows the BitLocker configuration service provider in tree ``` ->[!NOTE] +> [!NOTE] >When you disable the warning prompt, the OS drive's recovery key will back up to the user's Azure Active Directory account. When you allow the warning prompt, the user who receives the prompt can select where to back up the OS drive's recovery key. > >The endpoint for a fixed data drive's backup is chosen in the following order: @@ -855,7 +855,7 @@ The following diagram shows the BitLocker configuration service provider in tree **AllowStandardUserEncryption** Allows Admin to enforce "RequireDeviceEncryption" policy for scenarios where policy is pushed while current logged on user is non-admin/standard user Azure AD account. -> [!Note] +> [!NOTE] > This policy is only supported in Azure AD accounts. "AllowStandardUserEncryption" policy is tied to "AllowWarningForOtherDiskEncryption" policy being set to "0", i.e, silent encryption is enforced. diff --git a/windows/client-management/mdm/bulk-enrollment-using-windows-provisioning-tool.md b/windows/client-management/mdm/bulk-enrollment-using-windows-provisioning-tool.md index 6e07079869..955a7207d1 100644 --- a/windows/client-management/mdm/bulk-enrollment-using-windows-provisioning-tool.md +++ b/windows/client-management/mdm/bulk-enrollment-using-windows-provisioning-tool.md @@ -32,7 +32,7 @@ On the desktop, you can create an Active Directory account, such as "enrollment@ On the desktop and mobile devices, you can use an enrollment certificate or enrollment username and password, such as "enroll@contoso.com" and "enrollmentpassword." These credentials are used in the provisioning package, which you can use to enroll multiple devices to the MDM service. Once the devices are joined, many users can use them. ->[!NOTE] +> [!NOTE] > - Bulk-join is not supported in Azure Active Directory Join. > - Bulk enrollment does not work in Intune standalone environment. > - Bulk enrollment works in System Center Configuration Manager (SCCM) + Intune hybrid environment where the ppkg is generated from the SCCM console. diff --git a/windows/client-management/mdm/cleanpc-csp.md b/windows/client-management/mdm/cleanpc-csp.md index 1db25f77c0..5b7d432911 100644 --- a/windows/client-management/mdm/cleanpc-csp.md +++ b/windows/client-management/mdm/cleanpc-csp.md @@ -1,7 +1,7 @@ --- title: CleanPC CSP description: The CleanPC configuration service provider (CSP) allows removal of user-installed and pre-installed applications, with the option to persist user data. This CSP was added in Windows 10, version 1703. -ms.author: v-madhi +ms.author: dansimp ms.topic: article ms.prod: w10 ms.technology: windows diff --git a/windows/client-management/mdm/cleanpc-ddf.md b/windows/client-management/mdm/cleanpc-ddf.md index b92d596c4e..116930deb1 100644 --- a/windows/client-management/mdm/cleanpc-ddf.md +++ b/windows/client-management/mdm/cleanpc-ddf.md @@ -4,7 +4,7 @@ description: This topic shows the OMA DM device description framework (DDF) for ms.assetid: A2182898-1577-4675-BAE5-2A3A9C2AAC9B ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.topic: article ms.prod: w10 ms.technology: windows diff --git a/windows/client-management/mdm/clientcertificateinstall-csp.md b/windows/client-management/mdm/clientcertificateinstall-csp.md index d80e8b3401..5664409319 100644 --- a/windows/client-management/mdm/clientcertificateinstall-csp.md +++ b/windows/client-management/mdm/clientcertificateinstall-csp.md @@ -4,7 +4,7 @@ description: ClientCertificateInstall CSP ms.assetid: B624EB73-2972-47F2-9D7E-826D641BF8A7 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.topic: article ms.prod: w10 ms.technology: windows diff --git a/windows/client-management/mdm/clientcertificateinstall-ddf-file.md b/windows/client-management/mdm/clientcertificateinstall-ddf-file.md index fac4c7f79c..7c2db0122d 100644 --- a/windows/client-management/mdm/clientcertificateinstall-ddf-file.md +++ b/windows/client-management/mdm/clientcertificateinstall-ddf-file.md @@ -4,7 +4,7 @@ description: ClientCertificateInstall DDF file ms.assetid: 7F65D045-A750-4CDE-A1CE-7D152AA060CA ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.topic: article ms.prod: w10 ms.technology: windows diff --git a/windows/client-management/mdm/cm-cellularentries-csp.md b/windows/client-management/mdm/cm-cellularentries-csp.md index 4e20e3ff3e..6ef3f48d8b 100644 --- a/windows/client-management/mdm/cm-cellularentries-csp.md +++ b/windows/client-management/mdm/cm-cellularentries-csp.md @@ -4,7 +4,7 @@ description: CM\_CellularEntries CSP ms.assetid: f8dac9ef-b709-4b76-b6f5-34c2e6a3c847 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.topic: article ms.prod: w10 ms.technology: windows @@ -139,7 +139,7 @@ The following diagram shows the CM\_CellularEntries configuration service provid **IPType**Optional. Type: String. Specifies the network protocol of the connection. Available values are "IPv4", "IPv6", "IPv4v6", and "IPv4v6xlat". If a value is not specified, the default value is "IPv4". -> [!Warning] +> [!WARNING] > Do not use IPv6 or IPv4v6xlat on a device or network that does not support IPv6. Data functionality will not work. In addition, the device will not be able to connect to a roaming network that does not support IPv6 unless you configure roaming connections with an IPType of IPv4v6. @@ -149,7 +149,7 @@ The following diagram shows the CM\_CellularEntries configuration service provid
To allow MMS when data is set to OFF, set both ExemptFromDisablePolicy and UseRequiresMappingsPolicy to "1". This indicates that the connection is a dedicated MMS connection and that it should not be disabled when all other connections are disabled. As a result, MMS can be sent and received when data is set to OFF. Note that sending MMS while roaming is still not allowed. -> [!Important] +> [!IMPORTANT] > Do not set ExemptFromDisablePolicy to "1", ExemptFromRoaming to "1", or UseRequiresMappingsPolicy to "1" for general purpose connections.
To avoid UX inconsistency with certain value combinations of ExemptFromDisablePolicy and AllowMmsIfDataIsOff, when you do not set ExemptFromDisablePolicy to 1 (default is 0), you should: @@ -168,12 +168,11 @@ The following diagram shows the CM\_CellularEntries configuration service provid **IdleDisconnectTimeout**
Optional. Type: Int. Specifies how long an on-demand connection can be unused before Connection Manager tears the connection down. This value is specified in seconds. Valid value range is 5 to 60 seconds. If not specified, the default is 30 seconds. -> [!Important] +> [!IMPORTANT] >
You must specify the IdleDisconnectTimeout value when updating an on-demand connection to ensure that the desired value is still configured. If it is not specified, the default value of 30 seconds may be used. -> -> -> -> [!Note] + + +> [!NOTE] > If tear-down/activation requests occur too frequently, this value should be set to greater than 5 seconds. diff --git a/windows/client-management/mdm/cm-proxyentries-csp.md b/windows/client-management/mdm/cm-proxyentries-csp.md index ef176f2dab..432b10a418 100644 --- a/windows/client-management/mdm/cm-proxyentries-csp.md +++ b/windows/client-management/mdm/cm-proxyentries-csp.md @@ -4,7 +4,7 @@ description: CM\_ProxyEntries CSP ms.assetid: f4c3dc71-c85a-4c68-9ce9-19f408ff7a0a ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.topic: article ms.prod: w10 ms.technology: windows diff --git a/windows/client-management/mdm/cmpolicy-csp.md b/windows/client-management/mdm/cmpolicy-csp.md index d8cf450f41..e9c0f37c15 100644 --- a/windows/client-management/mdm/cmpolicy-csp.md +++ b/windows/client-management/mdm/cmpolicy-csp.md @@ -4,7 +4,7 @@ description: CMPolicy CSP ms.assetid: 62623915-9747-4eb1-8027-449827b85e6b ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.topic: article ms.prod: w10 ms.technology: windows diff --git a/windows/client-management/mdm/cmpolicyenterprise-csp.md b/windows/client-management/mdm/cmpolicyenterprise-csp.md index 3c64181792..f601f858de 100644 --- a/windows/client-management/mdm/cmpolicyenterprise-csp.md +++ b/windows/client-management/mdm/cmpolicyenterprise-csp.md @@ -4,7 +4,7 @@ description: CMPolicyEnterprise CSP ms.assetid: A0BE3458-ABED-4F80-B467-F842157B94BF ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.topic: article ms.prod: w10 ms.technology: windows diff --git a/windows/client-management/mdm/cmpolicyenterprise-ddf-file.md b/windows/client-management/mdm/cmpolicyenterprise-ddf-file.md index 47aa9e66c4..231c3a42a1 100644 --- a/windows/client-management/mdm/cmpolicyenterprise-ddf-file.md +++ b/windows/client-management/mdm/cmpolicyenterprise-ddf-file.md @@ -4,7 +4,7 @@ description: CMPolicyEnterprise DDF file ms.assetid: 065EF07A-0CF3-4EE5-B620-3464A75B7EED ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.topic: article ms.prod: w10 ms.technology: windows diff --git a/windows/client-management/mdm/configuration-service-provider-reference.md b/windows/client-management/mdm/configuration-service-provider-reference.md index 5aaeaf180d..b8cce9175a 100644 --- a/windows/client-management/mdm/configuration-service-provider-reference.md +++ b/windows/client-management/mdm/configuration-service-provider-reference.md @@ -4,7 +4,7 @@ description: A configuration service provider (CSP) is an interface to read, set ms.assetid: 71823658-951f-4163-9c40-c4d4adceaaec ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.topic: article ms.prod: w10 ms.technology: windows diff --git a/windows/client-management/mdm/create-a-custom-configuration-service-provider.md b/windows/client-management/mdm/create-a-custom-configuration-service-provider.md index b87b2182df..cb8579e827 100644 --- a/windows/client-management/mdm/create-a-custom-configuration-service-provider.md +++ b/windows/client-management/mdm/create-a-custom-configuration-service-provider.md @@ -4,7 +4,7 @@ description: Create a custom configuration service provider ms.assetid: 0cb37f03-5bf2-4451-8276-23f4a1dee33f ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.topic: article ms.prod: w10 ms.technology: windows diff --git a/windows/client-management/mdm/customdeviceui-csp.md b/windows/client-management/mdm/customdeviceui-csp.md index 180daaf203..6e5b89a1b1 100644 --- a/windows/client-management/mdm/customdeviceui-csp.md +++ b/windows/client-management/mdm/customdeviceui-csp.md @@ -4,7 +4,7 @@ description: CustomDeviceUI CSP ms.assetid: 20ED1867-7B9E-4455-B397-53B8B15C95A3 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.topic: article ms.prod: w10 ms.technology: windows diff --git a/windows/client-management/mdm/customdeviceui-ddf.md b/windows/client-management/mdm/customdeviceui-ddf.md index e220b8845a..e77efa5c6f 100644 --- a/windows/client-management/mdm/customdeviceui-ddf.md +++ b/windows/client-management/mdm/customdeviceui-ddf.md @@ -4,7 +4,7 @@ description: CustomDeviceUI DDF ms.assetid: E6D6B902-C57C-48A6-9654-CCBA3898455E ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.topic: article ms.prod: w10 ms.technology: windows diff --git a/windows/client-management/mdm/data-structures-windows-store-for-business.md b/windows/client-management/mdm/data-structures-windows-store-for-business.md index 2f914399ba..0bd426ee5a 100644 --- a/windows/client-management/mdm/data-structures-windows-store-for-business.md +++ b/windows/client-management/mdm/data-structures-windows-store-for-business.md @@ -7,7 +7,7 @@ ms.assetid: ABE44EC8-CBE5-4775-BA8A-4564CB73531B ms.reviewer: manager: dansimp description: -ms.author: v-madhi +ms.author: dansimp ms.topic: article ms.prod: w10 ms.technology: windows diff --git a/windows/client-management/mdm/defender-csp.md b/windows/client-management/mdm/defender-csp.md index c0c253a025..2579fa4d39 100644 --- a/windows/client-management/mdm/defender-csp.md +++ b/windows/client-management/mdm/defender-csp.md @@ -4,7 +4,7 @@ description: Defender CSP ms.assetid: 481AA74F-08B2-4A32-B95D-5A3FD05B335C ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.topic: article ms.prod: w10 ms.technology: windows diff --git a/windows/client-management/mdm/defender-ddf.md b/windows/client-management/mdm/defender-ddf.md index d9e0290636..0fdd2a3569 100644 --- a/windows/client-management/mdm/defender-ddf.md +++ b/windows/client-management/mdm/defender-ddf.md @@ -4,7 +4,7 @@ description: Defender DDF file ms.assetid: 39B9E6CF-4857-4199-B3C3-EC740A439F65 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.topic: article ms.prod: w10 ms.technology: windows diff --git a/windows/client-management/mdm/design-a-custom-windows-csp.md b/windows/client-management/mdm/design-a-custom-windows-csp.md index 52c0a36f2f..583e098cdc 100644 --- a/windows/client-management/mdm/design-a-custom-windows-csp.md +++ b/windows/client-management/mdm/design-a-custom-windows-csp.md @@ -7,7 +7,7 @@ MS-HAID: ms.assetid: 0fff9516-a71a-4036-a57b-503ef1a81a37 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.topic: article ms.prod: w10 ms.technology: windows diff --git a/windows/client-management/mdm/devdetail-csp.md b/windows/client-management/mdm/devdetail-csp.md index 1fe3abbba1..9292eb002c 100644 --- a/windows/client-management/mdm/devdetail-csp.md +++ b/windows/client-management/mdm/devdetail-csp.md @@ -4,7 +4,7 @@ description: DevDetail CSP ms.assetid: 719bbd2d-508d-439b-b175-0874c7e6c360 ms.reviewer: manager: dansimp -ms.author: v-madhi +ms.author: dansimp ms.topic: article ms.prod: w10 ms.technology: windows @@ -188,7 +188,7 @@ Value type is string. Supported operation is Get. **Ext/DeviceHardwareData**
Added in Windows 10 version 1703. Returns a base64-encoded string of the hardware parameters of a device. -> [!Note] +> [!NOTE] > This node contains a raw blob used to identify a device in the cloud. It's not meant to be human readable by design and you cannot parse the content to get any meaningful hardware information.
Supported operation is Get.
diff --git a/windows/client-management/mdm/devdetail-ddf-file.md b/windows/client-management/mdm/devdetail-ddf-file.md
index cf446d6f9a..c9b634f3d6 100644
--- a/windows/client-management/mdm/devdetail-ddf-file.md
+++ b/windows/client-management/mdm/devdetail-ddf-file.md
@@ -4,7 +4,7 @@ description: DevDetail DDF file
ms.assetid: 645fc2b5-2d2c-43b1-9058-26bedbe9f00d
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/developersetup-csp.md b/windows/client-management/mdm/developersetup-csp.md
index 0d4d601d86..40e1d4d82e 100644
--- a/windows/client-management/mdm/developersetup-csp.md
+++ b/windows/client-management/mdm/developersetup-csp.md
@@ -4,7 +4,7 @@ description: The DeveloperSetup configuration service provider (CSP) is used to
ms.assetid:
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/developersetup-ddf.md b/windows/client-management/mdm/developersetup-ddf.md
index 40345355d5..2348237256 100644
--- a/windows/client-management/mdm/developersetup-ddf.md
+++ b/windows/client-management/mdm/developersetup-ddf.md
@@ -4,7 +4,7 @@ description: This topic shows the OMA DM device description framework (DDF) for
ms.assetid:
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/device-update-management.md b/windows/client-management/mdm/device-update-management.md
index be9b52c3f1..4ab3bfd23f 100644
--- a/windows/client-management/mdm/device-update-management.md
+++ b/windows/client-management/mdm/device-update-management.md
@@ -5,7 +5,7 @@ ms.assetid: C27BAEE7-2890-4FB7-9549-A6EACC790777
ms.reviewer:
manager: dansimp
keywords: mdm,management,administrator
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/deviceinstanceservice-csp.md b/windows/client-management/mdm/deviceinstanceservice-csp.md
index c6e8ab6ccd..40379541ed 100644
--- a/windows/client-management/mdm/deviceinstanceservice-csp.md
+++ b/windows/client-management/mdm/deviceinstanceservice-csp.md
@@ -4,7 +4,7 @@ description: DeviceInstanceService CSP
ms.assetid: f113b6bb-6ce1-45ad-b725-1b6610721e2d
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/devicelock-csp.md b/windows/client-management/mdm/devicelock-csp.md
index 2bece89b6c..b2cf37371d 100644
--- a/windows/client-management/mdm/devicelock-csp.md
+++ b/windows/client-management/mdm/devicelock-csp.md
@@ -4,7 +4,7 @@ description: DeviceLock CSP
ms.assetid: 9a547efb-738e-4677-95d3-5506d350d8ab
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/devicelock-ddf-file.md b/windows/client-management/mdm/devicelock-ddf-file.md
index cc93e15019..db0167e5b9 100644
--- a/windows/client-management/mdm/devicelock-ddf-file.md
+++ b/windows/client-management/mdm/devicelock-ddf-file.md
@@ -4,7 +4,7 @@ description: DeviceLock DDF file
ms.assetid: 46a691b9-6350-4987-bfc7-f8b1eece3ad9
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/devicemanageability-csp.md b/windows/client-management/mdm/devicemanageability-csp.md
index a8dfc8baa9..724027f5f0 100644
--- a/windows/client-management/mdm/devicemanageability-csp.md
+++ b/windows/client-management/mdm/devicemanageability-csp.md
@@ -4,7 +4,7 @@ description: The DeviceManageability configuration service provider (CSP) is use
ms.assetid: FE563221-D5B5-4EFD-9B60-44FE4066B0D2
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/devicemanageability-ddf.md b/windows/client-management/mdm/devicemanageability-ddf.md
index 68319351d5..947982a58a 100644
--- a/windows/client-management/mdm/devicemanageability-ddf.md
+++ b/windows/client-management/mdm/devicemanageability-ddf.md
@@ -4,7 +4,7 @@ description: This topic shows the OMA DM device description framework (DDF) for
ms.assetid: D7FA8D51-95ED-40D2-AA84-DCC4BBC393AB
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/devicestatus-csp.md b/windows/client-management/mdm/devicestatus-csp.md
index aa39a5d6ed..8d704d0165 100644
--- a/windows/client-management/mdm/devicestatus-csp.md
+++ b/windows/client-management/mdm/devicestatus-csp.md
@@ -4,7 +4,7 @@ description: The DeviceStatus configuration service provider is used by the ente
ms.assetid: 039B2010-9290-4A6E-B77B-B2469B482360
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/devicestatus-ddf.md b/windows/client-management/mdm/devicestatus-ddf.md
index 5aa865e2d8..3cae11b3ff 100644
--- a/windows/client-management/mdm/devicestatus-ddf.md
+++ b/windows/client-management/mdm/devicestatus-ddf.md
@@ -4,7 +4,7 @@ description: This topic shows the OMA DM device description framework (DDF) for
ms.assetid: 780DC6B4-48A5-4F74-9F2E-6E0D88902A45
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/devinfo-csp.md b/windows/client-management/mdm/devinfo-csp.md
index ebaf036a85..7252e076c2 100644
--- a/windows/client-management/mdm/devinfo-csp.md
+++ b/windows/client-management/mdm/devinfo-csp.md
@@ -4,7 +4,7 @@ description: DevInfo CSP
ms.assetid: d3eb70db-1ce9-4c72-a13d-651137c1713c
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/devinfo-ddf-file.md b/windows/client-management/mdm/devinfo-ddf-file.md
index f4c3cd2ec3..9abf8c4152 100644
--- a/windows/client-management/mdm/devinfo-ddf-file.md
+++ b/windows/client-management/mdm/devinfo-ddf-file.md
@@ -4,7 +4,7 @@ description: DevInfo DDF file
ms.assetid: beb07cc6-4133-4c0f-aa05-64db2b4a004f
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/diagnose-mdm-failures-in-windows-10.md b/windows/client-management/mdm/diagnose-mdm-failures-in-windows-10.md
index 43537416dd..d110f44282 100644
--- a/windows/client-management/mdm/diagnose-mdm-failures-in-windows-10.md
+++ b/windows/client-management/mdm/diagnose-mdm-failures-in-windows-10.md
@@ -4,7 +4,7 @@ description: To help diagnose enrollment or device management issues in Windows
ms.assetid: 12D8263B-D839-4B19-9346-31E0CDD0CBF9
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/diagnosticlog-csp.md b/windows/client-management/mdm/diagnosticlog-csp.md
index 5336d57012..2ef2e01721 100644
--- a/windows/client-management/mdm/diagnosticlog-csp.md
+++ b/windows/client-management/mdm/diagnosticlog-csp.md
@@ -4,7 +4,7 @@ description: DiagnosticLog CSP
ms.assetid: F76E0056-3ACD-48B2-BEA1-1048C96571C3
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/diagnosticlog-ddf.md b/windows/client-management/mdm/diagnosticlog-ddf.md
index 3478b5e5d9..dc23032029 100644
--- a/windows/client-management/mdm/diagnosticlog-ddf.md
+++ b/windows/client-management/mdm/diagnosticlog-ddf.md
@@ -4,7 +4,7 @@ description: DiagnosticLog DDF
ms.assetid: 9DD75EDA-5913-45B4-9BED-20E30CDEBE16
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/disconnecting-from-mdm-unenrollment.md b/windows/client-management/mdm/disconnecting-from-mdm-unenrollment.md
index 416d53867b..6c7e0be2f3 100644
--- a/windows/client-management/mdm/disconnecting-from-mdm-unenrollment.md
+++ b/windows/client-management/mdm/disconnecting-from-mdm-unenrollment.md
@@ -7,7 +7,7 @@ MS-HAID:
ms.assetid: 33B2B248-631B-451F-B534-5DA095C4C8E8
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/dmacc-csp.md b/windows/client-management/mdm/dmacc-csp.md
index 52960d3977..09b61984c1 100644
--- a/windows/client-management/mdm/dmacc-csp.md
+++ b/windows/client-management/mdm/dmacc-csp.md
@@ -4,7 +4,7 @@ description: DMAcc CSP
ms.assetid: 43e73d8a-6617-44e7-8459-5c96f4422e63
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/dmacc-ddf-file.md b/windows/client-management/mdm/dmacc-ddf-file.md
index 08a6e0517f..88579bda87 100644
--- a/windows/client-management/mdm/dmacc-ddf-file.md
+++ b/windows/client-management/mdm/dmacc-ddf-file.md
@@ -4,7 +4,7 @@ description: DMAcc DDF file
ms.assetid: 44dc99aa-2a85-498b-8f52-a81863765606
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/dmclient-csp.md b/windows/client-management/mdm/dmclient-csp.md
index 61f105479e..4dd6ad8b3d 100644
--- a/windows/client-management/mdm/dmclient-csp.md
+++ b/windows/client-management/mdm/dmclient-csp.md
@@ -4,7 +4,7 @@ description: The DMClient configuration service provider is used to specify addi
ms.assetid: a5cf35d9-ced0-4087-a247-225f102f2544
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/dmclient-ddf-file.md b/windows/client-management/mdm/dmclient-ddf-file.md
index fe540b8745..4e1cabc80d 100644
--- a/windows/client-management/mdm/dmclient-ddf-file.md
+++ b/windows/client-management/mdm/dmclient-ddf-file.md
@@ -4,7 +4,7 @@ description: DMClient DDF file
ms.assetid: A21B33AF-DB76-4059-8170-FADF2CB898A0
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/dmprocessconfigxmlfiltered.md b/windows/client-management/mdm/dmprocessconfigxmlfiltered.md
index e915f4d790..25b59bccc1 100644
--- a/windows/client-management/mdm/dmprocessconfigxmlfiltered.md
+++ b/windows/client-management/mdm/dmprocessconfigxmlfiltered.md
@@ -14,7 +14,7 @@ api_location:
- dmprocessxmlfiltered.dll
api_type:
- DllExport
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/dmsessionactions-csp.md b/windows/client-management/mdm/dmsessionactions-csp.md
index c8c2490a37..b395c7c3ba 100644
--- a/windows/client-management/mdm/dmsessionactions-csp.md
+++ b/windows/client-management/mdm/dmsessionactions-csp.md
@@ -1,7 +1,7 @@
---
title: DMSessionActions CSP
description: DMSessionActions CSP
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/dmsessionactions-ddf.md b/windows/client-management/mdm/dmsessionactions-ddf.md
index 73f1b3bd8f..20f2578b73 100644
--- a/windows/client-management/mdm/dmsessionactions-ddf.md
+++ b/windows/client-management/mdm/dmsessionactions-ddf.md
@@ -1,7 +1,7 @@
---
title: DMSessionActions DDF file
description: DMSessionActions DDF file
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/dynamicmanagement-csp.md b/windows/client-management/mdm/dynamicmanagement-csp.md
index d4ae55a285..d8747df10d 100644
--- a/windows/client-management/mdm/dynamicmanagement-csp.md
+++ b/windows/client-management/mdm/dynamicmanagement-csp.md
@@ -1,7 +1,7 @@
---
title: DynamicManagement CSP
description: DynamicManagement CSP
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/dynamicmanagement-ddf.md b/windows/client-management/mdm/dynamicmanagement-ddf.md
index 535ff0c740..53a5e36596 100644
--- a/windows/client-management/mdm/dynamicmanagement-ddf.md
+++ b/windows/client-management/mdm/dynamicmanagement-ddf.md
@@ -4,7 +4,7 @@ description: DynamicManagement DDF file
ms.assetid: 7e266db0-2fd9-4412-b428-4550f41a1738
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/eap-configuration.md b/windows/client-management/mdm/eap-configuration.md
index f5c142c001..6a2d231208 100644
--- a/windows/client-management/mdm/eap-configuration.md
+++ b/windows/client-management/mdm/eap-configuration.md
@@ -4,7 +4,7 @@ description: The topic provides a step-by-step guide for creating an Extensible
ms.assetid: DD3F2292-4B4C-4430-A57F-922FED2A8FAE
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/email2-csp.md b/windows/client-management/mdm/email2-csp.md
index 1971fbca41..ddb14a8d3f 100644
--- a/windows/client-management/mdm/email2-csp.md
+++ b/windows/client-management/mdm/email2-csp.md
@@ -4,7 +4,7 @@ description: EMAIL2 CSP
ms.assetid: bcfc9d98-bc2e-42c6-9b81-0b5bf65ce2b8
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/email2-ddf-file.md b/windows/client-management/mdm/email2-ddf-file.md
index b0f92b1548..3042c4df79 100644
--- a/windows/client-management/mdm/email2-ddf-file.md
+++ b/windows/client-management/mdm/email2-ddf-file.md
@@ -4,7 +4,7 @@ description: EMAIL2 DDF file
ms.assetid: 7e266db0-2fd9-4412-b428-4550f41a1738
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/enable-admx-backed-policies-in-mdm.md b/windows/client-management/mdm/enable-admx-backed-policies-in-mdm.md
index bfee22a337..791d0949e0 100644
--- a/windows/client-management/mdm/enable-admx-backed-policies-in-mdm.md
+++ b/windows/client-management/mdm/enable-admx-backed-policies-in-mdm.md
@@ -1,7 +1,7 @@
---
title: Enable ADMX-backed policies in MDM
description: Guide to configuring ADMX-backed policies in MDM
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
@@ -61,7 +61,7 @@ See [Support Tip: Ingesting Office ADMX-backed policies using Microsoft Intune](
In this example you configure **Enable App-V Client** to **Enabled**.
-> [!Note]
+> [!NOTE]
> The \ payload must be XML encoded. To avoid encoding, you can use CData if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect). If you are using Intune, select String as the data type.
``` syntax
@@ -223,7 +223,7 @@ See [Support Tip: Ingesting Office ADMX-backed policies using Microsoft Intune](
Here is the example for **AppVirtualization/PublishingAllowServer2**:
-> [!Note]
+> [!NOTE]
> The \ payload must be XML encoded. To avoid encoding, you can use CData if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect). If you are using Intune, select String as the data type.
``` syntax
diff --git a/windows/client-management/mdm/enable-offline-updates-for-windows-embedded-8-1-handheld-devices-to-windows-10.md b/windows/client-management/mdm/enable-offline-updates-for-windows-embedded-8-1-handheld-devices-to-windows-10.md
index b177cf578b..645484d8fa 100644
--- a/windows/client-management/mdm/enable-offline-updates-for-windows-embedded-8-1-handheld-devices-to-windows-10.md
+++ b/windows/client-management/mdm/enable-offline-updates-for-windows-embedded-8-1-handheld-devices-to-windows-10.md
@@ -4,7 +4,7 @@ description: Like any Windows devices, Windows 10 Mobile devices use Microsoft
ms.assetid: ED3DAF80-847C-462B-BDB1-486577906772
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/enroll-a-windows-10-device-automatically-using-group-policy.md b/windows/client-management/mdm/enroll-a-windows-10-device-automatically-using-group-policy.md
index c6cbf4062b..1d7810f0e3 100644
--- a/windows/client-management/mdm/enroll-a-windows-10-device-automatically-using-group-policy.md
+++ b/windows/client-management/mdm/enroll-a-windows-10-device-automatically-using-group-policy.md
@@ -1,7 +1,7 @@
---
title: Enroll a Windows 10 device automatically using Group Policy
description: Enroll a Windows 10 device automatically using Group Policy
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
@@ -21,7 +21,7 @@ Requirements:
- The enterprise AD must be [registered with Azure Active Directory (Azure AD)](azure-active-directory-integration-with-mdm.md)
- The device should not already be enrolled in Intune using the classic agents (devices managed using agents will fail enrollment with `error 0x80180026`)
-> [!Tip]
+> [!TIP]
> [How to configure automatic registration of Windows domain-joined devices with Azure Active Directory](https://docs.microsoft.com/azure/active-directory/active-directory-conditional-access-automatic-device-registration-setup)
To verify if the device is Azure AD registered, run `dsregcmd /status` from the command line.
@@ -32,7 +32,7 @@ Here is a partial screenshot of the result:
The auto-enrollment relies of the presence of an MDM service and the Azure Active Directory registration for the PC. Starting in Windows 10, version 1607, once the enterprise has registered its AD with Azure AD, a Windows PC that is domain joined is automatically AAD registered.
-> [!Note]
+> [!NOTE]
> In Windows 10, version 1709, the enrollment protocol was updated to check whether the device is domain-joined. For details, see [\[MS-MDE2\]: Mobile Device Enrollment Protocol Version 2](https://msdn.microsoft.com/library/mt221945.aspx). For examples, see section 4.3.1 RequestSecurityToken of the MS-MDE2 protocol documentation.
When the auto-enrollment Group Policy is enabled, a task is created in the background that initiates the MDM enrollment. The task will use the existing MDM service configuration from the Azure Active Directory information of the user. If multi-factor authentication is required, the user will get a prompt to complete the authentication. Once the enrollment is configured, the user can check the status in the Settings page.
@@ -109,7 +109,7 @@ Requirements:
- Enterprise AD must be integrated with Azure AD.
- Ensure that PCs belong to same computer group.
->[!IMPORTANT]
+>[!IMPORTANT]
>If you do not see the policy, it may be because you don’t have the ADMX installed for Windows 10, version 1803 or version 1809. To fix the issue, follow these steps:
> 1. Download:
> 1803 -->[Administrative Templates (.admx) for Windows 10 April 2018 Update (1803)](https://www.microsoft.com/en-us/download/details.aspx?id=56880) or
@@ -128,7 +128,7 @@ Requirements:
4. Filter using Security Groups.
5. Enforce a GPO link.
->[!NOTE]
+> [!NOTE]
> Version 1903 (March 2019) is actually on the Insider program and doesn't yet contain a downloadable version of Templates (version 1903).
### Related topics
diff --git a/windows/client-management/mdm/enrollmentstatustracking-csp-ddf.md b/windows/client-management/mdm/enrollmentstatustracking-csp-ddf.md
index ae85ee06e1..36057caacf 100644
--- a/windows/client-management/mdm/enrollmentstatustracking-csp-ddf.md
+++ b/windows/client-management/mdm/enrollmentstatustracking-csp-ddf.md
@@ -1,7 +1,7 @@
---
title: EnrollmentStatusTracking CSP
description: EnrollmentStatusTracking CSP
-ms.author: v-madhi@microsoft.com
+ms.author: dansimp@microsoft.com
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/enrollmentstatustracking-csp.md b/windows/client-management/mdm/enrollmentstatustracking-csp.md
index 2f213bb910..f7c3018c82 100644
--- a/windows/client-management/mdm/enrollmentstatustracking-csp.md
+++ b/windows/client-management/mdm/enrollmentstatustracking-csp.md
@@ -1,7 +1,7 @@
---
title: EnrollmentStatusTracking CSP
description: EnrollmentStatusTracking CSP
-ms.author: v-madhi@microsoft.com
+ms.author: dansimp@microsoft.com
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/enterprise-app-management.md b/windows/client-management/mdm/enterprise-app-management.md
index 42c5475d1f..2502635341 100644
--- a/windows/client-management/mdm/enterprise-app-management.md
+++ b/windows/client-management/mdm/enterprise-app-management.md
@@ -4,7 +4,7 @@ description: This topic covers one of the key mobile device management (MDM) fea
ms.assetid: 225DEE61-C3E3-4F75-BC79-5068759DFE99
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/enterpriseapn-csp.md b/windows/client-management/mdm/enterpriseapn-csp.md
index 29b5d5bdd5..2b091686b2 100644
--- a/windows/client-management/mdm/enterpriseapn-csp.md
+++ b/windows/client-management/mdm/enterpriseapn-csp.md
@@ -4,7 +4,7 @@ description: The EnterpriseAPN configuration service provider is used by the ent
ms.assetid: E125F6A5-EE44-41B1-A8CC-DF295082E6B2
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/enterpriseapn-ddf.md b/windows/client-management/mdm/enterpriseapn-ddf.md
index 5ca35c5d4d..a0c86bd9a3 100644
--- a/windows/client-management/mdm/enterpriseapn-ddf.md
+++ b/windows/client-management/mdm/enterpriseapn-ddf.md
@@ -4,7 +4,7 @@ description: EnterpriseAPN DDF
ms.assetid: A953ADEF-4523-425F-926C-48DA62EB9E21
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/enterpriseappmanagement-csp.md b/windows/client-management/mdm/enterpriseappmanagement-csp.md
index 34a8571486..e5e5177782 100644
--- a/windows/client-management/mdm/enterpriseappmanagement-csp.md
+++ b/windows/client-management/mdm/enterpriseappmanagement-csp.md
@@ -4,7 +4,7 @@ description: EnterpriseAppManagement CSP
ms.assetid: 698b8bf4-652e-474b-97e4-381031357623
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/enterpriseappvmanagement-csp.md b/windows/client-management/mdm/enterpriseappvmanagement-csp.md
index 03c5e1ef06..1fe417dd0f 100644
--- a/windows/client-management/mdm/enterpriseappvmanagement-csp.md
+++ b/windows/client-management/mdm/enterpriseappvmanagement-csp.md
@@ -1,7 +1,7 @@
---
title: EnterpriseAppVManagement CSP
description: EnterpriseAppVManagement CSP
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/enterpriseappvmanagement-ddf.md b/windows/client-management/mdm/enterpriseappvmanagement-ddf.md
index 49a8f17488..bd17f6df77 100644
--- a/windows/client-management/mdm/enterpriseappvmanagement-ddf.md
+++ b/windows/client-management/mdm/enterpriseappvmanagement-ddf.md
@@ -1,7 +1,7 @@
---
title: EnterpriseAppVManagement DDF file
description: EnterpriseAppVManagement DDF file
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/enterpriseassignedaccess-csp.md b/windows/client-management/mdm/enterpriseassignedaccess-csp.md
index 0416e3badf..eada56f7eb 100644
--- a/windows/client-management/mdm/enterpriseassignedaccess-csp.md
+++ b/windows/client-management/mdm/enterpriseassignedaccess-csp.md
@@ -4,7 +4,7 @@ description: EnterpriseAssignedAccess CSP
ms.assetid: 5F88E567-77AA-4822-A0BC-3B31100639AA
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
@@ -41,7 +41,7 @@ Supported operations are Add, Delete, Get and Replace.
The Apps and Settings sections of lockdown XML constitute an Allow list. Any app or setting that is not specified in AssignedAccessXML will not be available on the device to users. The following table describes the entries in lockdown XML.
-> [!Important]
+> [!IMPORTANT]
> When using the AssignedAccessXml in the EnterpriseAssignedAccess CSP through an MDM, the XML must use escaped characters, such as \< instead of < because it is embedded in an XML. The examples provided in the topic are formatted for readability.
When using the AssignedAccessXml in a provisioning package using the Windows Configuration Designer tool, do not use escaped characters.
@@ -268,7 +268,7 @@ Here is an example for Windows 10, version 1703.
Starting in Windows 10, version 1511, you can specify the following quick action settings in the lockdown XML file. The following list shows the quick action settings and settings page dependencies (group and page).
-> [!Note]
+> [!NOTE]
> Only Windows 10, versions 1511 and 1607, the dependent settings group and pages are automatically added when the quick action item is specified in the lockdown XML. In Windows 10, version 1703, Quick action settings no longer require any dependencies from related group or page.
Custom3 Allows the user to decrypt files. If this is set to 0 (Not Allowed), then the user will not be able to remove protection from enterprise content through the operating system or the application user experiences.
-> [!Important]
+> [!IMPORTANT]
> Starting in Windows 10, version 1703, AllowUserDecryption is no longer supported.
The following list shows the supported values:
diff --git a/windows/client-management/mdm/enterprisedataprotection-ddf-file.md b/windows/client-management/mdm/enterprisedataprotection-ddf-file.md
index ba56cffc06..4073cc2aa7 100644
--- a/windows/client-management/mdm/enterprisedataprotection-ddf-file.md
+++ b/windows/client-management/mdm/enterprisedataprotection-ddf-file.md
@@ -4,7 +4,7 @@ description: The following topic shows the OMA DM device description framework (
ms.assetid: C6427C52-76F9-4EE0-98F9-DE278529D459
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
@@ -16,7 +16,7 @@ ms.date: 12/05/2017
The following topic shows the OMA DM device description framework (DDF) for the EnterpriseDataProtection configuration service provider.
-> [!Important]
+> [!IMPORTANT]
> Starting in Windows 10, version 1703, AllowUserDecryption is no longer supported.
Looking for the DDF XML files? See [CSP DDF files download](configuration-service-provider-reference.md#csp-ddf-files-download).
diff --git a/windows/client-management/mdm/enterprisedesktopappmanagement-csp.md b/windows/client-management/mdm/enterprisedesktopappmanagement-csp.md
index a8d02b09c0..8bdd114ece 100644
--- a/windows/client-management/mdm/enterprisedesktopappmanagement-csp.md
+++ b/windows/client-management/mdm/enterprisedesktopappmanagement-csp.md
@@ -4,7 +4,7 @@ description: The EnterpriseDesktopAppManagement configuration service provider i
ms.assetid: 2BFF7491-BB01-41BA-9A22-AB209EE59FC5
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/enterprisedesktopappmanagement-ddf-file.md b/windows/client-management/mdm/enterprisedesktopappmanagement-ddf-file.md
index b398685592..01692d547d 100644
--- a/windows/client-management/mdm/enterprisedesktopappmanagement-ddf-file.md
+++ b/windows/client-management/mdm/enterprisedesktopappmanagement-ddf-file.md
@@ -4,7 +4,7 @@ description: This topic shows the OMA DM device description framework (DDF) for
ms.assetid: EF448602-65AC-4D59-A0E8-779876542FE3
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/enterprisedesktopappmanagement2-xsd.md b/windows/client-management/mdm/enterprisedesktopappmanagement2-xsd.md
index f010fb161f..a6138b5f04 100644
--- a/windows/client-management/mdm/enterprisedesktopappmanagement2-xsd.md
+++ b/windows/client-management/mdm/enterprisedesktopappmanagement2-xsd.md
@@ -4,7 +4,7 @@ description: This topic contains the XSD schema file for the EnterpriseDesktopAp
ms.assetid: 60980257-4F48-4A68-8E8E-1EF0A3F090E2
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/enterpriseext-csp.md b/windows/client-management/mdm/enterpriseext-csp.md
index db803ea8c5..15eb1eeea4 100644
--- a/windows/client-management/mdm/enterpriseext-csp.md
+++ b/windows/client-management/mdm/enterpriseext-csp.md
@@ -4,7 +4,7 @@ description: EnterpriseExt CSP
ms.assetid: ACA5CD79-BBD5-4DD1-86DA-0285B93982BD
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/enterpriseext-ddf.md b/windows/client-management/mdm/enterpriseext-ddf.md
index 2595b3dd28..dc43984b7c 100644
--- a/windows/client-management/mdm/enterpriseext-ddf.md
+++ b/windows/client-management/mdm/enterpriseext-ddf.md
@@ -4,7 +4,7 @@ description: EnterpriseExt DDF
ms.assetid: 71BF81D4-FBEC-4B03-BF99-F7A5EDD4F91B
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/enterpriseextfilessystem-csp.md b/windows/client-management/mdm/enterpriseextfilessystem-csp.md
index a661803173..b5db3a8ed9 100644
--- a/windows/client-management/mdm/enterpriseextfilessystem-csp.md
+++ b/windows/client-management/mdm/enterpriseextfilessystem-csp.md
@@ -4,7 +4,7 @@ description: EnterpriseExtFileSystem CSP
ms.assetid: F773AD72-A800-481A-A9E2-899BA56F4426
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/enterpriseextfilesystem-ddf.md b/windows/client-management/mdm/enterpriseextfilesystem-ddf.md
index 86dc28c67d..2aef5100cf 100644
--- a/windows/client-management/mdm/enterpriseextfilesystem-ddf.md
+++ b/windows/client-management/mdm/enterpriseextfilesystem-ddf.md
@@ -4,7 +4,7 @@ description: EnterpriseExtFileSystem DDF
ms.assetid: 2D292E4B-15EE-4AEB-8884-6FEE8B92D2D1
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/enterprisemodernappmanagement-csp.md b/windows/client-management/mdm/enterprisemodernappmanagement-csp.md
index cdadc5ca2d..16b3c88b7c 100644
--- a/windows/client-management/mdm/enterprisemodernappmanagement-csp.md
+++ b/windows/client-management/mdm/enterprisemodernappmanagement-csp.md
@@ -4,7 +4,7 @@ description: EnterpriseModernAppManagement CSP
ms.assetid: 9DD0741A-A229-41A0-A85A-93E185207C42
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
@@ -167,7 +167,7 @@ Supported operations are Get and Delete.
**AppManagement/AppStore/ReleaseManagement**
Added in Windows 10, version 1809. Interior node for the managing updates through the Microsoft Store. These settings allow the IT admin to specify update channels for apps that they want their users to use for receiving updates. It allows the IT admin to assign a specific release to a smaller group for testing before the large deployment to the rest of the organization.
-> [!Note]
+> [!NOTE]
> ReleaseManagement settings only apply to updates through the Microsoft Store.
**AppManagement/AppStore/ReleaseManagement/_ReleaseManagementKey_**
diff --git a/windows/client-management/mdm/enterprisemodernappmanagement-ddf.md b/windows/client-management/mdm/enterprisemodernappmanagement-ddf.md
index 803f46cf73..9dcc1e70a6 100644
--- a/windows/client-management/mdm/enterprisemodernappmanagement-ddf.md
+++ b/windows/client-management/mdm/enterprisemodernappmanagement-ddf.md
@@ -4,7 +4,7 @@ description: EnterpriseModernAppManagement DDF
ms.assetid:
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/enterprisemodernappmanagement-xsd.md b/windows/client-management/mdm/enterprisemodernappmanagement-xsd.md
index 936f55389a..fb66cbc068 100644
--- a/windows/client-management/mdm/enterprisemodernappmanagement-xsd.md
+++ b/windows/client-management/mdm/enterprisemodernappmanagement-xsd.md
@@ -4,7 +4,7 @@ description: Here is the XSD for the application parameters.
ms.assetid: D393D094-25E5-4E66-A60F-B59CC312BF57
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/euiccs-csp.md b/windows/client-management/mdm/euiccs-csp.md
index 22341aa348..43626310a0 100644
--- a/windows/client-management/mdm/euiccs-csp.md
+++ b/windows/client-management/mdm/euiccs-csp.md
@@ -1,7 +1,7 @@
---
title: eUICCs CSP
description: eUICCs CSP
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/euiccs-ddf-file.md b/windows/client-management/mdm/euiccs-ddf-file.md
index 0f282ff7df..a2495584e3 100644
--- a/windows/client-management/mdm/euiccs-ddf-file.md
+++ b/windows/client-management/mdm/euiccs-ddf-file.md
@@ -4,7 +4,7 @@ description: eUICCs DDF file
ms.assetid: c4cd4816-ad8f-45b2-9b81-8abb18254096
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/federated-authentication-device-enrollment.md b/windows/client-management/mdm/federated-authentication-device-enrollment.md
index 2ff5dbb9e0..f173630cc1 100644
--- a/windows/client-management/mdm/federated-authentication-device-enrollment.md
+++ b/windows/client-management/mdm/federated-authentication-device-enrollment.md
@@ -4,7 +4,7 @@ description: This section provides an example of the mobile device enrollment pr
ms.assetid: 049ECA6E-1AF5-4CB2-8F1C-A5F22D722DAA
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/filesystem-csp.md b/windows/client-management/mdm/filesystem-csp.md
index f0745bb496..653b03b527 100644
--- a/windows/client-management/mdm/filesystem-csp.md
+++ b/windows/client-management/mdm/filesystem-csp.md
@@ -4,7 +4,7 @@ description: FileSystem CSP
ms.assetid: 9117ee16-ca7a-4efa-9270-c9ac8547e541
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/firewall-csp.md b/windows/client-management/mdm/firewall-csp.md
index c6322ae0bb..69bc4965a1 100644
--- a/windows/client-management/mdm/firewall-csp.md
+++ b/windows/client-management/mdm/firewall-csp.md
@@ -1,7 +1,7 @@
---
title: Firewall CSP
description: Firewall CSP
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/firewall-ddf-file.md b/windows/client-management/mdm/firewall-ddf-file.md
index c3d8ccf3cf..1242224bc0 100644
--- a/windows/client-management/mdm/firewall-ddf-file.md
+++ b/windows/client-management/mdm/firewall-ddf-file.md
@@ -1,7 +1,7 @@
---
title: Firewall DDF file
description: Firewall DDF file
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/get-inventory.md b/windows/client-management/mdm/get-inventory.md
index 12d263d212..94c9465267 100644
--- a/windows/client-management/mdm/get-inventory.md
+++ b/windows/client-management/mdm/get-inventory.md
@@ -7,7 +7,7 @@ MS-HAID:
ms.assetid: C5485722-FC49-4358-A097-74169B204E74
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/get-localized-product-details.md b/windows/client-management/mdm/get-localized-product-details.md
index 0670c37682..c2e89912d8 100644
--- a/windows/client-management/mdm/get-localized-product-details.md
+++ b/windows/client-management/mdm/get-localized-product-details.md
@@ -4,7 +4,7 @@ description: The Get localized product details operation retrieves the localizat
ms.assetid: EF6AFCA9-8699-46C9-A3BB-CD2750C07901
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/get-offline-license.md b/windows/client-management/mdm/get-offline-license.md
index c4c8f1d5a8..772d402b87 100644
--- a/windows/client-management/mdm/get-offline-license.md
+++ b/windows/client-management/mdm/get-offline-license.md
@@ -4,7 +4,7 @@ description: The Get offline license operation retrieves the offline license inf
ms.assetid: 08DAD813-CF4D-42D6-A783-994A03AEE051
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/get-product-details.md b/windows/client-management/mdm/get-product-details.md
index 3ccd310755..9ab64f1f8b 100644
--- a/windows/client-management/mdm/get-product-details.md
+++ b/windows/client-management/mdm/get-product-details.md
@@ -4,7 +4,7 @@ description: The Get product details operation retrieves the product information
ms.assetid: BC432EBA-CE5E-43BD-BD54-942774767286
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/get-product-package.md b/windows/client-management/mdm/get-product-package.md
index 116e40631b..7f75857534 100644
--- a/windows/client-management/mdm/get-product-package.md
+++ b/windows/client-management/mdm/get-product-package.md
@@ -4,7 +4,7 @@ description: The Get product package operation retrieves the information about a
ms.assetid: 4314C65E-6DDC-405C-A591-D66F799A341F
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/get-product-packages.md b/windows/client-management/mdm/get-product-packages.md
index ce6f18cad7..394b64e58c 100644
--- a/windows/client-management/mdm/get-product-packages.md
+++ b/windows/client-management/mdm/get-product-packages.md
@@ -4,7 +4,7 @@ description: The Get product packages operation retrieves the information about
ms.assetid: 039468BF-B9EE-4E1C-810C-9ACDD55C0835
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/get-seat.md b/windows/client-management/mdm/get-seat.md
index 598dc8d6a6..2169488622 100644
--- a/windows/client-management/mdm/get-seat.md
+++ b/windows/client-management/mdm/get-seat.md
@@ -4,7 +4,7 @@ description: The Get seat operation retrieves the information about an active se
ms.assetid: 715BAEB2-79FD-4945-A57F-482F9E7D07C6
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/get-seats-assigned-to-a-user.md b/windows/client-management/mdm/get-seats-assigned-to-a-user.md
index 9d03679ed5..016e2a8711 100644
--- a/windows/client-management/mdm/get-seats-assigned-to-a-user.md
+++ b/windows/client-management/mdm/get-seats-assigned-to-a-user.md
@@ -4,7 +4,7 @@ description: The Get seats assigned to a user operation retrieves information ab
ms.assetid: CB963E44-8C7C-46F9-A979-89BBB376172B
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/get-seats.md b/windows/client-management/mdm/get-seats.md
index 4b0862844a..21d8f631c1 100644
--- a/windows/client-management/mdm/get-seats.md
+++ b/windows/client-management/mdm/get-seats.md
@@ -4,7 +4,7 @@ description: The Get seats operation retrieves the information about active seat
ms.assetid: 32945788-47AC-4259-B616-F359D48F4F2F
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/healthattestation-csp.md b/windows/client-management/mdm/healthattestation-csp.md
index b794b4cf63..fda1c7d218 100644
--- a/windows/client-management/mdm/healthattestation-csp.md
+++ b/windows/client-management/mdm/healthattestation-csp.md
@@ -4,7 +4,7 @@ description: Device HealthAttestation CSP
ms.assetid: 6F2D783C-F6B4-4A81-B9A2-522C4661D1AC
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/healthattestation-ddf.md b/windows/client-management/mdm/healthattestation-ddf.md
index cc76cdd6c5..fa43c860a4 100644
--- a/windows/client-management/mdm/healthattestation-ddf.md
+++ b/windows/client-management/mdm/healthattestation-ddf.md
@@ -4,7 +4,7 @@ description: HealthAttestation DDF
ms.assetid: D20AC78D-D2D4-434B-B9FD-294BCD9D1DDE
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/hotspot-csp.md b/windows/client-management/mdm/hotspot-csp.md
index 114abc12f9..ce1fcddfbb 100644
--- a/windows/client-management/mdm/hotspot-csp.md
+++ b/windows/client-management/mdm/hotspot-csp.md
@@ -4,7 +4,7 @@ description: HotSpot CSP
ms.assetid: ec49dec1-fa79-420a-a9a7-e86668b3eebf
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/iconfigserviceprovider2.md b/windows/client-management/mdm/iconfigserviceprovider2.md
index 048b953696..c73e0ce0b4 100644
--- a/windows/client-management/mdm/iconfigserviceprovider2.md
+++ b/windows/client-management/mdm/iconfigserviceprovider2.md
@@ -4,7 +4,7 @@ description: IConfigServiceProvider2
ms.assetid: 8deec0fb-59a6-4d08-8ddb-6d0d3d868a10
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/iconfigserviceprovider2configmanagernotification.md b/windows/client-management/mdm/iconfigserviceprovider2configmanagernotification.md
index 55f2a25518..67ed91ca36 100644
--- a/windows/client-management/mdm/iconfigserviceprovider2configmanagernotification.md
+++ b/windows/client-management/mdm/iconfigserviceprovider2configmanagernotification.md
@@ -4,7 +4,7 @@ description: IConfigServiceProvider2 ConfigManagerNotification
ms.assetid: b1f0fe0f-afbe-4b36-a75d-34239a86a75c
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/iconfigserviceprovider2getnode.md b/windows/client-management/mdm/iconfigserviceprovider2getnode.md
index c89523b033..b1ed4618c7 100644
--- a/windows/client-management/mdm/iconfigserviceprovider2getnode.md
+++ b/windows/client-management/mdm/iconfigserviceprovider2getnode.md
@@ -4,7 +4,7 @@ description: IConfigServiceProvider2 GetNode
ms.assetid: 4dc10a59-f6a2-45c0-927c-d594afc9bb91
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/icspnode.md b/windows/client-management/mdm/icspnode.md
index c0a1f975f8..bb66997ee8 100644
--- a/windows/client-management/mdm/icspnode.md
+++ b/windows/client-management/mdm/icspnode.md
@@ -4,7 +4,7 @@ description: ICSPNode
ms.assetid: 023466e6-a8ab-48ad-8548-291409686ac2
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/icspnodeadd.md b/windows/client-management/mdm/icspnodeadd.md
index a373d48773..81f5b2cce5 100644
--- a/windows/client-management/mdm/icspnodeadd.md
+++ b/windows/client-management/mdm/icspnodeadd.md
@@ -4,7 +4,7 @@ description: ICSPNode Add
ms.assetid: 5f03d350-c82b-4747-975f-385fd8b5b3a8
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/icspnodeclear.md b/windows/client-management/mdm/icspnodeclear.md
index aad47f0a81..89db169b0f 100644
--- a/windows/client-management/mdm/icspnodeclear.md
+++ b/windows/client-management/mdm/icspnodeclear.md
@@ -4,7 +4,7 @@ description: ICSPNode Clear
ms.assetid: b414498b-110a-472d-95c0-2d5b38cd78a6
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/icspnodecopy.md b/windows/client-management/mdm/icspnodecopy.md
index 0d9ef070a4..1771aad0fa 100644
--- a/windows/client-management/mdm/icspnodecopy.md
+++ b/windows/client-management/mdm/icspnodecopy.md
@@ -4,7 +4,7 @@ description: ICSPNode Copy
ms.assetid: cd5ce0bc-a08b-4f82-802d-c7ff8701b41f
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/icspnodedeletechild.md b/windows/client-management/mdm/icspnodedeletechild.md
index e3c4861398..e08d2b025d 100644
--- a/windows/client-management/mdm/icspnodedeletechild.md
+++ b/windows/client-management/mdm/icspnodedeletechild.md
@@ -4,7 +4,7 @@ description: ICSPNode DeleteChild
ms.assetid: 8cf3663d-a4cf-4d11-b03a-f1d096ad7f9c
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/icspnodedeleteproperty.md b/windows/client-management/mdm/icspnodedeleteproperty.md
index 3bb5c390b4..6bcd73cc62 100644
--- a/windows/client-management/mdm/icspnodedeleteproperty.md
+++ b/windows/client-management/mdm/icspnodedeleteproperty.md
@@ -4,7 +4,7 @@ description: ICSPNode DeleteProperty
ms.assetid: 7e21851f-d663-4558-b3e8-590d24b4f6c4
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/icspnodeexecute.md b/windows/client-management/mdm/icspnodeexecute.md
index 95583c91f8..b5008f4972 100644
--- a/windows/client-management/mdm/icspnodeexecute.md
+++ b/windows/client-management/mdm/icspnodeexecute.md
@@ -4,7 +4,7 @@ description: ICSPNode Execute
ms.assetid: 5916e7b7-256d-49fd-82b6-db0547a215ec
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/icspnodegetchildnodenames.md b/windows/client-management/mdm/icspnodegetchildnodenames.md
index dd7dc2fe59..176e294eb1 100644
--- a/windows/client-management/mdm/icspnodegetchildnodenames.md
+++ b/windows/client-management/mdm/icspnodegetchildnodenames.md
@@ -4,7 +4,7 @@ description: ICSPNode GetChildNodeNames
ms.assetid: dc057f2b-282b-49ac-91c4-bb83bd3ca4dc
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/icspnodegetproperty.md b/windows/client-management/mdm/icspnodegetproperty.md
index 4b325efd51..e617650c97 100644
--- a/windows/client-management/mdm/icspnodegetproperty.md
+++ b/windows/client-management/mdm/icspnodegetproperty.md
@@ -4,7 +4,7 @@ description: ICSPNode GetProperty
ms.assetid: a2bdc158-72e0-4cdb-97ce-f5cf1a44b7db
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/icspnodegetpropertyidentifiers.md b/windows/client-management/mdm/icspnodegetpropertyidentifiers.md
index 4660b81365..479913e683 100644
--- a/windows/client-management/mdm/icspnodegetpropertyidentifiers.md
+++ b/windows/client-management/mdm/icspnodegetpropertyidentifiers.md
@@ -4,7 +4,7 @@ description: ICSPNode GetPropertyIdentifiers
ms.assetid: 8a052cd3-d74c-40c4-845f-f804b920deb4
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/icspnodegetvalue.md b/windows/client-management/mdm/icspnodegetvalue.md
index b01be8e614..0e8d591f35 100644
--- a/windows/client-management/mdm/icspnodegetvalue.md
+++ b/windows/client-management/mdm/icspnodegetvalue.md
@@ -4,7 +4,7 @@ description: ICSPNode GetValue
ms.assetid: c684036d-98be-4659-8ce8-f72436a39b90
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/icspnodemove.md b/windows/client-management/mdm/icspnodemove.md
index 2740a4caf3..40d917ca2f 100644
--- a/windows/client-management/mdm/icspnodemove.md
+++ b/windows/client-management/mdm/icspnodemove.md
@@ -4,7 +4,7 @@ description: ICSPNode Move
ms.assetid: efb359c3-5c86-4975-bf6f-a1c33922442a
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/icspnodesetproperty.md b/windows/client-management/mdm/icspnodesetproperty.md
index d27d12ce60..8052bf2d5d 100644
--- a/windows/client-management/mdm/icspnodesetproperty.md
+++ b/windows/client-management/mdm/icspnodesetproperty.md
@@ -4,7 +4,7 @@ description: ICSPNode SetProperty
ms.assetid: e235c38f-ea04-4cd8-adec-3c6c0ce7172d
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/icspnodesetvalue.md b/windows/client-management/mdm/icspnodesetvalue.md
index 1aa5cbdd52..afcbc3b99d 100644
--- a/windows/client-management/mdm/icspnodesetvalue.md
+++ b/windows/client-management/mdm/icspnodesetvalue.md
@@ -4,7 +4,7 @@ description: ICSPNode SetValue
ms.assetid: b218636d-fe8b-4a0f-b4e8-a621f65619d3
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/icspnodetransactioning.md b/windows/client-management/mdm/icspnodetransactioning.md
index 9e3b4e5d78..93b4a35b7b 100644
--- a/windows/client-management/mdm/icspnodetransactioning.md
+++ b/windows/client-management/mdm/icspnodetransactioning.md
@@ -4,7 +4,7 @@ description: ICSPNodeTransactioning
ms.assetid: 24dc518a-4a8d-41fe-9bc6-217bbbdf6a3f
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/icspvalidate.md b/windows/client-management/mdm/icspvalidate.md
index 9041f535c7..3d59448e68 100644
--- a/windows/client-management/mdm/icspvalidate.md
+++ b/windows/client-management/mdm/icspvalidate.md
@@ -4,7 +4,7 @@ description: ICSPValidate
ms.assetid: b0993f2d-6269-412f-a329-af25fff34ca2
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/implement-server-side-mobile-application-management.md b/windows/client-management/mdm/implement-server-side-mobile-application-management.md
index da6438913d..61a7890782 100644
--- a/windows/client-management/mdm/implement-server-side-mobile-application-management.md
+++ b/windows/client-management/mdm/implement-server-side-mobile-application-management.md
@@ -1,7 +1,7 @@
---
title: Implement server-side support for mobile application management on Windows
description: The Windows version of mobile application management (MAM) is a lightweight solution for managing company data access and security on personal devices. MAM support is built into Windows on top of Windows Information Protection (WIP).
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/index.md b/windows/client-management/mdm/index.md
index 02f521dce2..781e0924d0 100644
--- a/windows/client-management/mdm/index.md
+++ b/windows/client-management/mdm/index.md
@@ -29,7 +29,7 @@ Third-party MDM servers can manage Windows 10 by using the MDM protocol. The bu
With Windows 10, version 1809, Microsoft is also releasing a Microsoft MDM security baseline that functions like the Microsoft GP-based security baseline. You can easily integrate this baseline into any MDM to support IT pros’ operational needs, addressing security concerns for modern cloud-managed devices.
->[!NOTE]
+> [!NOTE]
>Intune support for the MDM security baseline is coming soon.
The MDM security baseline includes policies that cover the following areas:
diff --git a/windows/client-management/mdm/management-tool-for-windows-store-for-business.md b/windows/client-management/mdm/management-tool-for-windows-store-for-business.md
index c9c8076463..98f5020545 100644
--- a/windows/client-management/mdm/management-tool-for-windows-store-for-business.md
+++ b/windows/client-management/mdm/management-tool-for-windows-store-for-business.md
@@ -7,7 +7,7 @@ MS-HAID:
ms.assetid: 0E39AE85-1703-4B24-9A7F-831C6455068F
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/maps-csp.md b/windows/client-management/mdm/maps-csp.md
index d2e6000b6f..3de2401e8b 100644
--- a/windows/client-management/mdm/maps-csp.md
+++ b/windows/client-management/mdm/maps-csp.md
@@ -4,7 +4,7 @@ description: The Maps configuration service provider (CSP) is used to configure
ms.assetid: E5157296-7C31-4B08-8877-15304C9F6F26
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/maps-ddf-file.md b/windows/client-management/mdm/maps-ddf-file.md
index 9eeaa9f169..e5e4c7b7ad 100644
--- a/windows/client-management/mdm/maps-ddf-file.md
+++ b/windows/client-management/mdm/maps-ddf-file.md
@@ -4,7 +4,7 @@ description: This topic shows the OMA DM device description framework (DDF) for
ms.assetid: EF22DBB6-0578-4FD0-B8A6-19DC03288FAF
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/mdm-enrollment-of-windows-devices.md b/windows/client-management/mdm/mdm-enrollment-of-windows-devices.md
index 7c20cac4ef..18cb6c96e1 100644
--- a/windows/client-management/mdm/mdm-enrollment-of-windows-devices.md
+++ b/windows/client-management/mdm/mdm-enrollment-of-windows-devices.md
@@ -7,7 +7,7 @@ MS-HAID:
ms.assetid: 4651C81B-D2D6-446A-AA24-04D01C1D0883
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
@@ -364,7 +364,8 @@ Starting in Windows 10, version 1709, clicking the **Info** button will show a l
-> [Note] Starting in Windows 10, version 1709, the **Manage** button is no longer available.
+> [NOTE]
+> Starting in Windows 10, version 1709, the **Manage** button is no longer available.
### Disconnect
diff --git a/windows/client-management/mdm/messaging-csp.md b/windows/client-management/mdm/messaging-csp.md
index d7beeeadcc..f593722476 100644
--- a/windows/client-management/mdm/messaging-csp.md
+++ b/windows/client-management/mdm/messaging-csp.md
@@ -1,7 +1,7 @@
---
title: Messaging CSP
description: Messaging CSP
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/messaging-ddf.md b/windows/client-management/mdm/messaging-ddf.md
index dd130d307d..2f92333731 100644
--- a/windows/client-management/mdm/messaging-ddf.md
+++ b/windows/client-management/mdm/messaging-ddf.md
@@ -1,7 +1,7 @@
---
title: Messaging DDF file
description: Messaging DDF file
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/mobile-device-enrollment.md b/windows/client-management/mdm/mobile-device-enrollment.md
index 7c4a8ffb82..747ecc45c4 100644
--- a/windows/client-management/mdm/mobile-device-enrollment.md
+++ b/windows/client-management/mdm/mobile-device-enrollment.md
@@ -4,7 +4,7 @@ description: Mobile device enrollment is the first phase of enterprise managemen
ms.assetid: 08C8B3DB-3263-414B-A368-F47B94F47A11
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/multisim-csp.md b/windows/client-management/mdm/multisim-csp.md
index ec04186730..3e06ed3bd7 100644
--- a/windows/client-management/mdm/multisim-csp.md
+++ b/windows/client-management/mdm/multisim-csp.md
@@ -1,7 +1,7 @@
---
title: MultiSIM CSP
description: MultiSIM CSP allows the enterprise to manage devices with dual SIM single active configuration.
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/multisim-ddf.md b/windows/client-management/mdm/multisim-ddf.md
index 52afa1defc..6474094dc5 100644
--- a/windows/client-management/mdm/multisim-ddf.md
+++ b/windows/client-management/mdm/multisim-ddf.md
@@ -1,7 +1,7 @@
---
title: MultiSIM DDF file
description: XML file containing the device description framework
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/nap-csp.md b/windows/client-management/mdm/nap-csp.md
index ef8dfed272..c4dbd6410a 100644
--- a/windows/client-management/mdm/nap-csp.md
+++ b/windows/client-management/mdm/nap-csp.md
@@ -4,7 +4,7 @@ description: NAP CSP
ms.assetid: 82f04492-88a6-4afd-af10-a62b8d444d21
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/napdef-csp.md b/windows/client-management/mdm/napdef-csp.md
index f4d7d563df..80a87e53d1 100644
--- a/windows/client-management/mdm/napdef-csp.md
+++ b/windows/client-management/mdm/napdef-csp.md
@@ -4,7 +4,7 @@ description: NAPDEF CSP
ms.assetid: 9bcc65dd-a72b-4f90-aba7-4066daa06988
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/networkproxy-csp.md b/windows/client-management/mdm/networkproxy-csp.md
index cef8282c08..e4613c29a9 100644
--- a/windows/client-management/mdm/networkproxy-csp.md
+++ b/windows/client-management/mdm/networkproxy-csp.md
@@ -1,7 +1,7 @@
---
title: NetworkProxy CSP
description: NetworkProxy CSP
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
@@ -15,7 +15,7 @@ manager: dansimp
The NetworkProxy configuration service provider (CSP) is used to configure a proxy server for ethernet and Wi-Fi connections. These settings do not apply to VPN connections. This CSP was added in Windows 10, version 1703.
-> [!Note]
+> [!NOTE]
> In Windows 10 Mobile, the NetworkProxy CSP only works in ethernet connections. Use the WiFi CSP to configure per-network proxy for Wi-Fi connections in mobile devices.
How the settings work:
@@ -40,7 +40,7 @@ Added in Windows 10, version 1803. When set to 0, it enables proxy configuration
Supported operations are Add, Get, Replace, and Delete.
-> [!Note]
+> [!NOTE]
> Per user proxy configuration setting is not supported.
**AutoDetect**
diff --git a/windows/client-management/mdm/networkproxy-ddf.md b/windows/client-management/mdm/networkproxy-ddf.md
index 505da111aa..bf158a3cc1 100644
--- a/windows/client-management/mdm/networkproxy-ddf.md
+++ b/windows/client-management/mdm/networkproxy-ddf.md
@@ -1,7 +1,7 @@
---
title: NetworkProxy DDF file
description: AppNetworkProxyLocker DDF file
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/networkqospolicy-csp.md b/windows/client-management/mdm/networkqospolicy-csp.md
index f33f6a6ee2..564059ef4e 100644
--- a/windows/client-management/mdm/networkqospolicy-csp.md
+++ b/windows/client-management/mdm/networkqospolicy-csp.md
@@ -1,7 +1,7 @@
---
title: NetworkQoSPolicy CSP
description: he NetworkQoSPolicy CSP applies the Quality of Service (QoS) policy for Microsoft Surface Hub. This CSP was added in Windows 10, version 1703.
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/networkqospolicy-ddf.md b/windows/client-management/mdm/networkqospolicy-ddf.md
index 42b8ea6792..0eb83d5178 100644
--- a/windows/client-management/mdm/networkqospolicy-ddf.md
+++ b/windows/client-management/mdm/networkqospolicy-ddf.md
@@ -4,7 +4,7 @@ description: This topic shows the OMA DM device description framework (DDF) for
ms.assetid:
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md b/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md
index a39052ba19..d0e26ff6f1 100644
--- a/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md
+++ b/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md
@@ -7,7 +7,7 @@ MS-HAID:
ms.assetid: 9C42064F-091C-4901-BC73-9ABE79EE4224
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
@@ -1108,7 +1108,7 @@ For details about Microsoft mobile device management protocols for Windows 10 s
Added following deep link parameters to the table: This node executes a reboot of the device. RebootNow triggers a reboot within 5 minutes to allow the user to wrap up any active work. The supported operations are Execute and Get. \"Close other apps, error code: 0XA00F4243.” or or AMD Ryzen™ or AMD Ryzen™ Threadripper™ configured in SATA or NVMe RAID mode. “A driver is installed that causes stability problems on Windows. This driver will be disabled. Check with your software/driver provider for an updated version that runs on this version of Windows.”
@@ -376,7 +376,7 @@ Buttons | The following list identifies the hardware buttons on the device that
-> [!Note]
+> [!NOTE]
> Lock down of the Start button only prevents the press and hold event.
>
> Custom buttons are hardware buttons that can be added to devices by OEMs.
@@ -400,7 +400,7 @@ Buttons example:
```
The Search and custom buttons can be remapped or configured to open a specific application. Button remapping takes effect for the device and applies to all users.
-> [!Note]
+> [!NOTE]
> The lockdown settings for a button, per user role, will apply regardless of the button mapping.
>
> Button remapping can enable a user to open an application that is not in the Allow list. Use button lock down to prevent application access for a user role.
@@ -498,7 +498,7 @@ Entry | Description
----------- | ------------
MenuItems | Use **DisableMenuItems** to prevent use of the context menu, which is displayed when a user presses and holds an application in the All Programs list. You can include this entry in the default profile and in any additional user role profiles that you create.
-> [!Important]
+> [!IMPORTANT]
> If **DisableMenuItems** is not included in a profile, users of that profile can uninstall apps.
MenuItems example:
@@ -513,12 +513,12 @@ Entry | Description
----------- | ------------
Tiles | **Turning-on tile manipulation** - By default, under Assigned Access, tile manipulation is turned off (blocked) and only available if enabled in the user’s profile. If tile manipulation is enabled in the user’s profile, they can pin/unpin, move, and resize tiles based on their preferences. When multiple people use one device and you want to enable tile manipulation for multiple users, you must enable it for each user in their user profile.
-> [!Important]
+> [!IMPORTANT]
> If a device is turned off then back on, the tiles reset to their predefined layout. If a device has only one profile, the only way to reset the tiles is to turn off then turn on the device. If a device has multiple profiles, the device resets the tiles to the predefined layout based on the logged-in user’s profile.
The following sample file contains configuration for enabling tile manipulation.
-> [!Note]
+> [!NOTE]
> Tile manipulation is disabled when you don’t have a `Microsoft.XboxApp_8wekyb3d8bbwe!Microsoft.XboxApp
-
-
-
-
-
-
-
-
-
-
-
-
-
+
\ No newline at end of file
diff --git a/windows/client-management/mdm/enterpriseassignedaccess-ddf.md b/windows/client-management/mdm/enterpriseassignedaccess-ddf.md
index d1f0ed0a9f..1620155242 100644
--- a/windows/client-management/mdm/enterpriseassignedaccess-ddf.md
+++ b/windows/client-management/mdm/enterpriseassignedaccess-ddf.md
@@ -4,7 +4,7 @@ description: EnterpriseAssignedAccess DDF
ms.assetid: 8BD6FB05-E643-4695-99A2-633995884B37
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/enterpriseassignedaccess-xsd.md b/windows/client-management/mdm/enterpriseassignedaccess-xsd.md
index b71be0c522..63acfd38b3 100644
--- a/windows/client-management/mdm/enterpriseassignedaccess-xsd.md
+++ b/windows/client-management/mdm/enterpriseassignedaccess-xsd.md
@@ -4,7 +4,7 @@ description: EnterpriseAssignedAccess XSD
ms.assetid: BB3B633E-E361-4B95-9D4A-CE6E08D67ADA
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/enterprisedataprotection-csp.md b/windows/client-management/mdm/enterprisedataprotection-csp.md
index 725444b2b6..3e69ceaa92 100644
--- a/windows/client-management/mdm/enterprisedataprotection-csp.md
+++ b/windows/client-management/mdm/enterprisedataprotection-csp.md
@@ -4,7 +4,7 @@ description: The EnterpriseDataProtection configuration service provider (CSP) i
ms.assetid: E2D4467F-A154-4C00-9208-7798EF3E25B3
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
@@ -71,7 +71,7 @@ The following diagram shows the EnterpriseDataProtection CSP in tree format.
**Settings/AllowUserDecryption**
- Connecting your Windows 10-based device to work using a deep link
+Connecting your Windows 10-based device to work using a deep link
@@ -4378,7 +4378,7 @@ The following diagram shows the Policy configuration service provider in tree fo
- [CredentialsDelegation/RemoteHostAllowsDelegationOfNonExportableCredentials](./policy-csp-credentialsdelegation.md#credentialsdelegation-remotehostallowsdelegationofnonexportablecredentials)
- [CredentialsUI/DisablePasswordReveal](./policy-csp-credentialsui.md#credentialsui-disablepasswordreveal)
- [CredentialsUI/EnumerateAdministrators](./policy-csp-credentialsui.md#credentialsui-enumerateadministrators)
-- [Cryptography/AllowFipsAlgorithmPolicy](./policy-csp-cryptography.md#cryptography-allowfipsalgorithmpolicy)
+- [Cryptography/AllowFipsAlgorithmPolicy](./policy-csp-cryptography.md#cryptographyallowfipsalgorithmpolicy)
- [DataUsage/SetCost4G](./policy-csp-datausage.md#datausage-setcost4g)
- [Defender/AllowArchiveScanning](./policy-csp-defender.md#defender-allowarchivescanning)
- [Defender/AllowBehaviorMonitoring](./policy-csp-defender.md#defender-allowbehaviormonitoring)
@@ -5243,8 +5243,8 @@ The following diagram shows the Policy configuration service provider in tree fo
- [Camera/AllowCamera](#camera-allowcamera)
- [Cellular/ShowAppCellularAccessUI](#cellular-showappcellularaccessui)
-- [Cryptography/AllowFipsAlgorithmPolicy](#cryptography-allowfipsalgorithmpolicy)
-- [Cryptography/TLSCipherSuites](#cryptography-tlsciphersuites)
+- [Cryptography/AllowFipsAlgorithmPolicy](#cryptographyallowfipsalgorithmpolicy)
+- [Cryptography/TLSCipherSuites](#cryptographytlsciphersuites)
- [Defender/AllowArchiveScanning](#defender-allowarchivescanning)
- [Defender/AllowBehaviorMonitoring](#defender-allowbehaviormonitoring)
- [Defender/AllowCloudProtection](#defender-allowcloudprotection)
diff --git a/windows/client-management/mdm/policy-csp-abovelock.md b/windows/client-management/mdm/policy-csp-abovelock.md
index 19aca7f315..b5cb013a88 100644
--- a/windows/client-management/mdm/policy-csp-abovelock.md
+++ b/windows/client-management/mdm/policy-csp-abovelock.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - AboveLock
description: Policy CSP - AboveLock
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-accounts.md b/windows/client-management/mdm/policy-csp-accounts.md
index 2c501e743b..55f72ccd70 100644
--- a/windows/client-management/mdm/policy-csp-accounts.md
+++ b/windows/client-management/mdm/policy-csp-accounts.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Accounts
description: Policy CSP - Accounts
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-activexcontrols.md b/windows/client-management/mdm/policy-csp-activexcontrols.md
index 722bfbdd40..09639791f8 100644
--- a/windows/client-management/mdm/policy-csp-activexcontrols.md
+++ b/windows/client-management/mdm/policy-csp-activexcontrols.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - ActiveXControls
description: Policy CSP - ActiveXControls
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-applicationdefaults.md b/windows/client-management/mdm/policy-csp-applicationdefaults.md
index 929ca3cd9f..09d3644c12 100644
--- a/windows/client-management/mdm/policy-csp-applicationdefaults.md
+++ b/windows/client-management/mdm/policy-csp-applicationdefaults.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - ApplicationDefaults
description: Policy CSP - ApplicationDefaults
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-applicationmanagement.md b/windows/client-management/mdm/policy-csp-applicationmanagement.md
index 5c136c592b..29d419c3dd 100644
--- a/windows/client-management/mdm/policy-csp-applicationmanagement.md
+++ b/windows/client-management/mdm/policy-csp-applicationmanagement.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - ApplicationManagement
description: Policy CSP - ApplicationManagement
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
@@ -600,7 +600,7 @@ For this policy to work, the Windows apps need to declare in their manifest that
```
-> [!Note]
+> [!NOTE]
> This policy only works on modern apps.
diff --git a/windows/client-management/mdm/policy-csp-appruntime.md b/windows/client-management/mdm/policy-csp-appruntime.md
index 96fb236ede..6f998bebf9 100644
--- a/windows/client-management/mdm/policy-csp-appruntime.md
+++ b/windows/client-management/mdm/policy-csp-appruntime.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - AppRuntime
description: Policy CSP - AppRuntime
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-appvirtualization.md b/windows/client-management/mdm/policy-csp-appvirtualization.md
index a1c25ca11b..7ecd3a228b 100644
--- a/windows/client-management/mdm/policy-csp-appvirtualization.md
+++ b/windows/client-management/mdm/policy-csp-appvirtualization.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - AppVirtualization
description: Policy CSP - AppVirtualization
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-attachmentmanager.md b/windows/client-management/mdm/policy-csp-attachmentmanager.md
index 6253a5f07d..f5630e76f5 100644
--- a/windows/client-management/mdm/policy-csp-attachmentmanager.md
+++ b/windows/client-management/mdm/policy-csp-attachmentmanager.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - AttachmentManager
description: Policy CSP - AttachmentManager
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-authentication.md b/windows/client-management/mdm/policy-csp-authentication.md
index 183ee25611..71ca1629b3 100644
--- a/windows/client-management/mdm/policy-csp-authentication.md
+++ b/windows/client-management/mdm/policy-csp-authentication.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Authentication
description: Policy CSP - Authentication
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-autoplay.md b/windows/client-management/mdm/policy-csp-autoplay.md
index 6991b2357f..0845e952f8 100644
--- a/windows/client-management/mdm/policy-csp-autoplay.md
+++ b/windows/client-management/mdm/policy-csp-autoplay.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Autoplay
description: Policy CSP - Autoplay
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-bitlocker.md b/windows/client-management/mdm/policy-csp-bitlocker.md
index 544d40112c..a1ba855654 100644
--- a/windows/client-management/mdm/policy-csp-bitlocker.md
+++ b/windows/client-management/mdm/policy-csp-bitlocker.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Bitlocker
description: Policy CSP - Bitlocker
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-bits.md b/windows/client-management/mdm/policy-csp-bits.md
index 22f4c98cec..32fe01163f 100644
--- a/windows/client-management/mdm/policy-csp-bits.md
+++ b/windows/client-management/mdm/policy-csp-bits.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - BITS
description: Policy CSP - BITS
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
@@ -456,7 +456,7 @@ ADMX Info:
This policy setting specifies the number of days a pending BITS job can remain inactive before the job is considered abandoned. By default BITS will wait 90 days before considering an inactive job abandoned. After a job is determined to be abandoned, the job is deleted from BITS and any downloaded files for the job are deleted from the disk.
-> [!Note]
+> [!NOTE]
> Any property changes to the job or any successful download action will reset this timeout.
Value type is integer. Default is 90 days.
diff --git a/windows/client-management/mdm/policy-csp-bluetooth.md b/windows/client-management/mdm/policy-csp-bluetooth.md
index 12986ccfe5..51c93e97d7 100644
--- a/windows/client-management/mdm/policy-csp-bluetooth.md
+++ b/windows/client-management/mdm/policy-csp-bluetooth.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Bluetooth
description: Policy CSP - Bluetooth
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-browser.md b/windows/client-management/mdm/policy-csp-browser.md
index 1ba7caf16f..b49fa49949 100644
--- a/windows/client-management/mdm/policy-csp-browser.md
+++ b/windows/client-management/mdm/policy-csp-browser.md
@@ -3807,7 +3807,7 @@ Most restricted value: 0
[!INCLUDE [keep-favorites-in-sync-between-ie-and-edge-shortdesc](../../../browsers/edge/shortdesc/keep-favorites-in-sync-between-ie-and-edge-shortdesc.md)]
-> [!NOTE]
+> [!NOTE]
> This policy is only enforced in Windows 10 for desktop and not supported in Windows 10 Mobile.
diff --git a/windows/client-management/mdm/policy-csp-camera.md b/windows/client-management/mdm/policy-csp-camera.md
index 626376e2ba..0852d91632 100644
--- a/windows/client-management/mdm/policy-csp-camera.md
+++ b/windows/client-management/mdm/policy-csp-camera.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Camera
description: Policy CSP - Camera
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-cellular.md b/windows/client-management/mdm/policy-csp-cellular.md
index 09a587860d..ff738aa2e1 100644
--- a/windows/client-management/mdm/policy-csp-cellular.md
+++ b/windows/client-management/mdm/policy-csp-cellular.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Cellular
description: Policy CSP - Cellular
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-connectivity.md b/windows/client-management/mdm/policy-csp-connectivity.md
index 6a794dd7a4..f1fc3f9445 100644
--- a/windows/client-management/mdm/policy-csp-connectivity.md
+++ b/windows/client-management/mdm/policy-csp-connectivity.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Connectivity
description: Policy CSP - Connectivity
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-controlpolicyconflict.md b/windows/client-management/mdm/policy-csp-controlpolicyconflict.md
index 54c61771de..c9d03ef5de 100644
--- a/windows/client-management/mdm/policy-csp-controlpolicyconflict.md
+++ b/windows/client-management/mdm/policy-csp-controlpolicyconflict.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - ControlPolicyConflict
description: Policy CSP - ControlPolicyConflict
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
@@ -66,7 +66,7 @@ manager: dansimp
Added in Windows 10, version 1803. This policy allows the IT admin to control which policy will be used whenever both the MDM policy and its equivalent Group Policy (GP) are set on the device.
-> [!Note]
+> [!NOTE]
> MDMWinsOverGP only applies to policies in Policy CSP. It does not apply to other MDM settings with equivalent GP settings that are defined on other configuration service providers.
This policy is used to ensure that MDM policy wins over GP when policy is configured on MDM channel. The default value is 0. The MDM policies in Policy CSP will behave as described if this policy value is set 1.
diff --git a/windows/client-management/mdm/policy-csp-credentialproviders.md b/windows/client-management/mdm/policy-csp-credentialproviders.md
index 1eb6215b47..1e3b1dd91e 100644
--- a/windows/client-management/mdm/policy-csp-credentialproviders.md
+++ b/windows/client-management/mdm/policy-csp-credentialproviders.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - CredentialProviders
description: Policy CSP - CredentialProviders
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-credentialsdelegation.md b/windows/client-management/mdm/policy-csp-credentialsdelegation.md
index 0d204f9001..80a987c29b 100644
--- a/windows/client-management/mdm/policy-csp-credentialsdelegation.md
+++ b/windows/client-management/mdm/policy-csp-credentialsdelegation.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - CredentialsDelegation
description: Policy CSP - CredentialsDelegation
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-credentialsui.md b/windows/client-management/mdm/policy-csp-credentialsui.md
index 1c535f7394..723426a323 100644
--- a/windows/client-management/mdm/policy-csp-credentialsui.md
+++ b/windows/client-management/mdm/policy-csp-credentialsui.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - CredentialsUI
description: Policy CSP - CredentialsUI
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-cryptography.md b/windows/client-management/mdm/policy-csp-cryptography.md
index dde9829762..1921989b07 100644
--- a/windows/client-management/mdm/policy-csp-cryptography.md
+++ b/windows/client-management/mdm/policy-csp-cryptography.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Cryptography
description: Policy CSP - Cryptography
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
@@ -19,14 +19,23 @@ manager: dansimp
## Cryptography policies
+<<<<<<< HEAD
* [Cryptography/AllowFipsAlgorithmPolicy](#CryptographyAllowFipsAlgorithmPolicy)
* [Cryptography/TLSCipherSuites](#CryptographyTLSCipherSuites)
+=======
+* [Cryptography/AllowFipsAlgorithmPolicy](#cryptographyallowfipsalgorithmpolicy)
+* [Cryptography/TLSCipherSuites](#cryptographytlsciphersuites)
+>>>>>>> master
* [Cryptography/Microsoft Surface Hub](#cryptography-policies-supported-by-microsoft-surface-hub)
+<<<<<<< HEAD
## Cryptography/AllowFipsAlgorithmPolicy
+=======
+## Cryptography/AllowFipsAlgorithmPolicy
+>>>>>>> master
@@ -68,7 +77,11 @@ The following list shows the supported values:
+<<<<<<< HEAD
## Cryptography/TLSCipherSuites
+=======
+## Cryptography/TLSCipherSuites
+>>>>>>> master
|Home|Pro|Business |Enterprise |Education |Mobile |Mobile Enterprise |
diff --git a/windows/client-management/mdm/policy-csp-dataprotection.md b/windows/client-management/mdm/policy-csp-dataprotection.md
index efbd0b0ba5..cfa533aef2 100644
--- a/windows/client-management/mdm/policy-csp-dataprotection.md
+++ b/windows/client-management/mdm/policy-csp-dataprotection.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - DataProtection
description: Policy CSP - DataProtection
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-datausage.md b/windows/client-management/mdm/policy-csp-datausage.md
index acd292df91..1268e6243c 100644
--- a/windows/client-management/mdm/policy-csp-datausage.md
+++ b/windows/client-management/mdm/policy-csp-datausage.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - DataUsage
description: Policy CSP - DataUsage
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-defender.md b/windows/client-management/mdm/policy-csp-defender.md
index 536b67fd62..f796a9ae53 100644
--- a/windows/client-management/mdm/policy-csp-defender.md
+++ b/windows/client-management/mdm/policy-csp-defender.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Defender
description: Policy CSP - Defender
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
@@ -1244,7 +1244,7 @@ If this setting is on, Windows Defender Antivirus will be more aggressive when i
For more information about specific values that are supported, see the Windows Defender Antivirus documentation site.
-> [!Note]
+> [!NOTE]
> This feature requires the "Join Microsoft MAPS" setting enabled in order to function.
@@ -1315,7 +1315,7 @@ The typical cloud check timeout is 10 seconds. To enable the extended cloud chec
For example, if the desired timeout is 60 seconds, specify 50 seconds in this setting, which will enable the extended cloud check feature, and will raise the total time to 60 seconds.
-> [!Note]
+> [!NOTE]
> This feature depends on three other MAPS settings the must all be enabled- "Configure the 'Block at First Sight' feature; "Join Microsoft MAPS"; "Send file samples when further analysis is required".
diff --git a/windows/client-management/mdm/policy-csp-deliveryoptimization.md b/windows/client-management/mdm/policy-csp-deliveryoptimization.md
index dd2a915a30..66ac43c7f6 100644
--- a/windows/client-management/mdm/policy-csp-deliveryoptimization.md
+++ b/windows/client-management/mdm/policy-csp-deliveryoptimization.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - DeliveryOptimization
description: Policy CSP - DeliveryOptimization
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-desktop.md b/windows/client-management/mdm/policy-csp-desktop.md
index 3d779f0c64..ebe8a9efb2 100644
--- a/windows/client-management/mdm/policy-csp-desktop.md
+++ b/windows/client-management/mdm/policy-csp-desktop.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Desktop
description: Policy CSP - Desktop
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-deviceguard.md b/windows/client-management/mdm/policy-csp-deviceguard.md
index ed32572a3d..44a9b306d9 100644
--- a/windows/client-management/mdm/policy-csp-deviceguard.md
+++ b/windows/client-management/mdm/policy-csp-deviceguard.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - DeviceGuard
description: Policy CSP - DeviceGuard
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-deviceinstallation.md b/windows/client-management/mdm/policy-csp-deviceinstallation.md
index 29bff22868..bf819d4ba5 100644
--- a/windows/client-management/mdm/policy-csp-deviceinstallation.md
+++ b/windows/client-management/mdm/policy-csp-deviceinstallation.md
@@ -3,7 +3,7 @@ title: Policy CSP - DeviceInstallation
ms.reviewer:
manager: dansimp
description: Policy CSP - DeviceInstallation
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-devicelock.md b/windows/client-management/mdm/policy-csp-devicelock.md
index dcc8261939..78f0468640 100644
--- a/windows/client-management/mdm/policy-csp-devicelock.md
+++ b/windows/client-management/mdm/policy-csp-devicelock.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - DeviceLock
description: Policy CSP - DeviceLock
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-display.md b/windows/client-management/mdm/policy-csp-display.md
index 1e1c95c276..e6bdb26828 100644
--- a/windows/client-management/mdm/policy-csp-display.md
+++ b/windows/client-management/mdm/policy-csp-display.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Display
description: Policy CSP - Display
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-dmaguard.md b/windows/client-management/mdm/policy-csp-dmaguard.md
index 46b9b17b84..84edbd082b 100644
--- a/windows/client-management/mdm/policy-csp-dmaguard.md
+++ b/windows/client-management/mdm/policy-csp-dmaguard.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - DmaGuard
description: Policy CSP - DmaGuard
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
@@ -73,7 +73,7 @@ Device memory sandboxing allows the OS to leverage the I/O Memory Management Uni
This policy only takes effect when Kernel DMA Protection is supported and enabled by the system firmware. Kernel DMA Protection is a platform feature that cannot be controlled via policy or by end user. It has to be supported by the system at the time of manufacturing. To check if the system supports Kernel DMA Protection, please check the Kernel DMA Protection field in the Summary page of MSINFO32.exe.
-> [!Note]
+> [!NOTE]
> This policy does not apply to 1394/Firewire, PCMCIA, CardBus, or ExpressCard devices.
Supported values:
diff --git a/windows/client-management/mdm/policy-csp-education.md b/windows/client-management/mdm/policy-csp-education.md
index fe7b0e9b71..75f755f4fb 100644
--- a/windows/client-management/mdm/policy-csp-education.md
+++ b/windows/client-management/mdm/policy-csp-education.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Education
description: Policy CSP - Education
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-enterprisecloudprint.md b/windows/client-management/mdm/policy-csp-enterprisecloudprint.md
index de47e20c44..606cfc2ceb 100644
--- a/windows/client-management/mdm/policy-csp-enterprisecloudprint.md
+++ b/windows/client-management/mdm/policy-csp-enterprisecloudprint.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - EnterpriseCloudPrint
description: Policy CSP - EnterpriseCloudPrint
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-errorreporting.md b/windows/client-management/mdm/policy-csp-errorreporting.md
index 8535ed7dc0..d498c385d6 100644
--- a/windows/client-management/mdm/policy-csp-errorreporting.md
+++ b/windows/client-management/mdm/policy-csp-errorreporting.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - ErrorReporting
description: Policy CSP - ErrorReporting
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-eventlogservice.md b/windows/client-management/mdm/policy-csp-eventlogservice.md
index 5ca67b16c6..a12bf88937 100644
--- a/windows/client-management/mdm/policy-csp-eventlogservice.md
+++ b/windows/client-management/mdm/policy-csp-eventlogservice.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - EventLogService
description: Policy CSP - EventLogService
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-experience.md b/windows/client-management/mdm/policy-csp-experience.md
index 6ba6f5a35c..ed7998e6a3 100644
--- a/windows/client-management/mdm/policy-csp-experience.md
+++ b/windows/client-management/mdm/policy-csp-experience.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Experience
description: Policy CSP - Experience
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-exploitguard.md b/windows/client-management/mdm/policy-csp-exploitguard.md
index 41ed8b20f3..772d25390b 100644
--- a/windows/client-management/mdm/policy-csp-exploitguard.md
+++ b/windows/client-management/mdm/policy-csp-exploitguard.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - ExploitGuard
description: Policy CSP - ExploitGuard
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-fileexplorer.md b/windows/client-management/mdm/policy-csp-fileexplorer.md
index f0c7dbd3e0..f2666b4442 100644
--- a/windows/client-management/mdm/policy-csp-fileexplorer.md
+++ b/windows/client-management/mdm/policy-csp-fileexplorer.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - FileExplorer
description: Policy CSP - FileExplorer
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-games.md b/windows/client-management/mdm/policy-csp-games.md
index c3bfe395e7..750f00f237 100644
--- a/windows/client-management/mdm/policy-csp-games.md
+++ b/windows/client-management/mdm/policy-csp-games.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Games
description: Policy CSP - Games
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-handwriting.md b/windows/client-management/mdm/policy-csp-handwriting.md
index 939b2d50a6..12cb543539 100644
--- a/windows/client-management/mdm/policy-csp-handwriting.md
+++ b/windows/client-management/mdm/policy-csp-handwriting.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Handwriting
description: Policy CSP - Handwriting
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-internetexplorer.md b/windows/client-management/mdm/policy-csp-internetexplorer.md
index 7e8466865c..6f746062f9 100644
--- a/windows/client-management/mdm/policy-csp-internetexplorer.md
+++ b/windows/client-management/mdm/policy-csp-internetexplorer.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - InternetExplorer
description: Policy CSP - InternetExplorer
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
@@ -2227,7 +2227,7 @@ Value - A number indicating the zone with which this site should be associated f
If you disable or do not configure this policy, users may choose their own site-to-zone assignments.
-> [!Note]
+> [!NOTE]
> This policy is a list that contains the site and index value.
The list is a set of pairs of strings. Each string is seperated by F000. Each pair of strings is stored as a registry name and value. The registry name is the site and the value is an index. The index has to be sequential. See an example below.
diff --git a/windows/client-management/mdm/policy-csp-kerberos.md b/windows/client-management/mdm/policy-csp-kerberos.md
index d7aa81c2a1..2df8f06e1a 100644
--- a/windows/client-management/mdm/policy-csp-kerberos.md
+++ b/windows/client-management/mdm/policy-csp-kerberos.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Kerberos
description: Policy CSP - Kerberos
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-kioskbrowser.md b/windows/client-management/mdm/policy-csp-kioskbrowser.md
index df19d6da30..99fb4e9a1b 100644
--- a/windows/client-management/mdm/policy-csp-kioskbrowser.md
+++ b/windows/client-management/mdm/policy-csp-kioskbrowser.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - KioskBrowser
description: Policy CSP - KioskBrowser
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
@@ -88,7 +88,7 @@ These policies currently only apply to Kiosk Browser app. Kiosk Browser is a Mic
Added in Windows 10, version 1803. List of exceptions to the blocked website URLs (with wildcard support). This is used to configure URLs kiosk browsers are allowed to navigate to, which are a subset of the blocked URLs.
-> [!Note]
+> [!NOTE]
> This policy only applies to the Kiosk Browser app in Microsoft Store.
@@ -134,7 +134,7 @@ Added in Windows 10, version 1803. List of exceptions to the blocked website URL
Added in Windows 10, version 1803. List of blocked website URLs (with wildcard support). This is used to configure blocked URLs kiosk browsers cannot navigate to.
-> [!Note]
+> [!NOTE]
> This policy only applies to the Kiosk Browser app in Microsoft Store.
@@ -180,7 +180,7 @@ Added in Windows 10, version 1803. List of blocked website URLs (with wildcard s
Added in Windows 10, version 1803. Configures the default URL kiosk browsers to navigate on launch and restart.
-> [!Note]
+> [!NOTE]
> This policy only applies to the Kiosk Browser app in Microsoft Store.
@@ -269,7 +269,7 @@ Shows the Kiosk Browser's end session button. When the policy is enabled, the Ki
Added in Windows 10, version 1803. Enable/disable kiosk browser's home button.
-> [!Note]
+> [!NOTE]
> This policy only applies to the Kiosk Browser app in Microsoft Store.
@@ -315,7 +315,7 @@ Added in Windows 10, version 1803. Enable/disable kiosk browser's home button.
Added in Windows 10, version 1803. Enable/disable kiosk browser's navigation buttons (forward/back).
-> [!Note]
+> [!NOTE]
> This policy only applies to the Kiosk Browser app in Microsoft Store.
@@ -363,7 +363,7 @@ Added in Windows 10, version 1803. Amount of time in minutes the session is idle
The value is an int 1-1440 that specifies the amount of minutes the session is idle until the kiosk browser restarts in a fresh state. The default value is empty which means there is no idle timeout within the kiosk browser.
-> [!Note]
+> [!NOTE]
> This policy only applies to the Kiosk Browser app in Microsoft Store.
diff --git a/windows/client-management/mdm/policy-csp-lanmanworkstation.md b/windows/client-management/mdm/policy-csp-lanmanworkstation.md
index 51460c13dc..d185745718 100644
--- a/windows/client-management/mdm/policy-csp-lanmanworkstation.md
+++ b/windows/client-management/mdm/policy-csp-lanmanworkstation.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - LanmanWorkstation
description: Policy CSP - LanmanWorkstation
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-licensing.md b/windows/client-management/mdm/policy-csp-licensing.md
index a86f14229c..4c7c69815e 100644
--- a/windows/client-management/mdm/policy-csp-licensing.md
+++ b/windows/client-management/mdm/policy-csp-licensing.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Licensing
description: Policy CSP - Licensing
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-localpoliciessecurityoptions.md b/windows/client-management/mdm/policy-csp-localpoliciessecurityoptions.md
index b730a05ff6..b74019c352 100644
--- a/windows/client-management/mdm/policy-csp-localpoliciessecurityoptions.md
+++ b/windows/client-management/mdm/policy-csp-localpoliciessecurityoptions.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - LocalPoliciesSecurityOptions
description: Policy CSP - LocalPoliciesSecurityOptions
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
@@ -692,7 +692,7 @@ GP Info:
-> [!Warning]
+> [!WARNING]
> Starting in the version 1809 of Windows, this policy is deprecated.
Domain member: Digitally encrypt or sign secure channel data (always)
@@ -762,7 +762,7 @@ GP Info:
-> [!Warning]
+> [!WARNING]
> Starting in the version 1809 of Windows, this policy is deprecated.
Domain member: Digitally encrypt secure channel data (when possible)
@@ -829,7 +829,7 @@ GP Info:
-> [!Warning]
+> [!WARNING]
> Starting in the version 1809 of Windows, this policy is deprecated.
Domain member: Disable machine account password changes
diff --git a/windows/client-management/mdm/policy-csp-lockdown.md b/windows/client-management/mdm/policy-csp-lockdown.md
index 78acd3913e..0f90b19790 100644
--- a/windows/client-management/mdm/policy-csp-lockdown.md
+++ b/windows/client-management/mdm/policy-csp-lockdown.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - LockDown
description: Policy CSP - LockDown
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-maps.md b/windows/client-management/mdm/policy-csp-maps.md
index 1606fceb57..1028e204b8 100644
--- a/windows/client-management/mdm/policy-csp-maps.md
+++ b/windows/client-management/mdm/policy-csp-maps.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Maps
description: Policy CSP - Maps
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-messaging.md b/windows/client-management/mdm/policy-csp-messaging.md
index b42eb48017..b2efd6a840 100644
--- a/windows/client-management/mdm/policy-csp-messaging.md
+++ b/windows/client-management/mdm/policy-csp-messaging.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Messaging
description: Policy CSP - Messaging
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-mssecurityguide.md b/windows/client-management/mdm/policy-csp-mssecurityguide.md
index 36fa5d0cc8..4e53332f72 100644
--- a/windows/client-management/mdm/policy-csp-mssecurityguide.md
+++ b/windows/client-management/mdm/policy-csp-mssecurityguide.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - MSSecurityGuide
description: Policy CSP - MSSecurityGuide
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-msslegacy.md b/windows/client-management/mdm/policy-csp-msslegacy.md
index f12f2f997f..722b58c97c 100644
--- a/windows/client-management/mdm/policy-csp-msslegacy.md
+++ b/windows/client-management/mdm/policy-csp-msslegacy.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - MSSLegacy
description: Policy CSP - MSSLegacy
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-networkisolation.md b/windows/client-management/mdm/policy-csp-networkisolation.md
index a06abada5b..9404b184fc 100644
--- a/windows/client-management/mdm/policy-csp-networkisolation.md
+++ b/windows/client-management/mdm/policy-csp-networkisolation.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - NetworkIsolation
description: Policy CSP - NetworkIsolation
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-notifications.md b/windows/client-management/mdm/policy-csp-notifications.md
index c6d8e5217d..1624dfe21f 100644
--- a/windows/client-management/mdm/policy-csp-notifications.md
+++ b/windows/client-management/mdm/policy-csp-notifications.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Notifications
description: Policy CSP - Notifications
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
@@ -81,7 +81,7 @@ If you disable or do not configure this policy setting, the client computer will
No reboots or service restarts are required for this policy setting to take effect.
-> [!Warning]
+> [!WARNING]
> This policy is designed for zero exhaust. This policy may cause some MDM processes to break because WNS notification is used by the MDM server to send real time tasks to the device, such as remote wipe, unenroll, remote find, and mandatory app installation. When this policy is set to disallow WNS, those real time processes will no longer work and some time-sensitive actions such as remote wipe when the device is stolen or unenrollment when the device is compromised will not work.
diff --git a/windows/client-management/mdm/policy-csp-power.md b/windows/client-management/mdm/policy-csp-power.md
index 95e8f4591b..643ff5cea3 100644
--- a/windows/client-management/mdm/policy-csp-power.md
+++ b/windows/client-management/mdm/policy-csp-power.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Power
description: Policy CSP - Power
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-printers.md b/windows/client-management/mdm/policy-csp-printers.md
index 5d3b5f3b49..b8ebc7042d 100644
--- a/windows/client-management/mdm/policy-csp-printers.md
+++ b/windows/client-management/mdm/policy-csp-printers.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Printers
description: Policy CSP - Printers
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-privacy.md b/windows/client-management/mdm/policy-csp-privacy.md
index 8b9c744102..3395ba9cee 100644
--- a/windows/client-management/mdm/policy-csp-privacy.md
+++ b/windows/client-management/mdm/policy-csp-privacy.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Privacy
description: Policy CSP - Privacy
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
@@ -318,7 +318,7 @@ manager: dansimp
Allows or disallows the automatic acceptance of the pairing and privacy user consent dialog when launching apps.
-> [!Note]
+> [!NOTE]
> There were issues reported with the previous release of this policy and a fix was added in Windows 10, version 1709.
diff --git a/windows/client-management/mdm/policy-csp-remoteassistance.md b/windows/client-management/mdm/policy-csp-remoteassistance.md
index 35c9418f05..4a64d0d55d 100644
--- a/windows/client-management/mdm/policy-csp-remoteassistance.md
+++ b/windows/client-management/mdm/policy-csp-remoteassistance.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - RemoteAssistance
description: Policy CSP - RemoteAssistance
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-remotedesktopservices.md b/windows/client-management/mdm/policy-csp-remotedesktopservices.md
index 7ec935f89a..4a7f1eebd5 100644
--- a/windows/client-management/mdm/policy-csp-remotedesktopservices.md
+++ b/windows/client-management/mdm/policy-csp-remotedesktopservices.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - RemoteDesktopServices
description: Policy CSP - RemoteDesktopServices
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-remotemanagement.md b/windows/client-management/mdm/policy-csp-remotemanagement.md
index 5ab20bb4a9..ba8a7d6310 100644
--- a/windows/client-management/mdm/policy-csp-remotemanagement.md
+++ b/windows/client-management/mdm/policy-csp-remotemanagement.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - RemoteManagement
description: Policy CSP - RemoteManagement
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-remoteprocedurecall.md b/windows/client-management/mdm/policy-csp-remoteprocedurecall.md
index f91881863d..ade921ae21 100644
--- a/windows/client-management/mdm/policy-csp-remoteprocedurecall.md
+++ b/windows/client-management/mdm/policy-csp-remoteprocedurecall.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - RemoteProcedureCall
description: Policy CSP - RemoteProcedureCall
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-remoteshell.md b/windows/client-management/mdm/policy-csp-remoteshell.md
index 6e881739c8..21cfd117d2 100644
--- a/windows/client-management/mdm/policy-csp-remoteshell.md
+++ b/windows/client-management/mdm/policy-csp-remoteshell.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - RemoteShell
description: Policy CSP - RemoteShell
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-restrictedgroups.md b/windows/client-management/mdm/policy-csp-restrictedgroups.md
index ccbebbf6fa..9c125b8c0f 100644
--- a/windows/client-management/mdm/policy-csp-restrictedgroups.md
+++ b/windows/client-management/mdm/policy-csp-restrictedgroups.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - RestrictedGroups
description: Policy CSP - RestrictedGroups
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-search.md b/windows/client-management/mdm/policy-csp-search.md
index 8b85ea7b5a..d5903f1493 100644
--- a/windows/client-management/mdm/policy-csp-search.md
+++ b/windows/client-management/mdm/policy-csp-search.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Search
description: Policy CSP - Search
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-security.md b/windows/client-management/mdm/policy-csp-security.md
index abcd218b57..4467309f6d 100644
--- a/windows/client-management/mdm/policy-csp-security.md
+++ b/windows/client-management/mdm/policy-csp-security.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Security
description: Policy CSP - Security
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-settings.md b/windows/client-management/mdm/policy-csp-settings.md
index 1afcd6368d..cecaec5871 100644
--- a/windows/client-management/mdm/policy-csp-settings.md
+++ b/windows/client-management/mdm/policy-csp-settings.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Settings
description: Policy CSP - Settings
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-smartscreen.md b/windows/client-management/mdm/policy-csp-smartscreen.md
index ed50500741..61a11806fa 100644
--- a/windows/client-management/mdm/policy-csp-smartscreen.md
+++ b/windows/client-management/mdm/policy-csp-smartscreen.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - SmartScreen
description: Policy CSP - SmartScreen
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-speech.md b/windows/client-management/mdm/policy-csp-speech.md
index da41b5caa4..9d1d87faa3 100644
--- a/windows/client-management/mdm/policy-csp-speech.md
+++ b/windows/client-management/mdm/policy-csp-speech.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Speech
description: Policy CSP - Speech
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-start.md b/windows/client-management/mdm/policy-csp-start.md
index 5b21ccc24a..05e37d1dc9 100644
--- a/windows/client-management/mdm/policy-csp-start.md
+++ b/windows/client-management/mdm/policy-csp-start.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Start
description: Policy CSP - Start
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-storage.md b/windows/client-management/mdm/policy-csp-storage.md
index c889fc7bec..02d36e60d9 100644
--- a/windows/client-management/mdm/policy-csp-storage.md
+++ b/windows/client-management/mdm/policy-csp-storage.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Storage
description: Policy CSP - Storage
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-system.md b/windows/client-management/mdm/policy-csp-system.md
index cd2c32f688..3781130045 100644
--- a/windows/client-management/mdm/policy-csp-system.md
+++ b/windows/client-management/mdm/policy-csp-system.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - System
description: Policy CSP - System
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
@@ -444,7 +444,7 @@ This MDM setting corresponds to the EnableFontProviders Group Policy setting. If
This setting is used by lower-level components for text display and fond handling and has not direct effect on web browsers, which may download web fonts used in web content.
-> [!Note]
+> [!NOTE]
> Reboot is required after setting the policy; alternatively you can stop and restart the FontCache service.
diff --git a/windows/client-management/mdm/policy-csp-systemservices.md b/windows/client-management/mdm/policy-csp-systemservices.md
index ded40a8b16..1b98e5a487 100644
--- a/windows/client-management/mdm/policy-csp-systemservices.md
+++ b/windows/client-management/mdm/policy-csp-systemservices.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - SystemServices
description: Policy CSP - SystemServices
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-taskmanager.md b/windows/client-management/mdm/policy-csp-taskmanager.md
index 5e56b287a7..5e4b03fa34 100644
--- a/windows/client-management/mdm/policy-csp-taskmanager.md
+++ b/windows/client-management/mdm/policy-csp-taskmanager.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - TaskManager
description: Policy CSP - TaskManager
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-taskscheduler.md b/windows/client-management/mdm/policy-csp-taskscheduler.md
index 38a4f44179..ca2b448d50 100644
--- a/windows/client-management/mdm/policy-csp-taskscheduler.md
+++ b/windows/client-management/mdm/policy-csp-taskscheduler.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - TaskScheduler
description: Policy CSP - TaskScheduler
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-textinput.md b/windows/client-management/mdm/policy-csp-textinput.md
index 08dea14a3e..ce3e59ecc4 100644
--- a/windows/client-management/mdm/policy-csp-textinput.md
+++ b/windows/client-management/mdm/policy-csp-textinput.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - TextInput
description: Policy CSP - TextInput
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-timelanguagesettings.md b/windows/client-management/mdm/policy-csp-timelanguagesettings.md
index 72a3a6ee06..2d61990c7a 100644
--- a/windows/client-management/mdm/policy-csp-timelanguagesettings.md
+++ b/windows/client-management/mdm/policy-csp-timelanguagesettings.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - TimeLanguageSettings
description: Policy CSP - TimeLanguageSettings
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-update.md b/windows/client-management/mdm/policy-csp-update.md
index 2531787f7f..7fe7216b40 100644
--- a/windows/client-management/mdm/policy-csp-update.md
+++ b/windows/client-management/mdm/policy-csp-update.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Update
description: Policy CSP - Update
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
@@ -1896,7 +1896,7 @@ For Quality Updates, this policy specifies the deadline in days before automatic
The system will reboot on or after the specified deadline. The reboot is prioritized over any configured Active Hours and any existing system and user busy checks.
-> [!Note]
+> [!NOTE]
> If Update/EngagedDeadline is the only policy set (Update/EngagedRestartTransitionSchedule and Update/EngagedRestartSnoozeSchedule are not set), the behavior goes from reboot required -> engaged behavior -> forced reboot after deadline is reached with a 3-day snooze period.
Value type is integer. Default is 14.
@@ -3786,7 +3786,7 @@ Options:
- 1 – Turn off all notifications, excluding restart warnings
- 2 – Turn off all notifications, including restart warnings
-> [!Important]
+> [!IMPORTANT]
> If you choose not to get update notifications and also define other Group policies so that devices aren’t automatically getting updates, neither you nor device users will be aware of critical security, quality, or feature updates, and your devices may be at risk.
@@ -3847,7 +3847,7 @@ ADMX Info:
-> [!Important]
+> [!IMPORTANT]
> Starting in Windows 10, version 1703 this policy is not supported in Windows 10 Mobile Enteprise and IoT Mobile.
Allows the device to check for updates from a WSUS server instead of Microsoft Update. This is useful for on-premises MDMs that need to update devices that cannot connect to the Internet.
@@ -3939,7 +3939,7 @@ To use this setting, you must set two server name values: the server from which
Value type is string and the default value is an empty string, "". If the setting is not configured, and if Automatic Updates is not disabled by policy or user preference, the Automatic Updates client connects directly to the Windows Update site on the Internet.
-> [!Note]
+> [!NOTE]
> If the "Configure Automatic Updates" Group Policy is disabled, then this policy has no effect.
> If the "Alternate Download Server" Group Policy is not set, it will use the WSUS server by default to download updates.
> This policy is not supported on Windows RT. Setting this policy will not have any effect on Windows RT PCs.
diff --git a/windows/client-management/mdm/policy-csp-userrights.md b/windows/client-management/mdm/policy-csp-userrights.md
index ad3586a7b2..a045fc0a48 100644
--- a/windows/client-management/mdm/policy-csp-userrights.md
+++ b/windows/client-management/mdm/policy-csp-userrights.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - UserRights
description: Policy CSP - UserRights
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-wifi.md b/windows/client-management/mdm/policy-csp-wifi.md
index 1aa0d39661..ec997ee27b 100644
--- a/windows/client-management/mdm/policy-csp-wifi.md
+++ b/windows/client-management/mdm/policy-csp-wifi.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - Wifi
description: Policy CSP - Wifi
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-windowsconnectionmanager.md b/windows/client-management/mdm/policy-csp-windowsconnectionmanager.md
index 3765d7bdde..6824a34e5c 100644
--- a/windows/client-management/mdm/policy-csp-windowsconnectionmanager.md
+++ b/windows/client-management/mdm/policy-csp-windowsconnectionmanager.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - WindowsConnectionManager
description: Policy CSP - WindowsConnectionManager
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-windowsdefendersecuritycenter.md b/windows/client-management/mdm/policy-csp-windowsdefendersecuritycenter.md
index 0e523a9d77..cc8580325d 100644
--- a/windows/client-management/mdm/policy-csp-windowsdefendersecuritycenter.md
+++ b/windows/client-management/mdm/policy-csp-windowsdefendersecuritycenter.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - WindowsDefenderSecurityCenter
description: Policy CSP - WindowsDefenderSecurityCenter
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
@@ -436,7 +436,7 @@ Valid values:
Added in Windows 10, version 1709. Use this policy if you want Windows Defender Security Center to only display notifications which are considered critical. If you disable or do not configure this setting, Windows Defender Security Center will display critical and non-critical notifications to users.
-> [!Note]
+> [!NOTE]
> If Suppress notification is enabled then users will not see critical or non-critical messages.
Value type is integer. Supported operations are Add, Get, Replace and Delete.
diff --git a/windows/client-management/mdm/policy-csp-windowsinkworkspace.md b/windows/client-management/mdm/policy-csp-windowsinkworkspace.md
index 398b717f8d..ca2a0c7b72 100644
--- a/windows/client-management/mdm/policy-csp-windowsinkworkspace.md
+++ b/windows/client-management/mdm/policy-csp-windowsinkworkspace.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - WindowsInkWorkspace
description: Policy CSP - WindowsInkWorkspace
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-windowslogon.md b/windows/client-management/mdm/policy-csp-windowslogon.md
index 5c3f33f450..e147d62c40 100644
--- a/windows/client-management/mdm/policy-csp-windowslogon.md
+++ b/windows/client-management/mdm/policy-csp-windowslogon.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - WindowsLogon
description: Policy CSP - WindowsLogon
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-windowspowershell.md b/windows/client-management/mdm/policy-csp-windowspowershell.md
index fd6fa0ab4c..9e2d0223b5 100644
--- a/windows/client-management/mdm/policy-csp-windowspowershell.md
+++ b/windows/client-management/mdm/policy-csp-windowspowershell.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - WindowsPowerShell
description: Policy CSP - WindowsPowerShell
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-csp-wirelessdisplay.md b/windows/client-management/mdm/policy-csp-wirelessdisplay.md
index a35ddea58f..1ba5d5ec2d 100644
--- a/windows/client-management/mdm/policy-csp-wirelessdisplay.md
+++ b/windows/client-management/mdm/policy-csp-wirelessdisplay.md
@@ -1,7 +1,7 @@
---
title: Policy CSP - WirelessDisplay
description: Policy CSP - WirelessDisplay
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policy-ddf-file.md b/windows/client-management/mdm/policy-ddf-file.md
index 0155da04e8..82449daa56 100644
--- a/windows/client-management/mdm/policy-ddf-file.md
+++ b/windows/client-management/mdm/policy-ddf-file.md
@@ -4,7 +4,7 @@ description: Policy DDF file
ms.assetid: D90791B5-A772-4AF8-B058-5D566865AF8D
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/policymanager-csp.md b/windows/client-management/mdm/policymanager-csp.md
index ca6963743e..ad4bb24be7 100644
--- a/windows/client-management/mdm/policymanager-csp.md
+++ b/windows/client-management/mdm/policymanager-csp.md
@@ -4,7 +4,7 @@ description: PolicyManager CSP
ms.assetid: 048427b1-6024-4660-8660-bd91c583f7f9
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/provisioning-csp.md b/windows/client-management/mdm/provisioning-csp.md
index f6f151d7d1..9dfabcfba3 100644
--- a/windows/client-management/mdm/provisioning-csp.md
+++ b/windows/client-management/mdm/provisioning-csp.md
@@ -4,7 +4,7 @@ description: The Provisioning configuration service provider is used for bulk us
ms.assetid: 5D6C17BE-727A-4AFA-9F30-B34C1EA1D2AE
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/proxy-csp.md b/windows/client-management/mdm/proxy-csp.md
index 9078c67e05..cced09bc2b 100644
--- a/windows/client-management/mdm/proxy-csp.md
+++ b/windows/client-management/mdm/proxy-csp.md
@@ -4,7 +4,7 @@ description: PROXY CSP
ms.assetid: 9904d44c-4a1e-4ae7-a6c7-5dba06cb16ce
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/push-notification-windows-mdm.md b/windows/client-management/mdm/push-notification-windows-mdm.md
index 71cc999c8b..bcae3dceaf 100644
--- a/windows/client-management/mdm/push-notification-windows-mdm.md
+++ b/windows/client-management/mdm/push-notification-windows-mdm.md
@@ -7,7 +7,7 @@ MS-HAID:
ms.assetid: 9031C4FE-212A-4481-A1B0-4C3190B388AE
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/pxlogical-csp.md b/windows/client-management/mdm/pxlogical-csp.md
index 614473916d..5e0bc0b2d9 100644
--- a/windows/client-management/mdm/pxlogical-csp.md
+++ b/windows/client-management/mdm/pxlogical-csp.md
@@ -4,7 +4,7 @@ description: PXLOGICAL configuration service provider
ms.assetid: b5fc84d4-aa32-4edd-95f1-a6a9c0feb459
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
diff --git a/windows/client-management/mdm/reboot-csp.md b/windows/client-management/mdm/reboot-csp.md
index 227a21008a..9711b4b2a4 100644
--- a/windows/client-management/mdm/reboot-csp.md
+++ b/windows/client-management/mdm/reboot-csp.md
@@ -4,7 +4,7 @@ description: Reboot CSP
ms.assetid: 4E3F1225-BBAD-40F5-A1AB-FF221B6BAF48
ms.reviewer:
manager: dansimp
-ms.author: v-madhi
+ms.author: dansimp
ms.topic: article
ms.prod: w10
ms.technology: windows
@@ -29,7 +29,7 @@ The following diagram shows the Reboot configuration service provider management
**RebootNow**
> %SystemRoot%\MEMORY.DMP
@@ -187,19 +187,19 @@ The Performance Monitor log is located in the path: C:\PERFLOGS
#### Use memory dump to collect data for the physical computer that's running in a frozen state
-> [!Warning]
+> [!WARNING]
> Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, [back up the registry for restoration](https://support.microsoft.com/help/322756) in case problems occur.
If the physical computer is still running in a frozen state, follow these steps to enable and collect memory dump:
1. Make sure that the computer is set up to get a complete memory dump file and that you can access it through the network. To do this, follow these steps:
- > [!Note]
+ > [!NOTE]
> If it isn't possible to access the affected computer through the network, try to generate a memory dump file through NMI interruption. The result of the action may not collect a memory dump file if some of the following settings aren't qualified.
1. Try to access the desktop of the computer by any means.
- > [!Note]
+ > [!NOTE]
> In case accessing the operating system isn't possible, try to access Registry Editor on the computer remotely in order to check the type of memory dump file and page file with which the computer is currently configured.
2. From a remote computer that is preferably in the same network and subnet, go to **Registry Editor** \> **Connect Network Registry**. Then, connect to the concerned computer, and verify the following settings:
@@ -218,7 +218,7 @@ If the physical computer is still running in a frozen state, follow these steps
If the page file is customized, the size will be reflected in the registry, such as ‘?:\pagefile.sys 1024 1124’ where 1024 is the initial size and 1124 is the max size.
- > [!Note]
+ > [!NOTE]
> If the size isn't reflected in the Registry, try to access an Administrative share where the page file is located (such as \\\\**ServerName**\C$).
3. Make sure that there's a paging file (pagefile.sys) on the system drive of the computer, and it's at least 100 MB over the installed RAM.
@@ -244,7 +244,7 @@ If the physical computer is still running in a frozen state, follow these steps
4. Restart the computer.
3. When the computer exhibits the problem, hold down the right **CTRL** key, and press the **Scroll Lock** key two times to generate a memory dump.
- > [!Note]
+ > [!NOTE]
> By default, the dump file is located in the path: %SystemRoot%\MEMORY.DMP
### Use Pool Monitor to collect data for the physical computer that is no longer frozen
@@ -267,7 +267,7 @@ To debug the virtual machines on Hyper-V, run the following cmdlet in Windows Po
Debug-VM -Name "VM Name" -InjectNonMaskableInterrupt -ComputerName Hostname
```
-> [!Note]
+> [!NOTE]
> This method is applicable only to Windows 8, Windows Server 2012, and later versions of Windows virtual machines. For the earlier versions of Windows, see methods 1 through 4 that are described earlier in this section.
#### VMware
diff --git a/windows/configuration/customize-windows-10-start-screens-by-using-group-policy.md b/windows/configuration/customize-windows-10-start-screens-by-using-group-policy.md
index 95610629f1..5caeb82469 100644
--- a/windows/configuration/customize-windows-10-start-screens-by-using-group-policy.md
+++ b/windows/configuration/customize-windows-10-start-screens-by-using-group-policy.md
@@ -28,7 +28,7 @@ In Windows 10 Pro, Enterprise, and Education, you can use a Group Policy Object
This topic describes how to update Group Policy settings to display a customized Start and taskbar layout when the users sign in. By creating a domain-based GPO with these settings, you can deploy a customized Start and taskbar layout to users in a domain.
->[!WARNING]
+>[!WARNING]
>When a full Start layout is applied with this method, the users cannot pin, unpin, or uninstall apps from Start. Users can view and open all apps in the **All Apps** view, but they cannot pin any apps to Start. When a partial Start layout is applied, the contents of the specified tile groups cannot be changed, but users can move those groups, and can also create and customize their own groups. When you apply a taskbar layout, users will still be able to pin and unpin apps, and change the order of pinned apps.
@@ -49,14 +49,14 @@ Three features enable Start and taskbar layout control:
- The [Export-StartLayout](https://docs.microsoft.com/powershell/module/startlayout/export-startlayout?view=win10-ps) cmdlet in Windows PowerShell exports a description of the current Start layout in .xml file format.
- >[!NOTE]
+ >[!NOTE]
>To import the layout of Start to a mounted Windows image, use the [Import-StartLayout](https://docs.microsoft.com/powershell/module/startlayout/import-startlayout) cmdlet.
- [You can modify the Start .xml file](configure-windows-10-taskbar.md) to include `
-
+You can use Group Policy through the Group Policy Management Console (GPMC) to control how Windows Update for Business works. You should consider and devise a deployment strategy for updates before you make changes to the Windows Update for Business settings. See
- Simply enabling the **Defer Upgrades and Updates** policy sets the receiving client to the CBB servicing branch, which is what you want for your first deployment ring, **Ring 4 Broad business users**.
-
-8. Enable the **Defer Updates and Upgrades** setting, and then click **OK**.
+An IT administrator can set policies for Windows Update for Business by using Group Policy, or they can be set locally (per device). All of the relevant policies are under the path **Computer configuration > Administrative Templates > Windows Components > Windows Update**.
-9. Close the Group Policy Management Editor.
+To manage updates with Windows Update for Business as described in this topic, you should prepare with these steps, if you haven't already:
-Because the **Windows Update for Business - CBB1** GPO contains a computer policy and you only want to apply it to computers in the **Ring 4 Broad business users** group, use **Security Filtering** to scope the policy’s effect.
+- Create Active Directory security groups that align with the deployment rings you use to phase deployment of updates. See [Build deployment rings for Windows 10 updates](waas-deployment-rings-windows-10-updates.md) to learn more about deployment rings in Windows 10.
+- Allow access to the Windows Update service.
+- Download and install ADMX templates appropriate to your Windows 10 version. For more information, see [How to create and manage the Central Store for Group Policy Administrative Templates in Windows](https://support.microsoft.com/help/3087759) and [Step-By-Step: Managing Windows 10 with Administrative templates](https://blogs.technet.microsoft.com/canitpro/2015/10/20/step-by-step-managing-windows-10-with-administrative-templates/).
-### Scope the policy to the Ring 4 Broad business users group
-1. In the GPMC, select the **Windows Update for Business - CBB1** policy.
+## Set up Windows Update for Business
-2. In **Security Filtering** on the **Scope** tab, remove the default **AUTHENTICATED USERS** security group, and add the **Ring 4 Broad business users** group.
+In this example, one security group is used to manage updates. Typically we would recommend having at least three rings (early testers for pre-release builds, broad deployment for releases, critical devices for mature releases) to deploy. See [Build deployment rings for Windows 10 updates](waas-deployment-rings-windows-10-updates.md) for more information.
- 
-
+Follow these steps on a device running the Remote Server Administration Tools or on a domain controller:
-The **Ring 4 Broad business users** deployment ring has now been configured. Next, configure **Ring 5 Broad business users #2** to accommodate a 1-week delay for quality updates and a 2-week delay for feature updates.
+### Set up a ring
+1. Start Group Policy Management Console (gpmc.msc).
+2. Expand **Forest > Domains > *\
-
- Category
- Maximum deferral
- Deferral increments
- Classification type
- Classification GUID
-
-
- OS upgrades
- 8 months
- 1 month
- Upgrade
- 3689BDC8-B205-4AF4-8D4A-A63924C5E9D5
-
-
- OS updates
- 4 weeks
- 1 week
- Security updates
- 0FA1201D-4330-4FA8-8AE9-B877473B6441
-
-
- Drivers
- EBFC1FC5-71A4-4F7B-9ACA-3B9A503104A0
-
-
- Updates
- CD5FFD1E-E932-4E3A-BF74-18BF0B1BBD83
-
-
- Other/non-deferrable
- No deferral
- No deferral
- Definition updates
- E0789628-CE08-4437-BE74-2495B842F43B
-
-
+In this example, some problem is discovered during the deployment of the update to the "pilot" ring.
-9. Close the Group Policy Management Editor.
+
-Because the **Windows Update for Business – CB2** GPO contains a computer policy and you only want to apply it to computers in the **Ring 2 Pilot Business Users** group, use **Security Filtering** to scope the policy’s effect.
+At this point, the IT administrator can set a policy to pause the update. In this example, the admin selects the **Pause quality updates** check box.
-### Scope the policy to the Ring 2 Pilot Business Users group
+
-1. In the GPMC, select the **Windows Update for Business - CB2** policy.
+Now all devices are paused from updating for 35 days. When the the pause is removed, they will be offered the *next* quality update, which ideally will not have the same issue. If there is still an issue, the IT admin can pause updates again.
-2. In **Security Filtering** on the **Scope** tab, remove the default **AUTHENTICATED USERS** security group, and add the **Ring 2 Pilot Business Users** group.
- 
-The **Ring 2 Pilot Business Users** deployment ring has now been configured. Next, configure **Ring 4 Broad business users** to set those clients into the CBB servicing branch so that they receive feature updates as soon as they’re made available for the CBB servicing branch.
+#### Set branch readiness level for feature updates
-### Configure Ring 4 Broad business users policy
+This policy only applies to feature updates. To enable preview builds for devices in your organization, set the "Enable preview builds" policy and then use the "Select when preview builds and feature updates are received" policy.
-1. Open GPMC (gpmc.msc).
+We recommend that you set up a ring to receive preview builds by joining the Windows Insider Program for Business. By having a ring of devices receiving "pre-release slow" builds and learning about commercial pre-release features, you can ensure that any issues you have with the release are fixed before it is ever released and far before you broadly deploy.
-2. Expand **Forest** > **Domains** > *your domain*.
+- Enable preview builds: **Computer configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business > Manage Preview Builds**
-3. Right-click *your domain* and select **Create a GPO in this domain, and Link it here**.
-4. In the **New GPO** dialog box, type **Windows Update for Business - CBB1** for the name of the new GPO.
-
-5. Right-click the **Windows Update for Business - CBB1** GPO, and then click **Edit**.
-
-6. In the Group Policy Management Editor, go to **Computer Configuration** > **Policies** > **Administrative Templates** > **Windows Components** > **Windows Update** > **Defer Windows Updates**.
-7. Right-click **Select when Feature Updates are received**, and then click **Edit**.
+- Set branch readiness level: **Computer configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business > Select when Preview Builds and Feature Updates are Received**
-8. In the **Select when Feature Updates are received** policy, enable it, select a branch readiness level of **CBB**, and then click **OK**.
- 
-9. Close the Group Policy Management Editor.
-
-### Scope the policy to the Ring 4 Broad business users group
-
-1. In the GPMC, select the **Windows Update for Business - CBB1** policy.
-
-2. In **Security Filtering** on the **Scope** tab, remove the default **AUTHENTICATED USERS** security group, and add the **Ring 4 Broad business users** group.
-
-
-The **Ring 4 Broad business users** deployment ring has now been configured. Finally, configure **Ring 5 Broad business users #2** to accommodate a 7-day delay for quality updates and a 14-day delay for feature updates
-
-### Configure Ring 5 Broad business users \#2 policy
-
-1. Open GPMC (gpmc.msc).
-
-2. Expand **Forest** > **Domains** > *your domain*.
-
-3. Right-click *your domain* and select **Create a GPO in this domain, and Link it here**.
-
-4. In the **New GPO** dialog box, type **Windows Update for Business - CBB2** for the name of the new GPO.
-
-5. Right-click the **Windows Update for Business - CBB2** GPO, and then click **Edit**.
-
-6. In the Group Policy Management Editor, go to **Computer Configuration** > **Policies** > **Administrative Templates** > **Windows Components** > **Windows Update** > **Defer Windows Updates**.
-
-7. Right-click **Select when Feature Updates are received**, and then click **Edit**.
-
-8. In the **Select when Feature Updates are received** policy, enable it, select a branch readiness level of **CBB**, set the feature update delay to **14** days, and then click **OK**.
-
- 
-
-9. Right-click **Select when Quality Updates are received**, and then click **Edit**.
-
-10. In the **Select when Quality Updates are received** policy, enable it, set the quality update delay to **7** days, and then click **OK**.
-
- 
-
-11. Close the Group Policy Management Editor.
-
-
-
-### Scope the policy to the Ring 5 Broad business users \#2 group
-
-1. In the GPMC, select the **Windows Update for Business - CBB2** policy.
-
-2. In **Security Filtering** on the **Scope** tab, remove the default **AUTHENTICATED USERS** security group, and add the **Ring 5 Broad business users #2** group.
-
-## Known issues
-The following article describes the known challenges that can occur when you manage a Windows 10 Group policy client base:
-- [Known issues managing a Windows 10 Group Policy client in Windows Server 2012 R2](https://support.microsoft.com/help/4015786/known-issues-managing-a-windows-10-group-policy-client-in-windows-serv)
-
## Related topics
- [Update Windows 10 in the enterprise](index.md)
@@ -371,3 +142,8 @@ The following article describes the known challenges that can occur when you man
- [Deploy Windows 10 updates using Windows Server Update Services](waas-manage-updates-wsus.md)
- [Deploy Windows 10 updates using System Center Configuration Manager](waas-manage-updates-configuration-manager.md)
- [Manage device restarts after updates](waas-restart.md)
+
+
+
+
+
diff --git a/windows/deployment/update/windows-analytics-get-started.md b/windows/deployment/update/windows-analytics-get-started.md
index 73a21b96c2..17c051faaf 100644
--- a/windows/deployment/update/windows-analytics-get-started.md
+++ b/windows/deployment/update/windows-analytics-get-started.md
@@ -73,7 +73,7 @@ To enable data sharing, configure your proxy server to whitelist the following e
>[!NOTE]
>Proxy authentication and SSL inspections are frequent challenges for enterprises. See the following sections for configuration options.
-> [!Important]
+> [!IMPORTANT]
> For privacy and data integrity, Windows checks for a Microsoft SSL certificate when communicating with the diagnostic data endpoints. SSL interception and inspection aren't possible. To use Desktop Analytics, exclude these endpoints from SSL inspection.
diff --git a/windows/deployment/update/windows-update-logs.md b/windows/deployment/update/windows-update-logs.md
index 13bb51577d..854d12fc0e 100644
--- a/windows/deployment/update/windows-update-logs.md
+++ b/windows/deployment/update/windows-update-logs.md
@@ -63,7 +63,7 @@ The WU engine has different component names. The following are some of the most
- DataStore - Caching update data locally
- IdleTimer - Tracking active calls, stopping a service
->[!NOTE]
+>[!NOTE]
>Many component log messages are invaluable if you are looking for problems in that specific area. However, they can be useless if you don't filter to exclude irrelevant components so that you can focus on what’s important.
### Windows Update log structure
diff --git a/windows/deployment/update/wufb-compliancedeadlines.md b/windows/deployment/update/wufb-compliancedeadlines.md
index 7d4e473c54..eb8f6bcde2 100644
--- a/windows/deployment/update/wufb-compliancedeadlines.md
+++ b/windows/deployment/update/wufb-compliancedeadlines.md
@@ -29,7 +29,7 @@ This flow only enforces the deadline where the device will attempt to silently r
Once the device is in the pending restart state, it will attempt to restart the device during non-active hours. This is known as the auto-restart period, and by default it does not require user interaction to reboot the device.
->[!NOTE]
+>[!NOTE]
>Deadlines are enforced from pending restart state (for example, when the device has completed the installation and download from Windows Update).
### Policy overview
diff --git a/windows/deployment/upgrade/upgrade-readiness-get-started.md b/windows/deployment/upgrade/upgrade-readiness-get-started.md
index f65e38cc67..e5c2bfe712 100644
--- a/windows/deployment/upgrade/upgrade-readiness-get-started.md
+++ b/windows/deployment/upgrade/upgrade-readiness-get-started.md
@@ -47,7 +47,7 @@ Upgrade Readiness is offered as a *solution* which you link to a new or existing
1. Sign in to the [Azure Portal](https://portal.azure.com) with your work or school account or a Microsoft account. If you don't already have an Azure subscription you can create one (including free trial options) through the portal.
- >[!NOTE]
+ >[!NOTE]
> Upgrade Readiness is included at no additional cost with Windows 10 Professional, Education, and Enterprise editions. An Azure subscription is required for managing and using Upgrade Readiness, but no Azure charges are expected to accrue to the subscription as a result of using Upgrade Readiness.
2. In the Azure portal select **Create a resource**, search for "Upgrade Readiness", and then select **Create** on the **Upgrade Readiness** solution.
diff --git a/windows/deployment/upgrade/upgrade-readiness-requirements.md b/windows/deployment/upgrade/upgrade-readiness-requirements.md
index fb8f886a4e..4dce07d5b1 100644
--- a/windows/deployment/upgrade/upgrade-readiness-requirements.md
+++ b/windows/deployment/upgrade/upgrade-readiness-requirements.md
@@ -28,7 +28,7 @@ The compatibility update that sends diagnostic data from user computers to Micro
If you need to update user computers to Windows 7 SP1 or Windows 8.1, use Windows Update or download and deploy the applicable package from the Microsoft Download Center.
-> [!NOTE]
+> [!NOTE]
> Upgrade Readiness is designed to best support in-place upgrades. In-place upgrades do not support migrations from BIOS to UEFI or from 32-bit to 64-bit architecture. If you need to migrate computers in these scenarios, use the wipe-and-reload method. Upgrade Readiness insights are still valuable in this scenario, however, you can ignore in-place upgrade specific guidance.
See [Windows 10 Specifications](https://www.microsoft.com/en-US/windows/windows-10-specifications) for additional information about computer system requirements.
diff --git a/windows/deployment/volume-activation/install-vamt.md b/windows/deployment/volume-activation/install-vamt.md
index 87422aa8b3..cf26bea3e6 100644
--- a/windows/deployment/volume-activation/install-vamt.md
+++ b/windows/deployment/volume-activation/install-vamt.md
@@ -23,10 +23,10 @@ This topic describes how to install the Volume Activation Management Tool (VAMT)
You install VAMT as part of the Windows Assessment and Deployment Kit (ADK) for Windows 10.
->[!IMPORTANT]
+>[!IMPORTANT]
>VAMT requires local administrator privileges on all managed computers in order to deposit confirmation IDs (CIDs), get the client products’ license status, and install product keys. If VAMT is being used to manage products and product keys on the local host computer and you do not have administrator privileges, start VAMT with elevated privileges. For Active Directory-Based Activation use, for best results we recommend running VAMT while logged on as a domain administrator.
->[!NOTE]
+>[!NOTE]
>The VAMT Microsoft Management Console snap-in ships as an x86 package.
### Requirements
diff --git a/windows/deployment/volume-activation/plan-for-volume-activation-client.md b/windows/deployment/volume-activation/plan-for-volume-activation-client.md
index cc415fc1ac..92c3657316 100644
--- a/windows/deployment/volume-activation/plan-for-volume-activation-client.md
+++ b/windows/deployment/volume-activation/plan-for-volume-activation-client.md
@@ -35,7 +35,7 @@ ms.topic: article
During the activation process, information about the specific installation is examined. In the case of online activations, this information is sent to a server at Microsoft. This information may include the software version, the product key, the IP address of the computer, and information about the device. The activation methods that Microsoft uses are designed to help protect user privacy, and they cannot be used to track back to the computer or user. The gathered data confirms that the software is a legally licensed copy, and this data is used for statistical analysis. Microsoft does not use this information to identify or contact the user or the organization.
->[!NOTE]
+>[!NOTE]
>The IP address is used only to verify the location of the request, because some editions of Windows (such as “Starter” editions) can only be activated within certain geographical target markets.
## Distribution channels and activation
diff --git a/windows/deployment/windows-10-media.md b/windows/deployment/windows-10-media.md
index 532e6e41b1..77df5bd241 100644
--- a/windows/deployment/windows-10-media.md
+++ b/windows/deployment/windows-10-media.md
@@ -39,7 +39,7 @@ Windows 10, version 1709 is available starting on 10/17/2017 in all relevant dis
For ISOs that you download from the VLSC or Visual Studio Subscriptions, you can still search for the individual Windows editions. However, each of these editions (Windows 10 Pro, Windows 10 Enterprise, and Windows 10 Education) will point to the same ISO file, so you only need to download the ISO once. A single Windows image (WIM) file is included in the ISO that contains all the volume licensing images:
-
+
When using the contents of these ISOs with tools such as the Microsoft Deployment Toolkit or System Center Configuration Manager, make sure you select the appropriate image index in any task sequences that you create or update.
@@ -66,7 +66,7 @@ This Semi-Annual Channel release of Windows 10 continues the Windows as a servic
See the following example for Windows 10, version 1709:
-
+
### Features on demand
diff --git a/windows/deployment/windows-autopilot/TOC.md b/windows/deployment/windows-autopilot/TOC.md
index 30a33a05ff..a2ae9455f6 100644
--- a/windows/deployment/windows-autopilot/TOC.md
+++ b/windows/deployment/windows-autopilot/TOC.md
@@ -1,32 +1,28 @@
-# [Windows Autopilot](windows-autopilot.md)
+# [Windows Autopilot deployment](index.md)
+# [What's new](windows-autopilot-whats-new.md)
+# Understanding Windows Autopilot
+## [Overview](windows-autopilot.md)
## [Requirements](windows-autopilot-requirements.md)
-### [Configuration requirements](windows-autopilot-requirements-configuration.md)
-#### [Intune Connector (preview)](intune-connector.md)
-### [Network requirements](windows-autopilot-requirements-network.md)
-### [Licensing requirements](windows-autopilot-requirements-licensing.md)
-## [Scenarios and Capabilities](windows-autopilot-scenarios.md)
-### [Support for existing devices](existing-devices.md)
-### [White glove](white-glove.md)
-### [User-driven mode](user-driven.md)
-#### [Azure Active Directory joined](user-driven-aad.md)
-#### [Hybrid Azure Active Directory joined](user-driven-hybrid.md)
-### [Self-deploying mode](self-deploying.md)
-### [Windows Autopilot Reset](windows-autopilot-reset.md)
-#### [Remote reset](windows-autopilot-reset-remote.md)
-#### [Local reset](windows-autopilot-reset-local.md)
-## [Administering Autopilot](administer.md)
-### [Configuring](configure-autopilot.md)
-#### [Adding devices](add-devices.md)
-#### [Creating profiles](profiles.md)
-#### [Enrollment status page](enrollment-status.md)
-#### [BitLocker encryption](bitlocker.md)
-### [Administering Autopilot via Partner Center](https://docs.microsoft.com/en-us/partner-center/autopilot)
-### [Administering Autopilot via Microsoft Intune](https://docs.microsoft.com/intune/enrollment-autopilot)
-### [Administering Autopilot via Microsoft Store for Business](https://docs.microsoft.com/microsoft-store/add-profile-to-devices#manage-autopilot-deployment-profiles)
-### [Administering Autopilot via Microsoft 365 Business & Office 365 Admin portal](https://support.office.com/article/Create-and-edit-Autopilot-profiles-5cf7139e-cfa1-4765-8aad-001af1c74faa)
-## Getting started
-### [Demonstrate Autopilot deployment on a VM](demonstrate-deployment-on-vm.md)
-## [Customer consent](registration-auth.md)
+## [Scenarios and capabilities](windows-autopilot-scenarios.md)
+## [Get started](demonstrate-deployment-on-vm.md)
+
+# Deployment scenarios
+## [User-driven mode](user-driven.md)
+## [Self-deploying mode](self-deploying.md)
+## [Windows Autopilot Reset](windows-autopilot-reset.md)
+## [White glove](white-glove.md)
+## [Support for existing devices](existing-devices.md)
+
+# Administering Windows Autopilot
+## [Registering devices](add-devices.md)
+## [Configuring device profiles](profiles.md)
+## [Enrollment status page](enrollment-status.md)
+## [BitLocker encryption](bitlocker.md)
## [Troubleshooting](troubleshooting.md)
+## [Known issues](known-issues.md)
+
+# Support
## [FAQ](autopilot-faq.md)
-## [Support](autopilot-support.md)
+## [Contacts](autopilot-support.md)
+## [Registration authorization](registration-auth.md)
+## [Device guidelines](autopilot-device-guidelines.md)
\ No newline at end of file
diff --git a/windows/deployment/windows-autopilot/add-devices.md b/windows/deployment/windows-autopilot/add-devices.md
index 72ca57267c..8024b7af27 100644
--- a/windows/deployment/windows-autopilot/add-devices.md
+++ b/windows/deployment/windows-autopilot/add-devices.md
@@ -89,12 +89,74 @@ The commands can also be run remotely, as long as WMI permissions are in place a
## Registering devices
-Once the hardware IDs have been captured from existing devices, they can be uploaded through a variety of means. See the detailed documentation for each available mechanism:
+
-
- Category
- Maximum deferral
- Deferral increments
- Example
- Classification GUID
-
-
- Feature Updates
- 180 days
- Days
- From Windows 10, version 1511 to version 1607
- 3689BDC8-B205-4AF4-8D4A-A63924C5E9D5
-
-
- Quality Updates
- 30 days
- Days
- Security updates
- 0FA1201D-4330-4FA8-8AE9-B877473B6441
-
-
- Drivers (optional)
- EBFC1FC5-71A4-4F7B-9ACA-3B9A503104A0
-
- Non-security updates
- CD5FFD1E-E932-4E3A-BF74-18BF0B1BBD83
- Microsoft updates (Office, Visual Studio, etc.) varies
-
- Non-deferrable
- No deferral
- No deferral
- Definition updates
- E0789628-CE08-4437-BE74-2495B842F43B
- 
+
+
+Once the hardware IDs have been captured from existing devices, they can be uploaded through a variety of means. See the detailed documentation for each available mechanism.
- [Microsoft Intune](https://docs.microsoft.com/intune/enrollment-autopilot). This is the preferred mechanism for all customers.
-
- [Partner Center](https://msdn.microsoft.com/partner-center/autopilot). This is used by CSP partners to register devices on behalf of customers.
-
- [Microsoft 365 Business & Office 365 Admin](https://support.office.com/article/Create-and-edit-AutoPilot-profiles-5cf7139e-cfa1-4765-8aad-001af1c74faa). This is typically used by small and medium businesses (SMBs) who manage their devices using Microsoft 365 Business.
+- [Microsoft Store for Business](https://docs.microsoft.com/microsoft-store/add-profile-to-devices#manage-autopilot-deployment-profiles). You might already be using MSfB to manage your apps and settings.
+
+A summary of each platform's capabilities is provided below.
+
+
+
+
+>*Microsoft recommended platform to use
+
+## Summary
+
+When deploying new devices using Windows Autopilot, the following steps are required:
+
+1. [Register devices](#registering-devices). Ideally, this step is performed by the OEM, reseller, or distributor from which the devices were purchased, but this can also be done by the organization by collecting the hardware identity and uploading it manually.
+2. [Configure device profiles](profiles.md), specifying how the device should be deployed and what user experience should be presented.
+3. Boot the device. When the device is connected to a network with internet access, it will contact the Windows Autopilot deployment service to see if the device is registered, and if it is, it will download profile settings such as the [Enrollment Status page](enrollment-status.md), which are used to customize the end user experience.
+
+## Other configuration settings
+
+- [Bitlocker encryption settings](bitlocker.md): You can configure the BitLocker encryption settings to be applied before automatic encryption is started.
-- [Microsoft Store for Business](https://docs.microsoft.com/microsoft-store/add-profile-to-devices#manage-autopilot-deployment-profiles).
diff --git a/windows/deployment/windows-autopilot/administer.md b/windows/deployment/windows-autopilot/administer.md
deleted file mode 100644
index 9c7d729b96..0000000000
--- a/windows/deployment/windows-autopilot/administer.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: Administering Autopilot
-ms.reviewer:
-manager: laurawi
-description: A short description of methods for configuring Autopilot
-keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
-ms.prod: w10
-ms.mktglfcycl: deploy
-ms.localizationpriority: low
-ms.sitesec: library
-ms.pagetype: deploy
-author: greg-lindsay
-ms.author: greglin
-ms.collection: M365-modern-desktop
-ms.topic: article
----
-
-
-# Administering Autopilot
-
-**Applies to: Windows 10**
-
-Several platforms are available to register devices with Windows Autopilot. A summary of each platform's capabilities is provided below.
-
-
+
+
+Platform/Portal
+ Register devices?
+ Create/Assign profile
+ Acceptable DeviceID
+
+
+
+OEM Direct API
+YES - 1000 at a time max
+NO
+Tuple or PKID
+
+
+
+Partner Center
+YES - 1000 at a time max
+YES
+Tuple or PKID or 4K HH
+
+
+
+Intune
+YES - 500 at a time max\*
+YES\*
+4K HH
+
+
+
+Microsoft Store for Business
+YES - 1000 at a time max
+YES
+4K HH
+
+
+
+Microsoft Business 365
+YES - 1000 at a time max
+YES
+4K HH
+
-
-
-
->*Microsoft recommended platform to use
diff --git a/windows/deployment/windows-autopilot/autopilot-device-guidelines.md b/windows/deployment/windows-autopilot/autopilot-device-guidelines.md
new file mode 100644
index 0000000000..2997787bd1
--- /dev/null
+++ b/windows/deployment/windows-autopilot/autopilot-device-guidelines.md
@@ -0,0 +1,44 @@
+---
+title: Windows Autopilot device guidelines
+ms.reviewer:
+manager: laurawi
+description: Windows Autopilot deployment
+keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
+ms.prod: w10
+ms.mktglfcycl: deploy
+ms.localizationpriority: medium
+ms.sitesec: library
+ms.pagetype: deploy
+author: greg-lindsay
+ms.author: greglin
+ms.collection: M365-modern-desktop
+ms.topic: article
+---
+
+
+# Windows Autopilot device guidelines
+
+**Applies to**
+
+- Windows 10
+
+## Hardware and firmware best practice guidelines for Windows Autopilot
+
+All devices used with Windows Autopilot should meet the [minimum hardware requirements](https://docs.microsoft.com/windows-hardware/design/minimum/minimum-hardware-requirements-overview) for Windows 10.
+
+The following additional best practices ensure that devices can easily be provisioned by organizations as part of the Windows Autopilot deployment process:
+- Ensure that the TPM 2.0 is enabled and in a good state (not in Reduced Functionality Mode) by default on devices intended for Windows Autopilot self-deploying mode.
+- The OEM provisions unique tuple info (SmbiosSystemManufacturer, SmbiosSystemProductName, SmbiosSystemSerialNumber) or PKID + SmbiosSystemSerialNumber into the [SMBIOS fields](https://docs.microsoft.com/windows-hardware/drivers/bringup/smbios) per Microsoft specification (Manufacturer, Product Name and Serial Number stored in SMBIOS Type 1 04h, Type 1 05h and Type 1 07h).
+- The OEM uploads 4K Hardware Hashes obtained using OA3 Tool RS3+ run in Audit mode on full OS to Microsoft via CBR report prior to shipping devices to an Autopilot customer or channel partner.
+- As a best practice, Microsoft requires that OEM shipping drivers are published to Windows Update within 30 days of the CBR being submitted, and system firmware and driver updates are published to Windows Update within 14 days
+- The OEM ensures that the PKID provisioned in the SMBIOS is passed on to the channel.
+
+## Software best practice guidelines for Windows Autopilot
+
+- The Windows Autopilot device should be preinstalled with only a Windows 10 base image plus drivers and Office 365 Pro Plus Retail (C2R).
+- Unless explicitly requested by the customer, no other preinstalled software should be included.
+ - Per OEM Policy, Windows 10 features, including built-in apps, should not be disabled or removed.
+
+## Related topics
+
+[Windows Autopilot customer consent](registration-auth.md)
-
-
-Platform/Portal
- Register devices?
- Create/Assign profile
- Acceptable DeviceID
-
-
-
-OEM Direct API
-YES - 1000 at a time max
-NO
-Tuple or PKID
-
-
-
-Partner Center
-YES - 1000 at a time max
-YES
-Tuple or PKID or 4K HH
-
-
-
-Intune
-YES - 175 at a time max
-YES
-4K HH
-
-
-
-Microsoft Store for Business
-YES - 1000 at a time max
-YES
-4K HH
-
-
-
-Microsoft Business 365
-YES - 1000 at a time max
-YES
-4K HH
-
diff --git a/windows/deployment/windows-autopilot/bitlocker.md b/windows/deployment/windows-autopilot/bitlocker.md
index bc26574523..a3a91da1f5 100644
--- a/windows/deployment/windows-autopilot/bitlocker.md
+++ b/windows/deployment/windows-autopilot/bitlocker.md
@@ -19,6 +19,10 @@ ms.topic: article
# Setting the BitLocker encryption algorithm for Autopilot devices
+**Applies to**
+
+- Windows 10
+
With Windows Autopilot, you can configure the BitLocker encryption settings to be applied before automatic encryption is started. This ensures that the default encrytion algorithm is not applied automatically when this is not the desired setting. Other BitLocker policies that must be applied prior to encryption can also be delivered before automatic BitLocker encryption begins.
The BitLocker encryption algorithm is used when BitLocker is first enabled, and sets the strength to which full volume encryption should occur. Available encryption algorithms are: AES-CBC 128-bit, AES-CBC 256-bit, XTS-AES 128-bit or XTS-AES 256-bit encryption. The default value is XTS-AES 128-bit encryption. See [BitLocker CSP](https://docs.microsoft.com/en-us/windows/client-management/mdm/bitlocker-csp) for information about the recommended encryption algorithms to use.
diff --git a/windows/deployment/windows-autopilot/configure-autopilot.md b/windows/deployment/windows-autopilot/configure-autopilot.md
deleted file mode 100644
index 733affb834..0000000000
--- a/windows/deployment/windows-autopilot/configure-autopilot.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Configure Autopilot deployment
-ms.reviewer:
-manager: laurawi
-description: How to configure Windows Autopilot deployment
-keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
-ms.prod: w10
-ms.mktglfcycl: deploy
-ms.localizationpriority: medium
-ms.sitesec: library
-ms.pagetype: deploy
-author: greg-lindsay
-ms.author: greglin
-ms.collection: M365-modern-desktop
-ms.topic: article
----
-
-
-# Configure Autopilot deployment
-
-**Applies to**
-
-- Windows 10
-
-
-
-## Configuring Autopilot to deploy new devices
-
-When deploying new devices using Windows Autopilot, the following steps are required:
-
-1. [Register devices](add-devices.md). Ideally, this step would be performed by the OEM, reseller, or distributor from which the devices were purchased, but this can also be done by the organization by collecting the hardware identity and uploading it manually.
-2. [Configure device profiles](profiles.md), specifying how the device should be deployed and what user experience should be presented.
-3. Boot the device. When the device is connected to a network with internet access, it will contact the Windows Autopilot deployment service to see if the device is registered, and if it is, it will download profile settings such as the [Enrollment Status page](enrollment-status.md), which are used to customize the end user experience.
-
-## Other configuration settings
-
-- [Bitlocker encryption settings](bitlocker.md): You can configure the BitLocker encryption settings to be applied before automatic encryption is started.
-- [Cortana voiceover and speech recognition](windows-autopilot-scenarios.md): In Windows 10, version 1903 and later Cortana voiceover and speech recognition during OOBE is DISABLED by default for all Windows 10 Pro, Education and Enterprise SKUs.
-
-## Related topics
-
-[Windows Autopilot scenarios](windows-autopilot-scenarios.md)
diff --git a/windows/deployment/windows-autopilot/demonstrate-deployment-on-vm.md b/windows/deployment/windows-autopilot/demonstrate-deployment-on-vm.md
index f160c51abb..5cd9c37d9a 100644
--- a/windows/deployment/windows-autopilot/demonstrate-deployment-on-vm.md
+++ b/windows/deployment/windows-autopilot/demonstrate-deployment-on-vm.md
@@ -1,5 +1,5 @@
---
-title: Demonstrate Autopilot deployment on a VM
+title: Demonstrate Autopilot deployment
ms.reviewer:
manager: laurawi
description: Step-by-step instructions on how to set-up a Virtual Machine with a Windows Autopilot deployment
@@ -17,13 +17,17 @@ ms.custom: autopilot
---
-# Demonstrate Autopilot deployment on a VM
+# Demonstrate Autopilot deployment
**Applies to**
- Windows 10
-In this topic you'll learn how to set-up a Windows Autopilot deployment for a virtual machine (VM) using Hyper-V. Note: Although there are [multiple platforms](administer.md) available to enable Autopilot, this lab primarily uses Intune.
+To get started with Windows Autopilot, you should try it out with a virtual machine (VM) or you can use a physical device that will be wiped and then have a fresh install of Windows 10.
+
+In this topic you'll learn how to set-up a Windows Autopilot deployment for a VM using Hyper-V. Note: Although there are [multiple platforms](administer.md) available to enable Autopilot, this lab primarily uses Intune.
+
+>Hyper-V and a VM are not required for this lab. You can also use a physical device. However, the instructions assume that you are using a VM. To use a physical device, skip the instructions to install Hyper-V and create a VM. All references to 'device' in the guide refer to the client device, either physical or virtual.
The following video provides an overview of the process:
diff --git a/windows/deployment/windows-autopilot/enrollment-status.md b/windows/deployment/windows-autopilot/enrollment-status.md
index f1a105f176..4d5afba15c 100644
--- a/windows/deployment/windows-autopilot/enrollment-status.md
+++ b/windows/deployment/windows-autopilot/enrollment-status.md
@@ -19,6 +19,10 @@ ms.topic: article
# Windows Autopilot Enrollment Status page
+**Applies to**
+
+- Windows 10
+
The Windows Autopilot Enrollment Status page displaying the status of the complete device configuration process. Incorporating feedback from customers, this provides information to the user to show that the device is being set up and can be configured to prevent access to the desktop until the configuration is complete.
diff --git a/windows/deployment/windows-autopilot/existing-devices.md b/windows/deployment/windows-autopilot/existing-devices.md
index 36282fb100..e07ff8221c 100644
--- a/windows/deployment/windows-autopilot/existing-devices.md
+++ b/windows/deployment/windows-autopilot/existing-devices.md
@@ -1,17 +1,16 @@
---
title: Windows Autopilot for existing devices
-description: Listing of Autopilot scenarios
+description: Windows Autopilot deployment
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
+ms.reviewer: mniehaus
+manager: laurawi
ms.prod: w10
ms.mktglfcycl: deploy
-ms.localizationpriority: low
+ms.localizationpriority: medium
ms.sitesec: library
ms.pagetype: deploy
-author: dulcemontemayor
-ms.author: dolmont
-ms.date: 11/05/2018
-ms.reviewer:
-manager: dansimp
+author: greg-lindsay
+ms.author: greglin
ms.collection: M365-modern-desktop
ms.topic: article
---
@@ -24,6 +23,9 @@ Modern desktop management with Windows Autopilot enables you to easily deploy th
This topic describes how to convert Windows 7 or Windows 8.1 domain-joined computers to Azure Active Directory-joined computers running Windows 10 by using Windows Autopilot.
+>[NOTE!]
+>Windows Autopilot for existing devices only supports user-driven Azure Active Directory profiles. Hybrid AAD joined devices and self-deploying profiles are not supported.
+
## Prerequisites
- System Center Configuration Manager Current Branch (1806) OR System Center Configuration Manager Technical Preview (1808)
diff --git a/windows/deployment/windows-autopilot/images/allow-white-glove-oobe.png b/windows/deployment/windows-autopilot/images/allow-white-glove-oobe.png
index da8a68d535..0f458e9306 100644
Binary files a/windows/deployment/windows-autopilot/images/allow-white-glove-oobe.png and b/windows/deployment/windows-autopilot/images/allow-white-glove-oobe.png differ
diff --git a/windows/deployment/windows-autopilot/index.md b/windows/deployment/windows-autopilot/index.md
new file mode 100644
index 0000000000..9d21ace932
--- /dev/null
+++ b/windows/deployment/windows-autopilot/index.md
@@ -0,0 +1,75 @@
+---
+title: Windows Autopilot deployment
+description: Windows Autopilot deployment
+keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
+ms.reviewer: mniehaus
+manager: laurawi
+ms.prod: w10
+ms.mktglfcycl: deploy
+ms.localizationpriority: medium
+ms.sitesec: library
+ms.pagetype: deploy
+author: greg-lindsay
+ms.author: greglin
+ms.collection: M365-modern-desktop
+ms.topic: article
+---
+
+
+# Windows Autopilot deployment
+
+**Applies to**
+
+- Windows 10
+
+Windows Autopilot is a zero-touch, self-service Windows deployment platform introduced with Windows 10, version 1703. The Windows Autopilot process runs immediately after powering on a new computer for the first time, enabling employees to configure new devices to be business-ready with just a few clicks.
+
+This guide is intended for use by an IT-specialist, system architect, or business decision maker. The guide provides information about how Windows Autopilot deployment works, including detailed requirements, deployment scenarios, and platform capabilities. The document highlights options that are available to you when planning a modern, cloud-joined Windows 10 deployment strategy. Links are provided to detailed step by step configuration procedures.
+
+## In this guide
+
+
+
+
+### Understanding Windows Autopilot
+
+[What's new](windows-autopilot-whats-new.md) Windows Autopilot is always being updated with new features! Check this topic to read about the latests capabilities.
+
+
+
+### Deployment scenarios
+
+[Overview of Windows Autopilot](windows-autopilot.md) A review of Windows Autopilot is provided with a video walkthrough. Benefits and general requirements are discussed.
+ [Requirements](windows-autopilot-requirements.md) Detailed software, network, licensiing, and configuration requirments are provided.
+ [Scenarios and Capabilities](windows-autopilot-scenarios.md) A summary of Windows Autopilot deployment scenarios and capabilities.
+ [Get started](demonstrate-deployment-on-vm.md) Interested in trying out Autopilot? See this step-by-step walkthrough to test Windows Autopilot on a virtual machine or physical device with a free 30-day trial premium Intune account.
+
+
+
+### Using Windows Autopilot
+
+[User-driven mode](user-driven.md) Requirements and validation steps for deploying a new Azure Active Directory (AAD) joined or hybrid AAD-joined Windows 10 device are provided.
+ [Self-deploying mode](self-deploying.md) Requirements and validation steps for deploying a new Windows 10 device device with little to no user interaction are provided.
+ [Windows Autopilot Reset](windows-autopilot-reset.md) Using Windows Autopilot Reset, a device can be restored to its original settings, taking it back to a business-ready state. Both local and remote reset scenarios are discussed.
+ [Windows Autopilot for white glove deployment](white-glove.md) Requirements and procedures are described that enable additional policies and apps to be delivered to a Windows Autopilot device.
+ [Support for existing devices](existing-devices.md) This topic describes how Windows Autopilot can be used to convert Windows 7 or Windows 8.1 domain-joined computers to AAD-joined computers running Windows 10.
+
+
+
+### Support topics
+
+[Registering devices](add-devices.md) The process of registering a device with the Windows Autopilot deployment service is described.
+ [Configuring device profiles](profiles.md) The device profile settings that specifie its behavior when it is deployed are described.
+ [Enrollment status page](enrollment-status.md) Settings that are available on the Enrollment Status Page are described.
+ [Bitlocker encryptions](bitlocker.md) Available options for configuring BitLocker on Windows Autopilot devices are described.
+ [Troubleshooting Windows Autopilot](troubleshooting.md) Diagnotic event information and troubleshooting procedures are provided.
+ [Known issues](known-issues.md) A list of current known issues and solutions is provided.
+
+
+
+## Related topics
+
+[Windows Autopilot](https://www.microsoft.com/windowsforbusiness/windows-autopilot)
\ No newline at end of file
diff --git a/windows/deployment/windows-autopilot/intune-connector.md b/windows/deployment/windows-autopilot/intune-connector.md
deleted file mode 100644
index 8e79467853..0000000000
--- a/windows/deployment/windows-autopilot/intune-connector.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: Intune Connector (preview) requirements
-description: Intune Connector (preview) issue workaround
-keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
-ms.prod: w10
-ms.mktglfcycl: deploy
-ms.localizationpriority: low
-ms.sitesec: library
-ms.pagetype: deploy
-author: dulcemontemayor
-ms.author: dolmont
-ms.date: 11/26/2018
-ms.reviewer:
-manager: dansimp
-ms.collection: M365-modern-desktop
-ms.topic: article
----
-
-
-# Intune Connector (preview) language requirements
-
-**Applies to: Windows 10**
-
-Microsoft has released a [preview for Intune connector for Active Directory](https://docs.microsoft.com/intune/windows-autopilot-hybrid) that enables user-driven [Hybrid Azure Active Directory join](user-driven-hybrid.md) for Windows Autopilot.
-
-In this preview version of the Intune Connector, you might receive an error message indicating a setup failure with the following error code and message:
-
-**0x80070658 - Error applying transforms. Verify that the specified transform paths are valid.**
-
-An [example](#example) of the error message is displayed at the bottom of this topic.
-
-This error can be resolved by ensuring that the member server where Intune Connector is running has one of the following language packs installed and configured to be the default keyboard layout:
-
-| | | | | | | | | | | |
-| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
-| en-US | cs-CZ | da-DK | de-DE | el-GR | es-ES | fi-FI | fr-FR | hu-HU | it-IT | ja-JP |
-| ko-KR | nb-NO | nl-NL | pl-PL | pt-BR | ro-RO | ru-RU | sv-SE | tr-TR | zh-CN | zh-TW |
-
->[!NOTE]
->After installing the Intune Connector, you can restore the keyboard layout to its previous settings.[FAQ](autopilot-faq.md) Frequently asked questions on several topics are provided.
+ [Support contacts](autopilot-support.md) Support information is provided.
+ [Registration authorization](registration-auth.md) This article discusses how a CSP partner or OEM can obtain customer authorization to register Windows Autopilot devices.
+
->This solution is a workaround and will be fully resolved in a future release of the Intune Connector.
-
-To change the default keyboard layout:
-
-1. Click **Settings > Time & language > Region and language**
-2. Select one of the languages listed above and choose **Set as default**.
-
-If the language you need isn't listed, you can add additional languages by selecting **Add a language**.
-
-## Example
-
-The following is an example of the error message that can be displayed if one of the listed languages is not used during setup:
-
-
-
-
diff --git a/windows/deployment/windows-autopilot/known-issues.md b/windows/deployment/windows-autopilot/known-issues.md
new file mode 100644
index 0000000000..6a8bb7cc68
--- /dev/null
+++ b/windows/deployment/windows-autopilot/known-issues.md
@@ -0,0 +1,36 @@
+---
+title: Windows Autopilot known issues
+ms.reviewer:
+manager: laurawi
+description: Windows Autopilot deployment
+keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
+ms.prod: w10
+ms.mktglfcycl: deploy
+ms.localizationpriority: medium
+ms.sitesec: library
+ms.pagetype: deploy
+author: greg-lindsay
+ms.author: greglin
+ms.collection: M365-modern-desktop
+ms.topic: article
+---
+
+
+# Windows Autopilot - known issues
+
+**Applies to**
+
+- Windows 10
+
+
+
+
+
+## Related topics
+
+[Troubleshooting Windows Autopilot](troubleshooting.md)
\ No newline at end of file
diff --git a/windows/deployment/windows-autopilot/profiles.md b/windows/deployment/windows-autopilot/profiles.md
index 3da30456b0..996999fc4f 100644
--- a/windows/deployment/windows-autopilot/profiles.md
+++ b/windows/deployment/windows-autopilot/profiles.md
@@ -1,16 +1,16 @@
---
title: Configure Autopilot profiles
-ms.reviewer:
-manager: dansimp
-description: How to configure Windows Autopilot deployment
+description: Windows Autopilot deployment
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
+ms.reviewer: mniehaus
+manager: laurawi
ms.prod: w10
ms.mktglfcycl: deploy
ms.localizationpriority: medium
ms.sitesec: library
ms.pagetype: deploy
-author: dulcemontemayor
-ms.author: dolmont
+author: greg-lindsay
+ms.author: greglin
ms.collection: M365-modern-desktop
ms.topic: article
---
@@ -24,24 +24,6 @@ ms.topic: article
For each device that has been defined to the Windows Autopilot deployment service, a profile of settings needs to be applied that specifies the exact behavior of that device when it is deployed. For detailed procedures on how to configure profile settings and register devices, see [Registering devices](add-devices.md#registering-devices).
-## Profile download
-
-When an Internet-connected Windows 10 device boots up, it will attempt to connect to the Autopilot service and download an Autopilot profile. Note: It is important that a profile exists at this stage so that a blank profile is not cached locally on the PC. To remove the currently cached local profile in Windows 10 version 1803 and earlier, it is necessary to re-generalize the OS using **sysprep /generalize /oobe**, reinstall the OS, or re-image the PC. In Windows 10 version 1809 and later, you can retrieve a new profile by rebooting the PC.
-
-When a profile is downloaded depends on the version of Windows 10 that is running on the PC. See the following table.
-
-| Windows 10 version | Profile download behavior |
-| --- | --- |
-| 1703 and 1709 | The profile is downloaded after the OOBE network connection page. This page is not displayed when using a wired connection. In this case, the profile is downloaded just prior to the EULA screen. |
-| 1803 | The profile is downloaded as soon as possible. If wired, it is downloaded at the start of OOBE. If wireless, it is downloaded after the network connection page. |
-| 1809 | The profile is downloaded as soon as possible (same as 1803), and again after each reboot. |
-
-If you need to reboot a computer during OOBE:
-- Press Shift-F10 to open a command prompt.
-- Enter **shutdown /r /t 0** to restart immediately, or **shutdown /s /t 0** to shutdown immediately.
-
-For more information, see [Windows Setup Command-Line Options](https://docs.microsoft.com/windows-hardware/manufacture/desktop/windows-setup-command-line-options).
-
## Profile settings
The following profile settings are available:
@@ -62,4 +44,5 @@ The following profile settings are available:
## Related topics
-[Configure Autopilot deployment](configure-autopilot.md)
+[Profile download](troubleshooting.md#profile-download)
+[Registering devices](add-devices.md)
diff --git a/windows/deployment/windows-autopilot/registration-auth.md b/windows/deployment/windows-autopilot/registration-auth.md
index 346753c0e8..413adf3a32 100644
--- a/windows/deployment/windows-autopilot/registration-auth.md
+++ b/windows/deployment/windows-autopilot/registration-auth.md
@@ -1,16 +1,16 @@
---
title: Windows Autopilot customer consent
-ms.reviewer:
-manager: dansimp
-description: Support information for Windows Autopilot
-keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune, csp, OEM
+description: Windows Autopilot deployment
+keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
+ms.reviewer: mniehaus
+manager: laurawi
ms.prod: w10
ms.mktglfcycl: deploy
-ms.localizationpriority: low
+ms.localizationpriority: medium
ms.sitesec: library
ms.pagetype: deploy
-author: dulcemontemayor
-ms.author: dolmont
+author: greg-lindsay
+ms.author: greglin
ms.collection: M365-modern-desktop
ms.topic: article
---
diff --git a/windows/deployment/windows-autopilot/self-deploying.md b/windows/deployment/windows-autopilot/self-deploying.md
index 0bd771029c..e2fb1ecaa1 100644
--- a/windows/deployment/windows-autopilot/self-deploying.md
+++ b/windows/deployment/windows-autopilot/self-deploying.md
@@ -1,23 +1,22 @@
---
title: Windows Autopilot Self-Deploying mode (Preview)
-ms.reviewer:
-manager: dansimp
-description: Gives an overview of Autopilot Plug and Forget and how to use it.
-keywords: Autopilot Plug and Forget, Windows 10
+description: Windows Autopilot deployment
+keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
+ms.reviewer: mniehaus
+manager: laurawi
ms.prod: w10
-ms.technology: Windows
ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.pagetype:
ms.localizationpriority: medium
-author: dulcemontemayor
-ms.author: dolmont
+ms.sitesec: library
+ms.pagetype: deploy
+author: greg-lindsay
+ms.author: greglin
ms.collection: M365-modern-desktop
ms.topic: article
---
-# Windows Autopilot Self-Deploying mode (Preview)
+# Windows Autopilot Self-Deploying mode
**Applies to: Windows 10, version 1809 or later**
diff --git a/windows/deployment/windows-autopilot/troubleshooting.md b/windows/deployment/windows-autopilot/troubleshooting.md
index c3c2e4cfa9..52b66ab257 100644
--- a/windows/deployment/windows-autopilot/troubleshooting.md
+++ b/windows/deployment/windows-autopilot/troubleshooting.md
@@ -1,16 +1,16 @@
---
title: Troubleshooting Windows Autopilot
-ms.reviewer:
-manager: dansimp
-description: This topic goes over Windows Autopilot and how it helps setup OOBE Windows 10 devices.
+description: Windows Autopilot deployment
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
+ms.reviewer: mniehaus
+manager: laurawi
ms.prod: w10
ms.mktglfcycl: deploy
ms.localizationpriority: medium
ms.sitesec: library
ms.pagetype: deploy
-author: dulcemontemayor
-ms.author: dolmont
+author: greg-lindsay
+ms.author: greglin
ms.collection: M365-modern-desktop
ms.topic: article
---
@@ -22,7 +22,7 @@ ms.topic: article
Windows Autopilot is designed to simplify all parts of the Windows device lifecycle, but there are always situations where issues may arise, either due to configuration or other issues. To assist with troubleshooting efforts, review the following information.
-## Windows Autopilot deployment
+## Troubleshooting process
Regardless of whether performing user-driven or self-deploying device deployments, the troubleshooting process is the mostly the same. It is useful to understand the flow for a specific device:
@@ -35,17 +35,17 @@ Regardless of whether performing user-driven or self-deploying device deployment
For troubleshooting, key activities to perform are:
-- Configuration. Has Azure Active Directory and Microsoft Intune (or an equivalent MDM service) been configured as specified in [Windows Autopilot configuration requirements](windows-autopilot-requirements-configuration.md)?
-- Network connectivity. Can the device access the services described in [Windows Autopilot networking requirements](windows-autopilot-requirements-network.md)?
+- Configuration. Has Azure Active Directory and Microsoft Intune (or an equivalent MDM service) been configured as specified in [Windows Autopilot configuration requirements](windows-autopilot-requirements.md)?
+- Network connectivity. Can the device access the services described in [Windows Autopilot networking requirements](windows-autopilot-requirements.md)?
- Autopilot OOBE behavior. Were only the expected out-of-box experience screens displayed? Was the Azure AD credentials page customized with organization-specific details as expected?
- Azure AD join issues. Was the device able to join Azure Active Directory?
- MDM enrollment issues. Was the device able to enroll in Microsoft Intune (or an equivalent MDM service)?
-### Troubleshooting Autopilot OOBE issues
+## Troubleshooting Autopilot OOBE issues
If the expected Autopilot behavior does not occur during the out-of-box experience (OOBE), it is useful to see whether the device received an Autopilot profile and what settings that profile contained. Depending on the Windows 10 release, there are different mechanisms available to do that.
-#### Windows 10 version 1803 and above
+### Windows 10 version 1803 and above
To see details related to the Autopilot profile settings and OOBE flow, Windows 10 version 1803 and above adds event log entries. These can be viewed using Event Viewer, navigating to the log at **Application and Services Logs –> Microsoft –> Windows –> Provisioning-Diagnostics-Provider –> AutoPilot**. The following events may be recorded, depending on the scenario and profile configuration.
@@ -66,7 +66,7 @@ To see details related to the Autopilot profile settings and OOBE flow, Windows
In addition to the event log entries, the registry and ETW trace options described below also work with Windows 10 version 1803 and above.
-#### Windows 10 version 1709 and above
+### Windows 10 version 1709 and above
On Windows 10 version 1709 and above, information about the Autopilot profile settings are stored in the registry on the device after they are received from the Autopilot deployment service. These can be found at **HKLM\SOFTWARE\Microsoft\Provisioning\Diagnostics\AutoPilot**. Available registry entries include:
@@ -79,20 +79,38 @@ On Windows 10 version 1709 and above, information about the Autopilot profile se
| TenantMatched | This will be set to 1 if the tenant ID of the user matches the tenant ID that the device was registered with. If this is 0, the user would be shown an error and forced to start over. |
| CloudAssignedOobeConfig | This is a bitmap that shows which Autopilot settings were configured. Values include: SkipCortanaOptIn = 1, OobeUserNotLocalAdmin = 2, SkipExpressSettings = 4, SkipOemRegistration = 8, SkipEula = 16 |
-#### Windows 10 version 1703 and above
+### Windows 10 version 1703 and above
On Windows 10 version 1703 and above, ETW tracing can be used to capture detailed information from Autopilot and related components. The resulting ETW trace files can then be viewed using the Windows Performance Analyzer or similar tools. See [the advanced troubleshooting blog](https://blogs.technet.microsoft.com/mniehaus/2017/12/13/troubleshooting-windows-autopilot-level-300400/) for more information.
-### Troubleshooting Azure AD Join issues
+## Troubleshooting Azure AD Join issues
-The most common issue joining a device to Azure AD is related to Azure AD permissions. Ensure [the correct configuration is in place](windows-autopilot-requirements-configuration.md) to allow users to join devices to Azure AD. Errors can also happen if the user has exceeded the number of devices that they are allowed to join, as configured in Azure AD.
+The most common issue joining a device to Azure AD is related to Azure AD permissions. Ensure [the correct configuration is in place](windows-autopilot-requirements.md) to allow users to join devices to Azure AD. Errors can also happen if the user has exceeded the number of devices that they are allowed to join, as configured in Azure AD.
Error code 801C0003 will typically be reported on an error page titled "Something went wrong". This error means that the Azure AD join failed.
-### Troubleshooting Intune enrollment issues
+## Troubleshooting Intune enrollment issues
See [this knowledge base article](https://support.microsoft.com/help/4089533/troubleshooting-windows-device-enrollment-problems-in-microsoft-intune) for assistance with Intune enrollment issues. Common issues include incorrect or missing licenses assigned to the user or too many devices enrolled for the user.
Error code 80180018 will typically be reported on an error page titled "Something went wrong". This error means that the MDM enrollment failed.
If Autopilot Reset fails immediately with an error "Ran into trouble. Please sign in with an administrator account to see why and reset manually," see [Troubleshoot Autopilot Reset](https://docs.microsoft.com/education/windows/autopilot-reset#troubleshoot-autopilot-reset) for more help.
+
+## Profile download
+
+When an Internet-connected Windows 10 device boots up, it will attempt to connect to the Autopilot service and download an Autopilot profile. Note: It is important that a profile exists at this stage so that a blank profile is not cached locally on the PC. To remove the currently cached local profile in Windows 10 version 1803 and earlier, it is necessary to re-generalize the OS using **sysprep /generalize /oobe**, reinstall the OS, or re-image the PC. In Windows 10 version 1809 and later, you can retrieve a new profile by rebooting the PC.
+
+When a profile is downloaded depends on the version of Windows 10 that is running on the PC. See the following table.
+
+| Windows 10 version | Profile download behavior |
+| --- | --- |
+| 1703 and 1709 | The profile is downloaded after the OOBE network connection page. This page is not displayed when using a wired connection. In this case, the profile is downloaded just prior to the EULA screen. |
+| 1803 | The profile is downloaded as soon as possible. If wired, it is downloaded at the start of OOBE. If wireless, it is downloaded after the network connection page. |
+| 1809 | The profile is downloaded as soon as possible (same as 1803), and again after each reboot. |
+
+If you need to reboot a computer during OOBE:
+- Press Shift-F10 to open a command prompt.
+- Enter **shutdown /r /t 0** to restart immediately, or **shutdown /s /t 0** to shutdown immediately.
+
+For more information, see [Windows Setup Command-Line Options](https://docs.microsoft.com/windows-hardware/manufacture/desktop/windows-setup-command-line-options).
\ No newline at end of file
diff --git a/windows/deployment/windows-autopilot/user-driven-aad.md b/windows/deployment/windows-autopilot/user-driven-aad.md
deleted file mode 100644
index 3bea377212..0000000000
--- a/windows/deployment/windows-autopilot/user-driven-aad.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: User-driven mode for AAD
-ms.reviewer:
-manager: dansimp
-description: Listing of Autopilot scenarios
-keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
-ms.prod: w10
-ms.mktglfcycl: deploy
-ms.localizationpriority: low
-ms.sitesec: library
-ms.pagetype: deploy
-author: dulcemontemayor
-ms.author: dolmont
-ms.collection: M365-modern-desktop
-ms.topic: article
----
-
-
-# Windows Autopilot user-driven mode for Azure Active Directory join
-
-**Applies to: Windows 10**
-
-## Procedures
-
-In order to perform a user-driven deployment using Windows Autopilot, the following preparation steps need to be completed:
-
-- Ensure that the users who will be performing user-driven mode deployments are able to join devices to Azure Active Directory. See [Configure device settings](https://docs.microsoft.com/azure/active-directory/device-management-azure-portal#configure-device-settings) in the Azure Active Directory documentation for more information.
-- Create an Autopilot profile for user-driven mode with the desired settings. In Microsoft Intune, this mode is explicitly chosen when creating the profile. With Microsoft Store for Business and Partner Center, user-driven mode is the default and does not need to be selected.
-- If using Intune, create a device group in Azure Active Directory and assign the Autopilot profile to that group.
-
-For each device that will be deployed using user-driven deployment, these additional steps are needed:
-
-- Ensure that the device has been added to Windows Autopilot. This can be done automatically by an OEM or partner at the time the device is purchased, or it can be done through a manual harvesting process later. See [Adding devices to Windows Autopilot](add-devices.md) for more information.
-- Ensure an Autopilot profile has been assigned to the device:
- - If using Intune and Azure Active Directory dynamic device groups, this can be done automatically.
- - If using Intune and Azure Active Directory static device groups, manually add the device to the device group.
- - If using other methods (e.g. Microsoft Store for Business or Partner Center), manually assign an Autopilot profile to the device.
-
-Also see the **Validation** section in the [Windows Autopilot user-driven mode](user-driven.md) topic.
diff --git a/windows/deployment/windows-autopilot/user-driven-hybrid.md b/windows/deployment/windows-autopilot/user-driven-hybrid.md
deleted file mode 100644
index 462d9ae726..0000000000
--- a/windows/deployment/windows-autopilot/user-driven-hybrid.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Hybrid AAD Join
-ms.reviewer:
-manager: dansimp
-description: Listing of Autopilot scenarios
-keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
-ms.prod: w10
-ms.mktglfcycl: deploy
-ms.localizationpriority: low
-ms.sitesec: library
-ms.pagetype: deploy
-author: dulcemontemayor
-ms.author: dolmont
-ms.collection: M365-modern-desktop
-ms.topic: article
----
-
-
-
-# Windows Autopilot user-driven mode for hybrid Azure Active Directory join
-
-**Applies to: Windows 10**
-
-Windows Autopilot requires that devices be Azure Active Directory joined. If you have an on-premises Active Directory environment and want to also join devices to your on-premises domain, you can accomplish this by configuring Autopilot devices to be [hybrid Azure Active Directory (AAD) joined](https://docs.microsoft.com/azure/active-directory/devices/hybrid-azuread-join-plan).
-
-## Requirements
-
-To perform a user-driven hybrid AAD joined deployment using Windows Autopilot:
-
-- A Windows Autopilot profile for user-driven mode must be created and
- - **Hybrid Azure AD joined** must be specified as the selected option under **Join to Azure AD as** in the Autopilot profile.
-- If using Intune, a device group in Azure Active Directory must exist with the Windows Autopilot profile assigned to that group.
-- The device must be running Windows 10, version 1809 or later.
-- The device must be able to access an Active Directory domain controller, so it must be connected to the organization's network (where it can resolve the DNS records for the AD domain and the AD domain controller, and communicate with the domain controller to authenticate the user).
-- The device must be able to access the Internet, following the [documented Windows Autopilot network requirements](windows-autopilot-requirements-network.md).
-- The Intune Connector for Active Directory must be installed.
- - Note: The Intune Connector will perform an on-prem AD join, therefore users do not need on-prem AD-join permission, assuming the Connector is [configured to perform this action](https://docs.microsoft.com/intune/windows-autopilot-hybrid#increase-the-computer-account-limit-in-the-organizational-unit) on the user's behalf.
-- If using Proxy, WPAD Proxy settings option must be enabled and configured.
-
-**AAD device join**: The hybrid AAD join process uses the system context to perform device AAD join, therefore it is not affected by user based AAD join permission settings. In addition, all users are enabled to join devices to AAD by default.
-
-## Step by step instructions
-
-See [Deploy hybrid Azure AD joined devices using Intune and Windows Autopilot](https://docs.microsoft.com/intune/windows-autopilot-hybrid).
-
-Also see the **Validation** section in the [Windows Autopilot user-driven mode](user-driven.md) topic.
diff --git a/windows/deployment/windows-autopilot/user-driven.md b/windows/deployment/windows-autopilot/user-driven.md
index dee1841a13..0b60714d75 100644
--- a/windows/deployment/windows-autopilot/user-driven.md
+++ b/windows/deployment/windows-autopilot/user-driven.md
@@ -1,17 +1,16 @@
---
title: Windows Autopilot User-Driven Mode
-description: Canonical Autopilot scenario
+description: Windows Autopilot deployment
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
+ms.reviewer: mniehaus
+manager: laurawi
ms.prod: w10
ms.mktglfcycl: deploy
ms.localizationpriority: medium
ms.sitesec: library
ms.pagetype: deploy
-author: dulcemontemayor
-ms.date: 11/07/2018
-ms.reviewer:
-manager: dansimp
-ms.author: dolmont
+author: greg-lindsay
+ms.author: greglin
ms.collection: M365-modern-desktop
ms.topic: article
---
@@ -34,8 +33,52 @@ Today, Windows Autopilot user-driven mode supports joining devices to Azure Acti
The following options are available for user-driven deployment:
-- [Azure Active Directory join](user-driven-aad.md) is available if devices do not need to be joined to an on-prem Active Directory domain.
-- [Hybrid Azure Active Directory join](user-driven-hybrid.md) is available for devices that must be joined to both Azure Active Directory and your on-prem Active Directory domain.
+- [Azure Active Directory join](#user-driven-mode-for-azure-active-directory-join) is available if devices do not need to be joined to an on-prem Active Directory domain.
+- [Hybrid Azure Active Directory join](#user-driven-mode-for-hybrid-azure-active-directory-join) is available for devices that must be joined to both Azure Active Directory and your on-prem Active Directory domain.
+
+### User-driven mode for Azure Active Directory join
+
+In order to perform a user-driven deployment using Windows Autopilot, the following preparation steps need to be completed:
+
+- Ensure that the users who will be performing user-driven mode deployments are able to join devices to Azure Active Directory. See [Configure device settings](https://docs.microsoft.com/azure/active-directory/device-management-azure-portal#configure-device-settings) in the Azure Active Directory documentation for more information.
+- Create an Autopilot profile for user-driven mode with the desired settings. In Microsoft Intune, this mode is explicitly chosen when creating the profile. With Microsoft Store for Business and Partner Center, user-driven mode is the default and does not need to be selected.
+- If using Intune, create a device group in Azure Active Directory and assign the Autopilot profile to that group.
+
+For each device that will be deployed using user-driven deployment, these additional steps are needed:
+
+- Ensure that the device has been added to Windows Autopilot. This can be done automatically by an OEM or partner at the time the device is purchased, or it can be done through a manual harvesting process later. See [Adding devices to Windows Autopilot](add-devices.md) for more information.
+- Ensure an Autopilot profile has been assigned to the device:
+ - If using Intune and Azure Active Directory dynamic device groups, this can be done automatically.
+ - If using Intune and Azure Active Directory static device groups, manually add the device to the device group.
+ - If using other methods (e.g. Microsoft Store for Business or Partner Center), manually assign an Autopilot profile to the device.
+
+Also see the [Validation](#validation) section below.
+
+### User-driven mode for hybrid Azure Active Directory join
+
+Windows Autopilot requires that devices be Azure Active Directory joined. If you have an on-premises Active Directory environment and want to also join devices to your on-premises domain, you can accomplish this by configuring Autopilot devices to be [hybrid Azure Active Directory (AAD) joined](https://docs.microsoft.com/azure/active-directory/devices/hybrid-azuread-join-plan).
+
+#### Requirements
+
+To perform a user-driven hybrid AAD joined deployment using Windows Autopilot:
+
+- A Windows Autopilot profile for user-driven mode must be created and
+ - **Hybrid Azure AD joined** must be specified as the selected option under **Join to Azure AD as** in the Autopilot profile.
+- If using Intune, a device group in Azure Active Directory must exist with the Windows Autopilot profile assigned to that group.
+- The device must be running Windows 10, version 1809 or later.
+- The device must be able to access an Active Directory domain controller, so it must be connected to the organization's network (where it can resolve the DNS records for the AD domain and the AD domain controller, and communicate with the domain controller to authenticate the user).
+- The device must be able to access the Internet, following the [documented Windows Autopilot network requirements](windows-autopilot-requirements.md).
+- The Intune Connector for Active Directory must be installed.
+ - Note: The Intune Connector will perform an on-prem AD join, therefore users do not need on-prem AD-join permission, assuming the Connector is [configured to perform this action](https://docs.microsoft.com/intune/windows-autopilot-hybrid#increase-the-computer-account-limit-in-the-organizational-unit) on the user's behalf.
+- If using Proxy, WPAD Proxy settings option must be enabled and configured.
+
+**AAD device join**: The hybrid AAD join process uses the system context to perform device AAD join, therefore it is not affected by user based AAD join permission settings. In addition, all users are enabled to join devices to AAD by default.
+
+#### Step by step instructions
+
+See [Deploy hybrid Azure AD joined devices using Intune and Windows Autopilot](https://docs.microsoft.com/intune/windows-autopilot-hybrid).
+
+Also see the **Validation** section in the [Windows Autopilot user-driven mode](user-driven.md) topic.
## Validation
diff --git a/windows/deployment/windows-autopilot/white-glove.md b/windows/deployment/windows-autopilot/white-glove.md
index 9f6fa6b55a..d0a2891d0c 100644
--- a/windows/deployment/windows-autopilot/white-glove.md
+++ b/windows/deployment/windows-autopilot/white-glove.md
@@ -15,7 +15,7 @@ ms.topic: article
# Windows Autopilot for white glove deployment
-**Applies to: Windows 10, version 1903** (preview)
+**Applies to: Windows 10, version 1903**
Windows Autopilot enables organizations to easily provision new devices - leveraging the preinstalled OEM image and drivers with a simple process that can be performed by the end user to help get their device business-ready.
@@ -23,7 +23,7 @@ Windows Autopilot enables organizations to easily provision new devices - levera
Windows Autopilot can also provide a white glove service that enables partners or IT staff to pre-provision a Windows 10 PC so that it is fully configured and business-ready. From the end user’s perspective, the Windows Autopilot user-driven experience is unchanged, but getting their device to a fully provisioned state is faster.
-With **Windows Autopilot for white glove deployment**, the provisioning process is split. The time-consuming portions are performed by IT, partners, or OEMs. The end user simply completes a few neceesary settings and polices and then they can begin using their device.
+With **Windows Autopilot for white glove deployment**, the provisioning process is split. The time-consuming portions are performed by IT, partners, or OEMs. The end user simply completes a few necessary settings and polices and then they can begin using their device.
@@ -40,6 +40,8 @@ In addition to [Windows Autopilot requirements](windows-autopilot-requirements.m
## Preparation
+Devices slated for WG provisioning are registered for Autopilot via the normal registration process.
+
To be ready to try out Windows Autopilot for white glove deployment, ensure that you can first successfully use existing Windows Autopilot user-driven scenarios:
- User-driven Azure AD join. Devices can be deployed using Windows Autopilot and joined to an Azure Active Directory tenant.
@@ -47,7 +49,7 @@ To be ready to try out Windows Autopilot for white glove deployment, ensure that
If these scenarios cannot be completed, Windows Autopilot for white glove deployment will also not succeed since it builds on top of these scenarios.
-To enable white glove deployment, an additional Autopilot profile setting must be configured:
+To enable white glove deployment, an additional Autopilot profile setting must be configured by the customer or IT Admin via their Intune account, prior to beginning the white glove process in the provisioning service facility:
@@ -65,8 +67,7 @@ Each of these scenarios consists of two parts, a technician flow and a user flow
### Technican flow
-The first part of the Windows Autopilot for white glove deployment process is designed to be carried out by a technician; this could be a member of the IT staff, a services partner, or an OEM – each organization can decide who should perform these activities.
-Regardless of the scenario, the process to be performed by the technician is the same:
+After the customer or IT Admin has targeted all the apps and settings they want for their devices through Intune, the white glove technician can begin the white glove process. The technician could be a member of the IT staff, a services partner, or an OEM – each organization can decide who should perform these activities. Regardless of the scenario, the process to be performed by the technician is the same:
- Boot the device (running Windows 10 Pro, Enterprise, or Education SKUs, version 1903 or later).
- From the first OOBE screen (which could be a language selection or locale selection screen), do not click **Next**. Instead, press the Windows key five times to view an additional options dialog. From that screen, choose the **Windows Autopilot provisioning** option and then click **Continue**.
@@ -77,6 +78,7 @@ Regardless of the scenario, the process to be performed by the technician is the
- The organization name for the device.
- The user assigned to the device (if there is one).
- A QR code containing a unique identifier for the device, useful to look up the device in Intune to make any configuration changes needed (e.g. assigning a user, adding the device to any additional groups needed for app or policy targeting).
+ - **Note**: The QR codes can be scanned using a companion app, which will also configure the device to specify who it belongs to. An [open-source sample of the companion app](https://github.com/Microsoft/WindowsAutopilotCompanion) that integrates with Intune via the Graph API has been published to GitHub by the Autopilot team.
- Validate the information displayed. If any changes are needed, make these and then click **Refresh** to re-download the updated Autopilot profile details.
@@ -103,3 +105,6 @@ If the pre-provisioning process completed successfully and the device was reseal
- If using Hybrid Azure AD Join, the device will reboot; after the reboot, enter the user’s Active Directory credentials.
- Additional policies and apps will be delivered to the device, as tracked by the Enrollment Status Page (ESP). Once complete, the user will be able to access the desktop.
+## Related topics
+
+[White glove video](https://youtu.be/nE5XSOBV0rI)
\ No newline at end of file
diff --git a/windows/deployment/windows-autopilot/windows-autopilot-requirements-configuration.md b/windows/deployment/windows-autopilot/windows-autopilot-requirements-configuration.md
deleted file mode 100644
index 2255eedafe..0000000000
--- a/windows/deployment/windows-autopilot/windows-autopilot-requirements-configuration.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-title: Windows Autopilot configuration requirements
-ms.reviewer:
-manager: dansimp
-description: This topic goes over Windows Autopilot and how it helps setup OOBE Windows 10 devices.
-keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
-ms.prod: w10
-ms.mktglfcycl: deploy
-ms.localizationpriority: medium
-ms.sitesec: library
-ms.pagetype: deploy
-author: dulcemontemayor
-ms.author: dolmont
-ms.collection: M365-modern-desktop
-ms.topic: article
----
-
-
-# Windows Autopilot configuration requirements
-
-**Applies to: Windows 10**
-
-Before Windows Autopilot can be used, some configuration tasks are required to support the common Autopilot scenarios.
-
-- Configure Azure Active Directory automatic enrollment. For Microsoft Intune, see [Enable Windows 10 automatic enrollment](https://docs.microsoft.com/intune/windows-enroll#enable-windows-10-automatic-enrollment) for details. If using a different MDM service, contact the vendor for the specific URLs or configuration needed for those services.
-- Configure Azure Active Directory custom branding. In order to display an organization-specific logon page during the Autopilot process, Azure Active Directory needs to be configured with the images and text that should be displayed. See [Quickstart: Add company branding to your sign-in page in Azure AD](https://docs.microsoft.com/azure/active-directory/fundamentals/customize-branding) for more details. Note that the "square logo" and "sign-in page text" are the key elements for Autopilot, as well as the Azure Active Directory tenant name (configured separately in the Azure AD tenant properties).
-- Enable [Windows Subscription Activation](https://docs.microsoft.com/windows/deployment/windows-10-enterprise-subscription-activation) if desired, in order to automatically step up from Windows 10 Pro to Windows 10 Enterprise.
-
-Specific scenarios will then have additional requirements. Generally, there are two specific tasks:
-
-- Device registration. Devices need to be added to Windows Autopilot to support most Windows Autopilot scenarios. See [Adding devices to Windows Autopilot](add-devices.md) for more details.
-- Profile configuration. Once devices have been added to Windows Autopilot, a profile of settings needs to be applied to each device. See [Configure Autopilot profiles](profiles.md) for details. Note that Microsoft Intune can automate this profile assignment; see [Create an AutoPilot device group](https://docs.microsoft.com/intune/enrollment-autopilot#create-an-autopilot-device-group) and [Assign an AutoPilot deployment profile to a device group](https://docs.microsoft.com/intune/enrollment-autopilot#assign-an-autopilot-deployment-profile-to-a-device-group) for more information.
-
-See [Windows Autopilot Scenarios](windows-autopilot-scenarios.md) for additional details.
-
-For a walkthrough for some of these and related steps, see this video:
-
-
diff --git a/windows/deployment/windows-autopilot/windows-autopilot-requirements-licensing.md b/windows/deployment/windows-autopilot/windows-autopilot-requirements-licensing.md
deleted file mode 100644
index 18574ada24..0000000000
--- a/windows/deployment/windows-autopilot/windows-autopilot-requirements-licensing.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: Windows Autopilot licensing requirements
-ms.reviewer:
-manager: dansimp
-description: This topic goes over Windows Autopilot and how it helps setup OOBE Windows 10 devices.
-keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
-ms.prod: w10
-ms.mktglfcycl: deploy
-ms.localizationpriority: high
-ms.sitesec: library
-ms.pagetype: deploy
-author: dulcemontemayor
-ms.author: dolmont
-ms.collection: M365-modern-desktop
-ms.topic: article
----
-
-
-# Windows Autopilot licensing requirements
-
-**Applies to: Windows 10**
-
-Windows Autopilot depends on specific capabilities available in Windows 10 and Azure Active Directory; it also requires an MDM service such as Microsoft Intune. These capabilities can be obtained through various editions and subscription programs:
-
-- To provide needed Azure Active Directory (automatic MDM enrollment and company branding features) and MDM functionality, one of the following is required:
- - [Microsoft 365 Business subscriptions](https://www.microsoft.com/en-us/microsoft-365/business)
- - [Microsoft 365 F1 subscriptions](https://www.microsoft.com/en-us/microsoft-365/enterprise/firstline)
- - [Microsoft 365 Academic A1, A3, or A5 subscriptions](https://www.microsoft.com/en-us/education/buy-license/microsoft365/default.aspx)
- - [Microsoft 365 Enterprise E3 or E5 subscriptions](https://www.microsoft.com/en-us/microsoft-365/enterprise), which include all Windows 10, Office 365, and EM+S features (Azure AD and Intune)
- - [Enterprise Mobility + Security E3 or E5 subscriptions](https://www.microsoft.com/en-us/cloud-platform/enterprise-mobility-security), which include all needed Azure AD and Intune features
- - [Intune for Education subscriptions](https://docs.microsoft.com/en-us/intune-education/what-is-intune-for-education), which include all needed Azure AD and Intune features
- - [Azure Active Directory Premium P1 or P2](https://azure.microsoft.com/en-us/services/active-directory/) and [Microsoft Intune subscriptions](https://www.microsoft.com/en-us/cloud-platform/microsoft-intune) (or an alternative MDM service)
-
-Additionally, the following are also recommended (but not required):
-- [Office 365 ProPlus](https://www.microsoft.com/en-us/p/office-365-proplus/CFQ7TTC0K8R0), which can be deployed easily via Intune (or other MDM services)
-- [Windows Subscription Activation](https://docs.microsoft.com/windows/deployment/windows-10-enterprise-subscription-activation), to automatically step up devices from Windows 10 Pro to Windows 10 Enterprise
diff --git a/windows/deployment/windows-autopilot/windows-autopilot-requirements-network.md b/windows/deployment/windows-autopilot/windows-autopilot-requirements-network.md
deleted file mode 100644
index 26e9bb27d4..0000000000
--- a/windows/deployment/windows-autopilot/windows-autopilot-requirements-network.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-title: Windows Autopilot networking requirements
-ms.reviewer:
-manager: dansimp
-description: This topic goes over Windows Autopilot and how it helps setup OOBE Windows 10 devices.
-keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
-ms.prod: w10
-ms.mktglfcycl: deploy
-ms.localizationpriority: high
-ms.sitesec: library
-ms.pagetype: deploy
-author: dulcemontemayor
-ms.author: dolmont
-ms.collection: M365-modern-desktop
-ms.topic: article
----
-
-
-# Windows Autopilot networking requirements
-
-**Applies to: Windows 10**
-
-Windows Autopilot depends on a variety of internet-based services; access to these services must be provided for Autopilot to function properly. In the simplest case, enabling proper functionality can be achieved by ensuring the following:
-
-- Ensure DNS name resolution for internet DNS names
-
-- Allow access to all hosts via port 80 (HTTP), 443 (HTTPS), and 123 (UDP/NTP)
-
-In environments that have more restrictive internet access, or for those that require authentication before internet access can be obtained, additional configuration may be required to whitelist access to the needed services. For additional details about each of these services and their specific requirements, review the following details:
-
-- **Windows Autopilot Deployment Service (and Windows Activation).** After a network connection is in place, each Windows 10 device will contact the Windows Autopilot Deployment Service. With Windows 10 builds 18204 and above, the following URLs are used:
-
- - https://ztd.dds.microsoft.com
- - https://cs.dds.microsoft.com
-
- For all supported Windows 10 releases, Windows Autopilot also uses Windows Activation services. See the following link for details:
-
- - Issue More information
+ White glove gives a red screen White glove is not supported on a VM.
+ Error importing Windows Autopilot devices from a .csv file Ensure that you have not edited the .csv file in Microsoft Excel or an editor other than Notepad. Some of these editors can introduce extra characters causing the file format to be invalid.
+ Windows Autopilot for existing devices does not follow the Autopilot OOBE experience. Ensure that the JSON profile file is saved in **ANSI/ASCII** format, not Unicode or UTF-8.
+ **Something went wrong** is displayed page during OOBE. The client is likely unable to access all the required AAD/MSA-related URLs. For more information, see [Networking requirements](windows-autopilot-requirements.md#networking-requirements).
+
+
+## Licensing requirements
+
+Windows Autopilot depends on specific capabilities available in Windows 10 and Azure Active Directory. It also requires an MDM service such as Microsoft Intune. These capabilities can be obtained through various editions and subscription programs:
+
+To provide needed Azure Active Directory (automatic MDM enrollment and company branding features) and MDM functionality, one of the following is required:
+ - [Microsoft 365 Business subscriptions](https://www.microsoft.com/en-us/microsoft-365/business)
+ - [Microsoft 365 F1 subscriptions](https://www.microsoft.com/en-us/microsoft-365/enterprise/firstline)
+ - [Microsoft 365 Academic A1, A3, or A5 subscriptions](https://www.microsoft.com/en-us/education/buy-license/microsoft365/default.aspx)
+ - [Microsoft 365 Enterprise E3 or E5 subscriptions](https://www.microsoft.com/en-us/microsoft-365/enterprise), which include all Windows 10, Office 365, and EM+S features (Azure AD and Intune).
+ - [Enterprise Mobility + Security E3 or E5 subscriptions](https://www.microsoft.com/en-us/cloud-platform/enterprise-mobility-security), which include all needed Azure AD and Intune features.
+ - [Intune for Education subscriptions](https://docs.microsoft.com/en-us/intune-education/what-is-intune-for-education), which include all needed Azure AD and Intune features.
+ - [Azure Active Directory Premium P1 or P2](https://azure.microsoft.com/en-us/services/active-directory/) and [Microsoft Intune subscriptions](https://www.microsoft.com/en-us/cloud-platform/microsoft-intune) (or an alternative MDM service).
+
+Additionally, the following are also recommended (but not required):
+- [Office 365 ProPlus](https://www.microsoft.com/en-us/p/office-365-proplus/CFQ7TTC0K8R0), which can be deployed easily via Intune (or other MDM services).
+- [Windows Subscription Activation](https://docs.microsoft.com/windows/deployment/windows-10-enterprise-subscription-activation), to automatically step up devices from Windows 10 Pro to Windows 10 Enterprise.
+
+## Configuration requirements
+
+Before Windows Autopilot can be used, some configuration tasks are required to support the common Autopilot scenarios.
+
+- Configure Azure Active Directory automatic enrollment. For Microsoft Intune, see [Enable Windows 10 automatic enrollment](https://docs.microsoft.com/intune/windows-enroll#enable-windows-10-automatic-enrollment) for details. If using a different MDM service, contact the vendor for the specific URLs or configuration needed for those services.
+- Configure Azure Active Directory custom branding. In order to display an organization-specific logon page during the Autopilot process, Azure Active Directory needs to be configured with the images and text that should be displayed. See [Quickstart: Add company branding to your sign-in page in Azure AD](https://docs.microsoft.com/azure/active-directory/fundamentals/customize-branding) for more details. Note that the "square logo" and "sign-in page text" are the key elements for Autopilot, as well as the Azure Active Directory tenant name (configured separately in the Azure AD tenant properties).
+- Enable [Windows Subscription Activation](https://docs.microsoft.com/windows/deployment/windows-10-enterprise-subscription-activation) if desired, in order to automatically step up from Windows 10 Pro to Windows 10 Enterprise.
+
+Specific scenarios will then have additional requirements. Generally, there are two specific tasks:
+
+- Device registration. Devices need to be added to Windows Autopilot to support most Windows Autopilot scenarios. See [Adding devices to Windows Autopilot](add-devices.md) for more details.
+- Profile configuration. Once devices have been added to Windows Autopilot, a profile of settings needs to be applied to each device. See [Configure Autopilot profiles](profiles.md) for details. Note that Microsoft Intune can automate this profile assignment; see [Create an AutoPilot device group](https://docs.microsoft.com/intune/enrollment-autopilot#create-an-autopilot-device-group) and [Assign an AutoPilot deployment profile to a device group](https://docs.microsoft.com/intune/enrollment-autopilot#assign-an-autopilot-deployment-profile-to-a-device-group) for more information.
+
+See [Windows Autopilot Scenarios](windows-autopilot-scenarios.md) for additional details.
+
+For a walkthrough for some of these and related steps, see this video:
+Service Information
+ **Windows Autopilot Deployment Service and Windows Activation** After a network connection is in place, each Windows 10 device will contact the Windows Autopilot Deployment Service. With Windows 10 builds 18204 and above, the following URLs are used: https://ztd.dds.microsoft.com, https://cs.dds.microsoft.com.
+
+For all supported Windows 10 releases, Windows Autopilot also uses Windows Activation services. See [Windows activation or validation fails with error code 0x8004FE33](https://support.microsoft.com/help/921471/windows-activation-or-validation-fails-with-error-code-0x8004fe33) for details about problems that might occur when you connect to the Internet through a proxy server.
+**Azure Active Directory** User credentials are validated by Azure Active Directory, and the device can also be joined to Azure Active Directory. See [Office 365 IP Address and URL Web service](https://docs.microsoft.com/en-us/office365/enterprise/office-365-ip-web-service) for more information.
+ **Intune** Once authenticated, Azure Active Directory will trigger enrollment of the device into the Intune MDM service. See the following link for details about network communication requirements: [Intune network configuration requirements and bandwidth](https://docs.microsoft.com/intune/network-bandwidth-use#network-communication-requirements).
+ **Windows Update** During the OOBE process, as well as after the Windows 10 OS is fully configured, the Windows Update service is leveraged to retrieve needed updates. If there are problems connecting to Windows Update, see [How to solve connection problems concerning Windows Update or Microsoft Update](https://support.microsoft.com/help/818018/how-to-solve-connection-problems-concerning-windows-update-or-microsof).
+
+If Windows Update is inaccessible, the AutoPilot process will still continue but critical updates will not be available.
+
+**Delivery Optimization** When downloading Windows Updates, Microsoft Store apps and app updates, Office Updates and Intune Win32 Apps, the [Delivery Optimization](https://docs.microsoft.com/windows/deployment/update/waas-delivery-optimization) service is contacted to enable peer-to-peer sharing of content so that only a few devices need to download it from the internet.
+
+If the Delivery Optimization Service is inaccessible, the AutoPilot process will still continue with Delivery Optimization downloads from the cloud (without peer-to-peer).
+
+**Network Time Protocol (NTP) Sync** When a Windows device starts up, it will talk to a network time server to ensure that the time on the device is accurate. Ensure that UDP port 123 to time.windows.com is accessible.
+ **Domain Name Services (DNS)** To resolve DNS names for all services, the device communicates with a DNS server, typically provided via DHCP. This DNS server must be able to resolve internet names.
+ **Diagnostics data** To enable Windows Analytics and related diagnostics capabilities, see [Configure Windows diagnostic data in your organization](https://docs.microsoft.com/windows/configuration/configure-windows-diagnostic-data-in-your-organization).
+
+If diagnostic data cannot be sent, the Autopilot process will still continue, but services that depend on diagnostic data, such as Windows Analytics, will not work.
+**Network Connection Status Indicator (NCSI)** Windows must be able to tell that the device is able to access the internet. For more information, see [Network Connection Status Indicator (NCSI)](https://docs.microsoft.com/en-us/windows/privacy/manage-windows-1709-endpoints#network-connection-status-indicator-ncsi).
+
+[www.msftconnecttest.com](http://www.msftconnecttest.com) must be resolvable via DNS and accessible via HTTP.
+ **Windows Notification Services (WNS)** This service is used to enable Windows to receive notifications from apps and services. See [Microsoft Store](https://docs.microsoft.com/en-us/windows/privacy/manage-windows-1809-endpoints#microsoft-store) for more information.
+
+If the WNS services are not available, the Autopilot process will still continue without notifications.
+**Microsoft Store, Microsoft Store for Business** Apps in the Microsoft Store can be pushed to the device, triggered via Intune (MDM). App updates and additional apps may also be needed when the user first logs in. For more information, see [Prerequisites for Microsoft Store for Business and Education](https://docs.microsoft.com/microsoft-store/prerequisites-microsoft-store-for-business)(also includes Azure AD and Windows Notification Services).
+
+If the Microsoft Store is not accessible, the AutoPilot process will still continue without Microsoft Store apps.
+
+**Office 365** As part of the Intune device configuration, installation of Office 365 ProPlus may be required. For more information, see [Office 365 URLs and IP address ranges](https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2)(includes all Office services, DNS names, IP addresses; includes Azure AD and other services that may overlap with those listed above).
+ **Certificate revocation lists (CRLs)** Some of these services will also need to check certificate revocation lists (CRLs) for certificates used in the services. A full list of these is documented at [Office 365 URLs and IP address ranges](https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2#bkmk_crl) and [Office 365 Certificate Chains](https://aka.ms/o365chains).
+
+
There are no additional hardware requirements to use Windows 10 Autopilot, beyond the [requirements to run Windows 10](https://www.microsoft.com/windows/windows-10-specifications).
diff --git a/windows/deployment/windows-autopilot/windows-autopilot-reset-local.md b/windows/deployment/windows-autopilot/windows-autopilot-reset-local.md
deleted file mode 100644
index aa2c84a967..0000000000
--- a/windows/deployment/windows-autopilot/windows-autopilot-reset-local.md
+++ /dev/null
@@ -1,70 +0,0 @@
----
-title: Reset devices using local Windows Autopilot Reset
-ms.reviewer:
-manager: dansimp
-description: Gives an overview of Local Autopilot Reset and how to use it.
-keywords: Autopilot Reset, Windows 10
-ms.prod: w10
-ms.technology: Windows
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.pagetype:
-ms.localizationpriority: medium
-author: dulcemontemayor
-ms.author: dolmont
-ms.collection: M365-modern-desktop
-ms.topic: article
----
-
-
-# Reset devices with local Windows Autopilot Reset
-
-**Applies to: Windows 10, version 1709 and above
-
-The Intune Service Administrator role is required to perform this task. Learn more about how to [Assign Azure Active Directory roles](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-users-assign-role-azure-portal).
-
-IT admins can perform a local Windows Autopilot Reset to quickly remove personal files, apps, and settings, and reset Windows 10 devices from the lock screen any time and apply original settings and management enrollment (Azure Active Directory and device management) so the devices are ready to use. With a local Autopilot Reset, devices are returned to a fully configured or known IT-approved state.
-
-To enable local Autopilot Reset in Windows 10:
-
-1. [Enable the policy for the feature](#enable-local-windows-autopilot-reset)
-2. [Trigger a reset for each device](#trigger-local-windows-autopilot-reset)
-
-## Enable local Windows Autopilot Reset
-
-To enable a local Windows Autopilot Reset, the **DisableAutomaticReDeploymentCredentials** policy must be configured. This policy is documented in the [Policy CSP](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-credentialproviders), **CredentialProviders/DisableAutomaticReDeploymentCredentials**. By default, local Windows Autopilot is disabled. This ensures that a local Autopilot Reset is not triggered by accident.
-
-You can set the policy using one of these methods:
-
-- MDM provider
-
- - When using Intune, you can create a new device configuration profile, specifying "Windows 10 or later" for the platform, "Device restrictions" for the profile type, and "General" for the settings category. The **Automatic Redeployment** setting should be set to **Allow**. Deploy this setting to all devices where a local reset should be permitted.
- - If you're using an MDM provider other than Intune, check your MDM provider documentation on how to set this policy.
-
-- Windows Configuration Designer
-
- You can [use Windows Configuration Designer](https://docs.microsoft.com/windows/configuration/provisioning-packages/provisioning-create-package) to set the **Runtime settings > Policies > CredentialProviders > DisableAutomaticReDeploymentCredentials** setting to 0 and then create a provisioning package.
-
-- Set up School PCs app
-
- The latest release of the Set up School PCs app supports enabling local Windows Autopilot Reset.
-
-## Trigger local Windows Autopilot Reset
-
-Performing a local Windows Autopilot Reset is a two-step process: trigger it and then authenticate. Once you've done these two steps, you can let the process execute and once it is done, the device is again ready for use.
-
-**To trigger a local Autopilot Reset**
-
-1. From the Windows device lock screen, enter the keystroke: **CTRL +  + R**.
-
- 
-
- This will open up a custom login screen for the local Autopilot Reset. The screen serves two purposes:
- 1. Confirm/verify that the end user has the right to trigger Local Autopilot Reset
- 2. Notify the user in case a provisioning package, created using Windows Configuration Designer, will be used as part of the process.
-
- 
-
-2. Sign in with the admin account credentials. If you created a provisioning package, plug in the USB drive and trigger the local Autopilot Reset.
-
- Once the local Autopilot Reset is triggered, the reset process starts. Once provisioning is complete, the device is again ready for use.
diff --git a/windows/deployment/windows-autopilot/windows-autopilot-reset-remote.md b/windows/deployment/windows-autopilot/windows-autopilot-reset-remote.md
deleted file mode 100644
index 918f25dc45..0000000000
--- a/windows/deployment/windows-autopilot/windows-autopilot-reset-remote.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: Reset devices with remote Autopilot Reset (Preview)
-ms.reviewer:
-manager: dansimp
-description: Gives an overview of remote Autopilot Reset and how to use it.
-keywords: Autopilot Reset, Windows 10
-ms.prod: w10
-ms.technology: Windows
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.pagetype:
-ms.localizationpriority: medium
-author: dulcemontemayor
-ms.author: dolmont
-ms.collection: M365-modern-desktop
-ms.topic: article
----
-
-
-# Reset devices with remote Windows Autopilot Reset (Preview)
-
-**Applies to: Windows 10, build 17672 or later**
-
-When performing a remote Windows Autopilot Reset, an MDM service such an Microsoft Intune can be used to initiate the reset process, avoiding the need for IT staff or other administrators to visit each machine to initiate the process.
-
-To enable a device for a remote Windows Autopilot Reset, the device must be MDM managed and joined to Azure AD. This feature is not supported on devices that were enrolled using [Autopilot self deploying mode](self-deploying.md).
-
-## Triggering a remote Windows Autopilot Reset
-
-To trigger a remote Windows Autopilot Reset via Intune, follow these steps:
-
-- Navigate to **Devices** tab in the Intune console.
-- In the **All devices** view, select the targeted reset devices and then click **More** to view device actions.
-- Select **Autopilot Reset** to kick-off the reset task.
-
->[!NOTE]
->The Autopilot Reset option will not be enabled in Microsoft Intune for devices not running Windows 10 build 17672 or higher.
-
->[!IMPORTANT]
->The feature for Autopilot Reset (preview) will stay grayed out, **unless** you reset the device using Autopilot (either using Fresh Reset or manually sysprep the device).
-
-Once the reset is complete, the device is again ready for use.
-
diff --git a/windows/deployment/windows-autopilot/windows-autopilot-reset.md b/windows/deployment/windows-autopilot/windows-autopilot-reset.md
index ef3eb3a84b..8e06edad48 100644
--- a/windows/deployment/windows-autopilot/windows-autopilot-reset.md
+++ b/windows/deployment/windows-autopilot/windows-autopilot-reset.md
@@ -1,17 +1,16 @@
---
title: Windows Autopilot Reset
-ms.reviewer:
-manager: dansimp
-description: Gives an overview of Remote Autopilot Reset and how to use it.
-keywords: Autopilot Reset, Windows 10
+description: Windows Autopilot deployment
+keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
+ms.reviewer: mniehaus
+manager: laurawi
ms.prod: w10
-ms.technology: Windows
ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.pagetype:
ms.localizationpriority: medium
-author: dulcemontemayor
-ms.author: dolmont
+ms.sitesec: library
+ms.pagetype: deploy
+author: greg-lindsay
+ms.author: greglin
ms.collection: M365-modern-desktop
ms.topic: article
---
@@ -19,7 +18,8 @@ ms.topic: article
# Windows Autopilot Reset
-**Applies to: Windows 10**
+- Applies to: Windows 10, version 1709 and later (local reset)
+- Applies to: Windows 10, version 1809 and later (remote reset)
Windows Autopilot Reset removes personal files, apps, and settings and reapplies a device’s original settings, maintaining its identity connection to Azure AD and its management connection to Intune so that the device is once again ready for use. Windows Autopilot Reset takes the device back to a business-ready state, allowing the next user to sign in and get productive quickly and simply.
@@ -32,9 +32,6 @@ The Windows Autopilot Reset process automatically retains information from the e
Windows Autopilot Reset will block the user from accessing the desktop until this information is restored, including re-applying any provisioning packages. For devices enrolled in an MDM service, Windows Autopilot Reset will also block until an MDM sync is completed.
->[!IMPORTANT]
->To reestablish Wi-Fi connectivity after reset, make sure the **Connect automatically** box is checked for the device's wireless network connection.
-
>[!NOTE]
>The Autopilot Reset does not support Hybrid Azure AD joined devices.
@@ -42,11 +39,89 @@ Windows Autopilot Reset will block the user from accessing the desktop until thi
Windows Autopilot Reset supports two scenarios:
-- [Local reset](windows-autopilot-reset-local.md), initiated by IT personnel or other administrators from the organization.
-- [Remote reset](windows-autopilot-reset-remote.md), initiated remotely by IT personnel via an MDM service such as Microsoft Intune.
+- [Local reset](#reset-devices-with-local-windows-autopilot-reset) initiated by IT personnel or other administrators from the organization.
+- [Remote reset](#reset-devices-with-remote-windows-autopilot-reset) initiated remotely by IT personnel via an MDM service such as Microsoft Intune.
Additional requirements and configuration details apply with each scenario; see the detailed links above for more information.
+## Reset devices with local Windows Autopilot Reset
+
+**Applies to: Windows 10, version 1709 and above**
+
+The Intune Service Administrator role is required to perform this task. For more information, see [Add users and grant administrative permission to Intune](https://docs.microsoft.com/en-us/intune/users-add).
+
+IT admins can perform a local Windows Autopilot Reset to quickly remove personal files, apps, and settings, and reset Windows 10 devices from the lock screen any time and apply original settings and management enrollment (Azure Active Directory and device management) so the devices are ready to use. With a local Autopilot Reset, devices are returned to a fully configured or known IT-approved state.
+
+To enable local Autopilot Reset in Windows 10:
+
+1. [Enable the policy for the feature](#enable-local-windows-autopilot-reset)
+2. [Trigger a reset for each device](#trigger-local-windows-autopilot-reset)
+
+### Enable local Windows Autopilot Reset
+
+To enable a local Windows Autopilot Reset, the **DisableAutomaticReDeploymentCredentials** policy must be configured. This policy is documented in the [Policy CSP](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-credentialproviders), **CredentialProviders/DisableAutomaticReDeploymentCredentials**. By default, local Windows Autopilot is disabled. This ensures that a local Autopilot Reset is not triggered by accident.
+
+You can set the policy using one of these methods:
+
+- MDM provider
+
+ - When using Intune, you can create a new device configuration profile, specifying "Windows 10 or later" for the platform, "Device restrictions" for the profile type, and "General" for the settings category. The **Automatic Redeployment** setting should be set to **Allow**. Deploy this setting to all devices where a local reset should be permitted.
+ - If you're using an MDM provider other than Intune, check your MDM provider documentation on how to set this policy.
+
+- Windows Configuration Designer
+
+ You can [use Windows Configuration Designer](https://docs.microsoft.com/windows/configuration/provisioning-packages/provisioning-create-package) to set the **Runtime settings > Policies > CredentialProviders > DisableAutomaticReDeploymentCredentials** setting to 0 and then create a provisioning package.
+
+- Set up School PCs app
+
+ The latest release of the Set up School PCs app supports enabling local Windows Autopilot Reset.
+
+### Trigger local Windows Autopilot Reset
+
+Performing a local Windows Autopilot Reset is a two-step process: trigger it and then authenticate. Once you've done these two steps, you can let the process execute and once it is done, the device is again ready for use.
+
+**To trigger a local Autopilot Reset**
+
+1. From the Windows device lock screen, enter the keystroke: **CTRL +  + R**.
+
+ 
+
+ This will open up a custom login screen for the local Autopilot Reset. The screen serves two purposes:
+ 1. Confirm/verify that the end user has the right to trigger Local Autopilot Reset
+ 2. Notify the user in case a provisioning package, created using Windows Configuration Designer, will be used as part of the process.
+
+ 
+
+2. Sign in with the admin account credentials. If you created a provisioning package, plug in the USB drive and trigger the local Autopilot Reset.
+
+ Once the local Autopilot Reset is triggered, the reset process starts. Once provisioning is complete, the device is again ready for use.
+
+## Reset devices with remote Windows Autopilot Reset
+
+**Applies to: Windows 10, version 1809 or later**
+
+When performing a remote Windows Autopilot Reset, an MDM service such an Microsoft Intune can be used to initiate the reset process, avoiding the need for IT staff or other administrators to visit each machine to initiate the process.
+
+To enable a device for a remote Windows Autopilot Reset, the device must be MDM managed and joined to Azure AD. This feature is not supported on devices that were enrolled using [Autopilot self deploying mode](self-deploying.md).
+
+### Triggering a remote Windows Autopilot Reset
+
+To trigger a remote Windows Autopilot Reset via Intune, follow these steps:
+
+- Navigate to **Devices** tab in the Intune console.
+- In the **All devices** view, select the targeted reset devices and then click **More** to view device actions.
+- Select **Autopilot Reset** to kick-off the reset task.
+
+>[!NOTE]
+>The Autopilot Reset option will not be enabled in Microsoft Intune for devices not running Windows 10 build 17672 or higher.
+
+>[!IMPORTANT]
+>The feature for Autopilot Reset will stay grayed out, **unless** you reset the device using Autopilot (either using Fresh Reset or manually sysprep the device).
+
+Once the reset is complete, the device is again ready for use.
+
+
+
## Troubleshooting
Windows Autopilot Reset requires that the [Windows Recovery Environment (WinRE)](https://docs.microsoft.com/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference) is correctly configured and enabled on the device. If it is not configured and enabled, an error such as `Error code: ERROR_NOT_SUPPORTED (0x80070032)` will be reported.
diff --git a/windows/deployment/windows-autopilot/windows-autopilot-scenarios.md b/windows/deployment/windows-autopilot/windows-autopilot-scenarios.md
index 35df374f1f..ec85b05086 100644
--- a/windows/deployment/windows-autopilot/windows-autopilot-scenarios.md
+++ b/windows/deployment/windows-autopilot/windows-autopilot-scenarios.md
@@ -1,16 +1,16 @@
---
title: Windows Autopilot scenarios and capabilities
-ms.reviewer:
-manager: dansimp
-description: Listing of Autopilot scenarios
+description: Windows Autopilot deployment
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
+ms.reviewer: mniehaus
+manager: laurawi
ms.prod: w10
ms.mktglfcycl: deploy
ms.localizationpriority: medium
ms.sitesec: library
ms.pagetype: deploy
-author: dulcemontemayor
-ms.author: dolmont
+author: greg-lindsay
+ms.author: greglin
ms.collection: M365-modern-desktop
ms.topic: article
---
@@ -24,16 +24,20 @@ ms.topic: article
Windows Autopilot includes support for a growing list of scenarios, designed to support common organization needs which can vary based on the type of organization and their progress moving to Windows 10 and [transitioning to modern management](https://docs.microsoft.com/windows/client-management/manage-windows-10-in-your-organization-modern-management).
-For details about these scenarios, see these additional topics:
+The following Windows Autopilot scenarios are described in this guide:
-- [Windows Autopilot for existing devices](existing-devices.md), to deploy Windows 10 on an existing Windows 7 or 8.1 device.
-- [Windows Autopilot user-driven mode](user-driven.md), for devices that will be set up by a member of the organization and configured for that person.
-- [Windows Autopilot self-deploying mode](self-deploying.md), for devices that will be automatically configured for shared use, as a kiosk, or as a digital signage device.
-- [Windows Autopilot Reset](windows-autopilot-reset.md), to re-deploy a device in a business-ready state.
+
+
-## Capabilities
+## Windows Autopilot capabilities
-### Windows Autopilot is self-updating during OOBE:
+### Windows Autopilot is self-updating during OOBE
Starting with the Windows 10, version 1903, Autopilot functional and critical updates will begin downloading automatically during OOBE after a device gets connected to a network and the [critical driver and Windows zero-day patch (ZDP) updates](https://docs.microsoft.com/windows-hardware/customize/desktop/windows-updates-during-oobe) have completed. The user or IT admin cannot opt-out of these Autopilot updates; they are required for Windows Autopilot deployment to operate properly. Windows will alert the user that the device is checking for, downloading and installing the updates.
@@ -61,4 +65,4 @@ With Windows Autopilot, you can configure the BitLocker encryption settings to b
## Related topics
-[Windows Autopilot Enrollment Status page](enrollment-status.md)
+[Windows Autopilot: What's new](windows-autopilot-whats-new.md)
diff --git a/windows/deployment/windows-autopilot/windows-autopilot-whats-new.md b/windows/deployment/windows-autopilot/windows-autopilot-whats-new.md
new file mode 100644
index 0000000000..7bac5f16fa
--- /dev/null
+++ b/windows/deployment/windows-autopilot/windows-autopilot-whats-new.md
@@ -0,0 +1,47 @@
+---
+title: Windows Autopilot what's new
+ms.reviewer:
+manager: laurawi
+description: Windows Autopilot deployment
+keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
+ms.prod: w10
+ms.mktglfcycl: deploy
+ms.localizationpriority: medium
+ms.sitesec: library
+ms.pagetype: deploy
+author: greg-lindsay
+ms.author: greglin
+ms.collection: M365-modern-desktop
+ms.topic: article
+---
+
+
+# Windows Autopilot: What's new
+
+**Applies to**
+
+- Windows 10
+
+## New in Windows 10, version 1903
+
+[Windows Autopilot for white glove deployment](white-glove.md) is new in Windows 10, version 1903. See the following video:
+
+Scenario More information
+ Deploy devices that will be set up by a member of the organization and configured for that person [Windows Autopilot user-driven mode](user-driven.md)
+ Deploy devices that will be automatically configured for shared use, as a kiosk, or as a digital signage device. [Windows Autopilot self-deploying mode](self-deploying.md)
+ Re-deploy a device in a business-ready state. [Windows Autopilot Reset](windows-autopilot-reset.md)
+ Pre-provision a device with up-to-date applications, policies and settings. [White glove](white-glove.md)
+ Deploy Windows 10 on an existing Windows 7 or 8.1 device [Windows Autopilot for existing devices](existing-devices.md)
+
+>[!VIDEO https://www.youtube.com/embed/nE5XSOBV0rI]
+
+Also new in this version of Windows:
+- The Intune enrollment status page (ESP) now tracks Intune Management Extensions.
+- [Cortana voiceover and speech recognition during OOBE](windows-autopilot-scenarios.md#cortana-voiceover-and-speech-recognition-during-oobe) is disabled by default for all Windows 10 Pro Education, and Enterprise SKUs.
+- [Windows Autopilot is self-updating during OOBE](windows-autopilot-scenarios.md#windows-autopilot-is-self-updating-during-oobe). Starting with the Windows 10, version 1903 Autopilot functional and critical updates will begin downloading automatically during OOBE.
+- Windows Autopilot will set the diagnostics data level to Full on Windows 10 version 1903 and later during OOBE.
+
+## New in Windows 10, version 1809
+
+Windows Autopilot [self-deploying mode](self-deploying.md) enables a zero touch device provisioning experience. Simply power on the device, plug it into the Ethernet, and the device is fully configured by Windows Autopilot. This self-deploying capability removes the current need to have an end user interact by pressing the “Next” button during the deployment process.
+
+You can utilize Windows Autopilot self-deploying mode to register the device to an AAD tenant, enroll in your organization’s MDM provider, and provision policies and applications, all with no user authentication or user interaction required.
+
+## Related topics
+
+[What's new in Microsoft Intune](https://docs.microsoft.com/intune/whats-new)
+[What's new in Windows 10](https://docs.microsoft.com/windows/whats-new/)
\ No newline at end of file
diff --git a/windows/deployment/windows-autopilot/windows-autopilot.md b/windows/deployment/windows-autopilot/windows-autopilot.md
index d3bae5993f..abb38d35f2 100644
--- a/windows/deployment/windows-autopilot/windows-autopilot.md
+++ b/windows/deployment/windows-autopilot/windows-autopilot.md
@@ -1,16 +1,16 @@
---
title: Overview of Windows Autopilot
-ms.reviewer:
-manager: dansimp
-description: This topic goes over Windows Autopilot and how it helps setup OOBE Windows 10 devices.
-keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, msfb, intune
+description: Windows Autopilot deployment
+keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
+ms.reviewer: mniehaus
+manager: laurawi
ms.prod: w10
ms.mktglfcycl: deploy
ms.localizationpriority: medium
ms.sitesec: library
ms.pagetype: deploy
-author: dulcemontemayor
-ms.author: dolmont
+author: greg-lindsay
+ms.author: greglin
ms.collection: M365-modern-desktop
ms.topic: article
---
@@ -22,16 +22,22 @@ ms.topic: article
- Windows 10
-Windows Autopilot is a collection of technologies used to set up and pre-configure new devices, getting them ready for productive use. You can also use Windows Autopilot to reset, repurpose and recover devices.
-This solution enables an IT department to achieve the above with little to no infrastructure to manage, with a process that's easy and simple.
+Windows Autopilot is a collection of technologies used to set up and pre-configure new devices, getting them ready for productive use. You can also use Windows Autopilot to reset, repurpose and recover devices. This solution enables an IT department to achieve the above with little to no infrastructure to manage, with a process that's easy and simple.
-Windows Autopilot is designed to simplify all parts of the lifecycle of Windows devices, for both IT and end users, from initial deployment through the eventual end of life. Leveraging cloud-based services, it can reduce the overall costs for deploying, managing, and retiring devices by reducing the amount of time that IT needs to spend on these processes and the amount of infrastructure that they need to maintain, while ensuring ease of use for all types of end users.
+Windows Autopilot is designed to simplify all parts of the lifecycle of Windows devices, for both IT and end users, from initial deployment through the eventual end of life. Leveraging cloud-based services, it can reduce the overall costs for deploying, managing, and retiring devices by reducing the amount of time that IT needs to spend on these processes and the amount of infrastructure that they need to maintain, while ensuring ease of use for all types of end users. See the following diagram:
-When initially deploying new Windows devices, Windows Autopilot leverages the OEM-optimized version of Windows 10 that is preinstalled on the device, saving organizations the effort of having to maintain custom images as well as drivers for every model of device being used. Instead of re-imaging the device, that existing Windows 10 installation can be transformed into a “business-ready” state, applying settings and policies, installing apps, and even changing the edition of Windows 10 being used (e.g. from Windows 10 Pro to Windows 10 Enterprise, to support advanced features).
+When initially deploying new Windows devices, Windows Autopilot leverages the OEM-optimized version of Windows 10 that is preinstalled on the device, saving organizations the effort of having to maintain custom images and drivers for every model of device being used. Instead of re-imaging the device, your existing Windows 10 installation can be transformed into a “business-ready” state, applying settings and policies, installing apps, and even changing the edition of Windows 10 being used (e.g. from Windows 10 Pro to Windows 10 Enterprise) to support advanced features.
-Once deployed, Windows 10 devices can be managed by tools such as Microsoft Intune, Windows Update for Business, System Center Configuration Manager, and other similar tools. Windows Autopilot can help with device re-purposing scenarios, leveraging Windows Autopilot Reset to quickly prepare a device for a new user, as well as in break/fix scenarios to enable a device to quickly be brought back to a business-ready state.
+Once deployed, Windows 10 devices can be managed by tools such as Microsoft Intune, Windows Update for Business, System Center Configuration Manager, and other similar tools. Windows Autopilot can also be used to re-purpose a device by leveraging Windows Autopilot Reset to quickly prepare a device for a new user, or in break/fix scenarios to enable a device to quickly be brought back to a business-ready state.
+
+Windows Autopilot enables you to:
+* Automatically join devices to Azure Active Directory (Azure AD) or Active Directory (via Hybrid Azure AD Join). See [Introduction to device management in Azure Active Directory](https://docs.microsoft.com/azure/active-directory/device-management-introduction) for more information about the differences between these two join options.
+* Auto-enroll devices into MDM services, such as Microsoft Intune ([*Requires an Azure AD Premium subscription*](windows-autopilot-requirements-configuration.md)).
+* Restrict the Administrator account creation.
+* Create and auto-assign devices to configuration groups based on a device's profile.
+* Customize OOBE content specific to the organization.
## Windows Autopilot walkthrough
@@ -47,32 +53,13 @@ Traditionally, IT pros spend a lot of time building and customizing images that
From the user's perspective, it only takes a few simple operations to make their device ready to use.
-From the IT pro's perspective, the only interaction required from the end user is to connect to a network and to verify their credentials. Everything past that is automated.
+From the IT pro's perspective, the only interaction required from the end user is to connect to a network and to verify their credentials. Everything beyond that is automated.
## Requirements
-Windows 10 version 1703 or higher is required to use Windows Autopilot. The following editions are supported:
-- Pro
-- Pro Education
-- Pro for Workstations
-- Enterprise
-- Education
-
-See [Windows Autopilot requirements](windows-autopilot-requirements.md) for detailed information on configuration, network, and licensing requirements.
-
-## Windows Autopilot Scenarios
-
-Windows Autopilot enables you to pre-register devices to your organization so that they will be fully configured with no additional intervention required by the user.
-
-Windows Autopilot enables you to:
-* Automatically join devices to Azure Active Directory (Azure AD) or Active Directory (via Hybrid Azure AD Join). See [Introduction to device management in Azure Active Directory](https://docs.microsoft.com/azure/active-directory/device-management-introduction) for more information about the differences between these two join options.
-* Auto-enroll devices into MDM services, such as Microsoft Intune ([*Requires an Azure AD Premium subscription*](windows-autopilot-requirements-configuration.md)).
-* Restrict the Administrator account creation.
-* Create and auto-assign devices to configuration groups based on a device's profile.
-* Customize OOBE content specific to the organization.
-
-See [Windows Autopilot scenarios](https://docs.microsoft.com/en-us/windows/deployment/windows-autopilot/windows-autopilot-scenarios) for more information about scenarios for using Windows Autopilot.
+Windows 10 version 1703 or higher is required to use Windows Autopilot. See [Windows Autopilot requirements](windows-autopilot-requirements.md) for detailed information on software, configuration, network, and licensing requirements.
## Related topics
-[Enroll Windows devices in Intune by using Windows Autopilot](https://docs.microsoft.com/en-us/intune/enrollment-autopilot)
+[Enroll Windows devices in Intune by using Windows Autopilot](https://docs.microsoft.com/en-us/intune/enrollment-autopilot)
+[Windows Autopilot scenarios and capabilities](windows-autopilot-scenarios.md)
\ No newline at end of file
diff --git a/windows/privacy/windows-diagnostic-data-1703.md b/windows/privacy/windows-diagnostic-data-1703.md
index 9729e4791e..d398441cbc 100644
--- a/windows/privacy/windows-diagnostic-data-1703.md
+++ b/windows/privacy/windows-diagnostic-data-1703.md
@@ -33,7 +33,7 @@ The data covered in this article is grouped into the following categories:
- Browsing History data
- Inking, Typing, and Speech Utterance data
-> [!NOTE]
+> [!NOTE]
> The majority of diagnostic data falls into the first four categories.
## Common data
diff --git a/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019.yml b/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019.yml
index 34ef2a1b15..141727f4e2 100644
--- a/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019.yml
+++ b/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019.yml
@@ -58,7 +58,6 @@ sections:
Trend Micro OfficeScan and Worry-Free Business Security AV software not compatible
Upgrade block: Microsoft and Trend Micro identified a compatibility issue with the Trend Micro business endpoint security solutions OfficeScan and Worry-Free Business Security.
See details >OS Build 17763.134
November 13, 2018
KB4467708Resolved February 01, 2019
09:00 AM PTUnable to access hotspots with third-party applications
Third-party applications may have difficulty authenticating hotspots.
See details >OS Build 17763.253
January 08, 2019
KB4480116Resolved
KB4476976January 22, 2019
02:00 PM PTUnable to use Seek bar in Windows Media Player
Users may not be able to use the Seek bar in Windows Media Player when playing specific files.
See details >OS Build 17763.55
October 09, 2018
KB4464330Resolved
KB4471332December 11, 2018
10:00 AM PTAudio stops working after installing Intel audio driver
Upgrade block: Windows 10 audio stops working after installing Intel Smart Sound Technology driver (version 09.21.00.3755).
See details >OS Build 17763.134
November 13, 2018
KB4467708Resolved
KB4468550December 07, 2018
10:00 AM PTF5 VPN clients losing network connectivity
Back to topOS Build 17763.134
November 13, 2018
KB4467708Resolved
KB4482887Resolved:
March 01, 2019
10:00 AM PT
Opened:
November 13, 2018
10:00 AM PTIssues with lock screen and Microsoft Edge tabs for certain AMD Radeon video cards
Back to topOS Build 17763.134
November 13, 2018
KB4467708Resolved
KB4487044Resolved:
February 12, 2019
10:00 AM PT
Opened:
November 13, 2018
10:00 AM PTTrend Micro OfficeScan and Worry-Free Business Security AV software not compatible
Back to topOS Build 17763.134
November 13, 2018
KB4467708Resolved Resolved:
February 01, 2019
09:00 AM PT
Opened:
November 13, 2018
10:00 AM PTAudio stops working after installing Intel audio driver
Back to topOS Build 17763.134
November 13, 2018
KB4467708Resolved
KB4468550Resolved:
December 07, 2018
10:00 AM PT
Opened:
November 13, 2018
10:00 AM PT
"
@@ -107,16 +105,6 @@ sections:
Summary Originating update Status Last updated Some applications may fail to run as expected on clients of AD FS 2016
Some applications may fail to run as expected on clients of Active Directory Federation Services 2016 (AD FS 2016)
See details >OS Build 14393.2941
April 25, 2019
KB4493473Mitigated June 07, 2019
04:25 PM PTOpening Internet Explorer 11 may fail
Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.
See details >OS Build 14393.2999
May 23, 2019
KB4499177Mitigated June 05, 2019
07:51 PM PTSome applications may fail to run as expected on clients of AD FS 2016
Some applications may fail to run as expected on clients of Active Directory Federation Services 2016 (AD FS 2016)
See details >OS Build 14393.2941
April 25, 2019
KB4493473Mitigated June 04, 2019
05:55 PM PTDevices running Windows Server 2016 with Hyper-V seeing Bitlocker error 0xC0210000
Some devices running Windows Server with Hyper-V enabled may start into Bitlocker recovery with error 0xC0210000
See details >OS Build 14393.2969
May 14, 2019
KB4494440Mitigated May 23, 2019
09:57 AM PTCluster service may fail if the minimum password length is set to greater than 14
The cluster service may fail to start with the error “2245 (NERR_PasswordTooShort)” if the Group Policy “Minimum Password Length” is configured with greater than 14 characters.
See details >OS Build 14393.2639
November 27, 2018
KB4467684Mitigated April 25, 2019
02:00 PM PTIssue using PXE to start a device from WDS
There may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension.
See details >OS Build 14393.2848
March 12, 2019
KB4489882Mitigated April 25, 2019
02:00 PM PT
"
diff --git a/windows/release-information/status-windows-10-1809-and-windows-server-2019.yml b/windows/release-information/status-windows-10-1809-and-windows-server-2019.yml
index dabae3539b..f3ada14b3b 100644
--- a/windows/release-information/status-windows-10-1809-and-windows-server-2019.yml
+++ b/windows/release-information/status-windows-10-1809-and-windows-server-2019.yml
@@ -75,8 +75,6 @@ sections:
Details Originating update Status History Some applications may fail to run as expected on clients of AD FS 2016
Back to topOS Build 14393.2941
April 25, 2019
KB4493473Mitigated Last updated:
June 07, 2019
04:25 PM PT
Opened:
June 04, 2019
05:55 PM PTOpening Internet Explorer 11 may fail
Back to topOS Build 14393.2999
May 23, 2019
KB4499177Mitigated Last updated:
June 05, 2019
07:51 PM PT
Opened:
June 05, 2019
05:49 PM PTSome applications may fail to run as expected on clients of AD FS 2016
Back to topOS Build 14393.2941
April 25, 2019
KB4493473Mitigated Last updated:
June 04, 2019
05:55 PM PT
Opened:
June 04, 2019
05:55 PM PTWindows 10, version 1809 update history may show an update installed twice
Some customers are reporting that KB4494441 installed twice on their device
See details >OS Build 17763.503
May 14, 2019
KB4494441Resolved May 16, 2019
02:37 PM PTLayout and cell size of Excel sheets may change when using MS UI Gothic
When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel.
See details >OS Build 17763.475
May 03, 2019
KB4495667Resolved
KB4494441May 14, 2019
10:00 AM PTZone transfers over TCP may fail
Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail.
See details >OS Build 17763.475
May 03, 2019
KB4495667Resolved
KB4494441May 14, 2019
10:00 AM PTLatest cumulative update (KB 4495667) installs automatically
Reports that the optional cumulative update (KB 4495667) installs automatically.
See details >OS Build 17763.475
May 03, 2019
KB4495667Resolved May 08, 2019
03:37 PM PTSystem may be unresponsive after restart if ArcaBit antivirus software installed
After further investigation ArcaBit has confirmed this issue is not applicable to Windows 10, version 1809
See details >OS Build 17763.437
April 09, 2019
KB4493509Resolved May 08, 2019
03:30 PM PTWindows 10, version 1809 update history may show an update installed twice
Back to topOS Build 17763.503
May 14, 2019
KB4494441Resolved Resolved:
May 16, 2019
02:37 PM PT
Opened:
May 14, 2019
02:56 PM PTLayout and cell size of Excel sheets may change when using MS UI Gothic
Back to topOS Build 17763.475
May 03, 2019
KB4495667Resolved
KB4494441Resolved:
May 14, 2019
10:00 AM PT
Opened:
May 10, 2019
10:35 AM PTZone transfers over TCP may fail
Back to topOS Build 17763.475
May 03, 2019
KB4495667Resolved
KB4494441Resolved:
May 14, 2019
10:00 AM PT
Opened:
May 14, 2019
01:19 PM PTLatest cumulative update (KB 4495667) installs automatically
Back to topOS Build 17763.475
May 03, 2019
KB4495667Resolved Resolved:
May 08, 2019
03:37 PM PT
Opened:
May 05, 2019
12:01 PM PT
"
diff --git a/windows/release-information/status-windows-10-1903.yml b/windows/release-information/status-windows-10-1903.yml
index d00e89505d..4a95d4db9f 100644
--- a/windows/release-information/status-windows-10-1903.yml
+++ b/windows/release-information/status-windows-10-1903.yml
@@ -22,7 +22,7 @@ sections:
Details Originating update Status History System may be unresponsive after restart if ArcaBit antivirus software installed
Back to topOS Build 17763.437
April 09, 2019
KB4493509Resolved Resolved:
May 08, 2019
03:30 PM PT
Opened:
April 09, 2019
10:00 AM PT
"
@@ -74,7 +74,7 @@ sections:
Current status as of June 6, 2019:
-
Note follow @WindowsUpdate to find out when new content is published to the release information dashboard.
Note follow @WindowsUpdate to find out when new content is published to the release information dashboard.Intel Audio displays an intcdaud.sys notification
Microsoft and Intel have identified an issue with a range of Intel Display Audio device drivers that may result in battery drain.
See details >OS Build 18362.116
May 21, 2019
KB4505057Mitigated May 21, 2019
04:47 PM PTCannot launch Camera app
Microsoft and Intel have identified an issue affecting Intel RealSense SR300 or Intel RealSense S200 camera apps.
See details >OS Build 18362.116
May 21, 2019
KB4505057Mitigated May 21, 2019
04:47 PM PTIntermittent loss of Wi-Fi connectivity
Some older devices may experience loss of Wi-Fi connectivity due to an outdated Qualcomm driver.
See details >OS Build 18362.116
May 21, 2019
KB4505057Mitigated May 21, 2019
04:46 PM PTOlder versions of BattlEye anti-cheat software incompatible
Microsoft and BattlEye have identified a compatibility issue with some games that use older versions of BattlEye anti-cheat software.
See details >OS Build 18362.116
May 21, 2019
KB4505057Resolved June 06, 2019
01:33 PM PTOlder versions of BattlEye anti-cheat software incompatible
Microsoft and BattlEye have identified a compatibility issue with some games that use older versions of BattlEye anti-cheat software.
See details >OS Build 18362.116
May 21, 2019
KB4505057Resolved June 07, 2019
04:26 PM PTDuplicate folders and documents showing in user profile directory
If known folders (e.g. Desktop, Documents, or Pictures folders) are redirected, an empty folder with that same name may be created.
See details >OS Build 18362.116
May 21, 2019
KB4505057Resolved
KB4497935May 29, 2019
02:00 PM PTAMD RAID driver incompatibility
Installation process may stop when trying to install Windows 10, version 1903 update on computers that run certain versions of AMD RAID drivers.
See details >OS Build 18362.116
May 21, 2019
KB4505057Resolved June 06, 2019
11:06 AM PTError attempting to update with external USB device or memory card attached
PCs with an external USB device or SD memory card attached may get error: \"This PC can't be upgraded to Windows 10.\"
See details >OS Build 18362.116
May 21, 2019
KB4505057Resolved
KB4497935May 29, 2019
02:00 PM PTIntel Audio displays an intcdaud.sys notification
Back to topOS Build 18362.116
May 21, 2019
KB4505057Mitigated Last updated:
May 21, 2019
04:47 PM PT
Opened:
May 21, 2019
07:22 AM PTCannot launch Camera app
Back to topOS Build 18362.116
May 21, 2019
KB4505057Mitigated Last updated:
May 21, 2019
04:47 PM PT
Opened:
May 21, 2019
07:20 AM PTIntermittent loss of Wi-Fi connectivity
Back to topOS Build 18362.116
May 21, 2019
KB4505057Mitigated Last updated:
May 21, 2019
04:46 PM PT
Opened:
May 21, 2019
07:13 AM PTOlder versions of BattlEye anti-cheat software incompatible
Back to topOS Build 18362.116
May 21, 2019
KB4505057Resolved Resolved:
June 06, 2019
01:33 PM PT
Opened:
May 21, 2019
07:34 AM PTOlder versions of BattlEye anti-cheat software incompatible
Back to topOS Build 18362.116
May 21, 2019
KB4505057Resolved Resolved:
June 07, 2019
04:26 PM PT
Opened:
May 21, 2019
07:34 AM PTDuplicate folders and documents showing in user profile directory
Back to topOS Build 18362.116
May 21, 2019
KB4505057Resolved
KB4497935Resolved:
May 29, 2019
02:00 PM PT
Opened:
May 21, 2019
07:16 AM PTAMD RAID driver incompatibility
Back to topOS Build 18362.116
May 21, 2019
KB4505057Resolved Resolved:
June 06, 2019
11:06 AM PT
Opened:
May 21, 2019
07:12 AM PTError attempting to update with external USB device or memory card attached
Back to topOS Build 18362.116
May 21, 2019
KB4505057Resolved
KB4497935Resolved:
May 29, 2019
02:00 PM PT
Opened:
May 21, 2019
07:38 AM PT
Summary Originating update Status Last updated IE11 may stop working when loading or interacting with Power BI reports
Power BI reports that contain line charts with markers may cause Internet Explorer 11 to stop working
See details >May 14, 2019
KB4499164Mitigated June 07, 2019
02:57 PM PTSystem may be unresponsive after restart with certain McAfee antivirus products
Devices with McAfee Endpoint Security Threat Prevention 10.x, Host Intrusion Prevention 8.0, or VirusScan Enterprise 8.8 may be slow or unresponsive at startup.
See details >April 09, 2019
KB4493472Mitigated April 25, 2019
02:00 PM PTUnable to access some gov.uk websites
gov.uk websites that don’t support “HSTS” may not be accessible
See details >May 14, 2019
KB4499164Resolved
KB4505050May 18, 2019
02:00 PM PTSystem may be unresponsive after restart if ArcaBit antivirus software installed
Devices with ArcaBit antivirus software installed may become unresponsive upon restart.
See details >April 09, 2019
KB4493472Resolved May 14, 2019
01:23 PM PT
+ "
+
- title: May 2019
- items:
- type: markdown
diff --git a/windows/release-information/status-windows-8.1-and-windows-server-2012-r2.yml b/windows/release-information/status-windows-8.1-and-windows-server-2012-r2.yml
index e76412be72..8d3e9cc582 100644
--- a/windows/release-information/status-windows-8.1-and-windows-server-2012-r2.yml
+++ b/windows/release-information/status-windows-8.1-and-windows-server-2012-r2.yml
@@ -60,6 +60,7 @@ sections:
- type: markdown
text: "Details Originating update Status History IE11 may stop working when loading or interacting with Power BI reports
Back to topMay 14, 2019
KB4499164Mitigated Last updated:
June 07, 2019
02:57 PM PT
Opened:
June 07, 2019
02:57 PM PT
Summary Originating update Status Last updated IE11 may stop working when loading or interacting with Power BI reports
Power BI reports that contain line charts with markers may cause Internet Explorer 11 to stop working
See details >May 14, 2019
KB4499151Mitigated June 07, 2019
02:57 PM PTJapanese IME doesn't show the new Japanese Era name as a text input option
If previous dictionary updates are installed, the Japanese input method editor (IME) doesn't show the new Japanese Era name as a text input option.
See details >April 25, 2019
KB4493443Mitigated May 15, 2019
05:53 PM PTIssue using PXE to start a device from WDS
There may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension.
See details >March 12, 2019
KB4489881Mitigated April 25, 2019
02:00 PM PTCertain operations performed on a Cluster Shared Volume may fail
Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”.
See details >January 08, 2019
KB4480963Mitigated April 25, 2019
02:00 PM PT
+ "
+
- title: May 2019
- items:
- type: markdown
diff --git a/windows/release-information/status-windows-server-2012.yml b/windows/release-information/status-windows-server-2012.yml
index e98321c34c..878f02de70 100644
--- a/windows/release-information/status-windows-server-2012.yml
+++ b/windows/release-information/status-windows-server-2012.yml
@@ -60,6 +60,7 @@ sections:
- type: markdown
text: "Details Originating update Status History IE11 may stop working when loading or interacting with Power BI reports
Back to topMay 14, 2019
KB4499151Mitigated Last updated:
June 07, 2019
02:57 PM PT
Opened:
June 07, 2019
02:57 PM PT
->[!NOTE]
+>[!NOTE]
> If policy is not configured to explicitly require letters or special characters, users will be restricted to creating a numeric PIN.
diff --git a/windows/security/identity-protection/hello-for-business/hello-planning-guide.md b/windows/security/identity-protection/hello-for-business/hello-planning-guide.md
index cca50b7fcd..97ceac8319 100644
--- a/windows/security/identity-protection/hello-for-business/hello-planning-guide.md
+++ b/windows/security/identity-protection/hello-for-business/hello-planning-guide.md
@@ -247,7 +247,7 @@ If you use modern management for both domain and non-domain joined devices, writ
Windows Hello for Business is a feature exclusive to Windows 10. Some deployments and features are available using earlier versions of Windows 10. Others need the latest versions.
If box **1a** on your planning worksheet reads **cloud only**, write **N/A** in box **3a** on your planning worksheet. Optionally, you may write **1511 or later** in box **3b** on your planning worksheet if you plan to manage non-domain joined devices.
->[!NOTE]
+>[!NOTE]
>Azure Active Directory joined devices without modern management automatically enroll in Windows Hello for Business using the default policy settings. Use modern management to adjust policy settings to match the business needs of your organization.
Write **1511 or later** in box **3a** on your planning worksheet if any of the following are true.
diff --git a/windows/security/identity-protection/installing-digital-certificates-on-windows-10-mobile.md b/windows/security/identity-protection/installing-digital-certificates-on-windows-10-mobile.md
index c4d3f73cb4..a181ec72c9 100644
--- a/windows/security/identity-protection/installing-digital-certificates-on-windows-10-mobile.md
+++ b/windows/security/identity-protection/installing-digital-certificates-on-windows-10-mobile.md
@@ -31,7 +31,7 @@ Certificates in Windows 10 Mobile are primarily used for the following purposes
- For installation and licensing of applications (from the Windows Phone Store or a custom company distribution site).
->[!WARNING]
+>[!WARNING]
>In Windows 10, Version 1607, if you have multiple certificates provisioned on the device and the Wi-Fi profile provisioned does not have a strict filtering criteria, you may see connection failures when connecting to Wi-Fi. [Learn more about this known issue in Version 1607](https://go.microsoft.com/fwlink/p/?LinkId=786764)
## Install certificates using Microsoft Edge
@@ -45,6 +45,7 @@ The Windows 10 Mobile certificate installer supports .cer, .p7b, .pem, and .pfx
## Install certificates using mobile device management (MDM)
Windows 10 Mobile supports root, CA, and client certificate to be configured via MDM. Using MDM, an administrator can directly add, delete, or query root and CA certificates, and configure the device to enroll a client certificate with a certificate enrollment server that supports Simple Certificate Enrollment Protocol (SCEP). SCEP enrolled client certificates are used by Wi-Fi, VPN, email, and browser for certificate-based client authentication. An MDM server can also query and delete SCEP enrolled client certificate (including user installed certificates), or trigger a new enrollment request before the current certificate is expired.
+
>[!WARNING]
>Do not use SCEP for encryption certificates for S/MIME. You must use a PFX certificate profile to support S/MIME on Windows 10 Mobile. For instructions on creating a PFX certificate profile in Microsoft Intune, see [Enable access to company resources using certificate profiles with Microsoft Intune](https://go.microsoft.com/fwlink/p/?LinkID=718216).
@@ -72,5 +73,4 @@ Windows 10 Mobile supports root, CA, and client certificate to be configured vi
## Related topics
-[Configure S/MIME](configure-s-mime.md)
-
+[Configure S/MIME](configure-s-mime.md)
\ No newline at end of file
diff --git a/windows/security/identity-protection/windows-credential-theft-mitigation-guide-abstract.md b/windows/security/identity-protection/windows-credential-theft-mitigation-guide-abstract.md
index 5c4e5fc232..701083c55c 100644
--- a/windows/security/identity-protection/windows-credential-theft-mitigation-guide-abstract.md
+++ b/windows/security/identity-protection/windows-credential-theft-mitigation-guide-abstract.md
@@ -31,7 +31,7 @@ This guide explains how credential theft attacks occur and the strategies and co
- Respond to suspicious activity
- Recover from a breach
-
+
## Attacks that steal credentials
diff --git a/windows/security/information-protection/bitlocker/bitlocker-and-adds-faq.md b/windows/security/information-protection/bitlocker/bitlocker-and-adds-faq.md
index 26fd5e8431..144180cd40 100644
--- a/windows/security/information-protection/bitlocker/bitlocker-and-adds-faq.md
+++ b/windows/security/information-protection/bitlocker/bitlocker-and-adds-faq.md
@@ -39,7 +39,7 @@ For more info, see [BitLocker Group Policy settings](bitlocker-group-policy-sett
The BitLocker Windows Management Instrumentation (WMI) interface does allow administrators to write a script to back up or synchronize an online client's existing recovery information; however, BitLocker does not automatically manage this process. The manage-bde command-line tool can also be used to manually back up recovery information to AD DS. For example, to back up all of the recovery information for the C: drive to AD DS, you would use the following command from an elevated command prompt: **manage-bde -protectors -adbackup C:**.
-> [!IMPORTANT]
+> [!IMPORTANT]
> Joining a computer to the domain should be the first step for new computers within an organization. After computers are joined to a domain, storing the BitLocker recovery key to AD DS is automatic (when enabled in Group Policy).
## Is there an event log entry recorded on the client computer to indicate the success or failure of the Active Directory backup?
diff --git a/windows/security/information-protection/bitlocker/bitlocker-key-management-faq.md b/windows/security/information-protection/bitlocker/bitlocker-key-management-faq.md
index 349af8295f..fa1f49ee5d 100644
--- a/windows/security/information-protection/bitlocker/bitlocker-key-management-faq.md
+++ b/windows/security/information-protection/bitlocker/bitlocker-key-management-faq.md
@@ -58,7 +58,7 @@ For older hardware, where a PIN may be needed, it’s recommended to enable [enh
BitLocker is designed to make the encrypted drive unrecoverable without the required authentication. When in recovery mode, the user needs the recovery password or recovery key to unlock the encrypted drive.
-> [!IMPORTANT]
+> [!IMPORTANT]
> Store the recovery information in AD DS, along with your Microsoft Account, or another safe location.
## Can the USB flash drive that is used as the startup key also be used to store the recovery key?
diff --git a/windows/security/information-protection/bitlocker/bitlocker-management-for-enterprises.md b/windows/security/information-protection/bitlocker/bitlocker-management-for-enterprises.md
index 8775e52fb9..fb326e7977 100644
--- a/windows/security/information-protection/bitlocker/bitlocker-management-for-enterprises.md
+++ b/windows/security/information-protection/bitlocker/bitlocker-management-for-enterprises.md
@@ -46,7 +46,7 @@ For Windows PCs and Windows Phones that enroll using **Connect to work or school
## Managing servers
-Servers are often installed, configured, and deployed using PowerShell, so the recommendation is to also use [PowerShell to enable BitLocker on a server](bitlocker-use-bitlocker-drive-encryption-tools-to-manage-bitlocker.md#a-href-idbkmk-blcmdletsabitlocker-cmdlets-for-windows-powershell), ideally as part of the initial setup. BitLocker is an Optional Component (OC) in Windows Server, so follow the directions in [BitLocker: How to deploy on Windows Server 2012 and later](bitlocker-how-to-deploy-on-windows-server.md) to add the BitLocker OC.
+Servers are often installed, configured, and deployed using PowerShell, so the recommendation is to also use [PowerShell to enable BitLocker on a server](bitlocker-use-bitlocker-drive-encryption-tools-to-manage-bitlocker.md#bitlocker-cmdlets-for-windows-powershell), ideally as part of the initial setup. BitLocker is an Optional Component (OC) in Windows Server, so follow the directions in [BitLocker: How to deploy on Windows Server 2012 and later](bitlocker-how-to-deploy-on-windows-server.md) to add the BitLocker OC.
The Minimal Server Interface is a prerequisite for some of the BitLocker administration tools. On a [Server Core](https://docs.microsoft.com/windows-server/get-started/getting-started-with-server-core) installation, you must add the necessary GUI components first. The steps to add shell components to Server Core are described in [Using Features on Demand with Updated Systems and Patched Images](https://blogs.technet.microsoft.com/server_core/2012/11/05/using-features-on-demand-with-updated-systems-and-patched-images/) and [How to update local source media to add roles and features](https://blogs.technet.microsoft.com/joscon/2012/11/14/how-to-update-local-source-media-to-add-roles-and-features/).
@@ -135,6 +135,6 @@ PS C:\> Enable-BitLocker -MountPoint "C:" -EncryptionMethod XtsAes256 -UsedSpace
**Powershell**
-[BitLocker cmdlets for Windows PowerShell](bitlocker-use-bitlocker-drive-encryption-tools-to-manage-bitlocker.md#a-href-idbkmk-blcmdletsabitlocker-cmdlets-for-windows-powershell)
+[BitLocker cmdlets for Windows PowerShell](bitlocker-use-bitlocker-drive-encryption-tools-to-manage-bitlocker.md#bitlocker-cmdlets-for-windows-powershell)
[Surface Pro Specifications](https://www.microsoft.com/surface/support/surface-pro-specs)
diff --git a/windows/security/information-protection/bitlocker/bitlocker-overview-and-requirements-faq.md b/windows/security/information-protection/bitlocker/bitlocker-overview-and-requirements-faq.md
index 054d1aedf7..dd0439236b 100644
--- a/windows/security/information-protection/bitlocker/bitlocker-overview-and-requirements-faq.md
+++ b/windows/security/information-protection/bitlocker/bitlocker-overview-and-requirements-faq.md
@@ -40,7 +40,7 @@ Yes, BitLocker supports multifactor authentication for operating system drives.
For requirements, see [System requirements](bitlocker-overview.md#system-requirements).
-> [!NOTE]
+> [!NOTE]
> Dynamic disks are not supported by BitLocker. Dynamic data volumes will not be displayed in the Control Panel. Although the operating system volume will always be displayed in the Control Panel, regardless of whether it is a Dynamic disk, if it is a dynamic disk it is cannot be protected by BitLocker.
## Why are two partitions required? Why does the system drive have to be so large?
diff --git a/windows/security/information-protection/bitlocker/bitlocker-security-faq.md b/windows/security/information-protection/bitlocker/bitlocker-security-faq.md
index 0a3788fac9..a12e4c3b02 100644
--- a/windows/security/information-protection/bitlocker/bitlocker-security-faq.md
+++ b/windows/security/information-protection/bitlocker/bitlocker-security-faq.md
@@ -39,6 +39,6 @@ BitLocker on operating system drives in its basic configuration (with a TPM but
Most operating systems use a shared memory space and rely on the operating system to manage physical memory. A TPM is a hardware component that uses its own internal firmware and logic circuits for processing instructions, thus shielding it from external software vulnerabilities. Attacking the TPM requires physical access to the computer. Additionally, the tools and skills necessary to attack hardware are often more expensive, and usually are not as available as the ones used to attack software. And because each TPM is unique to the computer that contains it, attacking multiple TPM computers would be difficult and time-consuming.
-> [!NOTE]
+> [!NOTE]
> Configuring BitLocker with an additional factor of authentication provides even more protection against TPM hardware attacks.
diff --git a/windows/security/information-protection/bitlocker/bitlocker-upgrading-faq.md b/windows/security/information-protection/bitlocker/bitlocker-upgrading-faq.md
index db58b1db22..de4112e3d5 100644
--- a/windows/security/information-protection/bitlocker/bitlocker-upgrading-faq.md
+++ b/windows/security/information-protection/bitlocker/bitlocker-upgrading-faq.md
@@ -40,6 +40,6 @@ Users need to suspend BitLocker for Non-Microsoft software updates, such as:
- TPM firmware updates
- Non-Microsoft application updates that modify boot components
-> [!NOTE]
+> [!NOTE]
> If you have suspended BitLocker, you can resume BitLocker protection after you have installed the upgrade or update. Upon resuming protection, BitLocker will reseal the encryption key to the new values of the measured components that changed as a part of the upgrade or update. If these types of upgrades or updates are applied without suspending BitLocker, your computer will enter recovery mode when restarting and will require a recovery key or password to access the computer.
diff --git a/windows/security/information-protection/bitlocker/bitlocker-using-with-other-programs-faq.md b/windows/security/information-protection/bitlocker/bitlocker-using-with-other-programs-faq.md
index a8069a69e9..8c25c57e76 100644
--- a/windows/security/information-protection/bitlocker/bitlocker-using-with-other-programs-faq.md
+++ b/windows/security/information-protection/bitlocker/bitlocker-using-with-other-programs-faq.md
@@ -78,7 +78,7 @@ Limited BitLocker functionality is available in Safe Mode. BitLocker-protected d
Both fixed and removable data drives can be locked by using the Manage-bde command-line tool and the –lock command.
-> [!NOTE]
+> [!NOTE]
> Ensure all data is saved to the drive before locking it. Once locked, the drive will become inaccessible.
The syntax of this command is:
diff --git a/windows/security/information-protection/encrypted-hard-drive.md b/windows/security/information-protection/encrypted-hard-drive.md
index aa97e1a83e..cf637532f1 100644
--- a/windows/security/information-protection/encrypted-hard-drive.md
+++ b/windows/security/information-protection/encrypted-hard-drive.md
@@ -41,7 +41,7 @@ Encrypted Hard Drives are supported natively in the operating system through the
- **API**: API support for applications to manage Encrypted Hard Drives independently of BitLocker Drive Encryption (BDE)
- **BitLocker support**: Integration with the BitLocker Control Panel provides a seamless BitLocker end user experience.
->[!WARNING]
+>[!WARNING]
>Self-Encrypting Hard Drives and Encrypted Hard Drives for Windows are not the same type of device. Encrypted Hard Drives for Windows require compliance for specific TCG protocols as well as IEEE 1667 compliance; Self-Encrypting Hard Drives do not have these requirements. It is important to confirm the device type is an Encrypted Hard Drive for Windows when planning for deployment.
If you are a storage device vendor who is looking for more info on how to implement Encrypted Hard Drive, see the [Encrypted Hard Drive Device Guide](https://msdn.microsoft.com/library/windows/hardware/dn653989.aspx).
@@ -63,7 +63,7 @@ For an Encrypted Hard Drive used as a **startup drive**:
- The computer must have the Compatibility Support Module (CSM) disabled in UEFI.
- The computer must always boot natively from UEFI.
->[!WARNING]
+>[!WARNING]
>All Encrypted Hard Drives must be attached to non-RAID controllers to function properly.
## Technical overview
@@ -83,9 +83,9 @@ Configuration of Encrypted Hard Drives as startup drives is done using the same
There are three related Group Policy settings that help you manage how BitLocker uses hardware-based envryption and which encryption algorithms to use. If these settings are not configured or disabled on systems that are equipped with encrypted drives, BitLocker uses software-based encryption:
-- [Configure use of hardware-based encryption for fixed data drives](bitlocker/bitlocker-group-policy-settings.md#a-href-idbkmk-hdefxdaconfigure-use-of-hardware-based-encryption-for-fixed-data-drives)
-- [Configure use of hardware-based encryption for removable data drives](bitlocker/bitlocker-group-policy-settings.md#a-href-idbkmk-hderddaconfigure-use-of-hardware-based-encryption-for-removable-data-drives)
-- [Configure use of hardware-based encryption for operating system drives](bitlocker/bitlocker-group-policy-settings.md#a-href-idbkmk-hdeosdaconfigure-use-of-hardware-based-encryption-for-operating-system-drives)
+- [Configure use of hardware-based encryption for fixed data drives](bitlocker/bitlocker-group-policy-settings.md#bkmk-hdefxd)
+- [Configure use of hardware-based encryption for removable data drives](bitlocker/bitlocker-group-policy-settings.md#configure-use-of-hardware-based-encryption-for-removable-data-drives)
+- [Configure use of hardware-based encryption for operating system drives](bitlocker/bitlocker-group-policy-settings.md#configure-use-of-hardware-based-encryption-for-operating-system-drives)
## Encrypted Hard Drive Architecture
@@ -107,4 +107,4 @@ Many Encrypted Hard Drive devices come pre-configured for use. If reconfiguratio
1. Open Disk Management (diskmgmt.msc)
2. Initialize the disk and select the appropriate partition style (MBR or GPT)
3. Create one or more volumes on the disk.
-4. Use the BitLocker setup wizard to enable BitLocker on the volume.
+4. Use the BitLocker setup wizard to enable BitLocker on the volume.
\ No newline at end of file
diff --git a/windows/security/information-protection/windows-information-protection/create-and-verify-an-efs-dra-certificate.md b/windows/security/information-protection/windows-information-protection/create-and-verify-an-efs-dra-certificate.md
index 2636b5b98e..7bde4e34bf 100644
--- a/windows/security/information-protection/windows-information-protection/create-and-verify-an-efs-dra-certificate.md
+++ b/windows/security/information-protection/windows-information-protection/create-and-verify-an-efs-dra-certificate.md
@@ -90,7 +90,7 @@ It's possible that you might revoke data from an unenrolled device only to later
To start Robocopy in S mode, open Task Manager. Click **File** > **Run new task**, type the command, and click **Create this task with administrative privileges**.
- 
+ 
If the employee performed a clean installation and there is no user profile, you need to recover the keys from the System Volume folder in each drive. Type:
diff --git a/windows/security/information-protection/windows-information-protection/create-wip-policy-using-intune-azure.md b/windows/security/information-protection/windows-information-protection/create-wip-policy-using-intune-azure.md
index 00d2cad395..fef2b942c2 100644
--- a/windows/security/information-protection/windows-information-protection/create-wip-policy-using-intune-azure.md
+++ b/windows/security/information-protection/windows-information-protection/create-wip-policy-using-intune-azure.md
@@ -97,7 +97,7 @@ Select **Store apps**, type the app product name and publisher, and click **OK**
- **Publisher**: `CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US`
- **Product Name**: `Microsoft.MicrosoftPowerBIForWindows`
-
+
To add multiple Store apps, click the ellipsis **…**.
diff --git a/windows/security/information-protection/windows-information-protection/enlightened-microsoft-apps-and-wip.md b/windows/security/information-protection/windows-information-protection/enlightened-microsoft-apps-and-wip.md
index af4c35b94e..441e6d2b75 100644
--- a/windows/security/information-protection/windows-information-protection/enlightened-microsoft-apps-and-wip.md
+++ b/windows/security/information-protection/windows-information-protection/enlightened-microsoft-apps-and-wip.md
@@ -71,7 +71,7 @@ Microsoft has made a concerted effort to enlighten several of our more popular a
- Microsoft Remote Desktop
->[!NOTE]
+>[!NOTE]
>Microsoft Visio and Microsoft Project are not enlightended apps and need to be exempted from WIP policy. If they are allowed, there is a risk of data loss. For example, if a device is workplace-joined and managed and the user leaves the company, metadata files that the apps rely on remain encrypted and the apps stop functioining.
## List of WIP-work only apps from Microsoft
diff --git a/windows/security/threat-protection/device-control/control-usb-devices-using-intune.md b/windows/security/threat-protection/device-control/control-usb-devices-using-intune.md
index 2a2cd6a8bf..1ea71b62ad 100644
--- a/windows/security/threat-protection/device-control/control-usb-devices-using-intune.md
+++ b/windows/security/threat-protection/device-control/control-usb-devices-using-intune.md
@@ -46,7 +46,7 @@ Protecting authorized removable storage with Windows Defender Antivirus requires
- If real-time protection is enabled, files are scanned before they are accessed and executed. The scanning scope includes all files, including those on mounted removable devices such as USB drives. You can optionally [run a PowerShell script to perform a custom scan](https://aka.ms/scanusb) of a USB drive after it is mounted, so that Windows Defender Antivirus starts scanning all files on a removable device once the removable device is attached. However, we recommend enabling real-time protection for improved scanning performance, especially for large storage devices.
- If scheduled scans are used, then you need to disable the DisableRemovableDriveScanning setting (enabled by default) to scan the removable device during a full scan. Removable devices are scanned during a quick or custom scan regardless of the DisableRemovableDriveScanning setting.
->[!NOTE]
+>[!NOTE]
>We recommend enabling real-time monitoring for scanning. In Intune, you can enable real-time monitoring for Windows 10 in **Device Restrictions** > **Configure** > **Windows Defender Antivirus** > **Real-time monitoring**.
Summary Originating update Status Last updated IE11 may stop working when loading or interacting with Power BI reports
Power BI reports that contain line charts with markers may cause Internet Explorer 11 to stop working
See details >May 14, 2019
KB4499171Mitigated June 07, 2019
02:57 PM PTJapanese IME doesn't show the new Japanese Era name as a text input option
If previous dictionary updates are installed, the Japanese input method editor (IME) doesn't show the new Japanese Era name as a text input option.
See details >April 25, 2019
KB4493462Mitigated May 15, 2019
05:53 PM PTIssue using PXE to start a device from WDS
There may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension.
See details >March 12, 2019
KB4489891Mitigated April 25, 2019
02:00 PM PTCertain operations performed on a Cluster Shared Volume may fail
Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”.
See details >January 08, 2019
KB4480975Mitigated April 25, 2019
02:00 PM PT
+ "
+
- title: May 2019
- items:
- type: markdown
diff --git a/windows/security/identity-protection/credential-guard/additional-mitigations.md b/windows/security/identity-protection/credential-guard/additional-mitigations.md
index 9d212561c9..93d0011f35 100644
--- a/windows/security/identity-protection/credential-guard/additional-mitigations.md
+++ b/windows/security/identity-protection/credential-guard/additional-mitigations.md
@@ -75,7 +75,7 @@ Run the following command:
CertReq -EnrollCredGuardCert MachineAuthentication
```
-> [!NOTE]
+> [!NOTE]
> You must restart the device after enrolling the machine authentication certificate.
##### How a certificate issuance policy can be used for access control
@@ -126,7 +126,7 @@ Authentication policies have the following requirements:
11. Click **OK** to create the authentication policy.
12. Close Active Directory Administrative Center.
-> [!NOTE]
+> [!NOTE]
> When the authentication policy enforces policy restrictions, users will not be able to sign on using devices that do not have a certificate with the appropriate issuance policy deployed. This applies to both local and remote sign on scenarios. Therefore, it is strongly recommended to first only audit policy restrictions to ensure you don't have unexpected failures.
##### Discovering authentication failures due to authentication policies
@@ -327,7 +327,7 @@ write-host "There are no issuance policies which are not mapped to groups"
}
}
```
-> [!NOTE]
+> [!NOTE]
> If you're having trouble running this script, try replacing the single quote after the ConvertFrom-StringData parameter.
#### Link an issuance policy to a group
@@ -609,5 +609,5 @@ write-host $tmp -Foreground Red
}
```
-> [!NOTE]
+> [!NOTE]
> If you're having trouble running this script, try replacing the single quote after the ConvertFrom-StringData parameter.
diff --git a/windows/security/identity-protection/credential-guard/credential-guard-not-protected-scenarios.md b/windows/security/identity-protection/credential-guard/credential-guard-not-protected-scenarios.md
index a2e1958009..2e1a83d9b7 100644
--- a/windows/security/identity-protection/credential-guard/credential-guard-not-protected-scenarios.md
+++ b/windows/security/identity-protection/credential-guard/credential-guard-not-protected-scenarios.md
@@ -100,7 +100,7 @@ Run the following command:
CertReq -EnrollCredGuardCert MachineAuthentication
```
-> [!NOTE]
+> [!NOTE]
> You must restart the device after enrolling the machine authentication certificate.
##### How a certificate issuance policy can be used for access control
@@ -151,7 +151,7 @@ Authentication policies have the following requirements:
11. Click **OK** to create the authentication policy.
12. Close Active Directory Administrative Center.
-> [!NOTE]
+> [!NOTE]
> When the authentication policy enforces policy restrictions, users will not be able to sign on using devices that do not have a certificate with the appropriate issuance policy deployed. This applies to both local and remote sign on scenarios. Therefore, it is strongly recommended to first only audit policy restrictions to ensure you don't have unexpected failures.
##### Discovering authentication failures due to authentication policies
@@ -356,7 +356,7 @@ write-host "There are no issuance policies which are not mapped to groups"
}
}
```
-> [!NOTE]
+> [!NOTE]
> If you're having trouble running this script, try replacing the single quote after the ConvertFrom-StringData parameter.
#### Link an issuance policy to a group
@@ -638,7 +638,7 @@ write-host $tmp -Foreground Red
}
```
-> [!NOTE]
+> [!NOTE]
> If you're having trouble running this script, try replacing the single quote after the ConvertFrom-StringData parameter.
## See also
diff --git a/windows/security/identity-protection/credential-guard/credential-guard-scripts.md b/windows/security/identity-protection/credential-guard/credential-guard-scripts.md
index b6c7e284af..0b6d13f777 100644
--- a/windows/security/identity-protection/credential-guard/credential-guard-scripts.md
+++ b/windows/security/identity-protection/credential-guard/credential-guard-scripts.md
@@ -209,7 +209,7 @@ write-host "There are no issuance policies which are not mapped to groups"
}
}
```
-> [!NOTE]
+> [!NOTE]
> If you're having trouble running this script, try replacing the single quote after the ConvertFrom-StringData parameter.
## Link an issuance policy to a group
@@ -491,5 +491,5 @@ write-host $tmp -Foreground Red
}
```
-> [!NOTE]
+> [!NOTE]
> If you're having trouble running this script, try replacing the single quote after the ConvertFrom-StringData parameter.
diff --git a/windows/security/identity-protection/enterprise-certificate-pinning.md b/windows/security/identity-protection/enterprise-certificate-pinning.md
index c6f6c2f100..6747177c1d 100644
--- a/windows/security/identity-protection/enterprise-certificate-pinning.md
+++ b/windows/security/identity-protection/enterprise-certificate-pinning.md
@@ -26,7 +26,7 @@ ms.reviewer:
Enterprise certificate pinning is a Windows feature for remembering, or “pinning,” a root issuing certificate authority or end entity certificate to a given domain name.
Enterprise certificate pinning helps reduce man-in-the-middle attacks by enabling you to protect your internal domain names from chaining to unwanted certificates or to fraudulently issued certificates.
->[!NOTE]
+>[!NOTE]
> External domain names, where the certificate issued to these domains is issued by a public certificate authority, are not ideal for enterprise certificate pinning.
Windows Certificate APIs (CertVerifyCertificateChainPolicy and WinVerifyTrust) are updated to check if the site’s server authentication certificate chain matches a restricted set of certificates.
diff --git a/windows/security/identity-protection/hello-for-business/feature-multifactor-unlock.md b/windows/security/identity-protection/hello-for-business/feature-multifactor-unlock.md
index c33567fa7c..3923238254 100644
--- a/windows/security/identity-protection/hello-for-business/feature-multifactor-unlock.md
+++ b/windows/security/identity-protection/hello-for-business/feature-multifactor-unlock.md
@@ -273,7 +273,7 @@ This example configures an IPConfig signal type using Ipv4Prefix, Ipv4DnsServer,
#### Example 2
This example configures an IpConfig signal type using a dnsSuffix element and a bluetooth signal for phones. This configuration is wrapped for reading. Once properly formatted, the entire XML contents must be a single line. This example implies that either the ipconfig **or** the Bluetooth rule must evaluate to true, for the resulting signal evaluation to be true.
->[!NOTE]
+>[!NOTE]
>Separate each rule element using a comma.
```
diff --git a/windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md b/windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md
index fc0ae7661b..3d74e8a3b3 100644
--- a/windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md
+++ b/windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md
@@ -382,7 +382,7 @@ $deSCP.Properties["keywords"].Add("enterpriseDrsName:" + $enrollmentService)
$deSCP.CommitChanges()
```
->[!NOTE]
+>[!NOTE]
> You can save the modified script in notepad and save them as "add-scpadfs.ps1" and the way to run it is just navigating into the script path folder and running .\add-scpAdfs.ps1.
>
diff --git a/windows/security/identity-protection/hello-for-business/hello-manage-in-organization.md b/windows/security/identity-protection/hello-for-business/hello-manage-in-organization.md
index c154697610..e9c7937ed9 100644
--- a/windows/security/identity-protection/hello-for-business/hello-manage-in-organization.md
+++ b/windows/security/identity-protection/hello-for-business/hello-manage-in-organization.md
@@ -294,7 +294,7 @@ The following table lists the MDM policy settings that you can configure for Win
Details Originating update Status History IE11 may stop working when loading or interacting with Power BI reports
Back to topMay 14, 2019
KB4499171Mitigated Last updated:
June 07, 2019
02:57 PM PT
Opened:
June 07, 2019
02:57 PM PT