lappladmin
asked on
Transitioning from Exchange 2003 to 2007
I am preparing to transition to Exchange 2007. We are currently running a single Exchange 2003 server supporting approx. 60 mailboxes. The transition itself seems pretty straight forward as there is plenty of documentation for this. One thing that is not directly addressed is the client configuration. Currently our clients connect locally using cached exchange mode. We do not allow web access. Once i have the exchange 2007 server up what is the best method to reconfigure the clients.
Do i simply go into mail setup and change the FQDN to the new server? Will it require a "resync" process for cached exchange mode? What about local archive folders (PST files stored on client drives), will these be disconnected?
Any additional notes and warnings would be appreciatied.
Do i simply go into mail setup and change the FQDN to the new server? Will it require a "resync" process for cached exchange mode? What about local archive folders (PST files stored on client drives), will these be disconnected?
Any additional notes and warnings would be appreciatied.
ASKER
So i will not need to reconfigure the client at all if i use an alias in DNS? Should i continue to use the alias for new clients or use the new FQDN as i add them?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks... had not though of using alias to avoid client reconfig.
1. install 2007
2.migrate mailboxes from 2003 to 2007 - after the migration clients will loose connectivity, but, it's easier to have one 1 or 2 hour service unavaiable. migrate all mailvboxes and public folders
3. after beeing empty turn off the 2003 exchange
4. go to dns and create one alias pointing 2007 server name to the old 2003 server name.
no changes in the outlook will be necessary. configurating 60 profiles can be boring.
hope it helps
António Vargas