Exchange Migration Tool Exchange Profile Update Tool/ PFmigrate Tool

what is your original exchange server -5.5??

Yes It is..

Any reason you don't want to use an ADC?
Exchange 2003 will detect the Exchange 5.5 server and ask you to do what is required. You would have to remove the Exchange 5.5 server to install Exchange 2003 without the ADC.
Personally I would use the ADC so that you can use the built in methods for redirecting the Outlook clients. I find it much more reliable than scripts or anything to update Outlook.

Simon.

I understand that... I just tested it and have used that in the past. I had an issue with it at the client site and they do not want the 2 servers to talk!! I have to find another way then that. So will my above questions work?

If they don't want the two servers to talk then you are looking at either a total removal of the original server before you even start the Exchange 2003 install, or a new domain for Exchange 2003. You will be unable to install Exchange 2003 while the Exchange 5.5 server is there.

Depending on which method you use, then either method would potentially work - but you need to carry out extensive testing before hand.

Simon.

So i cant add the new exchange server in the existing domain while the Exchange 5.5 Server is still running
and just give it a different name.

Right now they have an ad environment called health-cost and one exchange 5.5 server. I thougt I could add the new Exchange 2003 Server while the current exchange 5.5 server is still running and then start the
migration process...

So if I can't add the Exchange 2003 Server while the Exchange 5.5 server...Can you please explain the reason why I can't?

Thanks

If you don't want the two servers to talk then you have to remove Exchange 5.5. The Exchange 2003 process will see the Exchange 5.5 server, tell you to upgrade the ADC to the Exchange 2003 version and refuse to continue until you do.

If you want to do a conventional migration then you need to first upgrade the ADC to the Exchange 2003 version (I would actually download SP2 for Exchange 2003 and use the version of ADC in that as you will have to upgrade to that version anyway). Then prep the forest and domain for E2003 and install Exchange 2003. You can then migrate in the usual way.

Simon.

They are currently not using the mail-box store right now. Their emails are reidrected to a centralized
file server where they use PST. Thats one thing that does not need to migrate... I was hoping I could put exchange 2003 server in the existing environment with the Exchange 5.5 server then Re-create the 62 Distribution Groups and 61 Contacts they have then Import their Public folder Shared calender resources they have. I would then create their email alias through RUS and verify OWA... I would then use the Exprofe.exe through a login script to redirect the Outlook Profile.

So are you saying while the server is on their prod environment. Go ahead and start the E2003 process and
...I am confused! Can you explain further please....

Thanks

Based on what you have written above, what I would do is upgrade the Active Directory Connector using E2003 SP2 code. Then install Exchange 2003 in the usual way for an Exchange 5.5 to 2003 migration. The distribution groups will be brought across, the contacts can also be brought across (all standard stuff at this time).

The email accounts can then be moved - again in the usual way and you can import the PST files in to the database on Exchange 2003 using exmerge.

Nothing you have written above is out of the ordinary - except for the way you are storing email - storing email in PST files is not a good idea as they get corrupted very easily.

Simon.

The stroing is the way it has to stay! Thats the way the client wants it! Once again they do not want the servers to talk..