Differences between Roaming Profiles and ProfileimagePath

We have and RDS cluster everythings is working fine.

We use roaming profiles, redirection to a share is working as well.

When a user logs on to any RDS node we can see a user folder appear in E:\Users\ of the RDS Server.

When I checked the registry, and i can see 2 keys about profiles :
– you can see that the redirection is OK : Centralprofile (in my exemple \\Sharename\…)
– you can see a ProfileImagePath to E:\Users

So what is :
– A ProfileImagePath ?
– A CentralProfile ?

E:\Users\<username> is the local cache of the roaming profile.  I’ve never seen a setting to avoid caching of the profile on the local system entirely.

There is a group policy setting to automatically delete the cached copy upon user logout. It’s under Computer Configuation->Policies->Administrative Templates->System->UserProfiles->Delete cached copies of roaming profiles.

Plus side : This avoids disk space from caching the users profiles

Down side
It will probably increase the logon time as the full profile will have to copy every time.
When testing, this also cleared out the cache from a custom application which didnt right back to the roaming profile.

Group Policy –Add the Administrator security group to roaming users profiles

Tested on Windows 2008 R2

Create a GPO – “Add the Administrator security group to roaming users profiles”

Computer Configuration > Policies > Administrative Templates > System > User Profiles” and applied to Windows XP / 2003 or later.

Add the Administrator security group to roaming users profiles

This setting adds the administrator ACL to the users roaming profile path on the server when it is first created.

Administrator are able to view users profiles without the need to take ownership

Enable this option as soon as possible as this setting does NOT apply retrospectively to existing users profiles as it only applied the administrators group to the profile when the roaming profile when  it is created on the server for the first time.

Original detail posted by Alan Burchill

 

Check if an AD user has a roaming profile configured (PowerShell) – OneScript Team

Check if an AD user has a roaming profile configured (PowerShell)

This script can query specified active directory users whether or not a roaming profile was configured.

Scenarios

IT admins may care about which users has a roaming profile was configured. This script can help IT admins check whether or not a roaming profile was configured.

Script

Step 1: Run the script in the Windows PowerShell Console, type the command: Import-Module <Script Path> at the prompt.  For example, type Import-Module C:\Script\CheckIfProfileExists.psm1

This is shown in the following figure.

Step 2: Type the command Get-Help Get-OSCADUserRoamingProfile -Full to display the entire help file for this function, such as the syntax, parameters, or examples.

OneScript Team

Temp Profile issue 2008 R2 RDS using roaming profiles

Issue
Some of our users keep getting logged on with a temporary profile.

Scenario
We have an RDS cluster using Window 2008 R2 x64 and users are setup with roaming profiles.

Profiles going to \\server\users\%username% Intermittently the folder is being created in the profile share but the folder is empty.

Permissions checked ok Shares checked ok

Cause
Possibly caused by a server crash corrupting the profiles instead of a natural logoff allowing the profile to write back.

Solution
Browse the registry on your terminal server under :  LM\software\Microsoft\Windows NT\CurrentVerision\ProfileList

Look for any keys under ProfileList with an extension “.bat”
Select key and click delete (export or backup any keys before making changes or deletions first.)

Solution found here : http://www.brianmadden.com/