Exchange 2003 Connection Agreement Wizard Error

0 pts.
Tags:
DataManagement
Exchange 2003
Exchange 5.5
Installation
Microsoft Exchange
Migration
Outlook
Tech support
We are in the process of migrating from Exchange 5.5 to Exchange Server 2003. We are part of a large public organization, but for security reasons, need to separate from a forest the "main" IT department is creating and maintain our own forest. While trying to migrate our environment via the Connection Agreement Wizard in ADC Tools, we were getting the following error message. Again, for security reasons, we have removed the original organization names and placed dummy entries: Error: The organization o=YYY is already installed into this forest but the configured 5.5 server is a member of organization o=XXX. Please choose a 5.5 server in the correct Org. In the 5.5 environment, we were a container within organization XXX. Now, we put together Windows Server 2003 forest YYY and would like to migrate the contents of XXX onto YYY. There are some constraints. First of all, because we are actively migrating users and computers from our old Windows NT 4.0 domain onto YYY, changing the name of the new domain is not an option. Also, if possible, because of the complexity of the hardware our Exchange 2003 installation is residing on, we would prefer not to uninstall and reinstall Exchange 2003. Searching through Microsoft support has not yielded useful information. The closest to useful advice I obtained from Microsoft alluded to destroying and rebuilding Exchange, as discussed in http://support.microsoft.com/?kbid=273478, but I personally think there has to be a better way (a registry hack, for instance?). Any suggestions you can provide will be VERY MUCH appreciated.
ASKED: July 5, 2005  1:02 PM
UPDATED: July 6, 2005  8:10 AM

Answer Wiki

Thanks. We'll let you know when a new response is added.

Hello,

First off let me ask, why do you need to create a seperate forest for security purposes? Why not create a child domain within the existing forest and use AD policy to secure it’s resources from other child domains within the forest? If you have a child domain within the same forest as your Exchange server resides you maintain the ability to move users around and share Exchange resources. If you create an entirely new forest you’ve now seperated your self on the top level from your original forest and loose the ability to simply move server objects from one forest to another. Basically you will have to build another Exchange server in your new forest to handle your mail.

Good luck!

Discuss This Question:  

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following