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

corrections to get-started and add-devices

Browse Source
This commit is contained in:
LauraKellerGitHub 2020-01-28 11:24:24 -08:00
parent 5ad477f1f1
commit df2badcb40
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
windows/deployment/update/windows-analytics-get-started.md
View File

@ -96,7 +96,7 @@ If your organization uses proxy server authentication for outbound traffic, use
## Deploy the compatibility update and related updates ## Deploy the compatibility update and related updates
The compatibility update scans your devices and enables application usage tracking. If you don’t already have these updates installed, you can download the applicable version from the Microsoft Update Catalog or deploy it using Windows Server Update Services (WSUS) or your software distribution solution, such as Microsoft Endpoint Configuration Manager. The compatibility update scans your devices and enables application usage tracking. If you don’t already have these updates installed, you can download the applicable version from the Microsoft Update Catalog or deploy it using Windows Server Update Services (WSUS) or your software distribution solution, such as System Center Configuration Manager.
| **Operating System** | **Updates** | | **Operating System** | **Updates** |
|----------------------|-----------------------------------------------------------------------------| |----------------------|-----------------------------------------------------------------------------|

2
windows/deployment/windows-autopilot/add-devices.md
View File

@ -61,7 +61,7 @@ Note that the hardware hash also contains details about when it was generated, s
### Collecting the hardware ID from existing devices using Microsoft Endpoint Configuration Manager ### Collecting the hardware ID from existing devices using Microsoft Endpoint Configuration Manager
Starting with Microsoft Endpoint Configuration Manager, the hardware hashes for existing Windows 10 version 1703 and higher devices are automatically collected by Configuration Manager. See the [What’s new in version 1802](https://docs.microsoft.com/configmgr/core/plan-design/changes/whats-new-in-version-1802#report-on-windows-autopilot-device-information) documentation for more details. The hash information can be extracted from Configuration Manager into a CSV file. Microsoft Endpoint Configuration Manager automaticaly collects the hardware hashes for existing Windows 10 devices. For more information, see . See the [What’s new in version 1802](https://docs.microsoft.com/configmgr/core/plan-design/changes/whats-new-in-version-1802#report-on-windows-autopilot-device-information) documentation for more details. The hash information can be extracted from Configuration Manager into a CSV file.
> [!Note] > [!Note]
> Before uploading the CSV file on Intune, please make sure that the first row contains the device serial number, Windows product ID, hardware hash, group tag, and assigned user. If there is header information on the top of CSV file, please delete that header information. See details at [Enroll Windows devices in Intune](https://docs.microsoft.com/intune/enrollment/enrollment-autopilot). > Before uploading the CSV file on Intune, please make sure that the first row contains the device serial number, Windows product ID, hardware hash, group tag, and assigned user. If there is header information on the top of CSV file, please delete that header information. See details at [Enroll Windows devices in Intune](https://docs.microsoft.com/intune/enrollment/enrollment-autopilot).