Working with date specific PST exports using PowerShell

With all the various email archiving tools in place across the world, invariably in the world of Exchange consulting we get involved in lots of mass exports/ingestions of data to and from various services. One task which is performed often is exporting mail from Exchange mailboxes from a specific date range.

In order to do this, you first need to have the required permissions to actually export data from Exchange 2010/2013. This is not part of your permission set as a member of the Organisation Management role group (which some admins assume is an account with god level rights). So to begin with, we will run some commands to create a new custom role group, and then add ourselves into said role group. If you try and run the export commands and receive the following error, then you need to follow the below process to setup a new role group.

The term ‘New-MailboxExportRequest’ is not recognized as the name of a cmdlet, function, script file, or operable program.

Open up your Exchange Management Shell (as Administrator of course!), and run the following commands:

New-RoleGroup "Mailbox Import-Export Management" -Roles "Mailbox Import Export"
Add-RoleGroupMember "Mailbox Import-Export Management" -Member DavidD

You will now have the required permissions to allow you to run the New-MailboxExportRequest commands. By the way, this powershell command only became available as of Exchange 2010 SP1 so if you are mad enough to be running Exchange 2010 RTM, this command will not be available.

In order to have access to your lovely new cmdlets, you will need to close and reopen the Exchange Management Shell (as Administrator!). Now you can run the command as shown below, just tweak the settings marked in bold to get your desired effect 🙂 As a side note, the -lt stands for less than, and the -gt is greater than. You can also use -le, which is less or equal to, or -ge, which is greater or equal to.

New-MailboxExportRequest -ContentFilter {(Received -lt '01/04/2014') -and (Received -gt '12/02/2012')} -Mailbox "DavidD" -Name DavidDExport -FilePath \\myserver\pst\DavidDExport.pst

At this stage, I’d like to point out a little gotcha to do with this command. As I am in the UK, the servers I work on are configured with UK regional settings, including date and time. This means that dates are displayed in a DD/MM/Year format rather than the American MM/DD/Year format. If your regional settings reflect the UK configuration, then the trick is to use UK date format but never use a number above 12. So if you were to use 15/03/2015 (15th March 2015) this would queue the request but would fail after a minute or two with the error:

“The value “15/03/2015 00:00:00 AM” could not be converted to type System.DateTime.”

However if you use 12/03/2015 (12th March 2015) this would work and would export the correct date ranges. If you used 03/12/2015 in the UK, Exchange would think you meant the 3rd December 2015. Obviously if you are in the US this is not a problem, but I struggled with this in the UK. If anybody has seem differently or knows a way around this, please comment and let me know! My advice at the moment though is to use UK date formats, but never use a number above 12 for the day.

Once your request has started, you can run the below command to see the status of your request.


If your request shows a status of failed, use the below command to retrieve some useful information about the failure.

Get-MailboxExportRequestStatistics -Identity DavidD\DavidDExport

Hopefully this can get the ball rolling for you when attempting to export mail out of Exchange 2010/2013.

Thanks for reading!

2 thoughts on “Working with date specific PST exports using PowerShell

  1. mvcampos says:

    I am working on server with date in Portuguese (Brazil) format. dd/MM/yyyy.

    If I use the filter “(Received -lt ’01/26/2016′)” the ExportRequest is queued and fails after a while with the “ContentFilter is invalid…” error message. If I use “(Received -lt ’26/01/2016′)”, the Export request is not queued and it immediately displays the same error about not being able to convert to System.DateTime.

    I found it weird since it worked for me a few days ago, when I used Jan 12, but now that I recall, I tried Jan 13 and it failed, then I tried the day before (12) and worked. I now realize that it makes sense with your comment on your post: “but never use a number above 12 for the day”


  2. Keith Williams says:

    The workaround (if you don’t want to rely on days number less than 12) is to set the system locale to English (United States) and restart the server so that the Exchange Service uses English (United States) System Locale date format. And then simply use US date format.

    The issue really is that the Exchange Powershell interpreter/command for the Content filter in New-MailboxExportRequest only accepts dates in US format MM/DD/YYYY, while the underlying Exchange Service correctly uses the System in Locale which in my case is English (New Zealand), so it expects format DD/MM/YYYY.

    The result is that a command meant to export mail dated between 18 June and 21 June, say, as follows
    New-MailboxExportRequest -Mailbox xxxxx -ContentFilter {(Received -ge “18/06/2020”) -and (Received -le “21/06/2020”)} -Filepath “C:\Temp\Mailbox.pst”
    will generate an error
    The provided ContentFilter value is invalid. ContentFilter is invalid. The value “18/06/2020” cou
    type System.DateTime. –> The value “18/06/2020” could not be converted to type System.DateTime.
    + CategoryInfo : InvalidArgument: ((Received -ge “…e “21/06/2020”):String) [], Con
    + FullyQualifiedErrorId : 2DE689AB

    and if we specify the date in US format
    New-MailboxExportRequest -Mailbox xxxxx -ContentFilter {(Received -ge “06/18/2020”) -and (Received -le “06/21/2020”)} -Filepath “C:\Temp\Mailbox.pst”
    it is accepted by the Powershell interpreter, but the underlying Exchange service says it is invalid. Check by using
    Get-MailboxExportRequestStatistics -Identity | FL and the Message property will show
    Error: ContentFilter is invalid. The value “18/06/2020 12:00:00 a.m.” could not be converted to type System.DateTime. –> The value “18/06/2020 12:00:00 a.m.” could not be converted to type System.DateTime.


Leave a Reply to mvcampos Cancel reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s