G
Guest
Hello all,
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
M
Matjaz Ladava [MVP]
Use ADMT (Active Directory Migration Tool to move objects from one W2k
domain to another W2k domain. You can grab ADMT from
http://www.microsoft.com/downloads/...b1-5849-4707-9817-8c9773c25c6c&displaylang=en
--
Regards
Matjaz Ladava
MVP Windows Server - Directory Services
(e-mail address removed), (e-mail address removed)
domain to another W2k domain. You can grab ADMT from
http://www.microsoft.com/downloads/...b1-5849-4707-9817-8c9773c25c6c&displaylang=en
--
Regards
Matjaz Ladava
MVP Windows Server - Directory Services
(e-mail address removed), (e-mail address removed)
R
Ryan Hanisco
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
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
G
Guest
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
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
R
Ryan Hanisco
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.
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.