Printer not being redirected to virtual desktop

Hi,

Thanks for the detailed post — this is actually one of the more common printing pain points in AVD, and the good news is it's very fixable. Even when RDP properties look correct on the surface, there are a few layers that all have to align for printer redirection to work. Let me walk you through each one.

WHY THIS HAPPENS

AVD uses a priority-based redirection model — the most restrictive setting always wins. So even if printer redirection is enabled in your RDP client, a conflicting GPO or a host pool default can silently block it. Importantly, printer redirection is DISABLED by default on newly created host pools, which catches a lot of people off guard.

STEP 1 — Enable Printer Redirection in Host Pool RDP Properties (Most Likely Culprit)

This is the first place to check. In the Azure Portal:

1. Go to Azure Virtual Desktop → Host Pools → [Your Host Pool]
2. Select RDP Properties → Device Redirection
3. Under Printer Redirection, change the setting to: "The printers on the local computer are available in remote session"
4. Click Save

This sets the RDP property: redirectprinters:i:1
https://learn.microsoft.com/en-us/azure/virtual-desktop/redirection-configure-printers?tabs=intune&pivots=azure-virtual-desktop

STEP 2 — Check GPO on Session Hosts Is Not Blocking Redirection

A Group Policy setting on the session host can override everything else. On each session host, open gpedit.msc and verify:

Computer Configuration → Administrative Templates → Windows Components

→ Remote Desktop Services → Remote Desktop Session Host → Printer Redirection

• "Do not allow client printer redirection" → must be set to Disabled or Not Configured

Remember: if this GPO is set to Disabled/Blocked at the session host level, enabling it in the host pool RDP properties will have NO effect — the most restrictive setting always wins.
https://learn.microsoft.com/en-us/azure/virtual-desktop/redirection-configure-printers?tabs=group-policy&pivots=azure-virtual-desktop

STEP 3 — Verify the Print Spooler Service Is Running on the Session Host

This one is easy to overlook. RDP on the session host: open services.msc and confirm:

• Print Spooler → Status: Running, Startup: Automatic

• Remote Desktop Services UserMode Port Redirector → Running

If either is stopped, printer redirection simply won't function regardless of your settings.

STEP 4 — Confirm Printer Driver Is Installed on the LOCAL Device

AVD uses the Remote Desktop Easy Print driver on the session host side — so you do NOT need drivers installed on the session host. However, the printer driver MUST be properly installed on the user's local physical machine. If the local driver is missing or corrupted, the printer won't redirect.
https://learn.microsoft.com/en-us/azure/virtual-desktop/redirection-configure-printers

STEP 5 — Verify the AVD Client Version

Make sure users are connecting via the latest Windows App or Remote Desktop client (not an outdated version or the web client, which has limited redirection support). Outdated clients have known issues with printer redirection in AVD.
https://learn.microsoft.com/en-us/azure/virtual-desktop/users/connect-windows

Thanks,
Manish.

Hey there! It sounds like you’ve enabled printer redirection in your host-pool RDP properties but your local printers still aren’t showing up in the AVD session. Here are the key things to check and steps you can try:

1. Verify Host-Pool RDP Properties • In the Azure portal, go to Azure Virtual Desktop > Host pools > select your host pool > RDP Properties > Device redirection. • Make sure you have redirectprinters:i:1 in your Custom RDP property string.
2. Confirm Client-Side Settings • In your Remote Desktop client (Windows App or Remote Desktop), open the connection settings and under Local Resources ensure Printers is checked. • If you’re on macOS/Linux/iOS/etc., verify that platform supports printer redirection.
3. Check Session-Host Configuration & Policies • On the session-host VMs, open gpedit.msc → Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Device and Resource Redirection. • Ensure “Do not allow printer redirection” is Disabled. • Confirm Windows Update is enabled on the session host so the Remote Desktop Easy Print driver can install automatically.
4. Test Inside the Remote Session • Open Settings → Devices → Printers & scanners and look for your printer(s) appended with “(redirected n)”. • Or run in PowerShell: Get-Printer | Where-Object DriverName -eq "Remote Desktop Easy Print"
5. Registry Check (Local Machine) • On your local Windows PC, open regedit and navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Terminal Server Client • Make sure there’s no DWORD named DisablePrinterRedirection set to 1.
6. Review Driver Compatibility • Redirected printers use the built-in Easy Print driver on the session host; you don’t need to install your specific printer driver there. Just have your printer driver installed on your local device.
7. (Optional) Consider Universal Print • If printer redirection remains flaky or you need more robust roaming/management, Universal Print can be an alternative.

If you go through all of the above and still don’t see your printers, please let us know:

• Which Remote Desktop client and OS you’re using (Windows, macOS, mobile, version, etc.)
• Your session-host OS version
• Whether your local printer is USB-attached or network-shared
• The exact Custom RDP property string you’re using
• Any errors or warnings in the session-host Event Viewer under Applications and Services → Microsoft → Windows → TerminalServices-ClientActiveXCore/DeviceRedirector

Hope this helps you get printing working in your AVD session!

References

1. Troubleshooting Remote Desktop Client Redirection Issues https://learn.microsoft.com/azure/virtual-desktop/troubleshoot-client-redirection
2. Configure printer redirection over RDP (azure-virtual-desktop) https://learn.microsoft.com/azure/virtual-desktop/redirection-configure-printers
3. Customize host-pool RDP properties https://learn.microsoft.com/azure/virtual-desktop/customize-rdp-properties
4. Supported RDP properties for Azure Virtual Desktop https://learn.microsoft.com/azure/virtual-desktop/rdp-properties
5. Redirection over the Remote Desktop Protocol – Overview https://learn.microsoft.com/azure/virtual-desktop/redirection-remote-desktop-protocol

Note: This content was drafted with the help of an AI system. Please verify the information before relying on it for decision-making.

cloudadmin hi & thx for join me here at Q&A portal,

test full client + GPO + spooler first, then printer driver/Universal Print path, this is usually policy/client side, not AVD host pool itself. See the user connects with the full Remote Desktop client, not browser, because printer redirection is limited there. & check host pool RDP properties include printer redirection enabled, and confirm no GPO blocks it: Do not allow client printer redirection, Do not set default client printer, and Remote Desktop Services device redirection policies. On the session host check Print Spooler is running and restart it, is printer is installed on the local physical PC and marked available before connecting. If using Universal Print or redirected printers from a print server, test with a simple local PDF printer first, because driver-heavy printers often fail.

rgds, Alex

&

if my answer helps pls accept it & follow me at Q&A portal of coz ;)