Select the product you need help with
Improved interoperability between the BranchCache feature and the Offline Files feature in Windows 7 or in Windows Server 2008 R2Article ID: 2675611 - View products that this article applies to. On This PageSUMMARYThis article introduces a hotfix that improves the interoperability between the BranchCache feature and the Offline Files feature in Windows 7 and in Windows Server 2008 R2. Currently, the BranchCache feature uses the WTSQueryUserToken function to maintain the token cache for users who log on in a local branch office environment. To make sure that the Offline Files feature can impersonate the appropriate skin, the client-side caching driver (Csc.sys) sends an upcall to the Offline Files feature (Cscservice.exe). Then, the upcall triggers a prefetch request that incorporates the logon ID of the VNetRoot pointer. This behavior enables the Offline Files feature to open a handle on behalf of the original user. However, the WTSQueryUserToken function cannot retrieve tokens that are not associated with Remote Desktop logon sessions (such as tokens that are created by using the runas.exe /netonly command or by using direct LogonUser() API calls). Therefore, when the BranchCache feature uses the WTSQueryUserToken function to retrieve tokens that are not associated with Romote Desktop logon sessions, the prefetch request fails. This behavior causes WAN connections to perform file IO operations. For example, consider the following scenario:
RESOLUTIONIf the BranchCache feature is deployed in distributed cache mode, install this hotfix only on the client computers that have the BranchCache feature enabled in the local branch environment. If the BranchCache feature is deployed in hosted cache mode, this hotfix is not required. Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: http://support.microsoft.com/contactus/?ws=support Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
(http://support.microsoft.com/contactus/?ws=support)
PrerequisitesTo apply this hotfix, you must be running one of the following operating systems:
976932
(http://support.microsoft.com/kb/976932/
)
Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
Registry informationTo apply the hotfix in this package, you do not have to make any changes to the registry.Restart requirementYou must restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace a previously released hotfix.File informationThe global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.Windows 7 and Windows Server 2008 R2 file information notes
For all supported x86-based versions of Windows 7Collapse this table
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2Collapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONFor more information about the BranchCache feature, visit the following Microsoft website: General information about the BranchCache feature For more information about how the BranchCache feature works, visit the following Microsoft website:
(http://technet.microsoft.com/en-us/network/dd425028)
How the BranchCache feature works in Windows 7 and in Windows Server 2008 R2 For more information about the WTSQueryUserToken function, visit the following Microsoft website:
(http://technet.microsoft.com/library/dd755969(v=WS.10).aspx)
General information about the WTSQueryUserToken function
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://msdn.microsoft.com/library/windows/desktop/aa383840(v=vs.85).aspx)
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
Additional file informationAdditional file information for Windows 7 and for Windows Server 2008 R2Additional files for all supported x86-based versions of Windows 7Collapse this table
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2Collapse this table
PropertiesArticle ID: 2675611 - Last Review: March 14, 2012 - Revision: 1.0 APPLIES TO
| Article Translations
|



Back to the top








