Archived from groups: microsoft.public.win2000.active_directory (
More info?)
Andrew,
If you have migrated the SIDHistory from the first domain, you will still be
able to use Exchange. From there you can either use the Exchange migration
tools, or, if you are in a small environment, you can just kick everything
to PST, import them into Exchange, Import the GAL, and then reconfigure the
Outlook. The outlook reconfiguration can even be automated with the ORK.
Once that is done, power down the old controller for a while to be sure its
not needed for anything, then repurpose it once you are fully tested.
Don't jump the gun on this. Do it slowly and test everything.
--
Ryan Hanisco
MCSE, MCDBA
Flagship Integration Services
"Andrew" <Andrew@discussions.microsoft.com> wrote in message
news:9EE8127A-F838-4555-8BDE-5FBF6FA7593F@microsoft.com...
> Thankyou both very much for your kind help : )
>
> I'm pretty interested in the exchange part, when the user are migrated to
> the new forest and domain, are they still able to use the exchange server
> from the original forest?
>
> How would you recommend migrating the mailboxes from one forest to
another.?
>
> Thanks again, Andrew
>
> "Ryan Hanisco" wrote:
>
> > Andrew,
> >
> > You can't do this as an in-place upgrade you will have to have new
hardware
> > on which to do the migration. ADMT is also the way you should go as
you
> > can even preserve the Exchange and do that as a separate migration after
you
> > have migrated the accounts -- just be sure that you maintain the SID
history
> > and the passwords.
> >
> > YOU MUST LAB THIS. Especially with the migration of workstation
accounts
> > and local permissions, you need to do this as a trial. Set up your new
> > server and directory, do a test migration and migrate a test OU of users
and
> > Computers... Make notes until you can do this perfectly, then start
over...
> > and I mean completely over. The last thing you need is to have to
rebuild
> > and touch hundreds of machines.
> >
> > Once you have the users and computers over, migrate Exchange as a
separate
> > project. Until then, run the two in tandem.
> >
> > Final piece of advice, Install the UPHClean utility on all workstations
as
> > anything that doesn't translate perfectly on the workstation conversion
can
> > kill you. Also, if you start losing local profiles,go back at the end
and
> > kill all of the old ProfileList keys in your registry so as not to have
> > multiples pointing to the same profile path...
> >
> > Cheers -- let me know if you have other questions as I have done this
> > several times.
> >
> > --
> > Ryan Hanisco
> > MCSE, MCDBA
> > Flagship Integration Services
> >
> > "Andrew" <Andrew@discussions.microsoft.com> wrote in message
> > news:EB61DD4F-FE1D-47C4-B18B-C2E7264F6856@microsoft.com...
> > > > Hello all,
> > > >
> > > > My current org runs a single win2k domain with exchange2k and needs
to
> > > > change the forest name, i have searched and found that it is not
> > possible.
> > > > How would you go about a migration to another win2k domain?
> > > > We are going to build a new AD win2k forest and setup trusts between
the
> > 2
> > > > domains, can the objects in AD be exported into the new forest?
> > > > Would the computer accounts need to be joined manualy to the new
domain?
> > > > Can the user accounts be migrated?
> > > > I realise exchange wil not transfer between domains, but is it
possible
> > to
> > > > move the mailboxes between servers in seperate forests, as oppossed
to
> > > > ripping them to pst files and recreating accounts on the new server
in
> > the
> > > > new domain?
> > > >
> > > > I appreciated theres a lot of questions there, but any info would be
> > much
> > > > appreciated. if anyone else has done this type of thing before, how
did
> > it
> > > > go for you?
> > > >
> > > > TIA, Andrew
> >
> >
> >