Local Settings folder being included to Roaming Profile

  • Thread starter Thread starter Neil
  • Start date Start date
N

Neil

Hello,

Our IT shop had encountered an issue on some of our users getting errors
that their profile storage space is going over the limit. I later found out
that it's due to the Local Settings folder being included on the roaming
profile, instead of being excluded. (We have a 50 MB limit on our profiles)
I also noticed that the Local Settings folder had been copied over to the
network location of the profiles (obviously).

By default, Microsoft has excluded the Local Settings folder from the
roaming profile so it should not even be counted. There's nothing to
configure to the Group Policy since this settings has been already hardcoded
by Microsoft to exclude the Local Settings folder.

This issue has just occured to 4 users yesterday and I'm hoping it wouldn't
spread to every users in our network. As a workaround, we had to rebuild
their profiles which is really a pain.

But I would like to know what would have caused this. Could it be a new
Windows update that have been deployed few weeks back?



Thanks,
 
Neil said:
Hello,

Our IT shop had encountered an issue on some of our users getting
errors that their profile storage space is going over the limit. I
later found out that it's due to the Local Settings folder being
included on the roaming profile, instead of being excluded. (We have
a 50 MB limit on our profiles) I also noticed that the Local Settings
folder had been copied over to the network location of the profiles
(obviously).

By default, Microsoft has excluded the Local Settings folder from the
roaming profile so it should not even be counted. There's nothing to
configure to the Group Policy since this settings has been already
hardcoded by Microsoft to exclude the Local Settings folder.

This issue has just occured to 4 users yesterday and I'm hoping it
wouldn't spread to every users in our network. As a workaround, we
had to rebuild their profiles which is really a pain.

But I would like to know what would have caused this. Could it be a
new Windows update that have been deployed few weeks back?



Thanks,
Click to expand...

I use roaming profiles & haven't seen this. Are you sure somebody hasn't
been manually copying folders over? If you delete the local settings folder
in a user's profile on the server, then login as that user to a workstation
that has no cached domain profile for that user, and log out, what happens?
 
The file that determines this is ntuser.ini, in the profile root.

Not that being a unicode file it is not compatible with all texteditors.
Ensure that the editor you use is capable of saving unicode correctly.
 
Back
Top