Anavem
Languagefr
IT security analyst configuring Print Spooler Redirection Guard policies in Microsoft Intune admin console

How to Enable Print Spooler Redirection Guard Using Microsoft Intune

Configure and deploy Print Spooler Redirection Guard security policy through Microsoft Intune to prevent file redirection attacks and achieve CIS Level 1 compliance in enterprise environments.

May 11, 2026 12 min
Start procedure
Mediumintune9 steps 12 min

Why Enable Print Spooler Redirection Guard in Enterprise Environments?

The Print Spooler Redirection Guard represents a critical security control that addresses one of the most significant attack vectors in Windows environments. Following the PrintNightmare vulnerabilities (CVE-2021-34527 and related exploits), Microsoft introduced this protection mechanism to prevent malicious actors from exploiting the Windows Print Spooler service for file redirection attacks and privilege escalation.

This security control has become a mandatory requirement under the CIS Microsoft Intune for Windows 11 Benchmark v4.0.0, specifically designated as Level 1 control 4.7.2. The policy prevents non-administrative processes from redirecting files through the print spooler, effectively blocking a common attack technique used in lateral movement and system compromise scenarios.

What Does Print Spooler Redirection Guard Actually Protect Against?

The Redirection Guard specifically targets file redirection attacks where malicious code attempts to use the print spooler service to access, modify, or redirect files to unauthorized locations. These attacks often involve symlink manipulation, where attackers create symbolic links that redirect file operations to sensitive system locations, potentially leading to privilege escalation or data exfiltration.

By enabling this control through Microsoft Intune, you're implementing a defense-in-depth strategy that complements other print security measures. The policy works at the system level, intercepting redirection attempts before they can compromise system integrity, while maintaining normal printing functionality for legitimate operations.

How Does Microsoft Intune Deployment Simplify Print Security Management?

Managing print security across hundreds or thousands of Windows devices traditionally required complex Group Policy deployments or manual registry modifications. Microsoft Intune's Settings Catalog approach streamlines this process by providing a centralized, cloud-based policy management system that can deploy the Print Spooler Redirection Guard configuration to all enrolled devices automatically.

This tutorial will guide you through the complete process of configuring, deploying, and monitoring this critical security control using Intune's modern device management capabilities, ensuring your organization meets CIS benchmark requirements while maintaining operational efficiency.

Implementation Guide

Full Procedure

01

Access Microsoft Intune Admin Center and Create Configuration Profile

Start by logging into the Microsoft Intune admin center and navigating to the configuration profiles section where you'll create a new policy.

Open your web browser and navigate to https://endpoint.microsoft.com. Sign in with your administrator credentials that have Intune permissions.

Once logged in, follow this navigation path:

  1. Click Devices in the left navigation pane
  2. Select Configuration profiles
  3. Click Create profile button

In the profile creation wizard, configure the basic settings:

  • Platform: Select "Windows 10 and later"
  • Profile type: Choose "Settings catalog"
  • Click Create
Pro tip: Settings catalog is the recommended approach as it provides ADMX-backed policies with better granular control compared to custom OMA-URI configurations.

Verification: You should now see the "Create profile" wizard with "Settings catalog" selected and ready for the next configuration step.

02

Configure Basic Profile Information and Metadata

Set up the profile name, description, and basic metadata that will help you identify and manage this policy in your Intune environment.

In the Basics tab of the profile creation wizard, enter the following information:

Name: CIS 4.7.2 - Print Spooler Redirection Guard
Description: Enable Print Spooler Redirection Guard (CIS Level 1 Benchmark 4.7.2) - Prevents file redirection attacks in spooler process and reduces attack surface

This naming convention follows CIS benchmark standards and clearly identifies the security control being implemented. The description provides context for other administrators who might review this policy later.

Warning: Use descriptive names that include the security control reference. This becomes critical when managing hundreds of policies in large enterprise environments.

Click Next to proceed to the configuration settings section.

Verification: Confirm that your profile name and description are saved correctly before moving to the next step. The profile should appear in your drafts with the specified name.

03

Add Print Spooler Redirection Guard Setting from Settings Catalog

Now you'll add the specific Print Spooler Redirection Guard setting from Microsoft's comprehensive settings catalog.

In the Configuration settings tab, click the Add settings button. This opens the settings picker where you can search for specific policies.

In the search box, type Redirection Guard and press Enter. You should see the following setting appear:

Category: Printers
Setting Name: Configure Redirection Guard: Redirection Guard Options
Path: ./Device/Vendor/MSFT/Policy/Config/Printers/ConfigureRedirectionGuardRedirectionGuardOptions

Select this setting by checking the box next to it, then click Add. The setting will now appear in your configuration list.

Configure the setting value:

  • Configure Redirection Guard: Redirection Guard Options: Set to Enabled: Redirection Guard Enabled
  • This corresponds to integer value 1 in the underlying registry
