Local Settings Folder within Roaming Profiles

  • Thread starter Thread starter lozza
  • Start date Start date
L

lozza

Guest
Hey Guys,

My dev setup: 2x TS Servers hooked into Session Directory. Load Balancing
achieved via DNS Round Robin. Roaming User profiles being used and pointed to
NAS device. Profile is stored on \\NAS\Profile\%UsernameOfEachUser%

My Issue: I;ve been told to limit profiles to a max of 40MB. Desktop/Start
Menu/Application Data/My Documents all redirected to their own folder on the
NAS. i.e. \\NAS\RedirectedMyDocuments\%username%,
\\NAS\RedirectedDesktop\%username%, \\NAS\RedirectedStartMenu\%username%,
\\NAS\RedirectedApplicationData\%username%.... This I believe prevents the
size of these folder counting towards the profile size as these folder are
not redirected to the Roaming Profile Path...So, First Question, Is my
understanding correct here?

So, one folder that is starting to take space is the Local Setting Folder on
each user user profile. My own profile (which is one of the smaller ones) for
example has:

C:\Documents and Settings\lozza\Local Settings\Application
Data\Microsoft\Terminal Server Client\Cache there is a file called
bcache22.bmc and this itself is 22MB

Not sure what this file is for or how it can be cleared down... any ideas
would be great? other users have varying sizes upto 100MB under other folders
located under Local Settings... Okay, so you say, but this folder by default
does not roam with the user or in turn other folders can also be excluded
from the roaming profile... that fine with me, but also confusing:

So, if this is the case... When a user logs off does this folder (Local
Settings) stay on the local machine? (i.e. the directory structure on the
machine will still remain C:\Documents and Settings\lozza\Local
Settings\Application Data\...\...\...\). What happens if cached copies of
profiles are set to delete, is this folder rebuild everytime the user logs on
and any application related settings are therefore lost? if it does stay on
the local machine, what if the next time a user comes into the cluster and
they are directed to the other server, will not having this folder as roaming
and excluded from the profile, cause user settings to not come over...

Just trying to understand what i;m getting myself in for here... before I go
starting to make changes... I hope this makes sense...

Lozza
 
Re: Local Settings Folder within Roaming Profiles

lozza <lozza@discussions.microsoft.com> wrote:
> Hey Guys,
>
> My dev setup: 2x TS Servers hooked into Session Directory. Load
> Balancing achieved via DNS Round Robin.

> Roaming User profiles being
> used

Do not use roaming profile paths for your TS users - you need to specify a
different Terminal Services profile path. You can keep your folder
redirection the same, but you have to use an entirely different folder tree
for roaming profiles. E.g.,

Regular roaming profiles: \\server\profiles%
TS profiles: \\server\tsprofiles$

> and pointed to NAS device. Profile is stored on
> \\NAS\Profile\%UsernameOfEachUser%
>
> My Issue: I;ve been told to limit profiles to a max of 40MB.
> Desktop/Start Menu/Application Data/My Documents all redirected to
> their own folder on the NAS. i.e.
> \\NAS\RedirectedMyDocuments\%username%,
> \\NAS\RedirectedDesktop\%username%,
> \\NAS\RedirectedStartMenu\%username%,
> \\NAS\RedirectedApplicationData\%username%.... This I believe
> prevents the size of these folder counting towards the profile size
> as these folder are not redirected to the Roaming Profile Path...So,
> First Question, Is my understanding correct here?

Yes.


>
> So, one folder that is starting to take space is the Local Setting
> Folder on each user user profile. My own profile (which is one of the
> smaller ones) for example has:
>
> C:\Documents and Settings\lozza\Local Settings\Application
> Data\Microsoft\Terminal Server Client\Cache there is a file called
> bcache22.bmc and this itself is 22MB
>
> Not sure what this file is for or how it can be cleared down... any
> ideas would be great? other users have varying sizes upto 100MB under
> other folders located under Local Settings... Okay, so you say, but
> this folder by default does not roam with the user

Of course. It's "local settings."

> or in turn other
> folders can also be excluded from the roaming profile... that fine
> with me, but also confusing:
>
> So, if this is the case... When a user logs off does this folder
> (Local Settings) stay on the local machine?

Yes.

> (i.e. the directory
> structure on the machine will still remain C:\Documents and
> Settings\lozza\Local Settings\Application Data\...\...\...\). What
> happens if cached copies of profiles are set to delete,

