When considering a 'Transition Strategy' from Ex2k3 to Ex2k7 it is imperative to read through the many Technical Documents provided by Microsoft (and others) and establish testing criteria prior to any Production changes. I have posted a number of prior Blog Entries that are required reading (or viewing) with some of them summarized as:
Moving from Exchange 2003 to Exchange 2007 using a Transition Strategy
Technical Architecture of Exchange Server 2007
Exchange 2007 High Availability Strategies
After spending a good amount of time reading, working with Virtualization Software and comparing notes with Colleagues it is time to introduce the first Ex2k7 Server into your existing Ex2k3 Messaging Environment. The following Screen Captures offer a step-by-step approach to installing this initial Ex2k7 Server.
<Click on the Image to Enlarge in a Separate Window>
I login to the Schema FSMO Role Holder in the Forest Root the '....\setup.com /preparead' parameter is initiated in the User Context of a Schema Administrator. This parameter provides the required Schema Updates along with Domain Global Security Group additions and ACL modifications on the appropriate Active Directory Configuration Naming Contexts and Organizational Units.
A series of 'checks' occur at both the Domain and Forest Level to validate receipt of the Schema Changes and Domain Level changes. If all is well the modifications occur on the Forest Root Schema Role Holder. Replication to other Domain Controllers occur at the defined Replication Interval per the Active Directory Sites and Services configuration.
Upon successful completion of the Schema and Domain Upgrade process we can see new Domain Global Security Groups are generated. Invoking Active Directory Users and Computers and connecting to a Domain Controller shows the new Organizational Unit for Exchange 2007 Security Groups.
Another validation method that Exchange 2007 Schema updates were applied is to use ADSI Edit and look for specific Exchange 2007 Attributes. Here, I isolate the 'ms-exch-Auto-Discover-VirtualDirectory' attribute which is new for Exchange 2007.
The 'repadmin /syncall' parameter forces a synchronization between Domain Controllers. The goal is to ensure the Exchange 2007 Schema updates are synchronized between Domain Controllers prior to performing the Installation of Exchange 2007 on the first Exchange 2007 Server in an Exchange 2003 Organization. I force a replication as no one should have to wait in a Lab Environment! 
On the second Domain Controller the Exchange 2007 Schema Attributes are present. The next step is to proceed with the Installation of Exchange 2007.
A 'Custom Installation' is necessary so we might select the Server Roles to be installed.
Three Server Roles are selected for this first Exchange 2007 Server in an Exchange 2003 Organization. The Client Access Server Role (formerly OWA Server), the Hub Transport Server Role and the Mailbox Server Role.
The moment of truth (not really, the moment of 'transition'!) whereby if we have configured all parameters correctly and are prepared - are offered the option to select an Exchange 2003 Server that the Routing Group Connector between Exchange 2007 and Exchange 2003 functions.
Upon completion of a successful installation the Exchange Best Practice Analyzer is run to identify areas of focus for configuration changes and parameters to be set for optimization.
Next the Exchange 2007 Update Rollup 4 is installed.
Perform a reboot of the Exchange 2007 Server after receiving the Exchange 2007 Update Rollup 4.
When the Exchange 2007 Server is available I start by using the 'Test-ServiceHealth' commandlet to validate critical Service availability. Additionally, I do a bevvy (whatever that means) of Commandlets to ensure proper installation and function of an Exchange 2007 Server.
Note that the 'Get-ExchangeServer' Commandlet shows both the Exchange 2003 Server (denoted as V6.5) and the Exchange 2007 Server (denoted as V8.0) in my Lab Environment. We are moving closer to being able to 'transition' Users and Public Folders to Exchange 2007.
Finally, we see our list of Exchange 2003 Mailbox Recipients denoted as 'Legacy Mailboxes'. These are our candidates for 'transitioning' to Exchange 2007. I will provide a separate Blog entry that provides step-by-step instructions in how to complete a 'Move Mailbox' using both the Exchange Console and using the Exchange Management Shell (PowerShell Commandlet).
We have a series of additional configuration parameters to complete. More about these steps in another Blog entry. We now have a healthy Exchange 2007 Server in our Exchange 2003 Organization.
If you'd like to 'Learn Advanced IT' - Check out the Free Video Lessons on Windows 2008 SP2 Failover Cluster Nodes for Highly Available File Services and other topics as well - http://www.exchangesummit.net.
Lynn Lunik
Independent Security Consultant
Windows(R) Platform
IT Pro Secure Corporation
and
exchangesummit.net
http://itprosecure.com and http://www.exchangesummit.net
blog <at> itprosecure.com
Posted
Aug 23 2007, 08:54 PM
by
lynn lunik