Anavem
Languagefr
preferencesUser ConfigurationNot configured

Redirect Documents Folder

Redirects My Documents to a network location. Ensures user data is backed up.

10 May 20264 min
Policy path
User Configuration > Windows Settings > Folder Redirection > Documents
Supported on
Windows 10, Windows 11, Windows Server 2016 and later

Redirects My Documents to a network location. Ensures user data is backed up. Security baselines recommend setting it to Redirect to UNC share or OneDrive.

Description

Redirect Documents Folder is a Windows Group Policy setting located under User Configuration > Windows Settings > Folder Redirection > Documents. It applies to the User Configuration branch and is classified as a Informational-level policy in the Folder Redirection category.

Redirects My Documents to a network location. Ensures user data is backed up.

Microsoft sets the default value to Not configured while industry security baselines (CIS, NIST, DISA STIG) recommend Redirect to UNC share or OneDrive.

In-depth explanation

This is primarily an operational or user-experience setting. It does not directly raise or lower the security posture, but it standardizes behavior across the fleet, which is important for predictable support, training, and troubleshooting in an MSP-managed environment.

The policy is grouped under Folder Redirection, which means it is typically applied through a domain-wide GPO linked at the OU level. In a multi-tenant MSP context, scope it through WMI filters or security group filtering rather than linking at the domain root, so that you can roll out progressively (pilot OU → wider rings → all production).

The setting takes effect after the next Group Policy refresh (gpupdate /force for immediate testing, or by default within ~90 minutes for workstations and ~5 minutes on domain controllers). For computer-side policies a reboot may be required; for user-side policies, a sign-off/sign-on cycle is enough.

Use cases

  • Apply organization-wide hardening of folder redirection on all domain-joined Windows endpoints.
  • Roll out a CIS Benchmark-aligned baseline targeting 'Redirect Documents Folder' via a dedicated GPO.
  • Reduce attack surface for accounts that handle privileged credentials or sensitive data.
  • Standardize the configuration across multiple customer tenants for an MSP-managed fleet.

Security implications

This control is primarily about consistency and supportability rather than security. The main risk of leaving it unconfigured is divergence between machines, which makes troubleshooting and standardized imaging harder, especially across multiple customer tenants in an MSP context.

How to configure

  1. Open Group Policy Management Console (gpmc.msc) on a domain controller or a workstation with RSAT installed.
  2. Create or edit a GPO linked to the OU containing the target user configurations. We recommend a dedicated baseline GPO (e.g. SEC – Folder Redirection) instead of editing Default Domain Policy.
  3. Navigate to User Configuration > Windows Settings > Folder Redirection > Documents.
  4. Open Redirect Documents Folder and set it to Redirect to UNC share or OneDrive.
  5. Click OK and close the editor.
  6. On the target endpoint, run gpupdate /force (or wait for the next refresh cycle), then verify with rsop.msc or gpresult /h report.html.

Frequently asked questions

What does the Redirect Documents Folder Group Policy do?
Redirects My Documents to a network location. Ensures user data is backed up.
Where do I find this setting in the GPO editor?
Open <code>gpmc.msc</code>, then navigate to <code>User Configuration > Windows Settings > Folder Redirection > Documents</code> and look for <strong>Redirect Documents Folder</strong>.
What is the Microsoft default value?
<code>Not configured</code> on a fresh Windows install. Domain-joined machines may inherit a different value if a baseline GPO is already in place.
What value do security baselines recommend?
<code>Redirect to UNC share or OneDrive</code> – aligned with CIS, NIST, and DISA STIG guidance for current Windows versions.
How quickly does the change take effect?
After the next Group Policy refresh — run <code>gpupdate /force</code> for immediate testing or wait ~90 minutes for workstations / ~5 minutes for domain controllers. Some computer-side policies require a reboot, and some user-side policies require sign-off/sign-on.