Remediation steps for the Configuration Manager management insights

Article
05/22/2023

Management insights in Microsoft Endpoint Configuration Manager provide information about the current state of your environment. Insights help you to better understand your environment and take action based on the insight. Use this article to learn more about insights and remediation steps from the view of a Microsoft Customer Engineer. The insights in this article are a small preview of the hundreds of checks that you can use from the Services Hub

For more information on other insights built in to Configuration Manager, see Management insights.

Reduce the number of applications and packages on distribution points

Microsoft officially supports a combined total of up to 10,000 packages and applications on a distribution point. Exceeding this total can lead to operational problems. For more information, see Size and scale numbers.

To determine the number of packages and applications distributed to a distribution point:

Open the Configuration Manager console.
Go to the Monitoring workspace.
Expand Distribution Status, and then select Distribution Point Configuration Status.
Select a distribution point.
At the bottom of the details pane, on the Summary tab, view the Completion Statistics. This data shows how many packages are distributed to the distribution point.

Update all sites to the same version

It's recommended to have the same version of Configuration Manager running on all site servers throughout your hierarchy. This practice increases the stability of your infrastructure. Maintaining this configuration also guarantees that you can use the same functionality throughout the hierarchy.

For more information, see Interoperability between different versions.

Heartbeat Discovery is disabled

Heartbeat discovery requires that you install the Configuration Manager client software on computers. It's also the only discovery method that clients start. (All other discovery methods run on site servers). Heartbeat discovery is essential to keep client activity status current. It makes sure that the site doesn't accidentally age out resource records from the Configuration Manager database.

To enable heartbeat discovery:

Open the Configuration Manager console.
Go to the Administration workspace.
Expand Hierarchy Configuration, and then select Discovery Methods.
Select Heartbeat Discovery for the target site, and then choose Properties in the ribbon.
Select the option to Enable Heartbeat Discovery.

For more information, see Heartbeat discovery.

Long running collection queries enabled for incremental updates

Collections with a last incremental refresh time higher than 30 seconds tie up site server and database resources. This configuration could potentially impact overall Configuration Manager performance.

To determine which collections have long running queries:

Run the Collection Evaluation Viewer (CEViewer) tool from the CD.Latest\SMSSETUP\Tools\ServerTools folder on the site server. For more information, see Collection Evaluation Viewer.
Connect to the relevant primary site.
Switch to the Incremental Evaluation tab.
Review the collections with the longest Run Time.
In the Configuration Manager console, adjust the membership rules of these collections.

Secondary site installation issues

You started the installation of one or more secondary site servers, but they didn't successfully complete. Until the secondary site installation successfully completes, clients at the secondary site don't properly communicate.

To identify secondary sites that are in a Pending or Failed state:

Check the installation status in the Configuration Manager console:
1. Open the Configuration Manager console.
2. Go to the Administration workspace.
3. Expand Site Configuration, then select Sites.
4. Select a secondary site server. On the Home tab of the ribbon, in the Site group, select Show Install Status.
Review the following Configuration Manager log files on the parent primary site for errors or more information:
1. Sitecomp.log
2. Hman.log
Check Configuration Manager logs on the secondary site. Check the following log files on the secondary site for errors or more information:
1. ConfigMgrSetup.log
2. ConfigMgrPrereq.log

For more information, see Retry installation of a failed update.

Tip

For more information on Configuration Manager log files including the default locations, see the following articles:

Active Directory System Discovery is configured to run too frequently

You typically don't need to configure Active Directory System Discovery to occur more frequently than every three hours. A more frequent configuration can have a negative performance impact on Active Directory, the network, and Configuration Manager. Enable incremental synchronization instead of using a full sync schedule.

To change the polling schedule for Active Directory System Discovery:

Open the Configuration Manager console.
Go to the Administration workspace.
Expand Hierarchy Configuration, and then select Discovery Methods.
Select Active Directory System Discovery for the target site, and then choose Properties in the ribbon.
Switch to the Polling Schedule tab.
If the full discovery polling schedule occurs more often than every three hours, it's too aggressive. Change the schedule to a less aggressive schedule. The recommended value is every seven days.

For more information, see Active Directory system discovery.

Active Directory Security Group Discovery is configured to run too frequently

You typically don't need to configure Active Directory Security Group Discovery to occur more frequently than every three hours. A more frequent configuration can have a negative performance impact on Active Directory, the network, and Configuration Manager. Enable incremental synchronization instead of using a full sync schedule.

To change the polling schedule for Active Directory Group Discovery:

Open the Configuration Manager console.
Go to the Administration workspace.
Expand Hierarchy Configuration, and then select Discovery Methods.
Select Active Directory Group Discovery for the target site, and then choose Properties in the ribbon.
Switch to the Polling Schedule tab.
If the full discovery polling schedule occurs more often than every three hours, it's too aggressive. Change the schedule to a less aggressive schedule. The recommended value is every seven days.

For more information, see Active Directory group discovery.

Active Directory User Discovery is configured to run too frequently

You typically don't need to configure Active Directory User Discovery to occur more frequently than every three hours. A more frequent configuration can have a negative performance impact on Active Directory, the network, and Configuration Manager. Enable incremental synchronization instead of using a full sync schedule.

To change the polling schedule for Active Directory User Discovery:

Open the Configuration Manager console.
Go to the Administration workspace.
Expand Hierarchy Configuration, and then select Discovery Methods.
Select Active Directory User Discovery for the target site, and then choose Properties in the ribbon.
Switch to the Polling Schedule tab.
If the full discovery polling schedule occurs more often than every three hours, it's too aggressive. Change the schedule to a less aggressive schedule.

For more information, see Active Directory user discovery.

Collections limited to All Systems or All Users

The All Systems and All Users collections include data from the Active Directory discovery methods, which may not include valid client information. Configuration Manager collections must be limited to the membership of another collection. When you use the All Systems or All Users as the limiting collection, this configuration can create data mismatch and inaccuracy of deployments.

Already a Microsoft Unified Support or Microsoft Premier customer?

To unlock the benefits of On-Demand Assessments, sign in to the Services Hub. For more information about Services Hub and Microsoft Support Offerings, see Support Solutions. To find out more, contact your local Microsoft representative.