Article ID: 811660 - View products that this article applies to.
If you add files to the Offline Files folder on a Microsoft Windows XP-based computer that is shared by more than one user, offline synchronization of those files will occur when another user logs on to that computer. Network shares and Web sites that require your security credentials cannot synchronize and will prompt other users to submit the correct credentials.
When you add files to the Offline Files folder, these files are synchronized whenever the computer connects to the network. Synchronization occurs when the computer connects to the network, not when a user logs on to the computer.
The Offline File folder cache is a mirror of the network file system. File access is based upon the same administrative credentials. Files on the network file system that grant access to everyone and that have been added by a user to the Offline File folder will be synchronized, regardless of who logs on to the computer. Therefore, when a user connects to the network on a shared computer, that user must wait until all files in the Offline Files folder are synchronized, whether the user wants to synchronize those files or not.
Service pack informationTo resolve this problem, obtain the latest service pack for Windows XP. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/322389/ )How to obtain the latest Windows XP service pack
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 this specific problem. 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:
http://support.microsoft.com/contactus/?ws=supportNote 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.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Date Time Version Size File name ---------------------------------------------------- 30-Dec-2002 08:20 5.1.2600.108 313,856 Cscui.dll
Windows XP Service Pack 1
Date Time Version Size File name ----------------------------------------------------- 31-Dec-2002 07:23 5.1.2600.1152 312,832 Cscui.dll
This hotfix includes four primary additions to Offline Files. To apply the additions that you want to use, you must edit the registry as directed in the section of this article that describes the specific addition. The four primary additions are:
Exclusion error suppressionThe Offline Files feature does not permit you to cache certain file types. This restriction prevents corruption of file sets and avoids conflicts with competing synchronization technologies. When you try to cache one of these file types, you may receive the following error message for each file:
Files of this type cannot be made available offline
This message is useful to users who are unfamiliar with the synchronization process. However, when users understand that certain file types cannot be cached, the message becomes an annoyance, because the message prevents the synchronization progress dialog box from closing automatically at the end of synchronization. This hotfix introduces a new registry key that prevents subsets of these files from generating this specific synchronization error. After you apply this hotfix, you must edit the registry and enter the appropriate file specification for the following registry subkeys:
At runtime, the lists under these two registry subkeys are merged into a single list. One list does not take precedence over the other. An empty key and a missing key are treated in the same way. An empty key and a missing key each produce a list of zero items.
File specificationsThe file specifications that you add to the new
ExclusionErrorSuppressionListkeys are Universal Naming Convention (UNC) path strings. These path strings may incorporate a wildcard character (asterisk) to indicate “match any” at that particular position in the specification.
Each file specification uses the following format:
\\Server\Share\Folder\Filename.extensionYou can include environment variables, such as the variable %username%, in a specification. A variable is expanded at runtime to the equivalent text value.
You can substitute the wildcard character for any part of the file specification and for the folder designation. For example,
\\corpsvr\staff\%username%\documents\*\*.docHowever, you cannot substitute the wildcard character for a folder that is followed by another folder name. For example, the following specification is not valid:
\\corpsvr\staff\%username%\documents\*\personal\*.docThis specification is rejected because the specification embeds a wildcard character between the folder names %username% and personal.
Note Windows XP does not recognize invalid specifications and does not log invalid specifications anywhere in the system. Window XP ignores invalid specifications at runtime.
Examples of the file specifications are:
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
System behaviorWhen the synchronization process encounters a file that is on the exclusion list, the file’s complete path is tested against the list of file specifications that are read from the registry. If the file's path matches any one of the specifications, the "files of this type cannot be made available offline" error message does not appear in the synchronization progress dialog. Windows XP does not record the suppression of this error message.
Purge files for non-primary users at logoffWhen a user briefly logs onto a computer that is not the user's regular workplace computer, and the user caches files from the network, either by autocaching or by pinning, those files remain in the cache on that computer until the files are removed.
The feature changes that are included in this hotfix introduce a new registry key that designates users of a computer as either primary or non-primary. With this designation, files that are cached for a non-primary user can be removed from the cache when the user logs off. This registry key contains zero or more values, and each value name designates a user account that will be considered primary by the Offline Files feature. Each value name may take one of the following forms:
Windows XP uses the following process to determine if a computer user is a primary or a non-primary user:
To apply this feature change, follow these steps:
Computer Configuration\Administrative Templates\Network\Offline Files\At logoff, delete local copy of user’s offline files
If you enable this policy, the PurgeNonPrimaryUserFilesAtLogoff registry value is ignored, and files for non-primary users will not be removed.
Prevent admin pinning of files for non-primary usersA user who has been assigned offline files for administrative purposes caches content on every computer the user logs on to. This scenario may cause unwanted content to be cached on some computers. To prevent this scenario, this hotfix introduces a modification to the processing of admin pinning. With this hotfix, admin pinning does not override the primary user list that is described in the "Purge files for non-primary users at logoff" section. If the current user is not in the primary users list, per-user admin pinning will not occur for that user on the current computer. To prevent per-user admin pinning for non-primary users, follow these steps:
Forced silent auto reconnectionWhen a server has been unavailable (offline mode) and then becomes available again for connection, Offline Files Client Side Caching tries to transition that server to online mode if all the following conditions are true:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft Windows XP Service Pack 2.
Article ID: 811660 - Last Review: August 29, 2007 - Revision: 4.2