From f25e55b3aea8621028997e1462c3e4bf01c844e8 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Sun, 7 Aug 2022 15:50:53 -0700 Subject: [PATCH] add tshoot and help --- .../includes/update-compliance-verify-device-configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/update/includes/update-compliance-verify-device-configuration.md b/windows/deployment/update/includes/update-compliance-verify-device-configuration.md index 8cd3dba72b..09a4902e26 100644 --- a/windows/deployment/update/includes/update-compliance-verify-device-configuration.md +++ b/windows/deployment/update/includes/update-compliance-verify-device-configuration.md @@ -39,4 +39,4 @@ In some cases, you may need to manually verify the device configuration has the - The **MSP** field value under **protocol** should be either `16` or `18`. - If you need to send this data to Microsoft Support, select **Export data**. - :::image type="content" alt-text="Screenshot of the Diagnostic Data Viewer displaying the data from SoftwareUpdateClientTelemetry. The export data option and the fields for MSP and EnrolledTenantID are outlined in red." source="../media/update-compliance-diagnostic-data-viewer.png" lightbox="./media/update-compliance-diagnostic-data-viewer.png"::: + :::image type="content" alt-text="Screenshot of the Diagnostic Data Viewer displaying the data from SoftwareUpdateClientTelemetry. The export data option and the fields for MSP and EnrolledTenantID are outlined in red." source="../media/update-compliance-diagnostic-data-viewer.png" lightbox="../media/update-compliance-diagnostic-data-viewer.png":::