Re: Profiles, Profiles, Profiles

From: Karl Burrows (karlspam_at_spam.yourbeacon.com)
Date: 03/18/05 

Date: Fri, 18 Mar 2005 01:12:32 -0500

That makes sense since it would differentiate where the drive location is
since it would be the same from any workstation.

At what point would the pst file start dragging on the application by using
it on a network location? I have several that are 500MB or more (don't
ask...I have talked to them until I am blue in the face about managing
attachments, sent items, etc. and it will juts not happen until one crashes
and they learn the hard way).

Thanks!

"Ja5on" <news@heaven.co.uk> wrote in message
news:423951bd$0$38038$bed64819@news.gradwell.net...
Karl Burrows wrote:

[snip PST file on server]

> Now, if I give the share a $ ending, how will they "browse" to it if they
> login to another workstation and want their email there? Since it is
> invisible, they won't be able to find it readily without having to get me
> to
> configure each time.
>
> I am not running roaming profiles, so there is no sync with the server.

Ah, you're not using roaming profiles. I tend to implement roaming
profiles on all Windows server systems now as it provides great backup
opportunities and additionally means that when a workstation implodes
all you need to do is rebuild/replace, join it to the domain and once
your user logs back in they shouldn't notice much in the way of change.

If you've implmented roaming profiles then your user will *never* need
to browse to the PST file location as this location will follow them
around with the profile. (Presumably the location data is somewhere in
the HKEY CURRENT USER hive).

> Now, if I move the pst file to the server, how will the roaming profile
> look
> to find the pst file location or do they have to do like Exchange and
> create
> the profile on that workstation to load it up there?

Nah. As above, if you're roaming, and have located the PST file on the
server - then once the local users Outlook has been configured to see
the PST file located on the server; and the user has been logged out
once to allow the appropriate bit of roaming magic to be
replicated/sync'd on the server - each time they roam to another machine
their Outlook will automagically look to the server location for the file.

Bandwidth shouldn't be too much of a problem depending on the size of
your organisation (I have a few < 50 user systems setup this way, on
100base without this becoming an issue). Also note that, provided your
users quit Outlook before leaving the office/lab/whatever, then all
their Outlook data is centralised and easily backed up.

> Thanks for the info!!

No Worries. 

-- 
Ja5on

Relevant Pages

  • Re: Slow to apply roaming profile
    ... It is on all workstations and all users that have roaming profiles. ... One user or all users on this workstation? ... Connection-specific DNS Suffix. ... PPP adapter RAS Server Interface: ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 roaming profiles
    ... documents and applications data in the roaming profiles. ... Make this unnecessary by using folder redirection. ... each workstation but thtas not too bad. ... I am creating a couple shares on the server for their data, ...
    (microsoft.public.windows.server.sbs)
  • Re: Profiles, Profiles, Profiles
    ... > I am not running roaming profiles, so there is no sync with the server. ... to browse to the PST file location as this location will follow them ... > to find the pst file location or do they have to do like Exchange and create ...
    (microsoft.public.windows.server.sbs)
  • Re: XP machine connection problem after SBS 2--3 Service pack 1
    ... I can ping the server but file sharing does not work nor do roaming profiles ... which are not visible to this workstation. ... > Hi Nick ...
    (microsoft.public.windows.server.sbs)
  • Roaming Profiles not working properly for 1 user
    ... I have recently setup roaming profiles for several users and it's working ... The failure is that on the workstation ... It does download data from profile path ... made on the workstation to propogate to the server so that backups can be ...
    (microsoft.public.windows.server.setup)