Then the local settings folder data is gone.

> is this
> folder rebuild everytime the user logs on and any application related
> settings are therefore lost?

Yep.

> if it does stay on the local machine,
> what if the next time a user comes into the cluster and they are
> directed to the other server, will not having this folder as roaming
> and excluded from the profile, cause user settings to not come
> over...

A new one will be created.
>
> Just trying to understand what i;m getting myself in for here...
> before I go starting to make changes... I hope this makes sense...
>
> Lozza
 
Re: Local Settings Folder within Roaming Profiles

Lanwench,

I like your thorough answering style, thanks man! :) So the final question
for me would be if this is local to every machine, as implied by the name of
the folder, then... what kind of real world application stuff is stored here?
any examples would be great. And also would this cause problems for roaming
users, i.e they set up a kind of application environment on one server, and
then when they log onto other (via Load balanced approach) servers, these
settings stored in Local Settings will all be lost, aren;t application
settings the important thing here when we talk about roaming profiles? I
guess i'm really confused as what this folder is actually used for...

Thanks much...
Lozza

"Lanwench [MVP - Exchange]" wrote:

> lozza <lozza@discussions.microsoft.com> wrote:
> > Hey Guys,
> >
> > My dev setup: 2x TS Servers hooked into Session Directory. Load
> > Balancing achieved via DNS Round Robin.
>
> > Roaming User profiles being
> > used
>
> Do not use roaming profile paths for your TS users - you need to specify a
> different Terminal Services profile path. You can keep your folder
> redirection the same, but you have to use an entirely different folder tree
> for roaming profiles. E.g.,
>
> Regular roaming profiles: \\server\profiles%
> TS profiles: \\server\tsprofiles$
>
> > and pointed to NAS device. Profile is stored on
> > \\NAS\Profile\%UsernameOfEachUser%
> >
> > My Issue: I;ve been told to limit profiles to a max of 40MB.
> > Desktop/Start Menu/Application Data/My Documents all redirected to
> > their own folder on the NAS. i.e.
> > \\NAS\RedirectedMyDocuments\%username%,
> > \\NAS\RedirectedDesktop\%username%,
> > \\NAS\RedirectedStartMenu\%username%,
> > \\NAS\RedirectedApplicationData\%username%.... This I believe
> > prevents the size of these folder counting towards the profile size
> > as these folder are not redirected to the Roaming Profile Path...So,
> > First Question, Is my understanding correct here?
>
> Yes.
>
>
> >
> > So, one folder that is starting to take space is the Local Setting
> > Folder on each user user profile. My own profile (which is one of the
> > smaller ones) for example has:
> >
> > C:\Documents and Settings\lozza\Local Settings\Application
> > Data\Microsoft\Terminal Server Client\Cache there is a file called
> > bcache22.bmc and this itself is 22MB
> >
> > Not sure what this file is for or how it can be cleared down... any
> > ideas would be great? other users have varying sizes upto 100MB under
> > other folders located under Local Settings... Okay, so you say, but
> > this folder by default does not roam with the user
>
> Of course. It's "local settings."
>
> > or in turn other
> > folders can also be excluded from the roaming profile... that fine
> > with me, but also confusing:
> >
> > So, if this is the case... When a user logs off does this folder
> > (Local Settings) stay on the local machine?
>
> Yes.
>
> > (i.e. the directory
> > structure on the machine will still remain C:\Documents and
> > Settings\lozza\Local Settings\Application Data\...\...\...\). What
> > happens if cached copies of profiles are set to delete,
>
> Then the local settings folder data is gone.
>
> > is this
> > folder rebuild everytime the user logs on and any application related
> > settings are therefore lost?
>
> Yep.
>
> > if it does stay on the local machine,
> > what if the next time a user comes into the cluster and they are
> > directed to the other server, will not having this folder as roaming
> > and excluded from the profile, cause user settings to not come
> > over...
>
> A new one will be created.
> >
> > Just trying to understand what i;m getting myself in for here...
> > before I go starting to make changes... I hope this makes sense...
> >
> > Lozza
>
>
>
>
 
Re: Local Settings Folder within Roaming Profiles

lozza <lozza@discussions.microsoft.com> wrote:
> Lanwench,
>
> I like your thorough answering style, thanks man! :)

No problem, lady. ;-)

> So the final
> question for me would be if this is local to every machine, as
> implied by the name of the folder, then... what kind of real world
> application stuff is stored here?

