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
About the Author
About the Reviewer

Managing Message tracking logs

In Exchange Server 2013/2016, message tracking is enabled by default and you can use the Set-TransportService and Set-MailboxServer cmdlets to configure various message tracking configuration tasks. The tracking log files exist in the %ExchangeInstallPath%TransportRoles\Logs\MessageTracking folder.

Here are different log files created in this folder:


Transport service logs


Moderated transport logs for example, approvals and rejections if enabled


Logs messages delivered to mailboxes using the Mailbox Transport Delivery Service


Logs messages sent from mailboxes using the Mailbox Transport Submission service 

These logs are stored in the directory using the following naming convention MSGTRXMDyyyymmdd-nnnn.log where yyyymmdd is the coordinated Universal time when the log file is created, and nnnn is the instance number, which starts at 1 every day for each message-tracking log file named prefix. Exchange uses circular logging...