Re: Roaming profiles vs OffLine File Sync
- From: PWT24 <PWT24@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 28 Sep 2006 06:41:03 -0700
Lanwench, I would like more info on roaming users in SBS2003 can you help? I
thought a roaming user meant simply logging off "system A" as user 1 and
logging into "system B" as user 1. Is this not a roaming user? If not where
do I get more info?
Thanks!
"Lanwench [MVP - Exchange]" wrote:
In news:ungWfCo4GHA.1848@xxxxxxxxxxxxxxxxxxxx,.
Mark Semans <mark_semans@xxxxxxxxxxxxx> typed:
I have my 1st SBS with 8 XP Pro clients. I originally set them up
with profile and My Docs redirected to the server.
With Users usually only using 1 PC, my thought was to allow them to
log into other machines, if a hardware failure occured, until I could
get the PC replaced (this is for our church, and I travel...).
Of course, I found if the server was not available, no body could log
in.... The server is is for file backup and Exchange to share
calendars (for resource scheduling).
Question is, how can I convert back to Off-line file sync (of My
Doc's), or is there a better way to do this?
If the server is not available, I still want users to be able to
login and use their PC
I have NOT converted anyone over to the Exchange server (they use
Outlook directly to the ISP)., but I am paranoid about adding a new
profile and moving data (which was one way I was told).
Since I am a real newbie at this, I'm looking for some direction to
point me in......and maybe some good learning material also.....
Thanks alot!
I love roaming profiles, and I love folder redirection. But I'm very wary of
offline files - and I especially don't like them with roaming profiles. I
suspect it will not work nicely for you as the workstation's offline file
cache is, as far as I know, shared file space - and I think you'll end up
with odd error messages when multiple domain users log in to the same
workstation and try to sync.
Ultimately, the best way to ensure your users can get to their data, is to
build a robust server with as much good & redundant hardware you can throw
at it, and keep an eye on it via the built in monitoring tools.
Note that roaming profiles, even without offline files, are going to be a
problem for you as you say they aren't yet using Exchange. The PST files
won't roam, and MS doesn't support accessing PST files across a LAN / WAN
connection. Many people *do* this anyway, but it is not recommended due to
performance issues and potential data loss. Just bite the bullet and migrate
them all to Exchange, and you won't have to deal with nasty PST files any
more! You should get a lot of help during this process if you plan it
thoroughly & post questions in here....
Re roaming profiles, here's my boilerplate on the topic.
General tips:
1. Set up a share on the server. For example - d:\profiles, shared as
profiles$ to make it hidden from browsing. Make sure this share is not set
to allow offline files/caching!
2. Make sure the share permissions on profiles$ indicate everyone=full
control. Set the NTFS security to administrators, system, and users=full
control.
3. In the users' ADUC properties, specify \\server\profiles$\%username% in
the profiles field
4. Have each user log into the domain once from their usual workstation
(where their existing profile lives) and log out. The profile is now
roaming.
5. If you want the administrators group to automatically have permissions to
the profiles folders, you'll need to make the appropriate change in group
policy. Look in computer configuration/administrative templates/system/user
profiles - there's an option to add administrators group to the roaming
profiles permissions.
Notes:
* Make sure users understand that they should never log into multiple
computers at the same time when they have roaming profiles (unless you make
the profiles mandatory by renaming ntuser.dat to ntuser.man so they can't
change them). Explain that the
last one out
wins, when it comes to uploading the final, changed copy of the profile.
* Keep your profiles TINY. Redirect My Documents; usually best done to the
user's home directory on the server - either via
group policy (folder redirection) or manually (far less advisable). If you
aren't going to also redirect the desktop using policies, tell users that
they are not to store any files on the desktop or you will beat them with a
stick. Big profile=slow login/logout, and possible profile corruption.
* Note that user profiles are not compatible between different OS versions,
even between W2k/XP. Keep all your computers. Keep your workstations as
identical as possible - meaning, OS version is the same, SP level is the
same, app load is (as much as possible) the same.
* Do not let people store any data locally - all data belongs on the server.
* The User Profile Hive Cleanup Utility should be running on all your
computers. You can download it here:
http://www.microsoft.com/downloads/details.aspx?familyid=1B286E6D-8912-4E18-B570-42470E2F3582&displaylang=en
- Follow-Ups:
- Re: Roaming profiles vs OffLine File Sync
- From: Lanwench [MVP - Exchange]
- Re: Roaming profiles vs OffLine File Sync
- References:
- Roaming profiles vs OffLine File Sync
- From: Mark Semans
- Re: Roaming profiles vs OffLine File Sync
- From: Lanwench [MVP - Exchange]
- Roaming profiles vs OffLine File Sync
- Prev by Date: Re: SBS2003 Contact in Active Directory Users and Computers.
- Next by Date: Re: SBS 2003 standard RDP access
- Previous by thread: Re: Roaming profiles vs OffLine File Sync
- Next by thread: Re: Roaming profiles vs OffLine File Sync
- Index(es):
Relevant Pages
|