Re: uphclean tool
rocketz21 <rocketz21@discussions.microsoft.com> wrote:
> Does anyone have some experience or know anything about the uphclean
> tool and how it works? We use roaming profiles on a small one domain
> company and experience strange issues time to time and wondering if
> it's recommended to use this tool or not.
It's part of my standard workstation build, and has been for years. There's
no downside to installing the service. I don't know why it's not built in,
frankly.
>
> Sometimes a user won't be able to log on with their roaming profile
> and logs them on with a default temp profile, sometimes the folder
> gets reset to a default empty desktop, other times the desktop
> doesn't even load and you need to restart. Just weird things like
> that and just curious if this tool is good to use on client pcs and
> what's the benefit? I don't want to slow down logon times anymore
> than they already are.
It won't slow anything down - but it not fix your problem, either.
Below is my boilerplate on roaming profiles....maybe something in there will
help isolate the cause of your issue. Of course, you will want to start by
reviewing the event logs on the workstation when you're having a profile
error.
---
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! (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