Questions? Feedback?powered byOlark live chat software
Bug 3153

Default printer redirect on Windows Server 2016 doesn't work with RemoteApp 10 September, 2019

Eric Cole
06 August, 2019
Product: PowerBuilder Category: PowerScript
Version: 2019 Publishing: Public
Status: Analyzing Priority: P3
Classification: Resolution:
Eric Cole 10 September, 2019
(In reply to Cedric Pernet from comment #1)
Hello Eric,
I'll be reproducing your issue and comparing it with the past cases that you
mention, I'll let you know any updates as soon as I can.

-Cedric
Any update on this? Were you able to reproduce?
Cedric Pernet 06 August, 2019
Hello Eric,
I'll be reproducing your issue and comparing it with the past cases that you mention, I'll let you know any updates as soon as I can.

-Cedric
Eric Cole 06 August, 2019
This is the same issue as Bug 1878 and 1732 except that it's only not working when running the application as a RemoteApp.

The weird thing is I remote in normally using the mstsc client and it works fine, default printer is the redirected local default printer, not the default printer of the server.

But if I publish it as a RemoteApp and connect through the server.address/RDWeb, it doesn't use the redirected default printer, it's back to using the default printer of the machine.
OS:
Windows Server 2016 
Platform:
64-bit 
Database Type:
Microsoft SQL Server 
Database Version: