Anavem
Languagefr
preferencesUser Configuration Enabled

Grant User Exclusive Rights to Redirected Folders

Ensures only the user and administrators have access to their redirected folder.

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

Ensures only the user and administrators have access to their redirected folder. Security baselines recommend setting it to Enabled.

Description

Grant User Exclusive Rights to Redirected Folders is a Windows Group Policy setting located under User Configuration > Windows Settings > Folder Redirection > [any folder] > Settings. It applies to the User Configuration branch and is classified as a Warning-level policy in the Folder Redirection category.

Ensures only the user and administrators have access to their redirected folder.

Microsoft sets the default value to Enabled while industry security baselines (CIS, NIST, DISA STIG) recommend Enabled.

In-depth explanation

This setting has a meaningful impact on the security posture or operational stability of the system. Leaving it at the Microsoft default is acceptable for standalone or low-risk environments, but most security baselines (CIS, NIST, DISA STIG) explicitly call for hardening it before the device is exposed to untrusted users or networks.

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 'Grant User Exclusive Rights to Redirected Folders' 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

Leaving this policy at default does not directly grant an attacker access, but it widens the blast radius once initial access is obtained – passwords are easier to guess, lockout doesn't fire, audit trails are incomplete, or lateral movement is quieter. Most regulators and cyber-insurance underwriters now expect this control to be in place at least at the recommended level.

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 > [any folder] > Settings.
  4. Open Grant User Exclusive Rights to Redirected Folders and set it to Enabled.
  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 Grant User Exclusive Rights to Redirected Folders Group Policy do?
Ensures only the user and administrators have access to their redirected folder.
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 > [any folder] > Settings</code> and look for <strong>Grant User Exclusive Rights to Redirected Folders</strong>.
What is the Microsoft default value?
<code>Enabled</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>Enabled</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.