Um - lots of stuff. Temp files, temp internet explorer files, Outlook cache
files, etc.

> any examples would be great. And
> also would this cause problems for roaming users, i.e they set up a
> kind of application environment on one server, and then when they log
> onto other (via Load balanced approach) servers, these settings
> stored in Local Settings will all be lost,

Load balancing doesn't really enter into it, and I've never had a problem
with anything important in that folder which wasn't available on another PC.

> aren;t application
> settings the important thing here when we talk about roaming
> profiles?

Yes - whether roaming, or TS, or local, Application Data is where the
important stuff generally lives.

> I guess i'm really confused as what this folder is actually
> used for...

Depends on the apps you run, but mostly it's volatile data and not very
important. I can't find a page with a description of all the profile
folders, sorry. I really wouldn't worry about this too much - unless you
have problems, in which case you should post back in a new message with the
specifics of them so we can try to help.

>
> Thanks much...

Hope this helps. :)


> Lozza
>
> "Lanwench [MVP - Exchange]" wrote:
>
>> lozza <lozza@discussions.microsoft.com> wrote:
>>> Hey Guys,
>>>
>>> My dev setup: 2x TS Servers hooked into Session Directory. Load
>>> Balancing achieved via DNS Round Robin.
>>
>>> Roaming User profiles being
>>> used
>>
>> Do not use roaming profile paths for your TS users - you need to
>> specify a different Terminal Services profile path. You can keep
>> your folder redirection the same, but you have to use an entirely
>> different folder tree for roaming profiles. E.g.,
>>
>> Regular roaming profiles: \\server\profiles%
>> TS profiles: \\server\tsprofiles$
>>
>>> and pointed to NAS device. Profile is stored on
>>> \\NAS\Profile\%UsernameOfEachUser%
>>>
>>> My Issue: I;ve been told to limit profiles to a max of 40MB.
>>> Desktop/Start Menu/Application Data/My Documents all redirected to
>>> their own folder on the NAS. i.e.
>>> \\NAS\RedirectedMyDocuments\%username%,
>>> \\NAS\RedirectedDesktop\%username%,
>>> \\NAS\RedirectedStartMenu\%username%,
>>> \\NAS\RedirectedApplicationData\%username%.... This I believe
>>> prevents the size of these folder counting towards the profile size
>>> as these folder are not redirected to the Roaming Profile Path...So,
>>> First Question, Is my understanding correct here?
>>
>> Yes.
>>
>>
>>>
>>> So, one folder that is starting to take space is the Local Setting
>>> Folder on each user user profile. My own profile (which is one of
>>> the smaller ones) for example has:
>>>
>>> C:\Documents and Settings\lozza\Local Settings\Application
>>> Data\Microsoft\Terminal Server Client\Cache there is a file called
>>> bcache22.bmc and this itself is 22MB
>>>
>>> Not sure what this file is for or how it can be cleared down... any
>>> ideas would be great? other users have varying sizes upto 100MB
>>> under other folders located under Local Settings... Okay, so you
>>> say, but this folder by default does not roam with the user
>>
>> Of course. It's "local settings."
>>
>>> or in turn other
>>> folders can also be excluded from the roaming profile... that fine
>>> with me, but also confusing:
>>>
>>> So, if this is the case... When a user logs off does this folder
>>> (Local Settings) stay on the local machine?
>>
>> Yes.
>>
>>> (i.e. the directory
>>> structure on the machine will still remain C:\Documents and
>>> Settings\lozza\Local Settings\Application Data\...\...\...\). What
>>> happens if cached copies of profiles are set to delete,
>>
>> Then the local settings folder data is gone.
>>
>>> is this
>>> folder rebuild everytime the user logs on and any application
>>> related settings are therefore lost?
>>
>> Yep.
>>
>>> if it does stay on the local machine,
>>> what if the next time a user comes into the cluster and they are
>>> directed to the other server, will not having this folder as roaming
>>> and excluded from the profile, cause user settings to not come
>>> over...
>>
>> A new one will be created.
>>>
>>> Just trying to understand what i;m getting myself in for here...
>>> before I go starting to make changes... I hope this makes sense...
>>>
>>> Lozza
 
Re: Local Settings Folder within Roaming Profiles

Hey Lanwench,

