Let’s understand ConfigMgr Scenario Health Checks in this post. With the 2010 version of SCCM, the health check of some specific scenarios can be performed from the console. This mostly helps to monitor the health of end-to-end scenarios. Let’s take a look at the tasks included in each supported scenario check.
It helps to simulate activities to expose performance metrics and failure points. Monitoring scenario health helps to enhance awareness of system latency and component backlogs. You have only two scenarios available with ConfigMgr 2010 version.
I’m sure there will be a lot of health scenario health check items coming down in this section of monitoring for the future versions of Configuration Manager. I think this feature would be more helpful with Tenant Attach scenarios.
Introduction
Let’s learn more about Scenario Health options got introduced in the 2010 version of SCCM. Configuration Manager monitors the health for the following two scenarios:
- SQL Server Service Broker: Many of the core subsystems in Configuration Manager use the service broker.
- Client action health: Monitor the health of the fast channel used for client actions.
Prerequisites
To launch ConfigMgr Scenario Health, the admin needs to have a Full administrator role with scope to the top-level site.
Launch
You can navigate to scenario health from \Monitoring\Overview\Scenario Health.
Actions Available for Scenario Health
Let’s now check what are the actions available for scenario health options.
- Show Status – This shows the latest results of tests of the health check in a different window.
- Scenario Settings – Change the scenario health check configurations.
- History – This provides a history of health scenario activities.
- Run Now – This gives you the option to manually start a health check evaluation.
You can have three (3) actions for Scenario Settings.
- Enable activity simulation and measurement
- Run time interval (minute)
- Job timeout (minute)
SQL Server Service Broker Health Check Scenario
Let’s check what are tests included in the scenario health task called SQL Server Service Broker. The SQL Server Service Broker is one of the critical configurations required for the site database. Many of the core subsystems in ConfigMgr use the SQL service broker.
The following are 4 four of the tasks performed by SQL server service broker scenario health check. These health checks help to identify issues with the ConfigMgr site and this can be a big helping hand for troubleshooting scenarios.
- Ping all sites through SQL Server services broker– Sent a ping message to itself. If in a hierarchy, also sent a ping message to all other primary sites.
- Received ping message – Received the ping message, and sent back the acknowledgment message.
- Received acknowledgment message – If there is a long delay, it will impact the performance of many core features. Please check SQL server log files.
- Check if SQL server service broker queue ConfigMgrHMSQueue is enabled – If the queue is disabled, it will impact many core features. Please check SQL server log files.
Client Action Health Scenario
Monitor the health of the fast channel used for client actions using client action health checks from 2010 onwards. I think this client action health scenario feature would be more helpful with Tenant Attach scenarios and other cloud scenarios.
The following are 9(nine) of the tasks performed by the client action scenario health check. These health checks help to identify issues with the ConfigMgr client action and can be a big helping hand for troubleshooting scenarios.
- Created Client Action – The administration service created the client action.
- Processed Client Action – The site server processed the client action. Check objreplmgr.log for details.
- Backlog for inbox Backlog – Backlog for inbox objmgr.box: 0. If there’s a big backlog, it impacts how soon the client actions are sent to the clients. Check objreplmgr.log for details.
- Message Processing Engine Backlog – Backlog for the Message Processing Engine queue: 0. If there’s a big backlog, it impacts how soon the results for client actions are processed. Check the SMS_MESSAGE_PROCESSING_ENGINE.log for details.
- Management Point Client Action Backlog – Backlog for the SQL Server service broker queue ConfigMgrBGBQueue: 0. If there’s a big backlog, it impacts how soon the management point can push actions to the clients. For details, check the scenario health for the SQL Server service broker and the management point’s bgbserver.log.
- Client Action Result Summary – The summary task, [Calculate Client Operation Summary], ran successfully. Check statesys.log for details.
- Management Point Online Status – Management points not online for processing client actions: If management points aren’t online, it impacts how soon the client’s actions can be processed. For details, check the management point’s ccmexec.log, bgbsetup.log, and bgbserver.log.
- Client Health Summary – The summary task, [Client Health Scheduled Task], ran successfully. Check statesys.log for details.
- Client State System Inbox Backlog – Backlog for the inbox auth\statesys.box\incoming: 0. If there’s a big backlog, it impacts how soon the results for client actions are processed. Check the statesys.log for details.
Resources
- Troubleshoot SCCM Fast Channel Push Notification Issues
- FIX SCCM Client Issues Using Automation Client Health
- FIX SCCM SQL Based Database Replication Failure Between CAS Primary| ConfigMgr
Author
Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is a blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. E writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…