Despite our care and attention, despite our best efforts to design the perfect Exchange server environment, something will inevitably go wrong at some point. Whether it's an unintended configuration setting, faulty hardware, a change to a dependency, or—gasp—a bug in the product, something invariably happens to cause problems for end users and ultimately for us, the administrators.
So what do you do when the lights go out on the Exchange server, figuratively speaking? The goal of this chapter is to outline tried-and-true strategies for recovering an Exchange server as quickly as possible.
IN THIS CHAPTER, YOU WILL LEARN TO:
We can't overemphasize this key point: to troubleshoot Exchange Server, you have to understand the architecture. Understanding which functions of Exchange Server are controlled by which server roles is absolutely critical, or else you could spend a lot of time troubleshooting the wrong server.
Troubleshooting Exchange Server 2016 often involves collecting and reviewing information from a series of servers, rather than focusing on one. For example, a user complains that he isn't receiving new email. There are a number of possible causes for this: