Another thought, unless the content of the existing domain is an issue. 1. Build the new Win2K DC as an NT4 BDC in the old domain. 2. Promote him to PDC 3. Build a second BDC (could be a desktop) and /net accounts sync 4. Pull the second BDC off the wire during migration as safety 5. Upgrade the new PDC to Active Directory with proper DNS
Test Test Test I would recommend a lot of testing off-line first, but that is the basic of the upgrade procedure. Done correctly you do not need to move the Exchange server at all and the users will never know they moved. Again, done right. If you lack the experience, it may be worth your time to bring in a good consultant to assist as design is 90% of a good AD ... maybe 95% CJP -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Friday, July 26, 2002 12:22 PM To: [EMAIL PROTECTED] Subject: RE: Moving an Exchange 5.5 server to a new domain. Why not just do the following: 1)create a trust between the two domains 2)follow and test the service account migration instructions in Q266041 3)change the Exchange server's domain membership No need to take it offline or run DR procedures. So long as both domains are in place and the trust exists, you just have to make sure the primary NT account for each mailbox actually matches what it should (currently) be. -----Original Message----- From: Billings, Art [mailto:[EMAIL PROTECTED]] Sent: Friday, July 26, 2002 10:03 To: MS-Exchange Admin Issues Subject: Moving an Exchange 5.5 server to a new domain. I've searched the archives, I've even searched the KBase, and TechNet but I haven't found a good answer to this dilemma I am going to face in the next few months. So I have to ask the experts. I have a client that is going to create a Windows 2000 domain to replace the current NT 4.0 domain. The plan right now is to have both domains running concurrently, and as we replace the workstations, have them join and use the new domain. I plan on creating the exact same user names as they currently exist, but here is the real challenge. The PM wants to move the current Exchange 5.5 SP4, NT 4 member server from its' current domain into the Windows 2000 domain. Of course we will activate the Active Directory connector and point all of the mailboxes to the accounts in the new domain. The plan to accomplish this looks something like this: 1. Stop all Exchange services. 2. Change the startup configuration to manual. 3. Remove the server from the current domain. 4. Add it to the new W2K domain. 5. Change the service account to the service account in the new domain. 6. Start the Exchange services. Of course we will do an offline backup of the exchange databases and logs. The reason the PM is looking at doing it this way, is because the client will be undergoing a migration to their MRP/ERP environment and she wants to minimize the trauma as much as possible. Otherwise we would scrap the idea of moving the server from one domain into another, and just migrate them to Exchange 2000. After boring you with all of this background information, I come to the crux of the matter. Will this work? Please point me to the correct resources that will help me make this happen as painlessly as possible, if this plan is totally bogus. I have talked with a couple of my colleagues about this and they can't see why it won't work, but they don't have the level of expertise that you all have. Art Billings, Senior Network Engineer TRG Networking, Inc List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm +++The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy any copies of this document.+++ The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy any copies of this document. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
