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

incorped more comments

Browse Source
This commit is contained in:
jaimeo
2017-07-11 09:15:33 -07:00
parent f364a24828
commit 62a125a24b
3 changed files with 21 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
windows/deployment/update/device-health-get-started.md
View File

@ -31,17 +31,17 @@ Connected User Experience and Telemetry component | v10.vortex-win.data.microsof
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 RS2, you must bypass authentication for the endpoints in Step 3. Windows Error Reporting did not support authenticating proxies until Windows 10 RS2.
>[!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.
## Add Device Health to Microsoft Operations Management Suite
Device Health is offered as a solution in the Microsoft Operations Management Suite (OMS), a collection of cloud-based servicing for monitoring and automating your on-premise and cloud environments. For more information about OMS, see [Operations Management Suite overview](https://azure.microsoft.com/en-us/documentation/articles/operations-management-suite-overview/).
If you are already using OMS, you’ll find Device Health in the Solutions Gallery. Select the **Device Health** tile in the gallery and then click **Add** on the solution's details page. Device Health is now visible in your workspace.
**If you are already using OMS**, you’ll find Device Health in the Solutions Gallery. Select the **Device Health** tile in the gallery and then click **Add** on the solution's details page. Device Health is now visible in your workspace.
If you are not yet using OMS, use the following steps to subscribe to OMS Device Health:
**If you are not yet using OMS**, use the following steps to subscribe to OMS Device Health:
1. Go to [Operations Management Suite](https://www.microsoft.com/en-us/cloud-platform/operations-management-suite) on Microsoft.com and click **Sign in**.
@ -116,5 +116,5 @@ In order for your devices to show up in Windows Analytics: Device Health, they m
## Related topics
[Use Device Health to monitor Windows Updates](device-health-using.md)
[Use Device Health to monitor Windows Updates](device-health-using.md)<BR>
For the latest information on Windows Analytics, including new features and usage tips, see the [Windows Analytics blog](https://blogs.technet.microsoft.com/upgradeanalytics)

16
windows/deployment/update/device-health-monitor.md
View File

@ -13,17 +13,19 @@ author: jaimeo
## Introduction
With Windows 10, organizations need to change the way they approach monitoring client computers and other devices in their deployments. 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.
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. 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 the Windows telemetry 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 does use 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 (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 provides the following:
- [ADDITIONAL SUMMARY BULLETS?]
- Cloud-connected access utilizing Windows 10 telemetry means no need for new complex, customized infrastructure
- Identification of devices that crash frequently, and therefore might need to be rebuilt or replaced
- Identification of device drivers that are causing device crashes, with suggestions of alternative versions of those drivers that might reduce the number of crashes
- Notification of Windows Information Protection misconfigurations that send prompts to end users
- No need for new complex customized infrastructure, thanks to cloud-connected access using Windows 10 telemetry
See the following topics in this guide for detailed information about configuring and using the Device Health solution:
@ -42,7 +44,7 @@ The Device Health architecture and data flow is summarized by the following five
**(2)** Telemetry data is analyzed by the Device Health Data Service.<BR>
**(3)** Telemetry data is pushed from the Device Health Data Service to your OMS workspace.<BR>
**(4)** Telemetry data is available in the Device Health solution.<BR>
**(5)** You are able to monitor and troubleshoot Windows updates and Windows Defender AV in your environment.<BR>
**(5)** You are now able to proactively monitor Device Health issues in your environment.<BR>
These steps are illustrated in following diagram:
@ -56,6 +58,8 @@ These steps are illustrated in following diagram:
 
## Related topics
[Get started with Device Health](device-health-get-started.md)<BR>
[Get started with Device Health](device-health-get-started.md)
[Use Device Health to monitor Windows Updates](device-health-using.md)
For the latest information on Windows Analytics, including new features and usage tips, see the [Windows Analytics blog](https://blogs.technet.microsoft.com/upgradeanalytics)

11
windows/deployment/update/device-health-using.md
View File

@ -40,16 +40,18 @@ This middle blade in Device Health displays the devices that crash most often. S
Clicking the Frequently Crashing Devices blade opens a reliability perspective view, where you can filter data using filters in the left pane, see trends, and compare to commercial averages:
![Reliability perspective](images/reliability-perspective.png)
![Reliability perspective](images/reliability-perspective2.png)
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.)
[FROM MARC: I'd remove descriptions; it is meant to be self-explanatory. The one thing I would add is the tip on how to get rid of a filter. E.g, if you select "Model=XXX" and apply (as mentioned before picture), their is no visual way to remove that filter. You have to notice that they query up top has changed to append (Model=XXX) - and you need to edit the query to remove that. MSIT stumbled on this and suggested we document it, so let's do that!]
![Device detail and history](images/device-crash-history.png)
This displays device records sorted by date and crash details by failure ID, also sorted by date.
>[!TIP]
>Once you've applied a filter, for example by clicking a particular model or computer name in the left pane, you can remove the applied filter by manually editing the query. For example, in the device detail screenshot above, the results are filtered to a particular computer named "joes-pc". Remove the filter focusing on that one computer, just delete the string "joes-pc" in the query.
### Driver Induced OS Crashes
@ -73,8 +75,6 @@ The records are sorted by the time generated and the computer. If a driver has c
![Additional driver detail and history](images/driver-deeper-detail.png)
[DEFINITIONS TABLE?]
[ONENOTE DESCRIBES CLICKTHROUGH BEHAVIOR THAT SEEMS LIKE IT'S SUPPOSED TO CHANGE FOR PUBLIC VERSION?]
## Windows Information Protection
@ -144,5 +144,6 @@ OMS enables you to export data to other tools. To do this, in any view that show
## Related topics
[Get started with Update Compliance](update-compliance-get-started.md)
[Get started with Update Compliance](update-compliance-get-started.md)<BR>
For the latest information on Windows Analytics, including new features and usage tips, see the [Windows Analytics blog](https://blogs.technet.microsoft.com/upgradeanalytics)