- You configure the following Folder Redirection Group Policy setting to use a Distributed File System (DFS) path as the redirect location or folders: Group Policy Object (GPO) name\User Configuration\Policies\Windows Settings\Folder Redirection
- You disable the following Do not automatically make redirected folders available offline Group Policy setting to make sure that the redirected folders can be accessed when they are offline:GPO name\User Configuration\Administrative Templates\System\Folder Redirection
- You configure the following Configure slow-linkmode Group Policy setting to use slow-link mode for the redirected folders when network latency is greater than a specified value:Computer Configuration\Policies\Administrative Templates\Network\Offline Files
- A domain user logs on to a client computer that is running Windows 8.1, Windows Server 2012 R2, Windows 7 Service Pack 1 (SP1), or Windows Server 2008 R2 SP1.
- The user uses a redirected folder to transfer files.
- Network latency is greater than the specified value. Therefore, the redirected folder is transitioned offline, and DFS path is transitioned offline.
- Another user who did not previously log on to the client computer logs on to this computer.
Note This issue also occurs when the whole DFS path is manually set to point to an offline location. If there is a drive that is mapped to the DFS path, the user also cannot access the drive.
To resolve this issue in Windows 7 and Windows Server 2008 R2, install the hotfix that is described in the "Hotfix information" section.
Update informationFor more information about how to obtain update rollup 2967917, click the following article number to view the article in the Microsoft Knowledge Base:
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that 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, go to the following Microsoft website: 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.
PrerequisitesTo apply this hotfix, you must first install SP1 on Windows 7 or Windows 2008 R2. For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
Registry informationTo use the hotfix in this package, you do not have to make any changes to the registry.
Restart requirementYou may have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace a previously released hotfix.
Article ID: 2967567 - Last Review: 29 Aug 2014 - Revision: 1