Force Local Profile to be used

[primate]

Hi,

This isn't a strictly Citrix question but I think its relevant to this forum.

I have a Win2K domain with two AD sites separated by a VPN. There is one Metaframe XPs server at one site. Citrix sits on a Win2K box.

Users have roaming user profiles and increasingly this is causing issues for users at the other end of the VPN since when they login to the Citrix box it drags their profile from the remote end. As some users have increasingly large profiles this is either causing huge delays or errors when logging in.

I have tried specifying a Terminal Services user profile for the affected users but this doesn't seem to do anything.

I've also tried specifying the following settings in the GPO applied to the OU in which the server sits:

Only allow local user Profiles - enabled
Prevent roaming profile changes from propagating to the server - enabled

The combination of these two settings is supposed to disable roaming profiles yet there seems to be no effect.

Confusing.......

Can anyone offer me some help? Please??

 

[Klae]

How did you set the Terminal Services profile? Did you enter it in as a UNC? e.g. "\\FileServer\HomeShare\ProfileFolder". In the "profileFolder" have you put a profile consisting of all the folders and the ntuser.dat (or ntuser.man) file at the root of "profilefolder"? Did you also set the appropriate permissions so they could see it and download it? If you do set a TS profile then I recommend you make it a mandatory one so each user gets the same basic small profile that doesnt't update and more importantly get any larger.

Klae

You're only as good as your last answer!

 

[CitrixEngineer]

I'd go one step further and recommend a hidden share on a file server for TS profiles - e.g. \\FileServer\profiles\username$ and use it for roaming profiles with paths to user files pointed to their home drives via Group Policy. If the fileserver is on the same LAN as the Citrix servers, it will take no time to load.

Hope this helps