Thats excellent, thanks for the confirmation. I havent got an issue just
yet,am trying to do some foward planning, for this whole limiting size of
profiles issues that we are faced with. Thanks for being so thorough with
your answers. the very fact its volatile data and the important stuff is
directly under THE Application Data folder (which is redirected) explains it
to me... and the fact you have probably, as an MVP, seen many many more TS
applications than me and never had problem when this folder wasn't available
on another machine, gives me confidence, thats its unlikely i'll break
anything

So, thanks again...

"Lanwench [MVP - Exchange]" wrote:

> lozza <lozza@discussions.microsoft.com> wrote:
> > Lanwench,
> >
> > I like your thorough answering style, thanks man! :)
>
> No problem, lady. ;-)
>
> > So the final
> > question for me would be if this is local to every machine, as
> > implied by the name of the folder, then... what kind of real world
> > application stuff is stored here?
>
> Um - lots of stuff. Temp files, temp internet explorer files, Outlook cache
> files, etc.
>
> > any examples would be great. And
> > also would this cause problems for roaming users, i.e they set up a
> > kind of application environment on one server, and then when they log
> > onto other (via Load balanced approach) servers, these settings
> > stored in Local Settings will all be lost,
>
> Load balancing doesn't really enter into it, and I've never had a problem
> with anything important in that folder which wasn't available on another PC.
>
> > aren;t application
> > settings the important thing here when we talk about roaming
> > profiles?
>
> Yes - whether roaming, or TS, or local, Application Data is where the
> important stuff generally lives.
>
> > I guess i'm really confused as what this folder is actually
> > used for...
>
> Depends on the apps you run, but mostly it's volatile data and not very
> important. I can't find a page with a description of all the profile
> folders, sorry. I really wouldn't worry about this too much - unless you
> have problems, in which case you should post back in a new message with the
> specifics of them so we can try to help.
>
> >
> > Thanks much...
>
> Hope this helps. :)
>
>
> > Lozza
> >
> > "Lanwench [MVP - Exchange]" wrote:
> >
> >> lozza <lozza@discussions.microsoft.com> wrote:
> >>> Hey Guys,
> >>>
> >>> My dev setup: 2x TS Servers hooked into Session Directory. Load
> >>> Balancing achieved via DNS Round Robin.
> >>
> >>> Roaming User profiles being
> >>> used
> >>
> >> Do not use roaming profile paths for your TS users - you need to
> >> specify a different Terminal Services profile path. You can keep
> >> your folder redirection the same, but you have to use an entirely
> >> different folder tree for roaming profiles. E.g.,
> >>
> >> Regular roaming profiles: \\server\profiles%
> >> TS profiles: \\server\tsprofiles$
> >>
> >>> and pointed to NAS device. Profile is stored on
> >>> \\NAS\Profile\%UsernameOfEachUser%
> >>>
> >>> My Issue: I;ve been told to limit profiles to a max of 40MB.
> >>> Desktop/Start Menu/Application Data/My Documents all redirected to
> >>> their own folder on the NAS. i.e.
> >>> \\NAS\RedirectedMyDocuments\%username%,
> >>> \\NAS\RedirectedDesktop\%username%,
> >>> \\NAS\RedirectedStartMenu\%username%,
> >>> \\NAS\RedirectedApplicationData\%username%.... This I believe
> >>> prevents the size of these folder counting towards the profile size
> >>> as these folder are not redirected to the Roaming Profile Path...So,
> >>> First Question, Is my understanding correct here?
> >>
> >> Yes.
> >>
> >>
> >>>
> >>> So, one folder that is starting to take space is the Local Setting
> >>> Folder on each user user profile. My own profile (which is one of
> >>> the smaller ones) for example has:
> >>>
> >>> C:\Documents and Settings\lozza\Local Settings\Application
> >>> Data\Microsoft\Terminal Server Client\Cache there is a file called
> >>> bcache22.bmc and this itself is 22MB
> >>>
> >>> Not sure what this file is for or how it can be cleared down... any
> >>> ideas would be great? other users have varying sizes upto 100MB
> >>> under other folders located under Local Settings... Okay, so you
> >>> say, but this folder by default does not roam with the user
> >>
> >> Of course. It's "local settings."
> >>
> >>> or in turn other
> >>> folders can also be excluded from the roaming profile... that fine
> >>> with me, but also confusing:
> >>>
> >>> So, if this is the case... When a user logs off does this folder
> >>> (Local Settings) stay on the local machine?
> >>
> >> Yes.
> >>
> >>> (i.e. the directory
> >>> structure on the machine will still remain C:\Documents and
> >>> Settings\lozza\Local Settings\Application Data\...\...\...\). What
> >>> happens if cached copies of profiles are set to delete,
> >>
> >> Then the local settings folder data is gone.
> >>
> >>> is this
> >>> folder rebuild everytime the user logs on and any application
> >>> related settings are therefore lost?
> >>
> >> Yep.
> >>
> >>> if it does stay on the local machine,
> >>> what if the next time a user comes into the cluster and they are
> >>> directed to the other server, will not having this folder as roaming
> >>> and excluded from the profile, cause user settings to not come
> >>> over...
> >>
> >> A new one will be created.
> >>>
> >>> Just trying to understand what i;m getting myself in for here...
> >>> before I go starting to make changes... I hope this makes sense...
> >>>
> >>> Lozza
>
>
>
>
 
