Option 3 is the only way to go. Start clean, and migrate just what you're taking with you to the new forest. If at all possible, build the desired structure then migrate into it.
Depending on your time frame, I'd suggest starting really easy - you just want to make an authentication platform. The better parts of AD can come after you're independent. Focus on what you *need* to have working when you cut the cord. Having been involved in more merger/acquisition/divestiture projects than most non-consultants, I've gone through this exercise more than once, and we have always come back to a clean start. The most recent example was exactly what you're describing - extracting ourselves from the parent company's resources. As one of my coworkers put it - "0 to AD in 45 Days." Look very seriously at ADMT V2 from Microsoft to manage the migration. Had we not already owned the Fastlane migrator tools, we would have used ADMT. ------------------------------------------------------ Roger D. Seielstad - MCSE Sr. Systems Administrator Inovis - Formerly Harbinger and Extricity Atlanta, GA > -----Original Message----- > From: Patton, Jim [mailto:[EMAIL PROTECTED]] > Sent: Monday, October 07, 2002 12:01 PM > To: [EMAIL PROTECTED] > Subject: [ActiveDir] Domain Migration > > > I am currently work for a startup, (not a dot-bomb), that is > in the process of becoming independent from our parent > company. At this time, all IT-related resources are provided > by our parent company. I would prefer to build a brand-new > Active Directory infrastructure from the start. However, > because of the current economic climate, I've had to develop > some alternative plans. > > > > Ultimately, the goal is to become fully independent with a > completely separate IT infrastructure. I can envision three > possible scenarios: > > > > 1) Create a new child domain within the existing > infrastructure, create a new Exchange server and complete the > migration all user accounts and data, transition the > remaining IT-resources to the new child domain, (SQL 2000 & > Sharepoint) and then eventually migrate the child domain to a > new Active Directory Tree / Forest? > > > > 2) Create a new Tree and Domain within the existing Forest, > migrate all IT-resources and then transition everything to a > new Forest. > > > > 3) Create a new Active Directory Forest, establish a two-way > trust between both Forests, and then begin the migration of > IT-resources starting with the Exchange and other user-specific data. > > > > Does anyone have any recommendations, suggestions or advice > on the best path to take with the ultimate goal in mind? > > > > Thanks > > > > Jim > > > > > > List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
