Microsoft Exchange Server Profile Analyzer

Overview

Use the Microsoft Exchange Server Profile Analyzer tool to collect estimated statistical information from a single mailbox store or across an Exchange Server organization. The collected data can be used for such tasks as analyzing the performance and health of a server that has mailboxes, improving capacity planning models, and improving testing methodologies and tools.
Prior to upgrading to this version, users should backup the default Profile Analyzer configuration XML file if any customizations have been made.
Important Notice: The Microsoft Exchange Profile Analyzer tool collects information related to user activity on production mailbox systems and can be used to generate aggregate user profile statistics for sets of Exchange users. Before using the tool in a production environment, you may wish to ensure that your collection and use of this information is consistent with the privacy and other laws of your country.

32 bit get it here

64 bit get it here

Exchange Pre-Deployment Analyzer

Brief Description

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.

Overview

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.

get it here

Update Rollup 1 for Exchange Server 2010 (KB976573)

get it here

Issues that the update rollup fixes.

Update Rollup 1 for Exchange Server 2010 fixes the issues that are described in the following Microsoft Knowledge Base articles:

977439 (http://support.microsoft.com/kb/977439/ ) Exchange Server 2010 users cannot open certain attachments when they access their mailboxes by using Outlook Web App

977551 (http://support.microsoft.com/kb/977551/ ) Meeting requests that are sent to a room mailbox are not processed in Exchange Server 2010

977552 (http://support.microsoft.com/kb/977552/ ) Exchange RPC Client Access service crashes in the Handler.dll that is located on an Exchange 2010 Client Access service server

977553 (http://support.microsoft.com/kb/977553/ ) Exchange RPC Client Access service crashes in Parser.dll on the Exchange Server 2010 CAS server

977554 (http://support.microsoft.com/kb/977554/ ) The subject or body of a message that is hosted in an Exchange Server 2010 mailbox is not set as expected

977555 (http://support.microsoft.com/kb/977555/ ) The message body is inaccessible when the property conversion from PR_BODY_HTML to PR_BODY fails

977556 (http://support.microsoft.com/kb/977556/ ) The body text of an e-mail message is invisible after you create exceptions for a recurring appointment or for a recurring meeting by using a CDO application together with Exchange Server 2010

977557 (http://support.microsoft.com/kb/977557/ ) An E_FAIL error occurs when you create an exception to a meeting request by using a CDO application for a Microsoft Exchange Server 2010 mailbox

977558 (http://support.microsoft.com/kb/977558/ ) A folder name is not changed when you try to move and then rename the folder in an Exchange Server 2010 mailbox by using the CopyFolder method of the IMAPIFolder interface

977559 (http://support.microsoft.com/kb/977559/ ) The location of a meeting or an appointment is not updated on an Exchange Server 2010 mailbox

977560 (http://support.microsoft.com/kb/977560/ ) Update fails when you use a CDO application to update a recurrence task on Exchange Server 2010

977561 (http://support.microsoft.com/kb/977561/ ) VSS backup process stops responding when you try to perform a Volume Shadow Copy Service (VSS) backup for Exchange Server 2010 databases

Exchange Server Remote Connectivity Analyzer

Great tool for testing Remote connection to Exchange.

www.testexchangeconnectivity.com

info here

I vote for a tool like this for OCS remote connectivity, incl. AV, Webconference, ISA/reverse proxy etc.

I know that OCS and Edge server problems isn’t just the external firewall ports and external Certificate, problems can also be internal firewalls, Loadbalancer and internal certificate incl. OCS configuration. If a OCS tool like this just could test all the external configuration – certificate and ports / firewall on the Edge server this would be nice.

(but creating a tool for OCS edge might not be as easy as posting this blog)  …… :)

Exchange Server 2010 Beta VHD

Download this fully configured virtual machine of the latest release of Exchange Server 2010 Beta. Evaluate the new capabilities of Exchange Server 2010 Beta, which helps you achieve new levels of reliability and performance by delivering features that help to simplify your administration, protect your communications, and delight your users by meeting their demands for greater business mobility.

get it here