Re: Local Settings Folder within Roaming Profiles

lozza <lozza@discussions.microsoft.com> wrote:
> Hey Lanwench,
>
> Thats excellent, thanks for the confirmation. I havent got an issue
> just yet,am trying to do some foward planning, for this whole
> limiting size of profiles issues that we are faced with. Thanks for
> being so thorough with your answers. the very fact its volatile data
> and the important stuff is directly under THE Application Data folder
> (which is redirected) explains it to me... and the fact you have
> probably, as an MVP, seen many many more TS applications than me and
> never had problem when this folder wasn't available on another
> machine, gives me confidence, thats its unlikely i'll break anything
>
> So, thanks again...

No problem; hope it helps.
>
> "Lanwench [MVP - Exchange]" wrote:
>
>> lozza <lozza@discussions.microsoft.com> wrote:
>>> Lanwench,
>>>
>>> I like your thorough answering style, thanks man! :)
>>
>> No problem, lady. ;-)
>>
>>> So the final
>>> question for me would be if this is local to every machine, as
>>> implied by the name of the folder, then... what kind of real world
>>> application stuff is stored here?
>>
>> Um - lots of stuff. Temp files, temp internet explorer files,
>> Outlook cache files, etc.
>>
>>> any examples would be great. And
>>> also would this cause problems for roaming users, i.e they set up a
>>> kind of application environment on one server, and then when they
>>> log onto other (via Load balanced approach) servers, these settings
>>> stored in Local Settings will all be lost,
>>
>> Load balancing doesn't really enter into it, and I've never had a
>> problem with anything important in that folder which wasn't
>> available on another PC.
>>
>>> aren;t application
>>> settings the important thing here when we talk about roaming
>>> profiles?
>>
>> Yes - whether roaming, or TS, or local, Application Data is where the
>> important stuff generally lives.
>>
>>> I guess i'm really confused as what this folder is actually
>>> used for...
>>
>> Depends on the apps you run, but mostly it's volatile data and not
>> very important. I can't find a page with a description of all the
>> profile folders, sorry. I really wouldn't worry about this too much
>> - unless you have problems, in which case you should post back in a
>> new message with the specifics of them so we can try to help.
>>
>>>
>>> Thanks much...
>>
>> Hope this helps. :)
>>
>>
>>> Lozza
>>>
>>> "Lanwench [MVP - Exchange]" wrote:
>>>
>>>> lozza <lozza@discussions.microsoft.com> wrote:
>>>>> Hey Guys,
>>>>>
>>>>> My dev setup: 2x TS Servers hooked into Session Directory. Load
>>>>> Balancing achieved via DNS Round Robin.
>>>>
>>>>> Roaming User profiles being
>>>>> used
>>>>
>>>> Do not use roaming profile paths for your TS users - you need to
>>>> specify a different Terminal Services profile path. You can keep
>>>> your folder redirection the same, but you have to use an entirely
>>>> different folder tree for roaming profiles. E.g.,
>>>>
>>>> Regular roaming profiles: \\server\profiles%
>>>> TS profiles: \\server\tsprofiles$
>>>>
>>>>> and pointed to NAS device. Profile is stored on
>>>>> \\NAS\Profile\%UsernameOfEachUser%
>>>>>
>>>>> My Issue: I;ve been told to limit profiles to a max of 40MB.
>>>>> Desktop/Start Menu/Application Data/My Documents all redirected to
>>>>> their own folder on the NAS. i.e.
>>>>> \\NAS\RedirectedMyDocuments\%username%,
>>>>> \\NAS\RedirectedDesktop\%username%,
>>>>> \\NAS\RedirectedStartMenu\%username%,
>>>>> \\NAS\RedirectedApplicationData\%username%.... This I believe
>>>>> prevents the size of these folder counting towards the profile
>>>>> size as these folder are not redirected to the Roaming Profile
>>>>> Path...So, First Question, Is my understanding correct here?
>>>>
>>>> Yes.
>>>>
>>>>
>>>>>
>>>>> So, one folder that is starting to take space is the Local Setting
>>>>> Folder on each user user profile. My own profile (which is one of
>>>>> the smaller ones) for example has:
>>>>>
>>>>> C:\Documents and Settings\lozza\Local Settings\Application
>>>>> Data\Microsoft\Terminal Server Client\Cache there is a file called
>>>>> bcache22.bmc and this itself is 22MB
>>>>>
>>>>> Not sure what this file is for or how it can be cleared down...
>>>>> any ideas would be great? other users have varying sizes upto
>>>>> 100MB under other folders located under Local Settings... Okay,
>>>>> so you say, but this folder by default does not roam with the user
>>>>
>>>> Of course. It's "local settings."
>>>>
>>>>> or in turn other
>>>>> folders can also be excluded from the roaming profile... that fine
>>>>> with me, but also confusing:
>>>>>
>>>>> So, if this is the case... When a user logs off does this folder
>>>>> (Local Settings) stay on the local machine?
>>>>
>>>> Yes.
>>>>
>>>>> (i.e. the directory
>>>>> structure on the machine will still remain C:\Documents and
>>>>> Settings\lozza\Local Settings\Application Data\...\...\...\). What
>>>>> happens if cached copies of profiles are set to delete,
>>>>
>>>> Then the local settings folder data is gone.
>>>>
>>>>> is this
>>>>> folder rebuild everytime the user logs on and any application
>>>>> related settings are therefore lost?
>>>>
>>>> Yep.
>>>>
>>>>> if it does stay on the local machine,
>>>>> what if the next time a user comes into the cluster and they are
>>>>> directed to the other server, will not having this folder as
>>>>> roaming and excluded from the profile, cause user settings to not
>>>>> come over...
>>>>
>>>> A new one will be created.
>>>>>
>>>>> Just trying to understand what i;m getting myself in for here...
>>>>> before I go starting to make changes... I hope this makes sense...
>>>>>
>>>>> Lozza
 
