Re: Local Profiles on Terminal Server
There is no way to stop the server from creating a local copy of
the roaming profile when the users logon.
The only supported way to change the location of the local profile
is by an unattended install of the server's OS, as described here:
236621 - Cannot Move or Rename the Documents and Settings Folder
http://support.microsoft.com/?kbid=236621
The above article also describes an unsupported way, but it's a
pain to do if you have more than a handfull of profiles, and I
would strongly recommend against it.
But as I wrote, when you delete the locally cached copy of the
profile when users logoff, disk space shouldn't be a problem, since
you will never have more profiles on the C: drive than the number
of concurrent users.
You won't be able to test this in the way you describe, since the
GPO setting to delete cached copies of the profile is a Computer
Configuration setting. It will apply to all users of the TS,
irrespective of the location of the user account in AD.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting:
http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
"Sarah Kingswell" <skingswell@xonitek.co.uk> wrote on 26 jul 2007
in microsoft.public.windows.terminal_services:
> Thanks Vera. In my situation all of the TS users are on the
> LAN. Therefore there shouldn't be any slow connections. I
> couldn't quite work out how I prevented the server from creating
> the cached copy as I really want to free up some disk space.
>
> I'd like to test this. Can you see any reason why I can't
> create a test OU and move one of the user's into the OU and test
> the delete cached copy option. If I redirect the profile to the
> D drive against the test OU GPO and set delete cached copy,
> should I only see the profile on the D drive. I will delete the
> profile on the C drive after logging successfully the first
> time. I am guessing I shouldn't get the user's profile on C.
> Is this correct
>
> "Vera Noest [MVP]" <Vera.Noest@remove-this.hem.utfors.se> wrote
> in message
> news:Xns9979A45F0429Averanoesthemutforsse@207.46.248.16...
>> The roaming TS profiles should be stored on a fileserver which
>> is located on the same network as the Terminal Servers, to
>> avoid long logon times.
>> If there is no other server available, you can even store them
>> on a shared folder on another drive on the TS.
>>
>> If the reason for wanting to implement roaming profiles is to
>> free up space on the server's C: drive (as the OP wrote), then
>> you have to delete the locally stored copies of the roaming
>> profiles. If you don't do that, you won't gain any disk space
>> at all.
>>
>> You can configure (also with a GPO) exactly what you want to
>> happen when a slow network link is detected, but you should
>> avoid slow network links between the TS and the profile share.
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> *----------- Please reply in newsgroup -------------*
>>
>> =?Utf-8?B?SmVmZg==?= <Jeff@discussions.microsoft.com> wrote on
>> 26 jul 2007:
>>
>> > Actually, that is the way I am setup except for the Deleting
>> > cached roaming profiles, I may do this but I have a question
>> > about it before implementing.
>> >
>> > Is there a substantial performance degradation in users
>> > logging in if you have 50+ users logging in at 8AM if you
>> > delete the cached roaming profiles? I was thinking of
>> > applying this after reading your reply but was curious about
>> > performance or slow network detection settings being enabled.
>> > If you have slow network detection enabled what happens if
>> > the cached copy is gone?
>> >
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> While this is true, a more efficient way to do this is to
>> >> define a roaming profile path in a GPO which is linked to
>> >> the OU which contains the terminal Servers:
>> >>
>> >> Computer Configuration - Administrative templates - Windows
>> >> Components - Terminal Services
>> >> "Set path for TS roaming profiles"
>> >>
>> >> That way, you don't have to change individual user accounts.
>> >>
>> >> When users logon, a copy of their roaming profile will still
>> >> be created in the C:\Documents and Settings folder, so be
>> >> sure to also use the GPO setting:
>> >>
>> >> Computer Configuration - Administrative Templates - System -
>> >> User profiles
>> >> "Delete cached copies of roaming profiles"
>> >>
>> >> This will ensure that your C: drive never stores more
>> >> profiles than the number of active users on the server.
>> >> _________________________________________________________
>> >> Vera Noest
>> >> MCSE, CCEA, Microsoft MVP - Terminal Server
>> >> TS troubleshooting: http://ts.veranoest.net
>> >> ___ please respond in newsgroup, NOT by private email ___
>> >>
>> >> =?Utf-8?B?SmVmZg==?= <Jeff@discussions.microsoft.com> wrote
>> >> on 26 jul 2007 in
>> >> microsoft.public.windows.terminal_services:
>> >>
>> >> > I'm not completely familiar with thin client terminals,
>> >> > but if you pull up the user in Active Directory and go to
>> >> > the Terminal Services Profile tab you can set a path for
>> >> > their profile. After you create the share and location for
>> >> > the profile and set the path in Active Directory you can
>> >> > copy their terminal profile (in C:\documents etc.) to that
>> >> > location. After the settings replicate to all DC's that
>> >> > the user may authenticate to, the session should use the
>> >> > roaming terminal profile you setup. One silly way to test
>> >> > if it works is to have them put a blank text file on their
>> >> > desktop and log off. You can check both profiles to see
>> >> > which Desktop it placed it in.
>> >> >
>> >> > "Sarah Kingswell" wrote:
>> >> >
>> >> >> For obvious reasons I would like to change the location
>> >> >> of the local user profiles on my Terminal Server. I have
>> >> >> several user's connecting to the Terminal server from
>> >> >> thin client terminals and I want to move the user profile
>> >> >> to a different drive which has more space. I have tried
>> >> >> to setup terminal server profiles against the user
>> >> >> account but I cannot get this working. I am not be
>> >> >> understanding exactly what this does but am I wrong in
>> >> >> thinking that I can do away with the profiles in the
>> >> >> default c\documents and settings\user.. folders.
>> >> >>
>> >> >> Any guidance appreciated.
>> >> >>
