Symptoms: Some Offline Files are inaccessible from the DFS namespace. Users may get the following errors when working on the files server from branch offices:
EVENT ID: 1004
Path \\file path transitioned to slow link with latency = 74 and bandwidth = 10580536
Windows Offline files measures for latency and sets the default threshold at 80ms for Windows 7. When the latency from the branch office passed the Offline threshold the DFS namespace directory automatically transitions to offline mode.
Even worse, if a client attempts to access the target Offline, and the target is unavailable, the Windows client interprets the entire namespace as unavailable; and will attempt to open a user’s locally cached files (if they exist). If they don't exist the user will get network unavailable or permission errors.
Here is a good explanation: http://blogs.technet.com/b/askds/archive/2011/12/14/slow-link-with-windows-7-and-dfs-namespaces.aspx
To resolve the cached DFS namespace must be manually deleted from the cache directory before the DFS root and the Offlies Files can run simultaneously. There may be an easier way but these are the steps I took:
2. Installed the Windows Resource Tool, SubinACL, to allow me to take ownership of the Offline cache directories.
SubinACL is located athttp://www.microsoft.com/download/en/details.aspx?id=23510
SubinACL doesn't have to be used but all files are owned by the System; manually changing ownership and permissions would take forever.
3. From the command line:
C:\Program Files (x86)\Windows Resource Kits\tools>subinacl.exe /subdirectories c:\windows\CSC\*.* /setowner=domain.com\username
4. Manually Deleted the domainname.com namespace directory from: C:\Windows\CSC\v2.0.6\
There may also be a directory for the local namespace file server that should be deleted as well.
Local Computer Policy > Administrative Templates > Network > Offline Files > Configure slow-link mode
Last updated July 16th, 2013 by Steven Jordan