I support a small Windows 2003 lan. Only a couple of admin staff have
roaming profiles. Well the roaming works but I just discovered that
Outlook.pst does not move to the next workstation. We want to use roaming
profile as a backup to single pc failure. There is no Exchange server, all
accounts are POP. (Exchange starts January 07 if budget permits).

Is there a good article on moving existing .pst file to a location such as
documents and settings\username\application data\microsoft\outlook?

On a test machine I tried just copying the file and of course it didn't
work.

tia.

In news:v1nQg.3174$5R2.1979@pd7urf3no,
NetTransplant typed:
I support a small Windows 2003 lan. Only a couple of admin staff have
roaming profiles. Well the roaming works but I just discovered that
Outlook.pst does not move to the next workstation. We want to use
roaming profile as a backup to single pc failure. There is no
Exchange server, all accounts are POP. (Exchange starts January 07 if
budget permits).
Is there a good article on moving existing .pst file to a location
such as documents and settings\username\application
data\microsoft\outlook?
On a test machine I tried just copying the file and of course it
didn't work.

tia.

I would be very, very, careful here. MS does not support accessing a PST
file across a LAN/WAN connection - many companies do it but many also end
up with performance problems and data corruption.

I would probably hold off on roaming profiles until you get Exchange, unless
your users don't actually *roam* and all you care about is backing up their
profile data. You can back up the PST files individually/separately - set up
a scheduled task that runs after hours to copy their PST file to their home
directory, for example.

When you get Exchange, ditch PST files entirely. Life will be much easier.

Lanwench [MVP - Exchange]
ahoo.com wrote:

When you get Exchange, ditch PST files entirely. Life will be much
easier.

But only if the Machiavellian Exchange admins don't clamp down on quota so
had that you have no choice.
--
Brian Tillman

I realise MS doesn't support access the .pst over the network but I'm not
really looking to do that.

With a roaming rofile the .pst would be basically mirrored on the server but
loaded and accessed on the workstation the user is on.
This does not break MS's suggestion.


"Brian Tillman" wrote in message
...
Lanwench [MVP - Exchange]
ahoo.com wrote:

When you get Exchange, ditch PST files entirely. Life will be much
easier.

But only if the Machiavellian Exchange admins don't clamp down on quota so
had that you have no choice.
--
Brian Tillman

In news:SLxQg.9152$1T2.524@pd7urf2no,
NetTransplant typed:
I realise MS doesn't support access the .pst over the network but I'm
not really looking to do that.

With a roaming rofile the .pst would be basically mirrored on the
server but loaded and accessed on the workstation the user is on.
This does not break MS's suggestion.

You'd have to manually move the PST file to a folder that would roam.
If you have large roaming profiles you will have other problems. I keep mine
to maybe 20, 30MB tops.


"Brian Tillman" wrote in message
...
Lanwench [MVP - Exchange]
ahoo.com wrote:

When you get Exchange, ditch PST files entirely. Life will be much
easier.

But only if the Machiavellian Exchange admins don't clamp down on
quota so had that you have no choice.
--
Brian Tillman

In ,
Brian Tillman typed:
Lanwench [MVP - Exchange]
ahoo.com wrote:

When you get Exchange, ditch PST files entirely. Life will be much
easier.

But only if the Machiavellian Exchange admins don't clamp down on
quota so had that you have no choice.

Quotas are a fact of life - they can often be relaxed if there's a business
justification for it, and there are (still) public folders.... and there are
archive management tools if the data is truly needed by the company.