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
ExBPA.Readiness.xml
* 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
ORIGINAL POST :
The Exchange Pre-Deployment Analyzer performs an overall topology readiness scan of your environment and provides you with a list of decisions that need to be made before you deploy Exchange Server 2010.
You can use the Exchange Pre-Deployment Analyzer to perform an overall topology readiness scan of your environment. When you run the Exchange Pre-Deployment Analyzer, it provides a detailed report that will alert you if there are any issues within your organization, which could prevent you from deploying Exchange 2010. For example, the Exchange Pre-Deployment Analyzer will notify you if you haven't deployed the minimum required Exchange service pack on all your existing Exchange servers.
The checks performed by ExPDA are similar to the pre-requisite checks implemented (via Exchange Best Practices Analyzer) in the Exchange 2010 Setup program; in fact ExPDA is based off the Exchange Best Practices Analyzer (ExBPA) engine. However, unlike Exchange 2010 setup, this tool focuses only on overall topology readiness and not the ability to run Exchange 2010 on the local computer. The scan also performs a deep analysis of each existing Exchange 2003/2007 server to verify that it has the necessary updates and configuration in-place to support Exchange 2010. The end report is structured as follows:
- Critical - A configuration problem that will prevent Exchange 2010 from being deployed in the organization. For example, the Active Directory Forest is not operating in Windows Server 2003 Forest Functional Mode or higher.
- Warning - A configuration item that may prevent customers having the best possible experience with Exchange 2010. A warning may also reflect some functionality that is not available in Exchange 2010.
ExPDA is another component in our vision to provide a seamless upgrade experience that reduces the complexities in deploying Exchange 2010. To start planning your upgrade, please utilize the Exchange Deployment Assistant. The Deployment Assistant allows a customer to create Exchange 2010 on-premises deployment instructions that are customized to their environment. The Assistant asks a small set of questions, and based on the answers, it provides a finite set of instructions that are designed to get a customer up and running on Exchange 2010. Running the Exchange Server Pre-Deployment Analyzer is now a recommended step within the pre-requisites section of the Deployment Assistant.
Download location :
Kind regards,
João Ribeiro
Comments
- Anonymous
May 05, 2010
Thanks a ton for the article. A Google search for "error when trying to access the web" turned up your page, and its excellent advice to run as administrator.