TK said:
Yes, I have heard this, but have been practicing this successfully since
Exchange 4.0.
I think we need to understand why you want to do this. What is it you think
you are achieving?
Ordinarily the Exchange server keeps everybody's emails and related
information in a mailbox held within the Exchange database on the server.
The backup facilities which you should have running on the server would
allow you to restore this database to a new or rebuilt server in the event
of loss.
On the client computer, the user configures Outlook to communicate with
Exchange. This process creates a local .PST file. Outlook synchronises the
data in the.PST file with the data held in the exchange mailbox. So the
purpose of the .PST file is to improve performance by ensuring that most
data is held locally - it is nothing more than a cache.
If the user logs in to a different workstation on the domain, he can
configure Outlook in the same way; indeed if the Administrator has arranged
for the user to have a roaming profile the configuration of Outlook will be
done for him. So it's easy for any user to log on to any workstation in the
domain and see the same working environment. This doesn't work if the
workstations run the "home" OS versions because these cannot join the
domain; but W2k Pro, XP Pro, and Vista Business can all connect to a domain.