Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Cannot access DFS root when the DFS path is offline and you log on to a Windows-based computer for the first time

Cannot access DFS root when the DFS path is offline and you log on to a Windows-based computer for the first time

View products that this article applies to.

Symptoms

Consider the following scenario:
  • 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.
In this scenario, the Folder Redirection Group Policy setting works correctly. However, the user cannot access the DFS root and cannot see the sync information about the redirected folders in Sync Center.

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.

↑ Back to the top

Resolution

To resolve this issue in Windows 8.1 and Windows Server 2012 R2, install update rollup 2967917.

To resolve this issue in Windows 7 and Windows Server 2008 R2, install the hotfix that is described in the "Hotfix information" section.

Update information

For more information about how to obtain update rollup 2967917, click the following article number to view the article in the Microsoft Knowledge Base:
2967917 July 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2

Hotfix information

A 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:
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.

Prerequisites

To 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:
976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.
File information
The 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
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    VersionProductMilestoneService branch
    6.1.760 1.22 xxxWindows 7 and Windows Server 2008 R2SP1LDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows 7 and Windows Server 2008 R2" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
File nameFile versionFile sizeDateTimePlatform
Cscui.dll6.1.7601.22699419,32823-May-201409:14x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Cscui.dll6.1.7601.22699499,20023-May-201410:05x64

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More Information

For more information about DFS, go to the following Microsoft website:
General information about DFS
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional file information

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
File propertyValue
File nameX86_e3a8fe2fac83997b1a41e1968862682a_31bf3856ad364e35_6.1.7601.22699_none_f3d4f61aeab9ae09.manifest
File versionNot applicable
File size708
Date (UTC)23-May-2014
Time (UTC)15:05
File nameX86_microsoft-windows-offlinefiles-shellui_31bf3856ad364e35_6.1.7601.22699_none_aec6fa1026897992.manifest
File versionNot applicable
File size22,749
Date (UTC)23-May-2014
Time (UTC)09:59
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File propertyValue
File nameAmd64_7f5fa0245ba209df01075943efb1cbf9_31bf3856ad364e35_6.1.7601.22699_none_f49b80a2430e668d.manifest
File versionNot applicable
File size712
Date (UTC)23-May-2014
Time (UTC)15:05
File nameAmd64_microsoft-windows-offlinefiles-shellui_31bf3856ad364e35_6.1.7601.22699_none_0ae59593dee6eac8.manifest
File versionNot applicable
File size22,753
Date (UTC)23-May-2014
Time (UTC)10:35

↑ Back to the top

Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 2967567
Revision : 1
Created on : 1/7/2017
Published on : 8/29/2014
Exists online : False
Views : 353