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)

Configuring Database Availability Group network settings

The Exchange Management Shell includes several cmdlets that allow you to configure the network connections used by the servers in a DAG. After you have created the DAG networks, or after they've been added automatically by DAG network discovery, you can view the DAG networks and their settings, modify the replication configuration, or remove them completely. This recipe provides multiple examples of how you can perform all of these tasks from the shell.

In previous versions of Exchange, Microsoft recommended at least two networks for DAGs: one MAPI network for client connections, and one replication network. With Exchange 2016, multiple networks are still supported, but Microsoft's recommendation depends on the physical network topology. When there are multiple physical networks between DAG members that are physically...