Re: Local Settings Folder within Roaming Profiles

You might want to take a look at using Login Consultant's Flex Profile kit
which allows one to persist users settings from session to session while
using a local mandatory profile. THe also have a True Control Template for
GPO that allows redirection of more directories than what are addressable by
default in GPO.

If you need a supported commercial product to do this, our virtual access
suite does this.

--
Patrick C. Rouse
Microsoft MVP - Terminal Server
SE, West Coast USA & Canada
Quest Software, Provision Networks Division
Virtual Client Solutions
http://www.provisionnetworks.com


"lozza" wrote:

> Hey Lanwench,
>
> Thats excellent, thanks for the confirmation. I havent got an issue just
> yet,am trying to do some foward planning, for this whole limiting size of
> profiles issues that we are faced with. Thanks for being so thorough with
> your answers. the very fact its volatile data and the important stuff is
> directly under THE Application Data folder (which is redirected) explains it
> to me... and the fact you have probably, as an MVP, seen many many more TS
> applications than me and never had problem when this folder wasn't available
> on another machine, gives me confidence, thats its unlikely i'll break
> anything
>
> So, thanks again...
>
> "Lanwench [MVP - Exchange]" wrote:
>
> > lozza <lozza@discussions.microsoft.com> wrote:
> > > Lanwench,
> > >
> > > I like your thorough answering style, thanks man! :)
> >
> > No problem, lady. ;-)
> >
> > > So the final
> > > question for me would be if this is local to every machine, as
> > > implied by the name of the folder, then... what kind of real world
> > > application stuff is stored here?
> >
> > Um - lots of stuff. Temp files, temp internet explorer files, Outlook cache
> > files, etc.
> >
> > > any examples would be great. And
> > > also would this cause problems for roaming users, i.e they set up a
> > > kind of application environment on one server, and then when they log
> > > onto other (via Load balanced approach) servers, these settings
> > > stored in Local Settings will all be lost,
> >
> > Load balancing doesn't really enter into it, and I've never had a problem
> > with anything important in that folder which wasn't available on another PC.
> >
> > > aren;t application
> > > settings the important thing here when we talk about roaming
> > > profiles?
> >
> > Yes - whether roaming, or TS, or local, Application Data is where the
> > important stuff generally lives.
> >
> > > I guess i'm really confused as what this folder is actually
> > > used for...
> >
> > Depends on the apps you run, but mostly it's volatile data and not very
> > important. I can't find a page with a description of all the profile
> > folders, sorry. I really wouldn't worry about this too much - unless you
> > have problems, in which case you should post back in a new message with the
> > specifics of them so we can try to help.
> >
> > >
> > > Thanks much...
> >
> > Hope this helps. :)
> >
> >
> > > Lozza
> > >
> > > "Lanwench [MVP - Exchange]" wrote:
> > >
> > >> lozza <lozza@discussions.microsoft.com> wrote:
> > >>> Hey Guys,
> > >>>
> > >>> My dev setup: 2x TS Servers hooked into Session Directory. Load
> > >>> Balancing achieved via DNS Round Robin.
> > >>
> > >>> Roaming User profiles being
> > >>> used
> > >>
> > >> Do not use roaming profile paths for your TS users - you need to
> > >> specify a different Terminal Services profile path. You can keep
> > >> your folder redirection the same, but you have to use an entirely
> > >> different folder tree for roaming profiles. E.g.,
> > >>
> > >> Regular roaming profiles: \\server\profiles%
> > >> TS profiles: \\server\tsprofiles$
> > >>
> > >>> and pointed to NAS device. Profile is stored on
> > >>> \\NAS\Profile\%UsernameOfEachUser%
> > >>>
> > >>> My Issue: I;ve been told to limit profiles to a max of 40MB.
> > >>> Desktop/Start Menu/Application Data/My Documents all redirected to
> > >>> their own folder on the NAS. i.e.
> > >>> \\NAS\RedirectedMyDocuments\%username%,
> > >>> \\NAS\RedirectedDesktop\%username%,
> > >>> \\NAS\RedirectedStartMenu\%username%,
> > >>> \\NAS\RedirectedApplicationData\%username%.... This I believe
> > >>> prevents the size of these folder counting towards the profile size
> > >>> as these folder are not redirected to the Roaming Profile Path...So,
> > >>> First Question, Is my understanding correct here?
> > >>
> > >> Yes.
> > >>
> > >>
> > >>>
> > >>> So, one folder that is starting to take space is the Local Setting
> > >>> Folder on each user user profile. My own profile (which is one of
> > >>> the smaller ones) for example has:
> > >>>
> > >>> C:\Documents and Settings\lozza\Local Settings\Application
> > >>> Data\Microsoft\Terminal Server Client\Cache there is a file called
> > >>> bcache22.bmc and this itself is 22MB
> > >>>
> > >>> Not sure what this file is for or how it can be cleared down... any
> > >>> ideas would be great? other users have varying sizes upto 100MB
> > >>> under other folders located under Local Settings... Okay, so you
> > >>> say, but this folder by default does not roam with the user
> > >>
> > >> Of course. It's "local settings."
> > >>
> > >>> or in turn other
> > >>> folders can also be excluded from the roaming profile... that fine
> > >>> with me, but also confusing:
> > >>>
> > >>> So, if this is the case... When a user logs off does this folder
> > >>> (Local Settings) stay on the local machine?
> > >>
> > >> Yes.
> > >>
> > >>> (i.e. the directory
> > >>> structure on the machine will still remain C:\Documents and
> > >>> Settings\lozza\Local Settings\Application Data\...\...\...\). What
> > >>> happens if cached copies of profiles are set to delete,
> > >>
> > >> Then the local settings folder data is gone.
> > >>
> > >>> is this
> > >>> folder rebuild everytime the user logs on and any application
> > >>> related settings are therefore lost?
> > >>
> > >> Yep.
> > >>
> > >>> if it does stay on the local machine,
> > >>> what if the next time a user comes into the cluster and they are
> > >>> directed to the other server, will not having this folder as roaming
> > >>> and excluded from the profile, cause user settings to not come
> > >>> over...
> > >>
> > >> A new one will be created.
> > >>>
> > >>> Just trying to understand what i;m getting myself in for here...
> > >>> before I go starting to make changes... I hope this makes sense...
> > >>>
> > >>> Lozza
> >
> >
> >
> >
 
Back
Top