You can use the Group Policy Management Console (GPMC) to locate Group Policy settings.
You disable the following Do not automatically make redirected folders available offline Group Policy setting to make the redirected folder available offline:
You configure the following Configure slow-link mode Group Policy setting to use the slow-link mode for the redirected folders when the network latency is greater than a specified value:
Note By default, all redirected folders are set to offline mode if the network latency is longer than 80 milliseconds (ms).
A user logs on to a client computer that is running Windows 7 or Windows Server 2008 R2.
The user uses a redirected folder to transfers files.
The network latency is greater than the specified value.
The redirected folder is transitioned to offline mode that is also known as the slow-connection mode, and the redirected folder is available offline.
The user maps a local drive on the client computer to a network share.
The user makes the network share available offline and uses Windows Explorer to set the network share to offline mode.
The user logs off from the client computer.
Another user logs on to the client computer. This user has not previously logged on to this client computer.
In this scenario, the Folder Redirection Group Policy setting does not work for this user. Additionally, an event that resembles the following is logged in the Application log:
Log Name: Application Source: Microsoft-Windows-Folder Redirection Date: datetime Event ID: 502 Task Category: None Level: Error Keywords: User: domain name\user name Computer: computer name Description: Failed to apply policy and redirect folder "folder name" to "\\DFS root\user name\folder name". Redirection options=0x1000. The following error occurred: "Can not create folder "\\DFS root\user name\folder name"". Error details: Access is denied.
If the user tries to access the redirected path manually, the user receives an error message that resembles the following:
You do not have permissions to access \\DFS root\.
Additionally, the user does not have access to the mapped drive.
Note When this issue occurs, only users who make the network path available offline can revert the redirected folder or the mapped drive back to the online state.
This issue occurs because the user cannot change the status of the redirected folders in the Client Side Caching (CSC) tool.
When the user tries to access the redirected home folder, the redirected folder is not online. However, the user does not have permission to bring the folder online. Therefore, the issue that is mentioned in the "Symptoms" section occurs.
After you apply the following hotfix, the folder redirection process sets the redirected folders back to the online state when a user logs on to a client computer. Specifically, this behavior occurs if the following conditions are true:
The user has not previously logged on to the computer.
The redirected folders are in offline mode that is also known as the slow-connection mode.
However, the folder redirection process does not set the folders that the first user manually made available offline to the online state. Additionally, the folder redirection process does not set any folders that are not redirected folders to the online state.
Hotfix information
A 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 Web site:
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 be running one of the following operating systems:
Windows 7
Windows 7 Service Pack 1 (SP1)
Windows Server 2008 R2
Windows Server 2008 R2 Service Pack 1 (SP1)
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:
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 must 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
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:
Collapse this tableExpand this table
Version
Product
Milestone
Service branch
6.1.760 0.21xxx
Windows 7 and Windows Server 2008 R2
RTM
LDR
6.1.760 1.21xxx
Windows 7 and Windows Server 2008 R2
SP1
LDR
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 Server 2008 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely 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
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Cscapi.dll
6.1.7600.21095
34,816
22-Nov-2011
05:36
x86
Cscdll.dll
6.1.7600.21095
23,040
22-Nov-2011
05:36
x86
Cscapi.dll
6.1.7601.21864
34,816
22-Nov-2011
05:24
x86
Cscdll.dll
6.1.7601.21864
23,040
22-Nov-2011
05:24
x86
Cscobj.dll
6.1.7600.21095
139,264
22-Nov-2011
05:36
x86
Offlinefileswmiprovider.mof
Not Applicable
14,568
22-Nov-2011
00:08
Not Applicable
Offlinefileswmiprovider_uninstall.mof
Not Applicable
14,568
22-Nov-2011
00:08
Not Applicable
Cscobj.dll
6.1.7601.21864
139,264
22-Nov-2011
05:24
x86
Offlinefileswmiprovider.mof
Not Applicable
14,568
22-Nov-2011
00:03
Not Applicable
Offlinefileswmiprovider_uninstall.mof
Not Applicable
14,568
22-Nov-2011
00:03
Not Applicable
Cscsvc.dll
6.1.7600.21095
546,816
22-Nov-2011
05:36
x86
Microsoft-windows-offlinefiles.mof
Not Applicable
1,776
13-Jul-2009
20:25
Not Applicable
Cscsvc.dll
6.1.7601.21864
547,328
22-Nov-2011
05:24
x86
Microsoft-windows-offlinefiles.mof
Not Applicable
1,776
13-Jul-2009
20:25
Not Applicable
Shell32.dll
6.1.7600.21095
12,871,168
22-Nov-2011
05:38
x86
Shell32.dll
6.1.7601.21864
12,873,728
22-Nov-2011
05:26
x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
To work around this issue, use one of the following methods:
Use the user account of the first user to revert the redirected folder or the mapped drive back to the online state.
Use the administrator account to clear the Offline Files database. When a user logs on the computer, the redirected folders are set to the online state.
For more information about how to clear the Offline Files database, click the following article number to view the article in the Microsoft Knowledge Base:
How to re-initialize the offline files cache and database
Note The administrator can use a logoff script that always sets the redirected folders back to the online state if the following conditions are true:
Multiple users usually log on to each client computer.
The users manually set network locations to the offline state.
This logoff script resembles the following:
'
' THIS CODE AND INFORMATION IS PROVIDED "AS IS" WITHOUT WARRANTY OF
' ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO
' THE IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A
' PARTICULAR PURPOSE.
'
' Copyright (c) Microsoft Corporation. All rights reserved.
'
'
' Usage: CscTransition.vbs /ItemPath:<path> /Online|Offline [/Force] [/Machine:value] [/User:value] [/Password:value]
'
'
' Set an item to an online or offline state.
'
' /Online - Transition online
' /Offline - Transition offline
' /Force - For offline transition, force any open handles closed. Default is no-force.
'
'
const cComputerName = "LocalHost"
const cWMINamespace = "root\cimv2"
const cWMIClass = "Win32_OfflineFilesCache"
set objWMILocator = WScript.CreateObject("WbemScripting.SWbemLocator")
'
' Process commandline arguments
'
strItemPath = WScript.Arguments.Named("ItemPath")'
if Len(strItemPath) = 0 Then
Wscript.Echo "ItemPath parameter required"
Err.Raise 449 ' "argument not optional" error
End if
bOnline = False
bOffline = False
bForce = False
If WScript.Arguments.Named.Exists("Online") Then
bOnline = True
End If
If WScript.Arguments.Named.Exists("Offline") Then
bOffline = True
End If
If WScript.Arguments.Named.Exists("Force") Then
bForce = True
End if
If NOT bOnline AND NOT bOffline Then
WScript.Echo "Must specify either Online or Offline parameter."
Err.Raise 449 ' "argument not optional" error
End if
If bOnline AND bOffline Then
WScript.Echo "Only one of Online and Offline parameters may be specified."
Err.Raise 450 ' "Wrong number of arguments" error
End if
strComputerName = WScript.Arguments.Named("Machine")
If Len(strComputerName) = 0 Then strComputerName = cComputerName
strUserID = WScript.Arguments.Named("User")
If Len(strUserID) = 0 Then strUserID = ""
strPassword = WScript.Arguments.Named("Password")
If Len(strPassword) = 0 Then strPassword = ""
Set objWMIServices = objWMILocator.ConnectServer(strComputerName, _
cWMINameSpace, _
strUserID, _
strPassword)
'
' Transition control flags from Win32_OfflineFilesCache.TransitionOnline and TransitionOffline
'
const fInteractive = &H00000001
const fConsole = &H00000002
TransitionFlags = fConsole + _
fInteractive
'
' Note that Win32_OfflineFilesCache is a singleton.
'
Set objCache = objWMIServices.Get("Win32_OfflineFilesCache=@")
WScript.Echo "Path = " & strItemPath & " bOnline = " & bOnline
If bOnline Then
objCache.TransitionOnline strItemPath, TransitionFlags
WScript.Echo strItemPath & " is online."
Else
bOpenFiles = False
objCache.TransitionOffline strItemPath, bForce, TransitionFlags, bOpenFiles
If bOpenFiles Then
WScript.Echo strItemPath & " is not offline. Open Files prevent offline transition."
Else
WScript.Echo strItemPath & " is offline."
End If
End If