|
If it's a single server single site it probably wouldn't be too hard. A little messy maybe. I would try this in a test environment to work out any kinks first. The 2000 domain is up and running (you will probably need a trust to let new domain access old domain resources.) You also need to consider your end-users access to mailboxes after the domain change. Where will their NT accounts reside? If not in the new domain do they have rights to the resources there? Add the new domain service account to the 3 levels of Exchange with SA rights Set the Exchange (and any related) services to manual Restart Join the Exchange server to the new domain Change the service account on the Exchange services to the new domain SA Start the services Install the active directory connector for Exchange 5.5 sync to AD It's worth a shot in a test environment if you have the time. Otherwise I would do a fresh install of Exchange on a box in the new domain and restore the databases.
[This message has been edited by Lorna (edited 06-30-2000).]
|
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [Microsoft Exchange 5.5] >> General >> Windows NT Domain Change 
Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM
Windows NT Domain Change - 
RE: Windows NT Domain Change - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread