migration question

  • Thread starter Thread starter BCE
  • Start date Start date
B

BCE

I am facing a business mandated migration due to business acquisition, a small company running a 2k3 domain on exch2003, where the larger company, quite larger is still 2k globally, so we it has been mandated to migrate the 2k3 structure into the 2k domain model.
Luckily we are at exch2003 so that is not too big of an issue.
Is there any concern or caveats in migating backwards?
 
If you are migrating, then you are creating a new domain and copying users and objects across essentially. In order to create that domain in the first instance, you will need to forestprep the target forest for Windows 2003 and Exchange 2003.

There are no concerns or caveats with what you are doing as far as I can see. If you were running in a mixed environment, I would recommend that you make a 2003 DC the PDCe as the PDCe manages security principals and the new well-known security principals introduced in 2003 won't work when the PDCe resides on a 2000 box. However it sounds like you are going to be pure 2003 so that isn't an issue.
 
Paul,
Thanks for the reply, but I don't think I explained myself well enough. The company I consult for is large, global forest with hundreds of DC's who just purchased a small company that is pure 2k3 domain. Business wants them absorbed into our existing 2k native domain, which means a migration from 2k3 to 2k.
My instinct is to do a domain to domain trust, since we cannot do a forest trust, and just migrate them to our exchange system.
But the business may push back demanding there complete absorption into our 2k infrastructure.
Is there any issues migrating from 2k3 to a 2k domain?
 
Good question!

I can't say I've tried this scenario, so can't be 100% sure, but cannot think of any adverse effects. I can't speak for Exchange though.

You may have problems (or at least errors) during the migration for attributes that are new to 2003.

You will need to test this in a lab first.
 
Back
Top