deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 13:27:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Update enable-offline-updates-for-windows-embedded-8-1-handheld-devices-to-windows-10.md

Browse Source
This commit is contained in:
Kelly Baker 2020-07-07 12:46:21 -07:00 committed by GitHub
parent 42d6ac0546
commit 22591d8087
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
windows/client-management/mdm/enable-offline-updates-for-windows-embedded-8-1-handheld-devices-to-windows-10.md
View File

@ -141,7 +141,7 @@ There are two ways to retrieve this file from the device; one pre-GDR1 and one p
3. After the report XML is sent to the device, Microsoft Endpoint Configuration Manager displays a compliance log that contains the report information. The log can contain significant amount of data. 3. After the report XML is sent to the device, Microsoft Endpoint Configuration Manager displays a compliance log that contains the report information. The log can contain significant amount of data.
4. Parse this log for the report XML content. 4. Parse this log for the report XML content.
For a step-by-step walkthrough, see [How to retrieve a device update report using Microsoft Endpoint Configuration Manager logs](#how-to-retrieve-a-device-update-report-using-microsoft-endpoint-configuration-manager-logs). For a step-by-step walkthrough, see [Retrieve a device update report using Microsoft Endpoint Configuration Manager logs](#retrieve-a-device-update-report-using-microsoft-endpoint-configuration-manager-logs).
**Post-GDR1: Retrieve the report xml file using an SD card** **Post-GDR1: Retrieve the report xml file using an SD card**
@ -197,7 +197,7 @@ Here are the two files.
   
For a walkthrough of these steps, see [How to deploy controlled updates](#how-to-deploy-controlled-updates). Ensure that the Trigger Scan configuration baseline has NOT been deployed. For a walkthrough of these steps, see [Deploy controlled updates](#deploy-controlled-updates). Ensure that the Trigger Scan configuration baseline has NOT been deployed.
<a href="" id="deploy-controlled-updates"></a> <a href="" id="deploy-controlled-updates"></a>