Pro tip: The setting has three possible values: 0 (Disabled), 1 (Enabled - default), and 2 (Audit mode). Use audit mode (2) initially in test environments to monitor impact before full enforcement.

Verification: Confirm the setting appears in your configuration list with the correct value selected. The policy path should show the full CSP path as listed above.

04

Configure Assignment Groups and Target Devices

Define which devices and users will receive this Print Spooler Redirection Guard policy through strategic group assignments.

Click Next to reach the Assignments tab. Here you'll specify which devices should receive this security policy.

For enterprise-wide deployment, configure assignments as follows:

  1. Click Add group under "Included groups"
  2. Select All devices or create a specific device group like "Windows 11 Enterprise Devices"
  3. Choose Assignment type: Required (this ensures the policy is enforced)

For phased deployment approach:

Phase 1: Pilot Group (10-50 devices)
Phase 2: Department Groups (IT, Security teams)
Phase 3: All Enterprise Devices

If you need to exclude specific devices (like print servers or legacy systems), use the "Excluded groups" section:

  1. Click Add group under "Excluded groups"
  2. Select groups containing devices that should not receive this policy
Warning: Excluding print servers from this policy might be necessary if they require specific file redirection capabilities. Test thoroughly in your environment first.

Verification: Review your assignment summary to ensure the correct groups are included and excluded. The assignment should show the expected device count.

05

Set Applicability Rules for Windows Version Compatibility

Configure applicability rules to ensure the policy only applies to compatible Windows versions that support Print Spooler Redirection Guard.

Click Next to access the Applicability Rules tab. This step is crucial because the Redirection Guard feature requires specific Windows versions.

Create a new applicability rule:

  1. Click Add rule
  2. Configure the rule parameters:
Rule: Device
Property: OS version
Operator: Greater than or equal to
Value: 10.0.22621 (Windows 11 22H2)

For organizations with mixed Windows 10/11 environments, add an additional rule:

Rule: Device
Property: OS version
Operator: Greater than or equal to
Value: 10.0.19044 (Windows 10 22H2)

Use OR logic between these rules to support both operating systems.

Pro tip: Applicability rules prevent policy conflicts and "Not Applicable" status reports on unsupported devices. This keeps your compliance reporting clean and accurate.

The rule ensures that only devices running Windows 11 22H2+ or Windows 10 22H2+ will receive this policy, preventing errors on older systems that don't support the CSP.

Verification: Confirm your applicability rules are correctly configured with the proper OS version numbers. Test the logic by checking which devices in your tenant would match these criteria.

06

Review Configuration and Deploy the Policy

Complete the policy creation process by reviewing all settings and deploying the Print Spooler Redirection Guard configuration to your target devices.

Click Next to reach the Review + create tab. This final step allows you to verify all configuration details before deployment.

Review the following key elements:

  • Profile name: CIS 4.7.2 - Print Spooler Redirection Guard
  • Settings: Configure Redirection Guard = Enabled
  • Assignments: Verify correct device groups
  • Applicability: Windows version rules are properly set

Once you've confirmed all settings are correct, click Create to deploy the policy.

The policy will now begin deploying to assigned devices. Initial deployment typically takes 15-30 minutes, but can take up to 8 hours for all devices to receive and apply the policy.

Warning: Monitor the first few devices closely after deployment. While this policy has minimal impact (it's enabled by default), always verify that printing functionality remains normal in your environment.

Verification: Navigate to DevicesConfiguration profiles and confirm your new policy appears in the list with "Assigned" status. Check the overview dashboard for deployment progress.

07

Monitor Policy Deployment and Device Compliance Status

Track the deployment progress and verify that devices are successfully receiving and applying the Print Spooler Redirection Guard policy.

Navigate to your newly created policy in the Intune admin center:

  1. Go to DevicesConfiguration profiles
  2. Click on your "CIS 4.7.2 - Print Spooler Redirection Guard" policy
  3. Review the Overview dashboard

The overview provides key deployment metrics:

Device status:
- Succeeded: Devices that successfully applied the policy
- Error: Devices that encountered errors
- Conflict: Devices with conflicting policies
- Not applicable: Devices that don't meet applicability rules

For detailed troubleshooting, click on Device status to see individual device results. Common status indicators include:

  • Success: Policy applied correctly
  • Pending: Device hasn't checked in yet (normal for up to 8 hours)
  • Error: Check device logs or applicability rules
Pro tip: Use the "Export" function to create reports for compliance auditing. This is especially important for CIS benchmark compliance documentation.

Verification: Aim for 95%+ success rate within 24 hours of deployment. Investigate any persistent errors or conflicts that appear in the status dashboard.

08

Verify Policy Application on Target Devices Using PowerShell

Confirm that the Print Spooler Redirection Guard policy has been successfully applied on individual Windows devices using PowerShell verification commands.

Connect to a target device (via RDP, local access, or remote PowerShell) and open an elevated PowerShell session. Run the following commands to verify policy application:

Check Registry Value (Applied State):

Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\PolicyManager\current\device\Printers" -Name "ConfigureRedirectionGuardRedirectionGuardOptions" -ErrorAction SilentlyContinue

Expected output should show:

ConfigureRedirectionGuardRedirectionGuardOptions : 1

Check Effective Policy State:

Get-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows NT\Printers" -Name "RedirectionguardPolicy" -ErrorAction SilentlyContinue

Verify Print Spooler Service Status:

Get-Service -Name "Spooler" | Select-Object Name, Status, StartType

Check Event Logs for Redirection Guard Activity:

Get-WinEvent -LogName "Microsoft-Windows-PrintService/Operational" -MaxEvents 10 | Where-Object {$_.Id -eq 316} | Select-Object TimeCreated, Id, LevelDisplayName, Message
Pro tip: Event ID 316 in the PrintService log indicates when Redirection Guard blocks a file redirection attempt. This helps you monitor the security control's effectiveness.

Verification: The registry value should be set to 1, and the print spooler service should be running normally. No immediate event log entries are expected unless redirection attempts occur.

09

Test Print Functionality and Security Controls

Perform comprehensive testing to ensure that normal printing operations work correctly while malicious file redirection attempts are properly blocked.

Test Normal Printing Operations:

  1. Print a test document to a network printer
  2. Print to a local USB printer
  3. Test print preview and print queue operations
  4. Verify PDF printing and XPS document writer functionality

Test Remote Desktop Printing (if applicable):

# Check RDP printer redirection status
Get-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" -Name "fDisableCpm" -ErrorAction SilentlyContinue

Simulate Security Test (Advanced Users Only):

The Redirection Guard specifically prevents non-administrative processes from redirecting files through the print spooler. This test should only be performed in isolated test environments:

# Check if redirection attempts are logged
Get-WinEvent -LogName "Microsoft-Windows-PrintService/Operational" -FilterHashtable @{ID=316} -MaxEvents 5 | Format-Table TimeCreated, Message -Wrap
Warning: Do not attempt to create actual malicious files or exploits for testing. The policy works at the system level and should be validated through proper security testing tools in isolated environments only.

Document Test Results:

  • Normal printing: ✓ Working
  • Network printers: ✓ Accessible
  • Print queues: ✓ Functional
  • Security controls: ✓ Active (no redirection events)

Verification: All standard printing functionality should work normally. The presence of the registry value confirms the security control is active, even if no blocking events are logged initially.

Frequently Asked Questions

What is Print Spooler Redirection Guard and why is it important for Windows security?+
Print Spooler Redirection Guard is a Windows security feature that prevents non-administrative processes from redirecting files through the print spooler service. It's crucial because it blocks a common attack vector used in PrintNightmare-style exploits where attackers manipulate the print spooler to access or redirect files to unauthorized locations. This control is now mandatory under CIS Level 1 benchmarks and helps prevent privilege escalation and lateral movement attacks in enterprise environments.
Does enabling Print Spooler Redirection Guard affect normal printing functionality?+
No, enabling Print Spooler Redirection Guard does not impact normal printing operations. The policy specifically targets malicious file redirection attempts while allowing legitimate printing functions to work normally. Users can still print to network printers, local printers, PDF writers, and use Remote Desktop printing redirection. The guard only blocks unauthorized file system operations that could be exploited by attackers, not standard print jobs or administrative printer management tasks.
How do I verify that Print Spooler Redirection Guard is working correctly on Windows devices?+
You can verify the policy is active by checking the registry value at HKLM:\SOFTWARE\Microsoft\PolicyManager\current\device\Printers for 'ConfigureRedirectionGuardRedirectionGuardOptions' which should equal 1. Additionally, monitor Event ID 316 in the Microsoft-Windows-PrintService/Operational log, which indicates when redirection attempts are blocked. Use PowerShell commands like Get-ItemProperty and Get-WinEvent to check these values. Normal printing should continue to work without any user-visible changes.
What are the minimum Windows versions required for Print Spooler Redirection Guard policy deployment?+
Print Spooler Redirection Guard requires Windows 11 22H2 (build 10.0.22621) or later, and Windows 10 22H2 (build 10.0.19044) or later. The policy uses the Printers CSP which was enhanced to support this feature in these versions. When deploying through Intune, you should configure applicability rules to target only these supported versions to avoid 'Not Applicable' status reports on older devices. Windows Server 2022 and Server 2025 also support this feature.
Can I use audit mode for Print Spooler Redirection Guard before full enforcement?+
Yes, you can configure the policy with value 2 to enable audit mode, which logs redirection attempts without blocking them. This allows you to monitor potential impacts in your environment before full enforcement. In audit mode, Event ID 316 will still be logged in the PrintService operational log when redirection attempts occur, but the attempts won't be blocked. This is useful for testing environments or gradual rollouts where you want to understand the baseline behavior before implementing full protection with value 1 (enabled/blocking mode).

Discussion

Share your thoughts and insights

Sign in to join the discussion