Book Image

Microsoft Exchange Server 2016 PowerShell Cookbook - Fourth Edition

By : Jonas Andersson, Nuno Mota, Mike Pfeiffer
Book Image

Microsoft Exchange Server 2016 PowerShell Cookbook - Fourth Edition

By: Jonas Andersson, Nuno Mota, Mike Pfeiffer

Overview of this book

We start with a set of recipes on core PowerShell concepts. This will provide you with a foundation for the examples in the book. Next, you'll see how to implement some of the common exchange management shell tasks, so you can effectively write scripts with this latest release. You will then learn to manage Exchange recipients, automate recipient-related tasks in your environment, manage mailboxes, and understand distribution group management within the Exchange Management Shell. Moving on, we'll work through several scenarios where PowerShell scripting can be used to increase your efficiency when managing databases, which are the most critical resources in your Exchange environment. Towards the end, you'll discover how to achieve Exchange High Availability and how to secure your environment, monitor the health of Exchange, and integrate Exchange with Office Online Server, Skype for Business Server, and Exchange Online (Office 365). By the end of the book, you will be able to perform administrative tasks efficiently.
Table of Contents (17 chapters)

Checking the server health and health sets

Exchange includes two built-in health reporting cmdlets that can be used by administrators to perform a variety of tasks related to Managed Availability, such as viewing the health of a server or group of servers; viewing a list of health sets; viewing a list of probes, monitors, and responders associated with a health set; and viewing a list of monitors and their current health.

In this recipe, you will learn how to use the Shell together with these cmdlets to assess the health of an Exchange server.

How to do it...

To determine the health information and the see all the health sets of an Exchange server named TLEX1, you can run either of the following cmdlets:

    Get-ServerHealth...