Chris’s Blog

Microsoft recently released the Exchange Pre-Deployment Analyzer. The Exchange Pre-Deployment Analyzer performs 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.

The checks performed by ExPDA are similar to the pre-requisite checks implemented (ExBPA) in the Exchange 2010 Setup program. 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.

For more information about the Exchange Pre-Deployment Analyzer (ExPDA), visit The Microsoft Exchange Team blog here

To download ExPDA, click here

I am often asked about virtualization when talking to my customers about Exchange. Virtualization has been a big thing in the industry for a while now, so it makes sense that many customers are looking to take advantage of the many benefits, including server consolidation. What does Microsoft support? Virtualization support has not changed much since Exchange Server 2007 SP1.

Microsoft supports Exchange Server in production on hardware virtualization software only when all the following conditions are true:

1. The hardware virtualization software is running:
   Windows Server 2008 with Hyper-V technology
   Windows Server 2008 R2 with Hyper-V technology
   Microsoft Hyper-V Server 2008
   Microsoft Hyper-V Server 2008 R2
   Any third-party hypervisor that has been validated under the Windows Server Virtualization Validation Program (SVVP).
2. The Exchange guest virtual machine:
   Is running Microsoft Exchange 2007 SP1 or Exchange 2010.
   Is deployed on the Windows Server 2008 and above
   Doesn’t have the Unified Messaging server role installed. All Exchange server roles, except for the Unified Messaging server role, are supported in a virtualization environment.
3. The storage used by the Exchange guest machine can be virtual storage of a fixed size, SCSI pass-through storage, or iSCSI storage. In a Hyper-V environment, each fixed VHD must be less than 2,040 GB.Virtual disks that dynamically expand or use differencing or delta mechanisms aren’t supported by Exchange.
4. Only management software can be deployed on the physical root machine. The root machine should be dedicated to running guest virtual machines.
5. Microsoft doesn’t support combining Exchange high availability solutions (SCC, CCR, DAGs) with hypervisor-based clustering, high availability, or migration solutions. DAGs are supported in hardware virtualization environments provided that the virtualization environment doesn’t employ clustered root servers.
6. Virtual machine snapshots of an Exchange guest virtual machine is not supported.
7. Exchange supports a virtual processor-to-logical processor ratio no greater than 2:1. For example, a dual processor system using quad core processors contains a total of 8 logical processors in the host system. On a system with this configuration, do not allocate more than a total of 16 virtual processors to all guest virtual machines combined.
8. The operating system for an Exchange guest machine must use a fixed sized disk that has a minimum size equal to 15 GB plus the size of the virtual memory that’s allocated to the guest machine. This requirement is necessary to account for the operating system and paging file disk requirements.

For more detailed information on Exchange Server Virtualization see the following Technet documentation:

• Microsoft Support Policies and Recommendations for Exchange Servers in Hardware Virtualization Environments
• Exchange 2010 System Requirements
• Microsoft server software and supported virtualization environments

“Gartner, Inc. has highlighted the key predictions that herald long-term changes in approach for IT organizations and the people they serve for 2010 and beyond. Gartner’s top predictions for 2010 showcase the trends and events that will change the nature of business today and beyond..”

Its a fascinating read, find the full article here

Microsoft have announced the release of Update Rollup 1 for Exchange Server 2010.

For more information about the rollup and to download it see Article ID: 976573

About a month ago I wrote a short post about how customers using Exchange 2010 are also able to make use of DAG’s for high availability provided that they are using Windows Server 2008 Enterprise edition.

The first question that then comes to mind is: “Why would I need Exchange 2010 Enterprise edition then?”. Standard edition is designed for the mailbox needs of small to medium organizations and is also appropriate for non-mailbox roles in a larger Exchange deployment while Enterprise edition is ideal for larger organizations that may require a greater number of mailbox databases.

The following table provides a feature breakdown for each server edition of Exchange Server 2010:

Now that Exchange 2010 has been officially launched and made available, I’m sure many organisations are already thinking about or planning their deployment. I my opinion, this will be especially true for those who still have Exchange 2003 deployed.

Microsoft have once again stepped up and just when you thought they’ve outdone themselves, they announce the release of the Exchange Server 2010 Deployment Assistant. This awesome tool is a result of feedback from the early adopters of Exchange 2010 and of course Microsoft wanting to help streamline the experience of deploying Exchange 2010.

The current version offers the Upgrade from Exchange 2003 scenario.Once the deployment scenario is selected, you are taken through a series of questions and then presented with a list of steps to complete. Each step has a huge amount of valuable information to guide you through your deployment.

Additional scenarios will be available in early 2010, these include:

• Upgrade from Exchange 2007
• Upgrade from Exchange 2003/2007
• New installation of Exchange 2010

The Exchange Server 2010 Deployment Assistant can be found here

Kevin Allison, GM Exchange Customer Experience announced on the Exchange Team blog yesterday that Microsoft will be releasing an update for Exchange 2007 enabling full support of Windows Server 2008 R2.

Microsoft had earlier decided not to update Exchange 2007 to support its latest server operating system, Windows Server 2008 R2. This change is a result of customer feedback, so all I can say about it is thanks for listening!

Microsoft have announced that the new high availability feature of Exchange 2010, namely, Database Availability Group, or DAG will be available in Exchange Standard edition. This is yet another great way they are helping make high availability affordable and appealing to smaller customers.

It is also worth mentioning though that since a DAG makes use of Windows Failover Clustering (WFC) included with Windows Server 2008 Enterprise edition, this Windows Server edition is still required.

For more info see this UC Blog post

For more info on DAG’s, click here

Microsoft have got a webcast coming up next week to discuss recommendations for virtualizing Exchange server and the benefits of using Hyper-V + System Center for virtualization.

The webcast is on Wednesday, Nov. 4 at 10am Pacific time, which is Thursday, Nov 5 at 5am for those in Sydney.

For more information and to register for the webcast, click here

The Exchange Team have released an updated version of the Exchange Remote Connectivity Analyzer

The tool simulates several client logon and mail flow scenarios. When a test fails, many of the errors have troubleshooting tips to assist you in correcting the problem. You may recall reading about it before..

Some new features include:

• Updated user interface
• New CAPTCHA implementation
• Updated the Outlook Anywhere test logic to work with Exchange 2010
• Added a password confirmation text box to ensure the proper password was entered before running a test. This will reduce the number of tests that fail simply due to a typo in the password.

Additional tests include:

• Exchange Web Services – This allows you to perform connectivity testing for Exchange Web Services client such as Entourage. Developers can also use the Service Account Verification test to ensure things are configured and working properly for access with an alternate account or Exchange Impersonation.
• Outbound SMTP – Performs Reverse DNS testing, DNS RBL Checks, and SenderID validation against a provided "outbound" IP address