Hi IT Pros,
Microsoft has just released Endpoint Manager – Endpoint Analytics. It is a cool feature, addressing service desk long time need to monitor and identify the devices which have delay sign-in time and performance issue even before Users make the support calls for help.
I have collected all the information related to setup, operation, troubleshooting of Endpoint Analytics and created this blog article for your reference.
Let’s review and enjoy our new EA feature exploration.
It is common for end users to experience long boot times or other disruptions. These disruptions can be due to a combination of:
Endpoint analytics, which was released on September 22nd, 2020, aims to improve user productivity and reduce IT support costs by providing insights into the user experience.
Endpoint Analytics structure
You can enroll devices via Configuration Manager or Microsoft Intune.
You can enroll devices via Configuration Manager or Microsoft Intune.
Click on link as shown:
Enable Endpoint Analytics in SCCM Console\Cloud Services\Co-Management
\Configure upload
Enable Endpoint Analytics data collection: Yes
Set baseline to observe progress made in a period.
Baseline management
Endpoint Analytics Overview
- If the Apply Group Policy permission is not set, but the Read permission is, the GPO is still inspected (although not applied) by any user or computer that is in the OU hierarchy where the GPO is linked.
This inspection process increases logon time slightly for each GPO with read access still set after removal of the Apply Group Policy permission.
Solution: remove unassigned group from Delegation (permission) tab
- Use WMI filters primarily for exception management only. WMI filters are evaluated every time Group Policy is processed, make sure WMI query time is fast, it increases startup and logon time
Solution: Limit use of WMI filter and make WMI query run efficiently.
- Broken Policy link result in failed applying policy process with timeout delay.
- Corruption of Sysvol\domain policies could cause big delay and need to be fixed on DFS replication end. The example of policies in Sysvol of a Domain Controller:
Solution: Fixing DFS replication for domain policies.
There are 2 built-in script packages:
You could create your own script package which includes detection script and remediation script, it is similar to SCCM Configuration Item with Compliance rule and SCCM Baseline Remediation, script example shown in the image:
The example results of Proactive remediation script running, is shown in the following image:
The infrastructure software recommended for the whole corporation environment such as Windows 10, Azure Active Directory, Cloud Management, …
Application reliability provide the important information about applications' s performance, how many crash times of each application during the last 14 days, mean time to failure and reliability score (the higher number is better). The feature also provide information about application usage and the number of devices with the installed application.
Solution:
Prerequisites for Intune managed devices
Prerequisites for Configuration Manager managed devices
Prerequisites for Proactive remediations
check Resultant client settings if there is an overriding client setting and endpoint analytics is disabled.
0x87D00321 is a script execution timeout error. This error typically occurs with machines that are connected remotely. A potential mitigation might be to only deploy to a dynamic collection of machines that have internal network connectivity.
Errors in the Dataldr.log file:
Begin transaction: Machine=<machine>
*** [23000][2627][Microsoft][SQL Server Native Client 11.0][SQL Server]Violation of PRIMARY KEY constraint 'BROWSER_USAGE_HIST_PK'. Cannot insert duplicate key in object 'dbo.BROWSER_USAGE_HIST'. The duplicate key value is (XXXX, Y). : dbo.dBROWSER_USAGE_DATA
ERROR - SQL Error in
ERROR - is NOT retyrable.
Rollback transaction: XXXX
Mitigation: Disable the collection of the Browser Usage (SMS_BrowerUsage) hardware inventory class. This class is not currently leveraged by Endpoint analytics.
If the option Enforce script signature check is enabled in the Settings page of creating a script package, then make sure that the scripts are encoded in UTF-8 not UTF-8 BOM.
This release is just the beginning. Microsoft will be rapidly rolling out new insights for other key user-experiences soon after the initial release.
___________________
Disclaimer
The sample scripts are not supported under any Microsoft standard support program or service. The sample scripts are provided AS IS without warranty of any kind. Microsoft further disclaims all implied warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample scripts and documentation remains with you. In no event shall Microsoft, its authors, or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample scripts or documentation, even if Microsoft has been advised of the possibility of such damages.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.