Re: Roaming profile learning experience

[Tom Jedrzejewicz <tomjedrz@xxxxxxxxxxxxxx>]

On Sat, Oct 3, 2009 at 4:33 PM, Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>wrote:

> See inline.
>
> On Sat, Oct 3, 2009 at 3:00 PM, Tom Jedrzejewicz <tomjedrz@xxxxxxxxxxxxxx
> > wrote:
>
> > I don't think it is just to blame the network guy  <<snip>>
>
> The Network Consultant took responsibility.  We initially were looking at
> Exchange on site vs hosted Exchange.  It was he who brought up the idea of
> Google Apps.  After investigating GApps, we had specifically discussed
> Outlook to a great extent, tasks specifically because that wasn't in GApps.

OK, my bad.  You should be irritated.


> Since this issue, I have:
>
> 1) Move all .pst files outside the Local Settings folder to a folder that
> does get pushed back to the domain server.  This means all .pst files are
> in
> at least 2 locations.  The domain server already has disk snapshots taken
> nightly.

I think putting the .PST file inside of the roaming profile is a bad idea.
 I don't know if Microsoft has an opinion.  But .PST files get big, and big
files cause problems for roaming profiles, both in data integrity and in
performance.  Better to put it into the Docs and Settings (i.e. "Documents")
and include it in your backup strategy.

<< snip>>


> One caution .. I would *not* put the PST file into the roaming profile.  It
> > gets corrupt far too easily.
>
> Roaming profiles get corrupted often?  I will have to look into tthat as
> well.

Yes, roaming profiles do get corrupted, particularly the local side.  That
was likely your original problem.

However, I was referring to .PST files, which have a tendency to get corrupt
when they get big or if they are on slow-responding drives.  There are
almost foolproof tools (scanpst and scanost) to fix them, but it is an
irritation.  However, combining that issue with the replication issues
multiplies the headaches.

Remember of course that YMMV, and quite likely others have different
opinions or experiences.

Hasta.