In an earlier article we looked at the New-MailboxImportRequest command, so in this post we’re going to examine the sibling command New-MailboxExportRequest. It stands to reason that there would be an Export version of this command to enable admins to easily export mailboxes to PST for archiving or discovery purposes, and the New-MailboxExportRequest command has a similar pedigree to the Import command, evolving the Export-Mailbox command and Exmerge before it. It also follows a similar pattern with regards to permissions, defaults, and supporting commands to let you perform an Exchange 2010 Export mailbox to PST operation.
With Exchange 2010 SP2 released, it’s past time for you to start putting all those old Exchange 2003 servers out to pasture, and any Exchange 2000 servers still hanging on out of their misery. The process to remove Exchange 2003 (or any other version) is not as simple as formatting the drive, but too often that is exactly what people do, and only then realize that to remove Exchange requires a process not too different from retiring a domain controller. In this post we will look at the process to remove Exchange Server from Active Directory and properly retire an old server, including the last legacy Exchange server your environment.
Exchange includes a great tool for checking on email messages called Exchange Message Tracking. Exchange 2010 message tracking enables administrators to consult Exchange 2010 message tracking logs to determine whether or not an email message was delivered, whether the message was between internal users, sent from an external user to an internal user, or sent from an internal user to an external address. Exchange 2010 message tracking is done using a browser-based tool which can be accessed through the Exchange Management Console or Exchange Control Panel through Outlook Web Access, and gives the Exchange admin a simple and quick-to-use interface for checking on email messages, whether they were sent from an internal user or to them from an external sender.