Re: roaming profiles

Tech-Archive recommends: Speed Up your PC by fixing your registry

Good point about the desktop files.

I set these up as you have suggested about three weeks ago. I then
activated redirected documents in the sbs server management window.

I have done this before on an enterprise system (every server had a
different function) but this is the first time for sbs.

None of these users roam but they like the thought that if their computer
dies they can jump on another computer.

So back to my orginal question. These couple of users have not done any of
the usual suspicious things that would make me think they've corrupted their
profile.

My first instinct would be to take control of her profile and delete it and
just let the system create another one. (Yes, I did give everyone full
control on the share). This is my first SBS setup for a client that is
mission orientated. (My enterprise setup was in a non-profit CTC so if I
messed up something it wasn't like the executive director lost her last three
grant proposals she was working on)

So the final question is why would she not be able to save to her profile on
logging out but it gives no errors when she logs in. Secondly, is there
anything I am not thinking of that she would lose if I just delete her
profile and let the system create a new one.

I'll also put the hive cleanup on their computers as you've suggested.
Thanks....

Albert

"Lanwench [MVP - Exchange]" wrote:

In news:4611742E-6ED3-4EAF-AAA9-CAFE9916E77D@xxxxxxxxxxxxx,
Albert Bricker <AlbertBricker@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
I have set up my SBS 2003 for my users to have roaming profiles as
well as redirected documents. This setup was done about 3 weeks ago.
No some of my users are getting the unable to locate network profile
error. Others are not getting the error until they sign off and it
says their roaming profile cannot be located or has insufficient
security rights.

What could be causeing this? I actually did this so that their my
documents would be on the server and backed up. Since I have set up
redirected documents to take care of this problem. They do not roam
from computer to computer. Should I just disable roaming profiles?
If I do by deleting the remote profile path will they just revert to
a local profile with no errors?

Or is there a better solution??????

Thanks,
Albert Bricker

I like roaming profiles, if you set them up right. Here's my boilerplate.

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



.

Quantcast