Jerry said:
I have a user, that when he logs on to the network, his desktop is
bare, but if i go to documents and settings\username\desktop\ i see
all his files, shortcuts and exe's
Hmmm - I'm wondering why would he have executables?
Regardless, I take it you aren't using folder redirection....this is a must
if you use roaming profiles, and is a really good idea even if you don't.
The profile needs to be kept tiny, and if you redirect My Documents,
Application Data & Desktop, it will be ....and nothing really important will
be stored in the profile if it does happen to go belly-up entirely.
this is the second time this has happened to him, and i have fixed it
both times by logging on as the local admin, renaming his profile on
the local machine,
I wouldn't rename it. If you want to remove a cached profile, do it in
control panel | system | advanced.... or use delprof from the resource kit.
What you're doing now isn't going to remove the old cached registry stuff
that is also part of the profile.
and then having him re-log on and pull down his
roaming profile.
is there a known cause/fix for this?
thank you
Check the event logs for errors (esp source=userenv).
Download & install the user profile hive cleanup service on all PCs.
Here's my boilerplate on roaming profiles....
--------------------------
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! (that's on by default - disable it)
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 not 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. Via group policy, redirect My Documents at the
very least - to a subfolder of the user's home directory or user folder.
Also consider redirecting Desktop & Application Data similarly..... so the
user will have:
\\server\home$\%username%\My Documents
\\server\home$\%username%\Desktop
\\server\home$\%username%\Application Data.
Alternatively, just manually re-target My Documents to
\\server\home$\%username% (this is not optimal, however.
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/...6D-8912-4E18-B570-42470E2F3582&displaylang=en