Test Layout

The first thing to be aware of when creating shared mailboxes in a hybrid deployment is security. Sharing mailboxes between on-premises and O365 is not supported. So, if a group of people need to share a mailbox then their mailboxes all need to be on-premises or all in O365. On-Premises Shared Mailboxes Creating an on-premises shared mailbox is pretty straight forward. Create the shared mailbox in the on-premises Exchange and it all works. In Exchange 2013, shared mailboxes are explicitly listed as a recipient type in the Exchange admin center (EAC). You can create and manage the shared mailboxes there. In Exchange 2010, shared mailboxes are not part of the Exchange Management Console (EMC). You need to create the shared mailbox by using the New-Mailbox cmdlet in the Exchange Management Shell (EMS). For example: New-Mailbox HelpDesk -shared -UserPrincipalName HelpDesk@MyDomain.com After creating the shared mailbox in Exchange 2010, you need to give users permission to access it. Assign

Exchange Server 2010 had a graphical utility for analyzing message tracking logs. Unfortunately, this tool was removed from Exchange Server 2013. Instead in Exchange Server 2013, you have only the Get-MessageTrackingLog cmdlet. The Get-MessageTrackingLog cmdlet is a pain in the butt for a few reasons: You need to memorize the syntax . Most of it is pretty straight forward, but you need to remember the correct parameters for searching by sender, recipient, or subject. It only searches the local server by default . Without specifying servers, it only searches the local Exchange server that you're running the tool on. In a lot of cases, you need to see information from all your servers to track it down. While working on a message delivery problem this week, I wrote up a short script help with simple message tracking based on time, sender, recipient, or message subject. The script is as follows: Write-Host "Current Date/Time: $(Get-Date)" $StartTime = Read-Host "Start