ok, I'm still struggling here...previous mail to thinlist attached below... the update is this... I have spoken with Microsoft and they have agreed to raise a change request to get this TS profile overrride to recognise the need to override with mandatory profiles!! in the meantime, I'm up a creek full of stuff without a paddle...and desperately need a migration mechanism.. this is my current plan.... ** change the default user profile to be a mandatory profile and continue to load the user hive on top using flex profile.. The problem with this however, is how to get the server to recognise that it should use the default profile and not the users normal roaming profile defined in the profile section of their user id in the AD? cheers, Brianos Previous message sent was..... Hi list! I am migrating 1.8 metaframe users from roaming user profiles to flex profiles. These users will continue to access their old 1.8 farms using the traditional client/server roaming user profiles but will use flex profiles with super mandatory profiles when accessing the shiney new ps3 global farm. So, as I am implementing 2003 TS servers, I thought I would simply override the TS profile using the GPO setting 'Set path for TS Roaming Profiles' so the 2003 servers only would direct the user to the mandatory profile. However, on first glance the 'Set path for TS Roaming Profiles' overrides the contents of the users' AD TS profile path, but it then seems to simply create a user directory under that share and not actually load the mandatory profile. As per its description -- "Specifies whether Terminal Services uses the specified network path for roaming user profiles. You can use this setting to specify a network share where the profiles are stored, allowing users to access the same profile for sessions on all terminal servers in the same organizational unit. By default, Terminal Services stores all user profiles locally on the terminal server. To use this setting, type the path to the network share in the form \\Computername\Sharename. Do not specify a placeholder for user alias, because Terminal Services automatically appends this at logon. If the specified network share does not exist, Terminal Services displays an error message at the server and stores the user profiles locally. If the status is set to Enabled, Terminal Services uses the specified path as the root directory for all user profiles. The profiles themselves are contained in subdirectories named for the alias of each user. If the status is set to Disabled or Not Configured, user profiles are stored locally on the server, unless specified otherwise by the server administrator. Note: The roaming profiles specified with this setting apply to Terminal Services connections only; a user might also have a Windows roaming profile, in which case the Terminal Services roaming profile always takes precedence in a Terminal Services session." So, how does one user mandatory profiles with this overrride? Maybe a question for the boys at Login? thanks again all for any help received ============================================================================== This message is for the sole use of the intended recipient. If you received this message in error please delete it and notify us. If this message was misdirected, CSFB does not waive any confidentiality or privilege. CSFB retains and monitors electronic communications sent through its network. Instructions transmitted over this system are not binding on CSFB until they are confirmed by us. Message transmission is not guaranteed to be secure. ============================================================================== ******************************************************** This Weeks Sponsor Activaeon.com Reduce licensing costs with activAeon XA and get one month completely free. http://www.activaeon.com ********************************************************** Useful Thin Client Computing Links are available at: http://thin.net/links.cfm ThinWiki community http://www.thinwiki.com *********************************************************** For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link: http://thin.net/citrixlist.cfm