Windows

My advice is to use Quest software's migration package for Exchange:

http://wm.quest.com/products/MigrationsuiteExchange/

ok, are you saying that your facility is going to be joining a larger AD environment rather than continuing to be a stand alone?

I think that you need more information from the higher ups as to what your facility will be within the Active Directory environment before you start to worry about how your going to accomplish a migration.

Will your facility be a site under the larger domain structure? Is your facility going to be a child domain of a higher level domian within the AD structure?

Another question is; are you going to upgrade your hardware?

The admins of the larger domain should not have created individual user accounts for your facility until they have decided what your facility was going to be in the Active Directory structure. Then created a plan for your facility and advised you what the migration/upgrade was going to be. your NT domain can be migrated to a Windows 2003 domain and further be a child domain of the larger AD environment. Your Exchange can be migrated to Exchange 2003 and used as a back-end Exchange to the larger clustered Mail servers.

Again this all depends upon how your facility is going to be intergrated within the larger logical and physical infrastructure.

Are you suggesting with this tool we can migrate all the mailboxes and the mailboxes with special permissions like send on behalf, owner ship, mail box without account etc? What about the public folders. And how do you attach the old mail box to the new AD account of same user?

Yes, no more stand alone domain.
Our faculty will be an OU as the other faculties are.
We do not have to upgrade any hardware every thing is outsourced. Our machines can be dumped.
The accounts are present in AD.
Child domain is no option.

Shashi

This question was closed by the author