Administratively Assigned Offline File Requires Repeated Synchronization After Conflict (253618)
The information in this article applies to:
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Professional
This article was previously published under Q253618 SYMPTOMS
An administrator can use the Group Policy Editor snap-in to make folder contents available offline by assigning folders to users or computers.
When a user modifies an administratively assigned file while offline, the user is prompted to synchronize files when the computer recognizes that the server is available. However, a conflict occurs if the server copy of that file is modified as well, and the following message is displayed in the Resolve File Conflicts dialog box:
While your computer was disconnected from the network, the following file was changed, both on your computer and on the network...
If the user accepts the default reconciliation option and saves both copies of the file, Synchronization Manager continuously indicates that the file needs to be synchronized.
CAUSE
This problem can occur if the file is cached from an administratively assigned folder specified as the root of a share point. For example, if you administratively assign a folder called \\Server\Share and the file is located in the Share folder, synchronization is completed successfully, but Synchronization Manager continues to indicate that synchronization is required for that server.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
WORKAROUND
To work around this problem, create a folder in the share root folder, and then configure this folder to be available offline by using the Group Policy Editor snap-in. For example, create a folder named \\Server\Share\Folder.
STATUSMicrosoft has confirmed that this is a problem in Microsoft Windows 2000. This problem was first corrected in Windows 2000 Service Pack 1.
Modification Type: | Minor | Last Reviewed: | 9/26/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbbug kberrmsg kbfix kbGPO kbnetwork kbQFE kbWin2000SP1Fix KB253618 |
---|
|