Table of Contents Overview / PurposeTroubleshooting Export IssuesTypes of Export ErrorsTroubleshooting Export ErrorsPOSSIBLE RESOLUTIONSTESTING YOUR EXPORT PROCESSSEE ALSO
The purpose of this wiki is to provide guidance on how to troubleshoot export problems. The main focus here will be exporting to Active Directory where Microsoft Exchange 2007 / 2010 is involved. However, you can put these practices to use to help troubleshoot
exporting to other connected data sources.
We need to understand if we have provisioning enabled for Microsoft Exchange 2007 or Microsoft Exchange 2010 when exporting to Active Directory. This is important because of the steps involved in exporting to Microsoft Exchange 2007 and/or Microsoft Exchange
Microsoft Exchange 2007 and Microsoft Exchange 2010 no longer utilize the Recipient Update Services (RUS) that previous versions of Microsoft Exchange utilized. Microsoft Exchange 2007 and Microsoft Exchange 2010 utilize a Microsoft Exchange PowerShell
CMDLET called Update-Recipient (
2007 / 2010
). How we call Update-Recipient (
2007 / 2010
) varies between the two Microsoft Exchange Servers.
Microsoft Exchange 2007 we call Update-Recipient locally on the Synchronization Service Server. This is the reason that the Microsoft Exchange 2007 Management Tools SP1 or later (preferred SP3) is installed on the Synchronization Service Server.
Microsoft Exchange 2010, we make a remote call from the Synchronization Service Server to the Microsoft Exchange 2010 Server using WinRM.
If you do not have a testing process to test your exports prior to executing the export in production, then I would recommend the following