From 7abaa191a2f62c8063d88ce21e3e1ba6787d1b0d Mon Sep 17 00:00:00 2001 From: ManikaDhiman Date: Wed, 13 May 2020 15:59:15 -0700 Subject: [PATCH 1/8] Added four new policies --- .../policy-configuration-service-provider.md | 12 + .../mdm/policy-csp-system.md | 271 ++++++++++++++++++ 2 files changed, 283 insertions(+) diff --git a/windows/client-management/mdm/policy-configuration-service-provider.md b/windows/client-management/mdm/policy-configuration-service-provider.md index 4f6316b7c7..c790ef7cdc 100644 --- a/windows/client-management/mdm/policy-configuration-service-provider.md +++ b/windows/client-management/mdm/policy-configuration-service-provider.md @@ -3367,6 +3367,9 @@ The following diagram shows the Policy configuration service provider in tree fo
System/AllowCommercialDataPipeline
+
+ System/AllowDesktopAnalyticsProcessing +
System/AllowDeviceNameInDiagnosticData
@@ -3382,15 +3385,24 @@ The following diagram shows the Policy configuration service provider in tree fo
System/AllowLocation
+
+ System/AllowMicrosoftManagedDesktopProcessing +
System/AllowStorageCard
System/AllowTelemetry +
+
+ System/AllowUpdateComplianceProcessing
System/AllowUserToResetPhone
+
+ System/AllowWUfBCloudProcessing +
System/BootStartDriverInitialization
diff --git a/windows/client-management/mdm/policy-csp-system.md b/windows/client-management/mdm/policy-csp-system.md index 7cb986c7fd..8329ee4f48 100644 --- a/windows/client-management/mdm/policy-csp-system.md +++ b/windows/client-management/mdm/policy-csp-system.md @@ -28,6 +28,9 @@ manager: dansimp
System/AllowCommercialDataPipeline
+
+ System/AllowDesktopAnalyticsProcessing +
System/AllowDeviceNameInDiagnosticData
@@ -43,15 +46,24 @@ manager: dansimp
System/AllowLocation
+
+ System/AllowMicrosoftManagedDesktopProcessing +
System/AllowStorageCard
System/AllowTelemetry
+
+ System/AllowUpdateComplianceProcessing +
System/AllowUserToResetPhone
+
+ System/AllowWUfBCloudProcessing +
System/BootStartDriverInitialization
@@ -250,6 +262,81 @@ The following list shows the supported values:
+ +**System/AllowDesktopAnalyticsProcessing** + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Windows EditionSupported?
Homecross mark
Procheck mark
Businesscheck mark
Enterprisecheck mark
Educationcheck mark
+ + +
+ + +[Scope](./policy-configuration-service-provider.md#policy-scope): + +> [!div class = "checklist"] +> * Device + +
+ + + +Available in Windows 10, version 1809 through 1909. This policy setting allows IT admins to enable diagnostic data from this device to be processed by Desktop Analytics. + +If you disable or do not configure this policy setting, diagnostic data from this device will not be processed by Desktop Analytics. + + + +ADMX Info: +- GP English name: *Allow Desktop Analytics Monitoring* +- GP name: *AllowDesktopAnalyticsMonitoring* +- GP path: *Windows Components/Data Collection and Preview Builds* +- GP ADMX file name: *DataCollection.admx* + + + +The following list shows the supported values: + +- 0 (default) – Diagnostic data is not processed by Desktop Analytics. + +- 2 – Diagnostic data is allowed to be processed by Desktop Analytics. + + + + + + + + + + +
+ **System/AllowDeviceNameInDiagnosticData** @@ -598,6 +685,65 @@ The following list shows the supported values: - 1 (default) – Location service is allowed. The user has control and can change Location Privacy settings on or off. - 2 – Force Location On. All Location Privacy settings are toggled on and grayed out. Users cannot change the settings and all consent permissions will be automatically suppressed. + + +
+ + +**System/AllowMicrosoftManagedDesktopProcessing** + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Windows EditionSupported?
Homecross mark
Procheck mark
Businesscheck mark
Enterprisecheck mark
Educationcheck mark
+ + +
+ + +[Scope](./policy-configuration-service-provider.md#policy-scope): + +> [!div class = "checklist"] +> * Device + +
+ + + +Available in Windows 10, version 1809 through 1909. This policy setting allows diagnostic data from this device to be processed by Microsoft Managed Desktop. + +If this policy is disabled or not configured, diagnostic data from this device will not be processed by Microsoft Managed Desktop. + + + +The following list shows the supported values: + +- 0 (default)– Diagnostic data is not processed by Microsoft Managed Desktop. +- 32 – Diagnostic data is processed by Microsoft Managed Desktop. + @@ -801,6 +947,73 @@ ADMX Info:
+ +**System/AllowUpdateComplianceProcessing** + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Windows EditionSupported?
Homecross mark
Procheck mark
Businesscheck mark
Enterprisecheck mark
Educationcheck mark
+ + +
+ + +[Scope](./policy-configuration-service-provider.md#policy-scope): + +> [!div class = "checklist"] +> * Device + +
+ + + +Available in Windows 10, version 1809 through 1909. This setting allows IT admins to enable diagnostic data from this device to be processed by Update Compliance. + +If you disable or do not configure this policy setting, diagnostic data from this device will not be processed by Update Compliance. + + + +ADMX Info: +- GP English name: *Enable Update Compliance monitoring* +- GP name: *AllowUpdateComplianceMonitoring* +- GP path: *Windows Components/Data Collection and Preview Builds* +- GP ADMX file name: *DataCollection.admx* + + + +The following list shows the supported values: + +- 0 (default)– Diagnostic data is not processed by Update Compliance. +- 16 – Diagnostic data is allowed to be processed by Update Compliance. + + + +
+ **System/AllowUserToResetPhone** @@ -861,6 +1074,64 @@ The following list shows the supported values:
+ +**System/AllowWUfBCloudProcessing** + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Windows EditionSupported?
Homecross mark
Procheck mark
Businesscheck mark
Enterprisecheck mark
Educationcheck mark
+ + +
+ + +[Scope](./policy-configuration-service-provider.md#policy-scope): + +> [!div class = "checklist"] +> * Device + +
+ + + +Available in Windows 10, version 1809 through 1909. This policy setting allows IT admins to enable diagnostic data from this device to be processed by Windows Update for Business cloud. + +If you disable or do not configure this policy setting, diagnostic data from this device will not be processed by Windows Update for Business cloud. + + + +The following list shows the supported values: +- 0 (default) – Diagnostic data is not processed by Windows Update for Business cloud. +- 8 – Diagnostic data is allowed to be processed by Windows Update for Business cloud. + + + + + **System/BootStartDriverInitialization** From de62288c0ec795bb7792dba1ce288889252d32ac Mon Sep 17 00:00:00 2001 From: ManikaDhiman Date: Wed, 13 May 2020 16:48:05 -0700 Subject: [PATCH 2/8] Added ADMX info --- windows/client-management/mdm/policy-csp-system.md | 8 ++++++++ windows/client-management/mdm/policy-csps-admx-backed.md | 2 ++ 2 files changed, 10 insertions(+) diff --git a/windows/client-management/mdm/policy-csp-system.md b/windows/client-management/mdm/policy-csp-system.md index 8329ee4f48..1bdd9ba4c6 100644 --- a/windows/client-management/mdm/policy-csp-system.md +++ b/windows/client-management/mdm/policy-csp-system.md @@ -1122,7 +1122,14 @@ Available in Windows 10, version 1809 through 1909. This policy setting allows I If you disable or do not configure this policy setting, diagnostic data from this device will not be processed by Windows Update for Business cloud. + +ADMX Info: +- GP English name: *Do not enforce safeguards for Feature Updates* +- GP name: *DisableWUfBSafeguards* +- GP path: *Windows Components/Windows Update/Windows Update for Business* +- GP ADMX file name: *WindowsUpdate.admx* + The following list shows the supported values: - 0 (default) – Diagnostic data is not processed by Windows Update for Business cloud. @@ -2046,6 +2053,7 @@ Footnotes: - 4 - Added in Windows 10, version 1803. - 5 - Added in Windows 10, version 1809. - 6 - Added in Windows 10, version 1903. +- 7 - Added in Windows 10, version 1909. diff --git a/windows/client-management/mdm/policy-csps-admx-backed.md b/windows/client-management/mdm/policy-csps-admx-backed.md index f79f85154e..fed6d0138d 100644 --- a/windows/client-management/mdm/policy-csps-admx-backed.md +++ b/windows/client-management/mdm/policy-csps-admx-backed.md @@ -406,6 +406,8 @@ ms.date: 07/18/2019 - [RemoteShell/SpecifyShellTimeout](./policy-csp-remoteshell.md#remoteshell-specifyshelltimeout) - [ServiceControlManager/SvchostProcessMitigation](./policy-csp-servicecontrolmanager.md#servicecontrolmanager-svchostprocessmitigation) - [Storage/EnhancedStorageDevices](./policy-csp-storage.md#storage-enhancedstoragedevices) +- [System/AllowDesktopAnalyticsProcessing](./policy-csp-system.md#system-allowdesktopanalyticsprocessing) +- [System/AllowUpdateComplianceProcessing](./policy-csp-system.md#system-allowppdatecomplianceprocessing) - [System/BootStartDriverInitialization](./policy-csp-system.md#system-bootstartdriverinitialization) - [System/DisableSystemRestore](./policy-csp-system.md#system-disablesystemrestore) - [WindowsConnectionManager/ProhitConnectionToNonDomainNetworksWhenConnectedToDomainAuthenticatedNetwork](./policy-csp-windowsconnectionmanager.md#windowsconnectionmanager-prohitconnectiontonondomainnetworkswhenconnectedtodomainauthenticatednetwork) From f27a8b447a4b80fd336a238de422c952dfddc290 Mon Sep 17 00:00:00 2001 From: ManikaDhiman Date: Wed, 24 Jun 2020 17:10:19 -0700 Subject: [PATCH 3/8] Updates to new system policy settings --- .../mdm/policy-csp-system.md | 51 ++++++++++++------- 1 file changed, 34 insertions(+), 17 deletions(-) diff --git a/windows/client-management/mdm/policy-csp-system.md b/windows/client-management/mdm/policy-csp-system.md index 501e8f7b77..4d53b23abd 100644 --- a/windows/client-management/mdm/policy-csp-system.md +++ b/windows/client-management/mdm/policy-csp-system.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.technology: windows author: manikadhiman ms.localizationpriority: medium -ms.date: 09/27/2019 +ms.date: 06/24/2020 ms.reviewer: manager: dansimp --- @@ -224,16 +224,14 @@ The following list shows the supported values: -> [!NOTE] -> This policy setting applies only to the Windows operating system and apps included with Windows, it does not apply to third-party apps or services running on Windows 10. +This policy setting controls whether Microsoft is a processor or controller for Windows diagnostic data collected from devices. -This policy setting opts the device into the Windows enterprise data pipeline. +If you enable this policy and enroll your devices in your Azure AD tenant, your organization becomes the controller and Microsoft is the processor of this data. -If you enable this setting, data collected from the device is opted into the Windows enterprise data pipeline. +If you disable or don't configure this policy setting, Microsoft will be the controller for Windows diagnostic data collected from the device. -If you disable or do not configure this setting, all data from the device is collected and processed in accordance with the policies for the Windows standard data pipeline. - -Configuring this setting does not change the telemetry collection level or the ability of the user to change the level. +>[!Note] +> This policy setting only controls if Microsoft is a processor for Windows diagnostic data from this device. Use the [System/AllowTelemetry](#system-allowtelemetry) policy setting to limit the diagnostic data that can be collected from the device. @@ -306,9 +304,14 @@ The following list shows the supported values: -Available in Windows 10, version 1809 through 1909. This policy setting allows IT admins to enable diagnostic data from this device to be processed by Desktop Analytics. +Available in Windows 10, version 1809 through 1909. This policy setting controls whether the Desktop Analytics service is configured to use Windows diagnostic data collected from devices. -If you disable or do not configure this policy setting, diagnostic data from this device will not be processed by Desktop Analytics. +If you enable this policy setting and enroll your devices in your Azure AD tenant, your organization becomes the controller and Microsoft is the processor of this data. + +If you disable or don't configure this policy setting, Microsoft will be the controller for Windows diagnostic data collected from the device. + +>[!Note] +> This policy setting only controls if Microsoft is a processor for Windows diagnostic data from this device. Use the [System/AllowTelemetry](#system-allowtelemetry) policy setting to limit the diagnostic data that can be collected from the device. @@ -323,7 +326,6 @@ ADMX Info: The following list shows the supported values: - 0 (default) – Diagnostic data is not processed by Desktop Analytics. - - 2 – Diagnostic data is allowed to be processed by Desktop Analytics. @@ -733,9 +735,14 @@ The following list shows the supported values: -Available in Windows 10, version 1809 through 1909. This policy setting allows diagnostic data from this device to be processed by Microsoft Managed Desktop. +Available in Windows 10, version 1809 through 1909. This policy setting controls whether the Microsoft Managed Desktop service is configured to use Windows diagnostic data collected from devices. -If this policy is disabled or not configured, diagnostic data from this device will not be processed by Microsoft Managed Desktop. +If you enable this policy setting and enroll your devices in your Azure AD tenant, your organization becomes the controller and Microsoft is the processor of this data. + +If you disable or don't configure this policy setting, Microsoft will be the controller for Windows diagnostic data collected from the device. + +> [!Note] +> This policy setting only controls if Microsoft is a processor for Windows diagnostic data from this device. Use the [System/AllowTelemetry](#system-allowtelemetry) policy setting to limit the diagnostic data that can be collected from the device. @@ -991,9 +998,14 @@ ADMX Info: -Available in Windows 10, version 1809 through 1909. This setting allows IT admins to enable diagnostic data from this device to be processed by Update Compliance. +Available in Windows 10, version 1809 through 1909. This policy setting controls whether the Update Compliance service is configured to use Windows diagnostic data collected from devices. -If you disable or do not configure this policy setting, diagnostic data from this device will not be processed by Update Compliance. +If you enable this policy setting and enroll your devices in your Azure AD tenant, your organization becomes the controller and Microsoft is the processor of this data. + +If you disable or don't configure this policy setting, Microsoft will be the controller for Windows diagnostic data collected from the device. + +>[!Note] +> This policy setting only controls if Microsoft is a processor for Windows diagnostic data from this device. Use the [System/AllowTelemetry](#system-allowtelemetry) setting to limit the diagnostic data that can be collected from the device. @@ -1118,9 +1130,14 @@ The following list shows the supported values: -Available in Windows 10, version 1809 through 1909. This policy setting allows IT admins to enable diagnostic data from this device to be processed by Windows Update for Business cloud. +Available in Windows 10, version 1809 through 1909. This policy setting controls whether the Windows Update for Business cloud service is configured to use Windows diagnostic data collected from devices. -If you disable or do not configure this policy setting, diagnostic data from this device will not be processed by Windows Update for Business cloud. +If you enable this policy setting and enroll your devices in your Azure AD tenant, your organization becomes the controller and Microsoft is the processor of this data. + +If you disable or don't configure this policy setting, Microsoft will be the controller for Windows diagnostic data collected from the device. + +>[!Note] +> This policy setting only controls if Microsoft is a processor for Windows diagnostic data from this device. Use the [System/AllowTelemetry](#system-allowtelemetry) policy setting to limit the diagnostic data that can be collected from the device. ADMX Info: From e55ac358560d22aa6bab7dbb23db17d4fecde115 Mon Sep 17 00:00:00 2001 From: ManikaDhiman Date: Thu, 25 Jun 2020 13:26:40 -0700 Subject: [PATCH 4/8] minor change to trigger the build --- windows/client-management/mdm/policy-csp-system.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/mdm/policy-csp-system.md b/windows/client-management/mdm/policy-csp-system.md index 4d53b23abd..74ff716b08 100644 --- a/windows/client-management/mdm/policy-csp-system.md +++ b/windows/client-management/mdm/policy-csp-system.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.technology: windows author: manikadhiman ms.localizationpriority: medium -ms.date: 06/24/2020 +ms.date: 06/25/2020 ms.reviewer: manager: dansimp --- From e41b2d806f4a07a1293f0621c2f155ca1a8b5468 Mon Sep 17 00:00:00 2001 From: ManikaDhiman Date: Thu, 2 Jul 2020 13:03:35 -0700 Subject: [PATCH 5/8] Added dev feedback --- ...new-in-windows-mdm-enrollment-management.md | 11 +++++++++++ .../client-management/mdm/policy-csp-system.md | 18 ++++++------------ 2 files changed, 17 insertions(+), 12 deletions(-) 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 eed052ba71..6998c66460 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 @@ -58,6 +58,7 @@ For details about Microsoft mobile device management protocols for Windows 10 s - [What is dmwappushsvc?](#what-is-dmwappushsvc) - **Change history in MDM documentation** + - [July 2020](#july-2020) - [June 2020](#june-2020) - [May 2020](#may-2020) - [February 2020](#february-2020) @@ -313,7 +314,12 @@ Policy, Policy/Channels, Policy/Channels/ChannelName, Policy/Channels/ChannelNam
  • Privacy/DisablePrivacyExperience
  • Privacy/UploadUserActivities
  • Security/RecoveryEnvironmentAuthentication
    • +
  • System/AllowCommercialDataPipeline
    • +
  • System/AllowDesktopAnalyticsProcessing
  • System/AllowDeviceNameInDiagnosticData
    • +
  • System/AllowMicrosoftManagedDesktopProcessing
    • +
  • System/AllowUpdateComplianceProcessing
    • +
  • System/AllowWUfBCloudProcessing
  • System/ConfigureMicrosoft365UploadEndpoint
  • System/DisableDeviceDelete
  • System/DisableDiagnosticDataViewer
    • @@ -1993,6 +1999,11 @@ What data is handled by dmwappushsvc? | It is a component handling the internal How do I turn if off? | The service can be stopped from the "Services" console on the device (Start > Run > services.msc). However, since this is a component part of the OS and required for the proper functioning of the device, we strongly recommend not to do this. | ## Change history in MDM documentation +### July 2020 +|New or updated topic | Description| +|--- | ---| +|[Policy CSP - System](policy-csp-system.md)|Added the following new policy settings:
    - System/AllowCommercialDataPipeline
    - System/AllowDesktopAnalyticsProcessing
    - System/AllowMicrosoftManagedDesktopProcessing
    - System/AllowUpdateComplianceProcessing
    - System/AllowWUfBCloudProcessing | + ### June 2020 |New or updated topic | Description| |--- | ---| diff --git a/windows/client-management/mdm/policy-csp-system.md b/windows/client-management/mdm/policy-csp-system.md index 74ff716b08..84be3c8c4d 100644 --- a/windows/client-management/mdm/policy-csp-system.md +++ b/windows/client-management/mdm/policy-csp-system.md @@ -316,9 +316,9 @@ If you disable or don't configure this policy setting, Microsoft will be the con ADMX Info: -- GP English name: *Allow Desktop Analytics Monitoring* -- GP name: *AllowDesktopAnalyticsMonitoring* -- GP path: *Windows Components/Data Collection and Preview Builds* +- GP English name: *Allow Desktop Analytics Processing* +- GP name: *AllowDesktopAnalyticsProcessing* +- GP path: *Data Collection and Preview Builds* - GP ADMX file name: *DataCollection.admx* @@ -1010,9 +1010,9 @@ If you disable or don't configure this policy setting, Microsoft will be the con ADMX Info: -- GP English name: *Enable Update Compliance monitoring* -- GP name: *AllowUpdateComplianceMonitoring* -- GP path: *Windows Components/Data Collection and Preview Builds* +- GP English name: *Enable Update Compliance Processing* +- GP name: *AllowUpdateComplianceProcessing* +- GP path: *Data Collection and Preview Builds* - GP ADMX file name: *DataCollection.admx* @@ -1140,12 +1140,6 @@ If you disable or don't configure this policy setting, Microsoft will be the con > This policy setting only controls if Microsoft is a processor for Windows diagnostic data from this device. Use the [System/AllowTelemetry](#system-allowtelemetry) policy setting to limit the diagnostic data that can be collected from the device. -ADMX Info: -- GP English name: *Do not enforce safeguards for Feature Updates* -- GP name: *DisableWUfBSafeguards* -- GP path: *Windows Components/Windows Update/Windows Update for Business* -- GP ADMX file name: *WindowsUpdate.admx* - The following list shows the supported values: From b6c3b5520b897cfcbc8a55085a9c86e8effdffa5 Mon Sep 17 00:00:00 2001 From: ManikaDhiman Date: Thu, 2 Jul 2020 14:35:29 -0700 Subject: [PATCH 6/8] minor update --- .../mdm/new-in-windows-mdm-enrollment-management.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) 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 6998c66460..aa0f6ee57d 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 @@ -314,7 +314,6 @@ Policy, Policy/Channels, Policy/Channels/ChannelName, Policy/Channels/ChannelNam
  • Privacy/DisablePrivacyExperience
  • Privacy/UploadUserActivities
  • Security/RecoveryEnvironmentAuthentication
    • -
  • System/AllowCommercialDataPipeline
  • System/AllowDesktopAnalyticsProcessing
  • System/AllowDeviceNameInDiagnosticData
  • System/AllowMicrosoftManagedDesktopProcessing
    • @@ -2002,7 +2001,7 @@ How do I turn if off? | The service can be stopped from the "Services" console o ### July 2020 |New or updated topic | Description| |--- | ---| -|[Policy CSP - System](policy-csp-system.md)|Added the following new policy settings:
    - System/AllowCommercialDataPipeline
    - System/AllowDesktopAnalyticsProcessing
    - System/AllowMicrosoftManagedDesktopProcessing
    - System/AllowUpdateComplianceProcessing
    - System/AllowWUfBCloudProcessing | +|[Policy CSP - System](policy-csp-system.md)|Added the following new policy settings:
    - System/AllowDesktopAnalyticsProcessing
    - System/AllowMicrosoftManagedDesktopProcessing
    - System/AllowUpdateComplianceProcessing
    - System/AllowWUfBCloudProcessing

    Updated the following policy setting:
    - System/AllowCommercialDataPipeline
    | ### June 2020 |New or updated topic | Description| From 6ae0e645aed3787f513e5a769ccedb3d75ea7fe4 Mon Sep 17 00:00:00 2001 From: Tina Burden Date: Mon, 6 Jul 2020 08:46:08 -0700 Subject: [PATCH 7/8] pencil edits --- .../mdm/new-in-windows-mdm-enrollment-management.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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 aa0f6ee57d..ed58df77d9 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 @@ -1763,7 +1763,7 @@ The software version information from **DevDetail/SwV** does not match the versi - Do not duplicate a product ID. Messaging and Skype Video use the same product ID. Duplicates cause an error. -- Silverlight xaps may not install even if publisher policy is specified using Windows Phone 8.1 publisher rule. For example, Silverlight app "Level" will not install even if you specify <Publisher PublisherName=”Microsoft Corporation” />. +- Silverlight apps may not install even if publisher policy is specified using Windows Phone 8.1 publisher rule. For example, Silverlight app "Level" will not install even if you specify <Publisher PublisherName=”Microsoft Corporation” />. To workaround this issue, remove the Windows Phone 8.1 publisher rule and add the specific product ID for each Silverlight app you want to allow to the allowed app list. @@ -1946,7 +1946,7 @@ Alternatively you can use the following procedure to create an EAP Configuration ![configure certificate selection window](images/certfiltering3.png) 6. Click **OK** to close the windows to get back to the main rasphone.exe dialog box. -7. Close the rasphone dialog box. +7. Close the rasphone.exe dialog box. 8. Continue following the procedure in the [EAP configuration](eap-configuration.md) topic from Step 9 to get an EAP TLS profile with appropriate filtering. > [!NOTE] From ad031445f7c99bc762f2a9308cb84c695d376535 Mon Sep 17 00:00:00 2001 From: Tina Burden Date: Mon, 6 Jul 2020 08:58:05 -0700 Subject: [PATCH 8/8] reverted acrolinx changes per manika --- .../mdm/new-in-windows-mdm-enrollment-management.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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 ed58df77d9..aa0f6ee57d 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 @@ -1763,7 +1763,7 @@ The software version information from **DevDetail/SwV** does not match the versi - Do not duplicate a product ID. Messaging and Skype Video use the same product ID. Duplicates cause an error. -- Silverlight apps may not install even if publisher policy is specified using Windows Phone 8.1 publisher rule. For example, Silverlight app "Level" will not install even if you specify <Publisher PublisherName=”Microsoft Corporation” />. +- Silverlight xaps may not install even if publisher policy is specified using Windows Phone 8.1 publisher rule. For example, Silverlight app "Level" will not install even if you specify <Publisher PublisherName=”Microsoft Corporation” />. To workaround this issue, remove the Windows Phone 8.1 publisher rule and add the specific product ID for each Silverlight app you want to allow to the allowed app list. @@ -1946,7 +1946,7 @@ Alternatively you can use the following procedure to create an EAP Configuration ![configure certificate selection window](images/certfiltering3.png) 6. Click **OK** to close the windows to get back to the main rasphone.exe dialog box. -7. Close the rasphone.exe dialog box. +7. Close the rasphone dialog box. 8. Continue following the procedure in the [EAP configuration](eap-configuration.md) topic from Step 9 to get an EAP TLS profile with appropriate filtering. > [!NOTE]