Book Image

Microsoft Exchange Server PowerShell Essentials

By : Biswanath Banerjee
Book Image

Microsoft Exchange Server PowerShell Essentials

By: Biswanath Banerjee

Overview of this book

PowerShell has become one of the most important skills in an Exchange administrator's armory. PowerShell has proved its mettle so widely that, if you're not already starting to learn PowerShell, then you're falling behind the industry. It isn't difficult to learn PowerShell at all. In fact, if you've ever run commands from a CMD prompt, then you'll be able to start using PowerShell straightaway. This book will walk you through the essentials of PowerShell in Microsoft Exchange Server and make sure you understand its nitty gritty effectively. You will first walk through the core concepts of PowerShell and their applications. This book discusses ways to automate tasks and activities that are performed by Exchange administrators and that otherwise take a lot of manual effort. Microsoft Exchange PowerShell Essentials will provide all the required details for Active Directory, System, and Exchange administrators to help them understand Windows PowerShell and build the required scripts to manage the Exchange Infrastructure.
Table of Contents (17 chapters)
Microsoft Exchange Server PowerShell Essentials
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Index

Understanding the EWS managed API


Let's take a quick peek into the EWS managed API 2.0 concepts before working on writing a basic client application:

  • Versioning: Using the EWS managed API, the client needs to set the version when creating an instance of the Exchange Service object. The client can then be made able to access the EWS managed API objects, properties, and methods that are available in this specific version. If the client tries to access an object, property, or method not supported by the version specified, an exception will be thrown.

  • Debugging: In order to debug applications that are created by the EWS-managed API, we need a combination of tools, such as network monitor tools, built into Visual Studio and internal tools such as network service tracing and logging tools. A part of your code application runs on a server and most of the developers do not have access to. But, you can take a look at the XML requests and responses exchanged between clients and servers to determine...