Transition/migrate Exchange 2007 from 2003 where domain controller and AD is Windows Server 2008

Posted on 2010-09-09
Medium Priority
Last Modified: 2012-05-10
We are in the final planning stages of moving Exchange 2003 (running on Server 2003 SP2) to Exchange 2007 (running on Server 2008 R2)

We have been following the guidelines and have run the Exchange Best Practices Analyzer.  We are getting results stating that:

Active Directory domain 'DC=domain,DC=co,DC=uk' does not contain at least one domain controller running Windows Server 2003 Service Pack 1 or later. This is required for the '/PrepareLegacyExchangePermissions' task when updating existing domains that have been previously prepared for Exchange Server


Active Directory site 'Default-First-Site-Name' does not contain any global catalog servers running Windows Server 2003 Service Pack 1 or later. This will prevent Exchange 2007 servers from being installed into site 'Default-First-Site-Name'.

Slightly confusing as both are talking about Server 2003 SP1 or later and we are running Server 2008 R2 as DC, so why are we getting these messages.  The Exchange 2003 box that is being replaced does use the domain provided by the 2008 R2 DC, and also the 2008 is the global catalog

So any advice as to why we are getting these messages where, as far as we are concerned, the Global Catalog and the DC are configured correctly and, obviously as they are running 2008, meet the prerequisites of "Windows Server 2003 SP1 or later".  Slightly confusing

Question by:Solpak
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
LVL 16

Expert Comment

ID: 33638951
Open up Active Directory Domains and Trusts on your DC and check the functional level of your domain and forest.  If they are not both set to the right level, this may cause the problem you are having.
LVL 19

Expert Comment

ID: 33639399
LVL 14

Expert Comment

ID: 33643977
The problem is with ExBPA

Try downloading the latest version of the ExBPA and run it again.

If the latest ExBPA doesn't do it, you will have to do it (update the ExBPA) the manual way:

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.


Expert Comment

ID: 33650791
Typically these sorts of errors crop up if someone has spilled coffee on the floor of the server room and one of your feet is in it while you're running the ExBPA. It's surprisingly common. Usually checking the functional level of the domain and moving your feet away from the spill is enough to get past these errors. In addition, you should always have ExBPA download updates when you first start it up, to ensure that it's ready to handle all the latest patches that may have been loaded on the products that it is testing.

Author Comment

ID: 33689730
I suppose I should rephrase this as all of the guides, from what I can see, are talking about transitioning from Exchange 2003 on Server 2003 to Exchange 2007 on Server 2003.

We have already moved the Active Directory and the Global Catalog to a new Server 2008 and have been running off that for 4 weeks.  The old 2003 AD does not exist anymore.  But the server that runs Exchange 2003 is still Server 2003.

So when I run the ExBPA on the Exchange 2003 on Server 2003 it is not picking up 2008.  "Server 2003 SP1 or later is required" seems to suggest that 2008 is not classed as later by this program.

So after the ExBPA all the other required pre-checks (functional levels, exchange native mode) that are mentioned for transitioning are complete.  Now the question I should rephrase this as is:

As we are running AD, DC and GC in 2008 do we need to do any of the Setup.com /prepare guidelines.  I have already tried and get no results whatsoever.

When Exchange 2007 is now installed will this just create the required permissions etc in the 2008 AD, create the bridge connector to Exchange 2003 (or the other way around) and then all we have to worry about is the moving of the mailboxes and then the decomissioning of the Exchange 2003 server?

It seems like we may have approached this the wrong way around by putting in the 2008 DC before transitioning to Exchange 2007 on 2003

Help would be very muchly appreciated
LVL 14

Expert Comment

ID: 33692235
Yes - you do need to run the Exchange-specific prep.  (I always do this manually, so that I can see if there are any errors, but the actual install of Exchange is supposed to do this for you in the background as part of the install - so if you didn't prep before, the installer will actually do it for you)

Yes - permissions will be added for Exchange 2010 (as long as you run the setup from an account with permissions)
Yes - connectors will be created for mail flow

No - there are more things to worry about than just moving mailboxes and decommissioning.  :-(     Examples - requesting, installing a properly configured SSL cert
- appropriate DNS records, especially for autodiscover (both internal and external DNS, in most cases)
- and many others too numerous to mention in one post without typing a boatload of stuff here.  (Sorry, don't feel like writing an Exchange book)

Here is the official 2003 to 2010 upgrade/coexistence guide (it might point out some things that you might have missed in your planning):

P.S.  Did you try manually upgrading the ExBPA so that it works properly?  It *can* be done.
LVL 14

Accepted Solution

Kaffiend earned 2000 total points
ID: 33692396
What I mentioned above applies for Exchange 2007 as well, except for the last link, obviously, although there is value in reading that if you wish to.  If you really are doing Exchange 2007 and not 2010, here you go:

Here's an "on-ramp" page for Exchange 2007:

And, a step-by-step guide (interesting formatting, but you get an insight into a well-thought out and executed transition)

And, of course, the official Exchange 2007 documentation:


Author Comment

ID: 33714756
Thanks guys

Followed Kaffiend's posts through (many thanks)

The transition went really well.  Actually at some stages I was thinking too well, but I'd definitely give kudos to MS for making it easy.


Featured Post

Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article will help to fix the below errors for MS Exchange Server 2013 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
There are times when we need to generate a report on the inbox rules, where users have set up forwarding externally in their mailbox. In this article, I will be sharing a script I wrote to generate the report in CSV format.
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

719 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question