From 6c3abbc92185c0b4b4f11bf45be62d456f1afcfe Mon Sep 17 00:00:00 2001 From: jaimeo Date: Tue, 11 Jul 2017 10:48:02 -0700 Subject: [PATCH] a few more wording tweaks --- windows/deployment/update/device-health-get-started.md | 2 +- windows/deployment/update/device-health-using.md | 3 +++ 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/windows/deployment/update/device-health-get-started.md b/windows/deployment/update/device-health-get-started.md index cf56e5db49..9f6c14c11a 100644 --- a/windows/deployment/update/device-health-get-started.md +++ b/windows/deployment/update/device-health-get-started.md @@ -32,7 +32,7 @@ Windows Error Reporting | watson.telemetry.microsoft.com Online Crash Analysis | oca.telemetry.microsoft.com >[!NOTE] -> If your deployment includes devices running Windows 10 versions prior to Windows 10, version 1703, you must bypass authentication for the endpoints in Step 3. Windows Error Reporting did not support authenticating proxies until Windows 10, version 1703. +> If your deployment includes devices running Windows 10 versions prior to Windows 10, version 1703, you must **exclude** authentication for the endpoints listed in Step 3. Windows Error Reporting did not support authenticating proxies until Windows 10, version 1703. See [Configure Windows telemetry in your organization](/windows/configuration/configure-windows-telemetry-in-your-organization) for steps to exclude these endpoints. ## Add Device Health to Microsoft Operations Management Suite diff --git a/windows/deployment/update/device-health-using.md b/windows/deployment/update/device-health-using.md index 07c5d01867..259ff56bc7 100644 --- a/windows/deployment/update/device-health-using.md +++ b/windows/deployment/update/device-health-using.md @@ -45,6 +45,9 @@ Clicking the Frequently Crashing Devices blade opens a reliability perspective v In this view, you can click a particular device to see the details of that particular device and for each crash recorded on it. (You can also reach this view by clicking a particular device on the Frequently Crashing Devices blade.) +>[!NOTE] +> Use caution when interpreting results filtered by model or operating system version. This is very useful for troubleshooting, but might not be accurate for *comparisons* because the crashes displayed could be of different types. + ![Device detail and history](images/device-crash-history.png)