Terminal Services Roaming Profiles

[Guest Irnbru]

I'd appreciate any thoughts on the following issue...

 

I have a farm of 5 Windows 2003 SP1 Citrix servers, to which users are

connecting via Windows XP.

 

On one of my servers I've created a new share called \\Servername

\TSProfiles$ and configure the permissions appropriately.

 

Then for testing I used the terminal services profile tab on my AD

user account in order to point to the folder. \\Servername\TSProfiles$

\%username%. Unfortunately when logging on to Citrix or when using

RDP itself, it won't create a roaming profile. I've used this exact

process within a single server VirtualPC instance and it worked fine,

however there are vast differences in the group policies applied.

Including loopback processing in the real environment.

 

As an alternative I've tried using group policy to apply the path \

\Servername\TSProfiles$ and experienced exactly the same result...

 

"Event ID: 1523. Your roaming profile (read only) is not available.

You are logged on with the locally stored profile. This may be caused

by incorrect file system permissions or network problems. Contact

your network administrator. DETAIL - The system cannot find the file

specified."

 

What is confusing is that it works with my testing in a simple

environment. Does anyone have any good trouble shooting suggestions?

Note that I've confirmed "ProtectionMode" is set to 1 in the registry.

 

Thanks in advance

[Guest Vera Noest [MVP]]

Re: Terminal Services Roaming Profiles

 

Make sure that offline caching is turned off on the profile share.

If that doesn't solve it, enable verbose logging of the user

environment to see exactly where the system is trying to locate the

profile.

 

221833 - How to enable user environment debug logging in retail

builds of Windows

http://support.microsoft.com/?kbid=221833

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

Irnbru <neil-quinn@hotmail.co.uk> wrote on 24 jan 2008 in

microsoft.public.windows.terminal_services:

> I'd appreciate any thoughts on the following issue...

>

> I have a farm of 5 Windows 2003 SP1 Citrix servers, to which

> users are connecting via Windows XP.

>

> On one of my servers I've created a new share called

> \\Servername \TSProfiles$ and configure the permissions

> appropriately.

>

> Then for testing I used the terminal services profile tab on my

> AD user account in order to point to the folder.

> \\Servername\TSProfiles$ \%username%. Unfortunately when

> logging on to Citrix or when using RDP itself, it won't create a

> roaming profile. I've used this exact process within a single

> server VirtualPC instance and it worked fine, however there are

> vast differences in the group policies applied. Including

> loopback processing in the real environment.

>

> As an alternative I've tried using group policy to apply the

> path \ \Servername\TSProfiles$ and experienced exactly the same

> result...

>

> "Event ID: 1523. Your roaming profile (read only) is not

> available. You are logged on with the locally stored profile.

> This may be caused by incorrect file system permissions or

> network problems. Contact your network administrator. DETAIL -

> The system cannot find the file specified."

>

> What is confusing is that it works with my testing in a simple

> environment. Does anyone have any good trouble shooting

> suggestions? Note that I've confirmed "ProtectionMode" is set to

> 1 in the registry.

>

> Thanks in advance

[Guest Irnbru]

Re: Terminal Services Roaming Profiles

 

On 24 Jan, 20:50, "Vera Noest [MVP]" <vera.no...@remove-

this.hem.utfors.se> wrote:

> Make sure that offline caching is turned off on the profile share.

> If that doesn't solve it, enable verbose logging of the user

> environment to see exactly where the system is trying to locate the

> profile.

>

> 221833 - How to enable user environment debug logging in retail

> builds of Windowshttp://support.microsoft.com/?kbid=221833

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting:  http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

 

 

Thanks Vera,

 

Unfortunately I can't do logging until Monday, however I'm sure that

offline caching was turned off. Interestingly enough by copying the

account's local profile to the roaming profile location, at log on the

roaming profile is loaded. However if any changes are made they are

not written to the TS roaming profile at logoff. So the problem seems

to bethat the users can't write to the share location. When I look at

the profile folder's property page the 'Read only' check boxed is

greyed suggesting that it is read only for some users, although since

I copied the NTFS permissions from our 'normal' user roaming profiles

folder I had expected these to work.

 

Is there anything that could be configured which is forcing this as a

manditory instead of a roaming profile, or should I focus on the NTFS

permissions?

[Guest Vera Noest [MVP]]

Re: Terminal Services Roaming Profiles

 

Irnbru <neil-quinn@hotmail.co.uk> wrote on 25 jan 2008 in

microsoft.public.windows.terminal_services:

> On 24 Jan, 20:50, "Vera Noest [MVP]" <vera.no...@remove-

> this.hem.utfors.se> wrote:

>> Make sure that offline caching is turned off on the profile

>> share. If that doesn't solve it, enable verbose logging of the

>> user environment to see exactly where the system is trying to

>> locate the profile.

>>

>> 221833 - How to enable user environment debug logging in retail

>> builds of Windowshttp://support.microsoft.com/?kbid=221833

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

>> TS troubleshooting:  http://ts.veranoest.net

>> ___ please respond in newsgroup, NOT by private email ___

>

>

> Thanks Vera,

>

> Unfortunately I can't do logging until Monday, however I'm sure

> that offline caching was turned off. Interestingly enough by

> copying the account's local profile to the roaming profile

> location, at log on the roaming profile is loaded. However if

> any changes are made they are not written to the TS roaming

> profile at logoff. So the problem seems to bethat the users

> can't write to the share location. When I look at the profile

> folder's property page the 'Read only' check boxed is greyed

> suggesting that it is read only for some users, although since

> I copied the NTFS permissions from our 'normal' user roaming

> profiles folder I had expected these to work.

>

> Is there anything that could be configured which is forcing this

> as a manditory instead of a roaming profile, or should I focus

> on the NTFS permissions?

 

This smells like an NTFS permission problem.

Check the rules for inheritance of permissions on the shared

profile folder.

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___