Chapter 20. What to do when things go wrong

 

The full title of this chapter should be, “What to do when things go wrong and it’s not ConfigMgr’s fault, regardless of what anyone else says.” As you’ve seen over the course of this book, ConfigMgr depends on the wider technical environment for much of its own functionality, and sometimes things don’t work the way they’re supposed to.

ConfigMgr does a decent job of informing you when things aren’t going as well as they should be, so as you can see in figure 20.1, this chapter is all about listening carefully to what your environment is telling you.

Figure 20.1. Work out when ConfigMgr is telling you that something’s wrong.

We’ll also cover scenarios in which problems elsewhere in the environment could be causing problems for ConfigMgr. It’s by no means an exhaustive list, but it’ll give you a solid basis for more-advanced troubleshooting.

20.1. Assessing site health

ConfigMgr constantly monitors and assesses all roles and components within the hierarchy, and if you want to get a quick overview of the health of your environment, this is the place to start.

In the ConfigMgr console, navigate to Monitoring > System Status > Site Status. As shown in figure 20.2, this pane shows the health of all of the site system roles currently installed in the hierarchy.

Figure 20.2. ConfigMgr constantly monitors site role health.

20.2. Understanding common environmental issues

20.3. Labs