Roaming User Profile - Wikipedia
Roaming User Profile - Wikipedia
Method of operation
When the user logs off from the desktop computer, the user's roaming
profile is merged from the local computer back to the central file server,
not including the temporary local profile items. Because this is a merge and
not a move/delete, the user's profile information remains on the local
computer in addition to being merged to the network.
When the user logs in on a second desktop computer, this process repeats,
merging the roaming profile from the server to the second desktop
computer, and then merging back from the desktop to the server when the
user logs off.
When the user returns to the first desktop computer and logs in, the
roaming profile is merged with the previous profile information, replacing
it. If profile caching is enabled, the server is capable of merging only the
newest files to the local computer, reusing the existing local files that have
not changed since the last login, and thereby speeding up the login process.
Limitations
Performance
Due to the profile copying at login and logout, a roaming profile set up
using the default configuration can be extremely slow and waste
considerable amounts of time for users with large amounts of data in their
account.
File servers tend to only transfer large files several megabytes in size at the
fastest possible network speed. Hundreds of very small files only a kilobyte
per file can reduce network performance by 90%. As a profile ages and
accumulates hundreds to thousands of cookies, favorites, and Recent
items, the login and logout times become progressively slower, even
though these files occupy only a few megabytes of profile data.
Local caching of the user profile on a desktop computer hard drive can
reduce and improve login and logout times, but at the penalty of cluttering
up the hard drive with profile data from every cached user who logs in.
Local caching is more suitable where people tend to use the same computer
every day. Local profile caching is not useful where hundreds to thousands
of students need to be able to use any computer across a school or
university campus—the cumulative cached data from so many different
profiles can consume all available lab computer disk space.
WAN links
Users with a roaming profile can encounter crippling logon delays when
logging in over a WAN. If connected to the domain from a remote site,
after authentication, Windows will attempt to pull the user's profile from
the location specified in Active Directory. If the location happens to be
across a WAN link it can potentially slow the WAN down to a crawl and
cause the logon to fail (after a very lengthy delay).
Users with a roaming profile working from a remote site should login to
the machine before connecting to the network, (so that the machine uses
its cached local copy) and connect to the network after logon has
Profile size
Working with large files, such as editing raw videos, can cause excessive
login and logout times, as Windows will copy files in the roaming profile to
the computer on login and back to the server on logout.
In environments where the large files are not mission-critical and do not
absolutely need to be backed up to a server on a per-login basis, the
applications requiring such excessively large amounts of user data are
instead usually run on a stand-alone local account that does not roam, to
bypass these network storage and retrieval problems.
Network congestion
Synchronization at logoff
Access conflict
Logging onto multiple computers with one account, and opening the same
document multiple times on each computer can result in inconsistencies
and loss of saved changes if the file is modified on two different computers
at the same time:
When the first computer with the modified document logs off, the
changes are written to the network copy of the profile.
When the second computer logs off, the different document version
overwrites the previously saved changes during profile logout.
Compatibility
Folder redirection
The question may be raised as to why the entire roaming profile can not be
accessed directly on the server, and no copying needs to be done at all. The
reasoning for this appears to be that certain Microsoft programs running
all the time on the client computer can not tolerate the sudden loss of their
data folders if the server goes down or the network is disconnected. Some
portions must still be copied back and forth before the desktop appears so
that these folders are available if the network-redirected folders go down.
Caveats
Some programs do not work properly with redirected profile folders that
refer to a UNC file path on a server share:
\\server\share\username\Application Data
These problems with UNC paths can usually be fixed by having the folders
redirected to a drive mapping for the UNC share:
Mandatory profiles
https://en.wikipedia.org/wiki/Roaming_user_profile Pagina 8 van 15
Roaming user profile - Wikipedia 06-01-18 02(42
Setup methods
Active Directory
Users and Computers snap-in. Windows NT 4.0 and earlier used the User
Manager for Domains program. When a user logs into a computer joined
to a domain, the roaming user profile is downloaded from the server onto
the local computer and applied. When the user logs off, the changes made
to the roaming profile are transferred back to the location where the users
roaming profile is stored.
Roaming profiles on Windows 95, 98 and Me are all compatible with each
other so if a network has mixture of Windows 95 and Windows 98
workstations the same user profile may be used for each workstation. This
is also the case with Roaming profiles between Windows NT 4.0, Windows
2000, Windows XP but there may be some compatibility issues due to
differences in each version of Windows. Roaming profiles in Windows
Vista and Windows 7 are compatible with each other but these versions are
not compatible with earlier versions of Windows. A separate profile folder
with the extension .V2 will be created when using Roaming profiles with
Windows Vista or 7. The easiest solution is to have all workstations
running the same version of Windows. (see Compatibility section)
Remote Desktop Server users can have a separate roaming profile to the
roaming profile used on a local desktop PC. The roaming profile for remote
desktop user is specified under the "Remote Desktop Services Profile" tab.
This applies to users who connect to a remote desktop server using Citrix
Novell eDirectory/Netware
For roaming to work with Novell servers, the Novell product "ZENworks
Desktop Management" needs to be installed on the server, and its
associated workstation management package installed on each of the client
computers. Within the directory, a User Package object is created, which
enables roaming, specifies where the roaming profile is stored, and also
stores any associated group policies for each version of Windows where
users will login. The User Package also enables Dynamic Local User, which
functions similar to Active Directory, allowing an account created in
eDirectory to log in on any desktop computer even if no local account exists
in advance, and assigns local account privileges such as User, Power User,
or Administrator to the newly created local user account. For Windows NT
the user profile files are stored in the users home directory under a
subfolder for each version of Windows, for example in Windows NT 4.0 the
folder will be called "Windows NT 4.0 Workstation Profile" and in
Windows XP the folder will be called "Windows NT 5.1 Workstation
Profile"
The User Package can be associated with a specific user account in the
directory, or is associated with an organizational unit that then applies to
all user accounts within that OU. The User Package also enables additional
ZENworks Desktop Management functions, such as remote view and
remote control of the desktop computer, network printers that follow the
user from one desktop to the next, and the scheduling of events that are to
be run wherever the user is logged in.
Windows 3.x
While Windows 3.x does not contain user profiles it was possible for users
to have their own personalised desktop in a business environment.
Resetting a profile
Advantages
Disadvantages
https://en.wikipedia.org/wiki/Roaming_user_profile Pagina 12 van 15
Roaming user profile - Wikipedia 06-01-18 02(42
Each time a user logs into a workstation, all of the files and settings are
transferred over the network; the result is that the login process takes
longer than if the user were to use a local profile. This is particularly the
case if the profile is large in size. The login time may be reduced if the
profile is cached as some files can be loaded from the local workstation and
by using folder redirection to redirect folders that can grow to a large size,
like My Documents, to a network share.
corruption, since Microsoft did not intend this for their application data to
be shared between the different OS versions.
Alternatives
See also
Folder redirection
References
External links