Microsoft Exchange Message Export and Import

I had faced a strange Microsoft Exchange issue last week, messages were getting stuck in the submission queue of an Exchange 2010 SP3 Hub Transport server possibly due to an issue on the Transport Rule Agent.

While troubleshooting the issue, since there were a lot of messages in the queue, around two thousands, I decided to export them and import them on the second Hub Transport server.

In order to export the messages I used the following command:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
$messages = Get-Message -Queue "EXCHANGESERVER\Submission"
ForEach($m in $messages)
{
    $Temp = "C:\Messages\" + $m.InternetMessageID + ".eml"
    $Temp = $Temp.Replace("<","_")
    $Temp = $Temp.Replace(">","_")
    $Temp = $Temp.Replace("\\","_")
    Export-Message $m.Identity |
        AssembleMessage -Path $Temp
}

 I used the Get-Message cmdlet to get all the messages in the server's submission queue and then exported each message to a file in the c:\messages folder.

Make sure you have enough disk space in the disk where you are going to export the messages!

When the export is completed, you can copy the messages to the Pickup directory on another Hub Transport server and Exchange will pick them up and send them. You do not have to remove the messages from the queue since they will not be delivered again if the service is restored, but I usually do so.

To avoid searching the internet for the pickup folder path, you may find it in the TransportRoles directory in the Exchange Server program files installation path.

One more thing, when importing the messages on the server, I always start with a few messages and wait to see what happened on the message tracking log and if everything is OK, I release more messages.

Popular posts from this blog

Domain Controller Machine Password Reset

Image
On my lab environment, I've configured two Active Directory sites since most enterprises have offices in more that one places. My lab however is not running 24/7 and the domain controllers in the second site are rarely turned on in order to save resources. This leads to issues with the Active Directory replication such as the "The target principal name is incorrect" error when I execute:  repadmin /syncall /AdeP. To remedy the issue, we have to reset the machine password of the domain controller that has been offline. First off, we are going to stop and disable the Kerberos Key Distribution Center (kdc) service on the problematic domain controller, in our case DC4. There may be some tickets in the cache so we should also clear them using klist purge Now it's time to change the machine password of the domain controller using the command netdom resetpwd /s:dc3 /ud:lab\administrator /pd:* Replace the "lab\administrator" with an account on your
Keep reading

Configuring a Certificate on Exchange Receive Connector

Today's article is about configuring Exchange receive connectors with specific certificates. Out of the box, Exchange uses self signed certificates to provide TLS secured mail flow. This will definitely be an issue if you expose the SMTP protocol to client computers since they won't trust the certificate. In this article we are going to configure a certificate that was issued by a third part authority to the Client Frontend receive connector. We'll start with getting the thumbprint of the certificate using the Get-ExchangeCertificate cmdlet: [PS] C:\> Get-ExchangeCertificate Thumbprint                               Subject ----------                               ------- 241B864DC82C664FECBA18B8D54987AAFB65B4C2 CN=*.lab.com, ... D4D210886B34E690191A1F008C78FDD0E7325DD4 CN=Exchange2013A 960171662EB261162F9C8CBE12E0B75D6F06ABB0 CN=Microsoft Exchange Server Auth Certificate 2690324B827A9F2B75D59104F81CAAA57CDD627B CN=WMSvc-Exchange2013A [PS]
Keep reading

Running Multiple NGINX Ingress Controllers in AKS

Image
In some of the previous articles of this blog, we went through the process of installing NGINX as the Ingress Controller in AKS clusters. Either for applications that should be available directly from the public internet, or for applications that should only be accessed from networks considered internal. In the majority of the cases, however, and given that an AKS cluster is an environment that is designed to host multiple applications and provide economy at scale, additional ingress controllers may be required. In this post, we're going to go through the process of deploying an additional NGINX ingress controller that is going to be used for internal applications. The below diagram depicts the desired outcome: The Angular application is published via the public NGINX through the Azure Load Balancer that has been assigned a public IP. The .NET app is published by a different set of NGINX pods that are deployed in a different namespace and their ingress controller service is connect
Keep reading