Wednesday, May 16, 2012 8:18 PMWe have thin client users with roaming profiles. We have several that also have laptops that they travel with. We changed their profile on the laptop to LOCAL but their roaming profile still follows them when they log into the laptop, and they have no way to power it off with no Start button. How can we turn off the roaming profile for these users?
Wednesday, May 16, 2012 9:28 PM
for the laptops, you could configure the GPO "Only allow local user profiles", and maybe "Prevent Roaming Profile changes from propagating to the server" ?
Thursday, May 17, 2012 6:42 AMModeratorHi,
You can prevent computers from receiving roaming profiles by enabling the “Only allow local user profiles policy” setting, which blocks roaming profiles from being used on a computer.
By default, when roaming profile users log on to a computer, the user’s roaming profile is copied to the local computer. If the user has previously logged on to this computer, the roaming profile is merged with the local profile. Similarly, when the user logs off from this computer, the local copy of the profile, including any changes the user made, is merged with the server copy of the profile.
If you enable the “Only allow local user profiles policy” setting, the following occurs on the affected computer: When the user first logs on, the user receives a new local profile instead of the roaming profile. At logoff, changes are saved to the local profile. All subsequent logons use the local profile.
If you enable both the Prevent Roaming Profile changes from propagating to the server setting and the “Only allow local user profiles” setting, roaming profiles are disabled for that computer. These policy settings are in the:
Computer Configuration\Administrative Templates\System\User Profiles
For more information please refer to following MS articles:
Configuring Roaming User Profiles
TechNet Community Support
Thursday, May 17, 2012 3:40 PM
You mentioned your users are "thin client users", so they are connecting to TS/RDS servers correct? If so, using the TS/RDS profile path rather than the generic profile path would take of the issue as well.