Windows XP Offline Files Synchronization

Offline Files in Windows XP Professional allowed users to access network share files even when disconnected from the corporate network, utilizing an underlying technology called Client-Side Caching (CSC). This article explains how Windows XP configured, cached, transitioned, and synchronized shared files between the local machine and network servers, as well as how the operating system handled file version conflicts.

The Client-Side Caching (CSC) Architecture

Windows XP implemented Offline Files through Client-Side Caching (CSC), managed by the csc.sys kernel-mode driver. When a user flagged a network file or folder for offline use, Windows downloaded a replica to a hidden, protected local directory located at %SystemRoot%\CSC. The operating system transparently redirected file input/output requests to this local cache whenever the network resource was inaccessible.

Server and Client Configuration

For synchronization to occur, both the host server and the Windows XP client had to support and enable caching:

  • Server-Side Settings: Administrators configured caching permissions directly on the Server Message Block (SMB) share. Options included:
    • Manual Caching: Users manually selected specific files and folders to make available offline.
    • Automatic Caching of Documents: Every file opened from the share by a client was automatically downloaded to the local CSC cache.
    • Automatic Caching of Programs and Documents: Designed for executable files and read-only data, preventing local writes from propagating back.
  • Client-Side Settings: In Windows XP Professional, users enabled the feature via Windows Explorer under Tools > Folder Options > Offline Files. From this interface, users allocated disk space limits for the cache and set synchronization triggers.

Online to Offline Transition

Windows XP monitored network connectivity using the Media Sense feature and SMB heartbeat requests. When a network connection dropped, failed, or the user unplugged an Ethernet cable:

  1. The system detected the absence of the network path.
  2. An Offline Files icon appeared in the system notification area (system tray).
  3. File requests to UNC paths (e.g., \\Server\Share\Folder) were dynamically redirected to the local %SystemRoot%\CSC database.
  4. Users continued reading and modifying documents as if they were still connected to the server.

The Synchronization Process

When network connectivity was restored, Windows XP synchronized data between the local CSC cache and the server share using the Synchronization Manager (mobsync.exe). Synchronization occurred through several mechanisms:

  • Logon and Logoff Sync: By default, Windows XP initiated a sync when the user logged on or logged off, ensuring changes made during disconnected sessions uploaded to the network.
  • Background and Idle Sync: Users could configure the system to synchronize during system idle periods or at specific scheduled intervals.
  • Manual Sync: Users could right-click any mapped drive, network share, or folder and select Synchronize to immediately compare versions.

Synchronization Manager compared the file time stamps and directory entries between the local cache and the server. New files created locally were uploaded, deleted files were removed from the server (if permitted), and updated network files replaced outdated cached copies.

Conflict Resolution

If a file was modified locally while disconnected and simultaneously modified by another user on the network share, Windows XP identified a conflict during synchronization.

Instead of automatically overwriting either version, the Synchronization Manager halted and displayed a Conflict Resolution dialog box. The user was presented with three options:

  1. Keep the local version: Overwrite the version on the network share with the offline edits.
  2. Keep the network version: Discard local changes and update the cache with the server’s file.
  3. Keep both versions: Retain the server copy and save the local offline copy under a modified filename that included the user's name and computer name.