Welcome to Microsoft Q&A Forum!
Thank you for providing the details information about the environment.
Based on your description, the safest approach is to migrate the redirected data to the new file server first and then update the existing Folder Redirection GPO to point to the new UNC path. I would not recommend removing Folder Redirection or redirecting folders back to local profiles during the migration, as this can result in large data transfers, extended logon times, and potential synchronization issues.
If Offline Files is enabled, it is a recommend enabling the "Enable optimized move of contents in Offline Files cache on Folder Redirection server path change" policy before updating the redirection path. This allows clients to handle the server-path change more efficiently, helping to minimize logon delays, synchronization conflicts, and the risk of data loss.
I would like to share with you the following migration process:
1. Pre-stage the data on the new server
- Copy the redirected folders to the new file server using a method that preserves NTFS permissions, ownership, timestamps, and ACLs (for example, Robocopy with the appropriate switches).
- Verify that the share permissions and NTFS permissions on the new server match the existing configuration before proceeding with the cutover.
2. Enable the optimized move policy (recommended)
In Group Policy, navigate to:
User Configuration -> Policies -> Administrative Templates -> System -> Folder Redirection
Enable the following setting:
Enable optimized move of contents in Offline Files cache on Folder Redirection server path change
This setting helps prevent unnecessary copying of cached redirected data and reduces the likelihood of long logon times or data loss when the Folder Redirection target path changes.
3. Update the Folder Redirection target path
Modify the existing Folder Redirection GPO and change the target path from:
\OldServer\RedirectedFolders
to:
\NewServer\RedirectedFolders
In most cases, updating the existing GPO is cleaner and less disruptive than removing and recreating the Folder Redirection configuration.
4. Allow clients to receive the updated policy
Allow Group Policy to refresh normally, or manually force a refresh:
gpupdate /target:user /force
After the updated policy is applied, users should sign out and sign back in to ensure the new settings take effect.
5. Validate synchronization and access
- Confirm that redirected folders are resolving to the new UNC path.
- Verify the Offline Files synchronization status and resolve any outstanding sync conflicts before decommissioning the old file server. Microsoft specifically recommends ensuring Offline Files is synchronized prior to the move.
6. Keep the old server available during the transition period
Consider keeping the original share available, preferably in a read-only state, until you have confirmed that all clients have successfully redirected to the new location and completed synchronization. This provides a rollback option if any unexpected issues occur.
For future migrations, consider using a DFS Namespace path for Folder Redirection instead of a server-specific UNC path. This can simplify future file server migrations because the backend server can be changed without requiring another Folder Redirection policy update.
Reference: Disable Offline Files on individual redirected folders | Microsoft Learn
Configure Folder Redirection with Group Policy on Windows Server | Microsoft Learn
Deploy Folder Redirection with Offline Files | Microsoft Learn
Enable optimized moves of redirected folders | Microsoft Learn
If this answer was helpful, please Accept the Answer. Thank you for choosing Microsoft Q&A to raise your concern