Environment:
Windows Server 2003 R2 SP2 domain
Windows 7 Enterprise client
Roaming profile configured for the account in question
For some reason, when the Win 7 client logs off the user's AppData\Local folder is ALSO copied to the server. This folder alone is close to 100 MB in size and this is causing storage\network bandwidth issues.
I've spent all day searching the Internet for similar cases but cannot seem to find any. Everything I have found says that only the AppData\Roaming folder is copied to the server as part of the roaming profile configuration.
For what it is worth, the AppData\LocalLow folder also gets copied to the server, but this doesn't cause an issue as the size is tiny if not zero.
Can anyone shed any light on this, or explain how to prevent the AppData\Local folder from being copied to the server as part of the roaming profile configuration?
Windows Server 2003 R2 SP2 domain
Windows 7 Enterprise client
Roaming profile configured for the account in question
For some reason, when the Win 7 client logs off the user's AppData\Local folder is ALSO copied to the server. This folder alone is close to 100 MB in size and this is causing storage\network bandwidth issues.
I've spent all day searching the Internet for similar cases but cannot seem to find any. Everything I have found says that only the AppData\Roaming folder is copied to the server as part of the roaming profile configuration.
For what it is worth, the AppData\LocalLow folder also gets copied to the server, but this doesn't cause an issue as the size is tiny if not zero.
Can anyone shed any light on this, or explain how to prevent the AppData\Local folder from being copied to the server as part of the roaming profile configuration?