Crashes (Blue Screens, etc) aren't currently surfaced centrally in the reporting section of InTune.
It would be useful to have a view across all endpoints about common crashes to help better manage software rollouts and updates.
This is like the Startup Performance remediation, except it's User Quality of Experience instead.39 votes
When you schedule a proactive remediation package, by default the time is 1:00:00 AM.
It could be useful to have a checkbox "Run now" or "Run ASAP" allowing us to un the script directly instead of waiting.
If you create quickly the package and don't pay attention to the schedule part, you can wait a while before it will run.3 votes
I think right now both of them have seperate portal. Would be great if we can have a single console to access both of these.
Also their integration with log analytics.3 votes
It could be useful to have a button that allows us to export the result from the device status part in Endpoint Analytics Remediation scripts.3 votes
It would be much more user friendly if Endpoint Analytics showed
ThinkPad T490 instead of 20N3S70500
or ThinkPad E495 instead of 20NES01600
in all Model performance related views. The exact model code can be shown if needed.
Even though, this is caused by Lenovo's own stupid way of showing their models from WMI, Endpoint Analytics should be smart enough to show more meaningful model names. Lenovo is very popular vendor within enterprises.3 votes
When you select a specific device from Endpoint Analytics --> Startup performance --> Device performance, in "OS restart history" view, you see the date & OS version of the startup.
It would be very useful to see the full OS version build in this view. Now you see e.g.
10.0.18363, but you should see: 10.0.18363.1171.
Thus, you could easily see when a specific CU was installed. From "Boot history" chart you see when a CU is installed, but that doesn't tell you which CU.2 votes
Endpoint analytics is in preview. I suggest adding support for applicability similar to what you have in SCCM compliance settings - configuration item - detection method.
For example, if you do not have Office365 installed, it should ideally be a column in Endpoint analytics saying "Not Applicable". You would need to expand with a separate script in addition to the script you already have for detection and remediation or support additional exit code.
Other examples include BIOS settings, they would be vendor specific.1 vote
Would it be possible to have baseline and all the endpoint analytics information scoped to a set of devices. Maybe like a security group so that we can seperate the information that is shown to the IT group who can take action on them and see how it improves.1 vote
Endpoint Analytics overview page should have the following info:
1) When the data was last updated. Like that you see in Desktop Analytics
2) Number of clients who have reported info1 vote
Microsoft receives telemetry across the Windows line, desktop and server. With the introduction of Endpoint Analytics, it would be great if Microsoft combined that with the ingestion of local app, system logs, to find and help remediate Microsoft and third-party application issues.
Similar to Operations Management packs, but instead sent to Intune, combined with signals from other tenants/clients, offering analytics and solutions to errors.1 vote
- Don't see your idea?