diff --git a/windows/deployment/update/device-health-get-started.md b/windows/deployment/update/device-health-get-started.md index 9df4b51c9b..7c8f74f2cc 100644 --- a/windows/deployment/update/device-health-get-started.md +++ b/windows/deployment/update/device-health-get-started.md @@ -5,6 +5,7 @@ keywords: Device Health, oms, operations management suite, prerequisites, requir ms.prod: w10 ms.mktglfcycl: deploy ms.sitesec: library +ms.date: 10/17/2017 ms.pagetype: deploy author: jaimeo --- diff --git a/windows/deployment/update/device-health-monitor.md b/windows/deployment/update/device-health-monitor.md index f620c80953..1d1ee3d3b6 100644 --- a/windows/deployment/update/device-health-monitor.md +++ b/windows/deployment/update/device-health-monitor.md @@ -5,6 +5,7 @@ keywords: oms, operations management suite, wdav, health, log analytics ms.prod: w10 ms.mktglfcycl: deploy ms.sitesec: library +ms.date: 10/17/2017 ms.pagetype: deploy author: jaimeo --- @@ -15,9 +16,9 @@ author: jaimeo Device Health is the newest Windows Analytics solution that complements the existing Upgrade Readiness and Update Compliance solutions by providing IT with reports on some common problems the end users might experience so they can be proactively remediated, thus saving support calls and improving end-user productivity. -Like Upgrade Readiness and Update Compliance, Device Health is a solution built within Operations Management Suite (OMS), a cloud-based monitoring and automation service that has a flexible servicing subscription based on data usage and retention. This preview release is free for customers to try and will not incur charges on your OMS workspace for its use. For more information about OMS, see [Operations Management Suite overview](http://azure.microsoft.com/en-us/documentation/articles/operations-management-suite-overview/). +Like Upgrade Readiness and Update Compliance, Device Health is a solution built within Operations Management Suite (OMS), a cloud-based monitoring and automation service that has a flexible servicing subscription based on data usage and retention. This release is free for customers to try and will not incur charges on your OMS workspace for its use. For more information about OMS, see [Operations Management Suite overview](http://azure.microsoft.com/en-us/documentation/articles/operations-management-suite-overview/). -Device Health uses Windows diagnostic data that is part of all Windows 10 devices. If you have already employed Upgrade Readiness or Update Compliance solutions, all you need to do is select Device Health (preview) from the OMS solution gallery and add it to your OMS workspace. Device Health requires enhanced telemetry, so you might need to implement this policy if you've not already done so. +Device Health uses Windows diagnostic data that is part of all Windows 10 devices. If you have already employed Upgrade Readiness or Update Compliance solutions, all you need to do is select Device Health from the OMS solution gallery and add it to your OMS workspace. Device Health requires enhanced telemetry, so you might need to implement this policy if you've not already done so. Device Health provides the following: @@ -34,6 +35,17 @@ See the following topics in this guide for detailed information about configurin An overview of the processes used by the Device Health solution is provided below. +## Device Health licensing + +Use of Windows Analytics Device Health requires one of the following licenses: + +- Windows 10 Enterprise E3 per-device with active Software Assurance +- Windows 10 Enterprise E3 or E5 per-device or per-user subscription (including Microsoft 365 F1, E3, or E5) +- Windows VDA E3 or E5 per-device or per-user subscription + +You don't have to install Windows 10 Enterprise on a per-device basis--you just need enough of the above licenses for the number of devices using Device Health. + + ## Device Health architecture The Device Health architecture and data flow is summarized by the following five-step process: diff --git a/windows/deployment/update/device-health-using.md b/windows/deployment/update/device-health-using.md index 9fa09d1431..5892aacc02 100644 --- a/windows/deployment/update/device-health-using.md +++ b/windows/deployment/update/device-health-using.md @@ -4,6 +4,7 @@ description: Explains how to begin usihg Device Health. ms.prod: w10 ms.mktglfcycl: deploy ms.sitesec: library +ms.date: 10/17/2017 ms.pagetype: deploy author: jaimeo --- diff --git a/windows/deployment/update/images/OMS-after-adding-solution.jpg b/windows/deployment/update/images/OMS-after-adding-solution.jpg index d06a896f6e..f3a5d855ff 100644 Binary files a/windows/deployment/update/images/OMS-after-adding-solution.jpg and b/windows/deployment/update/images/OMS-after-adding-solution.jpg differ diff --git a/windows/deployment/update/images/WIPNEW1-chart-selected-sterile.png b/windows/deployment/update/images/WIPNEW1-chart-selected-sterile.png index eb2cabdcfd..d093eff951 100644 Binary files a/windows/deployment/update/images/WIPNEW1-chart-selected-sterile.png and b/windows/deployment/update/images/WIPNEW1-chart-selected-sterile.png differ diff --git a/windows/deployment/update/images/WIPNEWMAIN-sterile.png b/windows/deployment/update/images/WIPNEWMAIN-sterile.png index 5efc5250c1..a210aa9ed1 100644 Binary files a/windows/deployment/update/images/WIPNEWMAIN-sterile.png and b/windows/deployment/update/images/WIPNEWMAIN-sterile.png differ diff --git a/windows/deployment/update/images/WIPappID-sterile.png b/windows/deployment/update/images/WIPappID-sterile.png index 43bad68ed0..e7b5ae5571 100644 Binary files a/windows/deployment/update/images/WIPappID-sterile.png and b/windows/deployment/update/images/WIPappID-sterile.png differ diff --git a/windows/deployment/update/images/dev-health-main-tile-sterile.png b/windows/deployment/update/images/dev-health-main-tile-sterile.png index 1619d8bf70..afe19b622e 100644 Binary files a/windows/deployment/update/images/dev-health-main-tile-sterile.png and b/windows/deployment/update/images/dev-health-main-tile-sterile.png differ diff --git a/windows/deployment/update/images/device-crash-history2-sterile.png b/windows/deployment/update/images/device-crash-history2-sterile.png index 18056ed801..e5a70f2d7d 100644 Binary files a/windows/deployment/update/images/device-crash-history2-sterile.png and b/windows/deployment/update/images/device-crash-history2-sterile.png differ diff --git a/windows/deployment/update/images/device-reliability2-sterile.png b/windows/deployment/update/images/device-reliability2-sterile.png index 28fbf3725b..bff4878fa3 100644 Binary files a/windows/deployment/update/images/device-reliability2-sterile.png and b/windows/deployment/update/images/device-reliability2-sterile.png differ diff --git a/windows/deployment/update/images/driver-detail-1-sterile.png b/windows/deployment/update/images/driver-detail-1-sterile.png index 7dcd86366f..03551d5783 100644 Binary files a/windows/deployment/update/images/driver-detail-1-sterile.png and b/windows/deployment/update/images/driver-detail-1-sterile.png differ diff --git a/windows/deployment/update/images/driver-detail-2-sterile.png b/windows/deployment/update/images/driver-detail-2-sterile.png index e5fa480c3e..66023722b3 100644 Binary files a/windows/deployment/update/images/driver-detail-2-sterile.png and b/windows/deployment/update/images/driver-detail-2-sterile.png differ