I’ve come across a handful of things that were especially irritating when using the export-mailbox cmdlet so I thought it might be good to share them here.

The first thing I ran into was:  “The specified module could not be found., error code: -1073282946″ Gosh, that sure is a helpful message.  Maybe it would be easier to troubleshoot if you told me what specified module you were looking for!  Ok, not to worry, I have run into this on more than one occasion and the common thread seems to be the installation or uninstallation of Outlook or the Exchange management tools.  To fix this error, simply open a command prompt (can also be done from PowerShell or EMS) and type fixmapi.  That’s it, no special parameters or crazy syntax, just fixmapi.

I should also point out that the previous module could not be found error message also in some cases caused the Exchange Management Shell to crash completely.  In these cases it also left NO traces of its crash in any event log that I could find.

Now the export-mailbox cmdlet should work right?  Well… not exactly…

Instead of a freshly exported PST file, I am greeted by another helpful error message “Failed to copy messages to the destination mailbox store with error MAPI or an unspecified service provider” the error message goes on and has some meaningless numbers associated with it, but you get the point.  There are a couple of causes for this but to my knowledge there is little information out there on how to fix it.

1. You may not have permissions to the mailbox.  If this is the case you need to run the Add-MailboxPermission cmdlet.  If you have never worked with this cmdlet then you may have found your solution.
2. The account that you are running the Export-Mailbox cmdlet with MUST have an Exchange mailbox itself.  I know this might sound silly, but it is not uncommon to have separate admin accounts separate from your normal user accounts that do not have mailboxes.
3. I have read on a couple of forums that using some of the more advanced features of the Export-Mailbox cmdlet, such as the -EndDate parameter will also cause this error.  Also from what I have read, there is currently no fix for this.  Again this is what I have read… your mileage may vary.

Hopefully these quick tips will help someone save a few hours of wasted time on trying to do something as simple as export a mailbox.

http://www.microsoft.com/downloads/details.aspx?familyid=3403d74e-8942-421b-8738-b3664559e46f&displaylang=en

Post – http://msexchangeteam.com/archive/2008/08/07/449501.aspx

Song – http://msexchangeteam.com/files/12/attachments/entry449511.aspx

This particular bit of EMS code will allow for the creation of an E-mail address policy called North America that is based on the Co or country attribute in Active Directory. Of course we have chosen United States, Canada, and Mexico for this particular one but you could easily modify the syntax to create an unlimited number of combinations.

New-EmailAddressPolicy -Name 'North America' -EnabledEmailAddressTemplates 'SMTP:@contoso.com' -RecipientFilter {((Co -eq 'United States') -or (Co -eq 'Canada') -or (Co -eq 'Mexico'))}

At this point don’t worry about getting fancy with the SMTP addresses. Once this new policy is created you can use the E-mail Address Policy wizard to customize the addresses. The important thing is that the recipient filter must be created via the EMS.

To create a new Edge subscription configuration file:
New-EdgeSubscription -FileName "C:\EdgeSubscription.xml"

To import the configuration file on a Hub Transport server:
New-EdgeSubscription -FileName "C:\EdgeSbuscription.xml" -CreateInternetSendConnector $true -CreateInboundSendConnector $true -site "Default-First-Site-Name" -Force

To force synchronization:
Start-EdgeSynchronization

Edge Synchronization Frequencies (not configurable)

1. Open the Exchange Management Shell
2. To view the policies:  get-EmailAddressPolicy
3. To upgrade the default policy:  set-EmailAddressPolicy "Default Policy" -IncludedRecipients AllRecipients
4. Depending on the filtering parameters of the remaining policies you can continue to use this command.  However, if the other policies contain advanced LDAP queries you will want to review the Exchange Team Blog.

Command:
Set-OutlookProvider expr -CertPrincipalName:"msstd:*.domain.com"

Verification:
Get-OutlookProvider |fl
Look for the property EXPR called CertPrincipalName

1. Open the Exchange Management Shell
2. Change directory to %SYSTEM DRIVE%\Program Files\Microsoft\Exchange Server\Scripts
3. ./install-AntispamAgents.ps1
4. Restart-Service MSExchangeTransport

You should now see an Anti-Spam tab in your Exchange Management Console.  Organization Configuration > Hub Transport > Anti-Spam.

http://exchange-genie.blogspot.com/2007/07/autodiscover-ad-attribute.html

1. Open the Exchange Management Console and navigate to Organization Configuration > Hub Transport
2. Change to the Transport Rules tab
3. Select the New Transport Rule action from the actions menu on the right
4. Give your new rule a descriptive name, click Next
5. Depending on your environment, you may wish to select different conditions on the conditions page.  Most configurations will use the “sent to users inside or outside the organization” condition
   • After selecting this condition change the Step 2 configuration by clicking on the Inside and changing it to Outside, click Next to proceed.
6. On the actions page we are again presented with lots of options, for this purpose we will choose the “append disclaimer text using font…” option.
   • We have to configure the disclaimer text in Step 2.  You can also change several options like font, text size, and text color.  When you are done, click Next to proceed.
7. For this example we will not add any exceptions, click Next to continue.
8. Review the settings on the Create Rule page, click New to apply this rule.