Device Health Public Preview now available

%3CLINGO-SUB%20id%3D%22lingo-sub-91862%22%20slang%3D%22en-US%22%3EDevice%20Health%20Public%20Preview%20now%20available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-91862%22%20slang%3D%22en-US%22%3E%3CP%3EDevice%20Health%2C%20the%20newest%20solution%20in%20the%20Windows%20Analytics%20suite%2C%20lets%20you%20know%20about%26nbsp%3Bcommon%20issues%20that%20your%20end%20users%20might%20experience%20so%20that%20you%20can%20proactively%20remediate%20those%20issues%20and%20prevent%20unnecessary%20support%20calls--for%20example%2C%20devices%20that%20crash%20frequently%20or%20specific%26nbsp%3Bdrivers%20that%20are%20causing%20crashes.%20As%20with%20other%20Windows%20Analytics%20solutions%20(Upgrade%20Readiness%2C%20Update%20Compliance)%2C%20you%20don't%20need%20a%20complex%20infrastructure%20to%20obtain%20this%20information.%20You%20just%20need%20to%20enable%20enhanced%20Windows%20telemetry%20and%20add%20Device%20Health%20to%20Microsoft%20Operations%20Management%20Suite.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHere%20is%20an%20example%20of%20how%20Device%20Health%20displays%20information%20on%20the%20devices%20that%20have%20crashed%20the%20most%20often%20in%20the%20past%20week%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Device-Health-jpg.jpg%22%20style%3D%22width%3A%20598px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F17993i7EE7423EAEE22F7E%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22Device-Health-jpg.jpg%22%20alt%3D%22Device-Health-jpg.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you're%20interested%20in%20trying%20Device%20Health%20today%2C%20see%20the%20%3CA%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Fupgradeanalytics%2F2017%2F07%2F31%2Fannouncing-device-health%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EPublic%20Preview%20announcement%3C%2FA%3E%20and%2C%20for%20detailed%20instructions%20on%20setup%26nbsp%3Bincluding%20prerequisites%2C%20see%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fdeployment%2Fupdate%2Fdevice-health-get-started%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EGet%20started%20with%20Device%20Health%3C%2FA%3E.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-93290%22%20slang%3D%22en-US%22%3ERe%3A%20Device%20Health%20Public%20Preview%20now%20available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-93290%22%20slang%3D%22en-US%22%3Eso%20the%20device%20has%20now%20received%20the%20ID%20and%20connected%20to%20our%20OMS.%3CBR%20%2F%3EBut%20took%20a%20while%20for%20the%20device%20to%20appear.%20Also%20I%20get%20the%20following%20error%20for%20Update%20Complaince%20%22Failed%20to%20locate%20component%20definition%20for%20id%3A%20UpdateComplianceSolutionTile%22%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-93077%22%20slang%3D%22en-US%22%3ERe%3A%20Device%20Health%20Public%20Preview%20now%20available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-93077%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20this%20feedback.%20I'll%20pass%20it%26nbsp%3Balong%20to%20the%20product%20team.%20The%20best%20way%20to%20submit%20feedback%20is%20through%20the%20Windows%2010%20Feedback%20Hub.%20Just%20look%20for%20the%20%22Windows%20Analytics%20for%20Enterprises%22%20category.%20You%20can%20also%20submit%20feedback%20through%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fdeployment%2Fupdate%2Fwaas-windows-insider-for-business-aad%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EWindows%20Insider%20Program%20for%20Business%3C%2FA%3E.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-92947%22%20slang%3D%22en-US%22%3ERe%3A%20Device%20Health%20Public%20Preview%20now%20available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-92947%22%20slang%3D%22en-US%22%3EHaving%20issues%20with%20this%20and%20trying%20to%20push%20to%20devices%20using%20Intune.%3CBR%20%2F%3EIntune%20shows%20that%20the%20custom%20policy%20has%20successfully%20applied%20but%2048%20hours%20later%20not%20relaying%20info%20to%20OMS.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-92252%22%20slang%3D%22en-US%22%3ERe%3A%20Device%20Health%20Public%20Preview%20now%20available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-92252%22%20slang%3D%22en-US%22%3EHave%20just%20pushed%20these%20WorkplaceID%20out%20to%20a%20subset%20of%20devices%20for%20testing.%3C%2FLINGO-BODY%3E
Community Manager

Device Health, the newest solution in the Windows Analytics suite, lets you know about common issues that your end users might experience so that you can proactively remediate those issues and prevent unnecessary support calls--for example, devices that crash frequently or specific drivers that are causing crashes. As with other Windows Analytics solutions (Upgrade Readiness, Update Compliance), you don't need a complex infrastructure to obtain this information. You just need to enable enhanced Windows telemetry and add Device Health to Microsoft Operations Management Suite.

 

Here is an example of how Device Health displays information on the devices that have crashed the most often in the past week:

 

Device-Health-jpg.jpg

 

If you're interested in trying Device Health today, see the Public Preview announcement and, for detailed instructions on setup including prerequisites, see Get started with Device Health.

4 Replies
Have just pushed these WorkplaceID out to a subset of devices for testing.
Having issues with this and trying to push to devices using Intune.
Intune shows that the custom policy has successfully applied but 48 hours later not relaying info to OMS.

Thanks for this feedback. I'll pass it along to the product team. The best way to submit feedback is through the Windows 10 Feedback Hub. Just look for the "Windows Analytics for Enterprises" category. You can also submit feedback through the Windows Insider Program for Business.

so the device has now received the ID and connected to our OMS.
But took a while for the device to appear. Also I get the following error for Update Complaince "Failed to locate component definition for id: UpdateComplianceSolutionTile"