User Profiles Setting In Group Policy

By Author: iris
Total Articles: 286
Comment this article

In Windows Server 2003, there are several Group Policy settings that affect A+ training course user profiles:
Prevent Roaming Profile Changes From Propagating To The Server Thispolicy determines if the changes a user makes to his or her roaming profile are
merged with the server copy of his or her roaming profile. If this policy is set at
user logon, the user receives his or her roaming profile, but any changes the user
makes to his or her profile will not be merged to his or her roaming user profile
at logoff.
Add The Administrator Security Group To Roaming User Profiles This policy allows an administrator to choose the same behavior as Windows NT 4 and
permit the administrators group to have full control of the user's profile directories. In Windows Server 2003, the default file permissions for newly generated roaming profiles are full control, or read and write access for the user, and no file access for the Administrators group.
Only Allow Local User Profiles This setting determines whether roaming user profiles are available ...
... on a particular computer. By default, when roaming profile users log on to a computer, their roaming profile is copied to the local computer.
By using this setting, an 220-702 exam administrator can prevent users configured to use roaming profiles from receiving their roaming profile on a specific computer.
Temporary User Profiles
A temporary user profile is issued any time an error condition prevents a user's profile from being loaded. Temporary profiles are deleted at the end of each session. Changes made to a user's desktop settings and files are lost when the user logs off.
Creating Roaming User Profiles
Create roaming user profiles on a file server that you frequently back up, so that you have copies of the latest roaming user profiles. To improve logon performance for a busy network, place the roaming user profile folder on a member server instead of a domain controller. The copying of roaming user profiles between the server and client computers can use a lot of system resources, such as bandwidth and computer processing. If the profiles are on the domain controller, this can delay the authentication of users by the domain controller.
The Windows Server 2003 family does not support the use of encrypted files within the roaming user profile. Roaming user profiles that are used with Terminal Services clients are not replicated to the Free Network+ study guides server until the interactive user logs off and the interactive session is closed.