It all depends on what point the migration is at (ie. are you almost done? Just starting?)
You are new to the company, and the company was not fortunate to have the insight to see what you see...having a anchor root domain (which I am assuming is what you are trying to get to). Never-the-less, all is not lost. Option 1: Finish the Migration and then create sub-domain structure. * The advantage of leaving things alone is that you do not need to recreat the migration plan. If you were to change the direction of the migration now, say to a child domain corp.company.com, then you have to go back to planning and testing the new design. * When the migration is finished, you can still create the corp.company.com and use tools to move users to the new domain. The user's will get new SIDs, but they will still be able to access resources in the root domain because their old SID will be retained in a history list. Option 2: Change the Migration Plan Now. * If the 4 sites that have been migrated is part of a 100 site system, then it may be worth your while to go back to the drawing board. Since the migration of 100 sites may take a long time, you have time to develop a new migration plan and move to it. I would give yourself 2 - 3 months before it's fully deployed. In the meantime, let the mgiration team continue with migrating to the root domain or stop all migration activities. * What to do with the existing users and domain resources that have been already migrated to the root domain? I would leave this alone until you finish the migration to other sites to the new corp.company.com. These users can still access resources in the corp.company.com domain if you design your security groups correctly (ie. add users in company.com domain to Global Groups and add them to resources in Domain Local groups for the corp.company.com...and vise versa for users in the Corp.company.com domain who need to access resources in the company.com domain....easy as 123.) When the migration is complete, threat the migration of users and resources in company.com as the plan in option 1 above. Any questions? Cheers, Leonard Lee -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] Sent: Monday, March 18, 2002 7:51 AM To: NT 2000 Discussions Subject: Domain Restructure Hi All I have a root directory ... company.com and I inherited this from an NT upgrade. Of course now all my objects are dumped in this root which I know is not an ideal solution? and perhaps I should have kept a pristine root? How much of a problem would it be to restructure this, I have 4 sites upgraded so far and these have also been put into the comapny.com root. I would like to move the lot into another branch i.e. corp.company.com. This is giving me a headache... Any ideas? Robert Rutherford **************************************************************************** **************** This E-mail and any files transmitted with it are in commercial confidence and intended solely for the use of the individual or entity to whom they are addressed. If you have received this E-mail in error please notify the Administrator by E-mail ([EMAIL PROTECTED]). Any views or opinions expressed are solely those of the author and do not necessarily represent those of DEK Printing Machines Ltd., or its affiliates. **************************************************************************** **************** ------ You are subscribed as [EMAIL PROTECTED] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to %%email.unsub%% ------ You are subscribed as [email protected] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED]
