Roaming profile location being misinterpreted.

[Guest BMC]

We set the location for users' roaming profile through terminal services

through the GPO setting "Set path for TS Roaming Profiles". This expects the

setting to be specified as \\Computername\Sharename. The explain text further

details that a placeholder for the username (%username%) should not be added

as this is appended automatically.

 

With this setting set to the location we want, \\user\tsprofiles, this

should therefore be interpreted not as the location at which all users'

profiles should reside, i.e.

user1's profile is at \\user\tsprofiles\user1

user2's profile is at \\user\tsprofiles\user2

 

Today however, when any user tries to log on, Windows tries to load the

entire contents of \\user\tsprofiles (including every user's profile) into

the local profile.

 

Having created a new share (\\user\tsprofiles2) and repointed the location

in the policy, any user logging on sees this message:

Windows did not load your roaming profile [...] Windows did not load your

profile because a server copy of the profile folder already exists that does

not have the correct security. Either the current user or the administrator's

group must be the owner of the folder. Contact your network administrator.

 

There are no folders already in the share. The owner of the share is the

domain administrators. All authenticated users have full control to the

share, so createing a folder shouldn't be a problem.

The contents of userenv.log suggest that again the server is trying to load

the profile from \\user\profiles2, not creating a profile as

\user\profiles2\user1:

USERENV(198.1114) 12:50:29:843 LoadUserProfile: lpProfileInfo->lpProfilePath

= <\\USER\PROFILES2\>

 

Any ideas why this is happening?