Book Image

Microsoft Exchange Server 2013 PowerShell Cookbook: Second Edition - Second Edition

Book Image

Microsoft Exchange Server 2013 PowerShell Cookbook: Second Edition - Second Edition

Overview of this book

Microsoft Exchange Server 2013 is a complex messaging system. Windows PowerShell 3 can be used in conjunction with Exchange Server 2013 to automate and manage routine and complex tasks to save time, money, and eliminate errors.Microsoft Exchange Server 2013 PowerShell Cookbook: Second Edition offers more than 120 recipes and solutions to everyday problems and tasks encountered in the management and administration of Exchange Server. If you want to write scripts that help you create mailboxes, monitor server resources, and generate detailed reports, then this Cookbook is for you. This practical guide to Powershell and Exchange Server 2013 will help you automate and manage time-consuming and reoccurring tasks quickly and efficiently. Starting by going through key PowerShell concepts and the Exchange Management Shell, this book will get you automating tasks that used to take hours in no time.With practical recipes on the management of recipients and mailboxes as well as distribution groups and address lists, this book will save you countless hours on repetitive tasks. Diving deeper, you will then manage your mailbox database, client access, and your transport servers with simple but effective scripts.This book finishes with advanced recipes on Exchange Server problems such as server monitoring as well as maintaining high availability and security. If you want to control every aspect of Exchange Server 2013 and learn how to save time with PowerShell, then this cookbook is for you.
Table of Contents (23 chapters)
Microsoft Exchange Server 2013 PowerShell Cookbook
Credits
About the Authors
Acknowledgement
About the Reviewers
www.PacktPub.com
Preface
Index

Introduction


The Client Access Server (CAS) role was introduced in Exchange 2007 to provide a dedicated access point to various services such as Outlook Web Access (OWA), ActiveSync, POP3, and IMAP4 to clients. However, all MAPI clients could directly connect to the mailbox server role. The CAS role was extended even further in Exchange 2010 and included some new features, including functionality that will change the architecture of every Exchange deployment. At that time, the connections to public folders were still made by MAPI clients to the mailbox server role; connections from these clients to Exchange 2010 mailboxes were handled by the CAS role.

In this latest release, with Exchange 2013, Microsoft has simplified the CAS role. The CAS role is now stateless, which means that it does not save any data. Its job is more or less to help the clients to find a route for connecting to the mailbox or any required service, such as ActiveSync; in short, it is a proxy server. This major architectural...