Hello Thomas Gellar,
Thank you for posting question on Microsoft Windows Forum!
The fact of the matter is that Microsoft Print to PDF and Mac printer redirection are two entirely separate mechanisms. The former is a local virtual printer on the server for creating PDFs inside the session, while the latter is the feature that allows a Mac's local printer to appear as a redirected queue inside the remote session. Microsoft Print to PDF itself does not enable or provide Mac printer redirection.
The suggestion here is to verify Mac RDP client settings and making sure the Mac client is explicitly configured to pass local printers through to the AWS session. Open the Microsoft Remote Desktop app on your Mac. Right-click your connection profile (or click the Edit pencil icon) and navigate to Devices & Audio (or Devices) and ensure the Printers checkbox is selected. Save the settings, disconnect completely, and log back in. Also, making sure access is enabled for Windows App or Microsoft Remote Desktop under System Settings → Privacy & Security → Local Network .Then fully quit and reopen the app.
Another point worth mentioning is that the server must be configured to allow client printer redirection and to use the Easy Print driver. On the Server 2022 host, making sure the following two settings Do not allow client printer redirection is set to Disabled or Not Configured and Use Remote Desktop Easy Print printer driver first is set to Enabled under this path Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Printer Redirection. This is crucial because it allows redirection without needing to install the Mac printer's specific driver on the server. After applying the policy, run gpupdate /force and restart the server to ensure the changes take effect.
Also, it is worth verifying the status of Print Spooler in state of "start" or restart the service and navigate to Control Panel -> Devices and Printers on the server during an active user session. Check if the Mac's local printers show up as [Printer Name] (redirected X). Please note: If a Mac user is looking for "Microsoft Print to PDF", they should ideally select Save as PDF or print to their Mac's native PDF handler natively from their local Mac preview, which maps through smoothly via Easy Print. If they expect the server's "Microsoft Print to PDF" to generate a file on the AWS server, remember that it saves to the remote server's C: drive, not the local Mac.
If the Microsoft Print to PDF virtual printer itself is missing from the server's printer list (for creating PDFs locally), you can try to reinstall Microsoft print to PDF by running OptionalFeatures.exe and enable the Microsoft Print to PDF feature, then restart if prompted.
I hope you have found something useful here. If it helps you get more insight into the issue, it is appreciated to accept the answer. Should you have more questions, feel free to leave a message.