Folder Redirection

From PiRho Knowledgebase
Jump to navigationJump to search

Summary:

Folder Redirection is a Windows feature that allows user data folders such as Documents, Desktop, Pictures and Downloads to be stored in a location other than the local computer. It is commonly used in Active Directory environments to centralise user data, simplify backup strategies, reduce workstation storage requirements and improve the user experience when moving between devices.

Context

Historically, user data was stored within the user's profile on the local computer. This created several challenges:

  • User files were difficult to back up.
  • Computer failures often resulted in data loss.
  • Users moving between computers could not easily access their files.
  • Profile sizes became large and slow to manage.

Folder Redirection addresses these issues by separating user data from the computer itself.

In most enterprise environments, redirected folders are stored on a file server rather than on the local disk.

Common Misconceptions

  • Folder Redirection is not the same as Roaming Profiles.
  • Folder Redirection does not move the entire user profile.
  • Folder Redirection is not a backup solution by itself.
  • Folder Redirection can be used independently of OneDrive or other cloud storage solutions.

Core Concepts

User Profile Structure

A Windows user profile typically contains:

  • Desktop
  • Documents
  • Pictures
  • Videos
  • Music
  • Downloads
  • AppData

Only selected folders are normally redirected.

AppData is generally left within the local profile unless there is a specific requirement to roam application settings.

Redirection Target

A target location may be:

  • Another volume on the same computer
  • A network file share
  • A DFS Namespace
  • Cloud-synchronised storage

In domain environments, a network file share is the most common approach.

Policy-Based Management

Folder Redirection is typically controlled through Group Policy.

This allows administrators to:

  • Apply consistent settings to many users.
  • Change storage locations centrally.
  • Control permissions automatically.
  • Migrate users without manual intervention.

Practical Application

Redirecting a Single Folder

A user can manually relocate supported folders:

  1. Right-click the folder.
  2. Select Properties.
  3. Open the Location tab.
  4. Choose Move.
  5. Select a new location.

Windows updates the required registry settings and moves the existing content.

Redirecting Through Group Policy

Group Policy provides the preferred enterprise approach.

Example folders commonly redirected:

  • Documents
  • Desktop
  • Pictures
  • Favourites

Benefits include:

  • Centralised storage
  • Simplified backup
  • Reduced profile size
  • Easier workstation replacement

Example Architecture

+-------------+
| User Device |
+------+------+
       |
       v
+-------------+
| Active      |
| Directory   |
+------+------+
       |
       v
+-------------+
| File Server |
| Home Folders|
+-------------+

Users access their files as normal while data is actually stored on the server.

Common Pitfalls

Redirecting Too Much

Redirecting every available folder can create unexpected behaviour.

Downloads, for example, may contain large temporary files that consume server storage unnecessarily.

Incorrect Permissions

Misconfigured NTFS or Share permissions frequently cause:

  • Access denied errors
  • Synchronisation failures
  • Missing folders

Network Dependency

Redirected folders stored on a file server become dependent upon network connectivity.

Poor network performance often presents itself as:

  • Slow file access
  • Delayed login times
  • Application performance issues

Legacy Applications

Some older applications assume all user data exists locally.

Such applications may not function correctly when data is redirected to remote storage.

Design & Architecture Considerations

Scalability

For small environments, a single file server may be sufficient.

Larger organisations often use:

  • DFS Namespaces
  • DFS Replication
  • Clustered storage
  • Cloud-integrated file services

Security

Consider:

  • NTFS permissions
  • Share permissions
  • Access Based Enumeration
  • Encryption
  • Backup retention

User data often contains sensitive business information and should be protected accordingly.

Maintainability

Folder structures should remain predictable.

A common example:

\\FILESERVER\Users\%USERNAME%\Documents

Consistent naming simplifies support and migration activities.

Modern Alternatives

Many organisations are now adopting:

  • OneDrive Known Folder Move (KFM)
  • Microsoft 365 integration
  • Hybrid file storage solutions

These approaches provide similar benefits while extending access beyond the traditional corporate network.

Troubleshooting & Diagnostics

Verify Group Policy

Check:

gpresult /r

or

gpresult /h report.html

to confirm that Folder Redirection policies have been applied.

Verify Folder Path

Confirm the expected path using:

echo %USERPROFILE%

and examine the folder's Location properties.

Check Permissions

Verify:

  • NTFS permissions
  • Share permissions
  • Effective permissions

Permission issues account for a large proportion of Folder Redirection support cases.

Event Logs

Review:

  • Application Log
  • System Log
  • GroupPolicy Operational Log

These frequently contain useful diagnostics relating to redirection failures.

Design Recommendations

  • Use Folder Redirection rather than junction points wherever practical.
  • Avoid moving the entire C:\Users structure on existing systems.
  • Redirect only the folders that provide business value.
  • Combine Folder Redirection with a robust backup strategy.
  • Consider OneDrive integration for modern Microsoft 365 environments.
  • Test policy changes with a pilot group before enterprise-wide deployment.

Related Topics

References

  • Microsoft Group Policy Documentation
  • Microsoft Folder Redirection Documentation
  • Microsoft FSLogix Documentation
  • Microsoft OneDrive Known Folder Move Documentation