AnsweredAssumed Answered

Local default printer not recognized as default printer in remote desktop

Question asked by mislav on Dec 7, 2018
Latest reply on Jan 11, 2019 by mislav

When local printers are redirected to a Microsoft remote desktop (running Windows Server 2016), I would expect the local default printer to be designated as the default printer on that remote desktop when trying to print using FileMaker Pro running. That's how it works with other applications; e.g. Notepad. But FileMaker Pro seems to default to one of the printers on the remote server instead.

 

The local printers are correctly redirected, but the default isn't recognized by FileMaker Pro, even though it's recognized by other applications.

 

Here's the FileMaker Pro print dialog. The five printers that have the word "redirected" in their names are the ones that have been redirected from the local workstation. The "Fax (redirected 117)" printer has been configured as the default printer on the local workstation. But FileMaker Pro defaults to the "Microsoft Print to PDF" printer instead (shown highlighted in the screenshot), which is one of the printers on the server.

 

FileMaker Pro printers.png

 

This Microsoft TechNet post (RemoteApp Default Printer Redirection Not Working in Server 2016 ) seems to describe a similar situation where another software product (not FileMaker) had the same issue.

 

Based on suggestions from that Microsoft TechNet post, I can see in the registry that the local default printer has carried over correctly to the remote desktop:

 

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\SessionDefaultDevices

Default local printer.png

 

And it gets correctly picked up by other applications, like Notepad for example, but not by FileMaker Pro.

 

Maybe FileMaker Pro is getting its default from this registry key instead?

 

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\

Server printer.png

Outcomes