Re: roaming profiles

rajeshmehta832 <> wrote:
> i have created a roaming profile of users through active directory.for
> this i created a shared folder on server with full permission.when i
> create user throug active directory.i set profile path in user for
> example for rajesh (profile path will be \\file-server\share folder
> name\rajesh .)
>
>
> when i login on client system after joing computer with domain it
> logs.and we lof off then it transfer all data to server.also it leaves
> copy of data on local computer.i do not want that a roaming profile to
> leave a copy on local computer.

Yep, that's what they do by default. You can set up a GPO to remove the
locally cached copy. http://support.microsoft.com/kb/274152
I don't like to do this in general - it takes much longer when people log
in, if they have to download a profile every time.
>
> and second thing is when i log off then it transfer all data to
> server.

Don't use offline files. You don't have to use them just because you use
roaming profiles.

> i want to transfer data while user creating at the same time to
> the server not the time of log off.can we synchronise all data from
> client to server when user create it in real time.i means at the same
> timme when it creates any file on his computer.

No, offline files doesn't work that way. Just have them work "live" on the
server data. Offline files is not something I would want on any
LAN-connected computer - maybe a laptop (although I have other methods for
those). Then this is not an issue.

My boilerplate on roaming profiles is below.

********************
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 - if this is an existing user
with a profile you wish to keep, have them log in at their usual
workstationand 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. Do this *before* the users' roaming profile folders
are created - it isn't retroactive.

********************
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, which has major disadvantages),. Explain that the 'last one out wins'
when it comes to uploading the final, changed copy of the profile. If you
want to restrict multiple simultaneous network logins, look at LimitLogon
(too much overhead for me), or this:
http://www.jsifaq.com/SF/Tips/Tip.aspx?id=8768

********************
Keep your profiles TINY. Via group policy, you should be redirecting 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 end up with:

\\server\users\%username%\My Documents,
\\server\users\%username%\Desktop,
\\server\users\%username%\Application Data.

[Alternatively, just manually re-target My Documents to
\\server\users\%username% (this is not optimal, however!)]

You should use folder redirection even without roaming profiles, but it's
especially critical if you *are* using them.

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.

*********************
If you also have Terminal Services users, make sure you set up a different
TS profile path for them in their ADUC properties - e.g.,
\\server\tsprofiles$\%username%

********************
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/d...displaylang=en

********************
Roaming profile & folder redirection article -
http://www.windowsnetworking.com/art...rver-2003.html