corrections to get-started and add-devices

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

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
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 [Whats 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 [Whats 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]
> 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).