• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 527
  • Last Modified:

Exchange 2000 to 2003 Migration - ADC Upgrade

I am migrating from an existing Exchange 2000 server (lets call it Server1) running on W2K to a new Exchange 2003 Server on W2K3 (Server2).  Native AD domain.  Mix of 2K and 2K3 servers, though the master AD Controller is a 2K server.  The existing Exchange server, Server1, is also an AD Controller.  The new Exchg2003 server will not be an AD Controller.

I have completed all of the steps in the Exchange Server 2003 Deployment Tools, including all necessary domainprep and forestprep actions.  All passed.

When I actually begin the Exchange 2003 install on the new server, it returns the following message:
'The component "Microsoft Exchange Messaging and Collaboration Services" cannot be assigned the action "install" because:
- All Active Directory Connectors in the Windows forest must be upgraded to the most current version before you can upgrade Microsoft Exchange. The following ADC servers have not been upgraded:
Server1'

I believe the solution was provided in this post:
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_21540827.html?sfQueryTermInfo=1+%22all+activ+directori+connector%22+%22most+current+version%22+2003+exchang+instal

However, given that the old email server (server1) is an AD Controller, and will continue to remain active in that role, should I really remove the AD Connector from that server?

Also, as a side question, I've read somewhere that it's preferable for Exchange 2003 is NOT installed onto a machine which is an AD Controller.  Is this correct?  

Any input will be greatly appreciated!
0
Ken Moody
Asked:
Ken Moody
  • 6
  • 4
1 Solution
 
Zenith63Commented:
The "Active Directory Connector" is PURELY to synchronise an Exchange 5.5 directory of users into Active Directory.  Once the last Exchange 5.5 server has been removed from the Exchange Organisation the Active Directory Connector no longer serves any purpose so can be removed.  It can be removed from Server1 from using Add/Remove Programs.

The main reason for not having Exchange on a DC is spreading the load that servers in an organisation have to deal with.  I don't know what size your site is, but on most sites I do (10-200 users) having servers only doing Domain Controlling isn't feasible so most Exchange servers are DCs as well.  There is no technical reason not to do it that I'm aware of (think of an SBS server where Exchange is on the DC by design).
0
 
Ken MoodyAuthor Commented:
Thanks for the clarification, Zenith!
0
 
Ken MoodyAuthor Commented:
One catch though.  There is no Active Directory Connector listed in the Add/Remove Programs.  Is there some other name under which it might appear?  
0
Veeam and MySQL: How to Perform Backup & Recovery

MySQL and the MariaDB variant are among the most used databases in Linux environments, and many critical applications support their data on them. Watch this recorded webinar to find out how Veeam Backup & Replication allows you to get consistent backups of MySQL databases.

 
Zenith63Commented:
Interesting! :)

It should be called Microsoft Active Directory Connector - http://support.microsoft.com/kb/841667
0
 
Zenith63Commented:
It should be listed in Start->Programs or C:\Program Files also?
0
 
Zenith63Commented:
Sorry for all the replies, brainstorming :).

If you run the ADC installer (from the Exchange 2000/2003 CD) it will give you the option to "Remove All" if it is already installed?  This should all be done from Server01 of course...
0
 
Ken MoodyAuthor Commented:
Nada on all three.  I just tried the Exchange2003 install again on server2 just to make sure I'm still getting the same message, and I am.  Just before posting the original question, I did run the Exchange Server 2000 post SP3 rollup.  Dont know if that would affect it or not.

I will run the ADC installer and let you know.  Thanks so much, your brainstorming is much appreciated!!
0
 
Zenith63Commented:
I'd guess in the past somebody upgraded from Exchange 5.5 but didn't remove the ADC properly from Server1.

If the Remove option isn't there when you run the installer I guess you have two options.  You could install the latest version of the ADC on Server1 from the Exchange 2003 SP2 CD, do the install of Exchange 2003 as you intend, then just uninstall the ADC.

Or you could use ADSIEdit to remove the ADC manually from Active Directory.  (It might be worth at least having a look with ADSIEdit and see if you can see the ADC in Active Directory).  The MS link I posted above explains how to do this, or even better have a look at this video - http://www.netometer.net/video/indexkey.html?tutorials/adcremove/index.php
0
 
Ken MoodyAuthor Commented:
I was unable to delete the ADC through ADSIEdit.  Finally had to use the ADC installer on the Exch2003 install disk to completely remove all ADC components.  That worked, E2K3 is now installed on the new server and the migration is moving forward.  Thank you very much for your assistance Zenith, very much appreciated!

0
 
Zenith63Commented:
Great, glad it worked out!
0

Featured Post

Configuration Guide and Best Practices

Read the guide to learn how to orchestrate Data ONTAP, create application-consistent backups and enable fast recovery from NetApp storage snapshots. Version 9.5 also contains performance and scalability enhancements to meet the needs of the largest enterprise environments.

  • 6
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now