Updated ExPDA Configuration XML File Released


On Tuesday we released an updated ExPDA configuration XML file designed to address the issues raised by you:

  1. Corrected the issue where ExPDA did not report that Exchange 2007 servers without Service Pack 2 were in the environment.
  2. Corrected an issue that identified Delivery Transport Agent connectors as EDK connectors.
  3. Corrected several rules that did not have proper titles to match their descriptions.

You have two ways to download the update:

  1. Launch ExPDA.  If you had selected to allow for automatic updates on startup, then ExPDA should detect the update and install it*.  If you did not select to enable automatic updates, you can select “Updates and Customer Feedback” from the left-hand navigation and click “Check for updates now”*.
  2. You can manually download the updated configuration file and place it into the %Program Files%\Microsoft\Exchange Server\V14\ExPDA\<language> directory

* In some instances, you may receive “an error occurred while trying to access the web”. If you receive this error, try launching ExPDA with elevated credentials (right-click the shortcut and select “Run as administrator”).  In addition, certain proxy configurations prevent the BPA engine from downloading updates, so if this does not work, proceed with manually downloading the XML file.

Thanks for using ExPDA and reporting these issues!

Ross Smith IV

Comments (3)
  1. Franc says:

    Three issues:

    – On Exchange 2010 it reports that no updates are available

    – On Exchange 2010 the folder mentioned (%Program Files%MicrosoftExchange ServerV14ExPDA<language>) doesn’t exist, on my installation the file is located in C:Program FilesMicrosoftExchange ServerV14Binen

    – The error about the invalid signature (Active Directory domain ‘SWV’ has an unrecognized Exchange signature. Current DomainPrep version: 12639) is still present.

  2. bday says:

    @Franc, this is for the new ExPDA tool and not the familiar ExBPA. That is why you’re not seeing this directly on an Exchange 2010 server:)

Comments are closed.