Folder redirection and Offline Files are designed to sync at user logon/logoff time, not necessarily at OS shutdown. The key difference is that a user sign-out (logoff) reliably triggers the user-profile and Offline Files logoff processing pipeline, while a direct shutdown can bypass or truncate that processing if services are forced to close.
Relevant behavior from the provided content:
- The "Network directories to sync at Logon/Logoff time only" Group Policy explicitly ties synchronization to logon/logoff events, not to system shutdown. When this policy is used, the specified network directories are made offline and are synced only at those user session transitions.
- Logoff processing is part of the user profile lifecycle. The system applies Folder Redirection and Offline Files logic when a user logs on and logs off. At shutdown, Windows has a fixed time (typically 30 seconds per service) to close services; if the system is busy, some operations may not complete before services are forcibly terminated.
- For services like DFSR and other background components, a forced or fast shutdown can be treated as a “dirty shutdown,” which can interrupt normal sync/cleanup behavior. The documentation notes that services have 30 seconds to shut down, and if they are forcibly closed, it can trigger dirty-shutdown recovery scenarios instead of a clean sync.
So:
- On log out/sign out, the user session ends cleanly, Folder Redirection and Offline Files run their configured logoff sync, and the server sees the updates.
- On shutdown, Windows may not run the same user logoff sync path in full, or it may terminate services before sync completes, especially with fast startup or if the system is under load.
To get consistent sync behavior, configure and rely on logon/logoff-based policies (such as Folder Redirection plus Offline Files and, if used, "Network directories to sync at Logon/Logoff time only"), and instruct users to sign out before shutting down if immediate sync is required.
References: