- Leif Olsson
- PowerBuilder
- Wednesday, 4 December 2019 01:41 PM UTC
Scenario:
- In Windows client printer settings "Let Windows manage my default printer" is checked
- Local printers are redirected to remote server
- Our PowerBuilder application starts through RemoteApp
Issue: At first print in a RemoteApp-session PrintGetPrinter() function seems to randomly get a printer (and not the last used in client).
When the user has printed, the PrintGetPrinter() function gets the last used printer. But only in that session.
There are printerfixes in PowerBuilder 2019 regarding Windows server 2016, but those fixes does not resolve this issue.
We have the same problem with runtime for PowerBuilder 2017 R3 and PowerBuilder 2019. We have added the Swedish language pack to the runtime.
I have searched this forum and the Internet. The only suggestions is to turn off setting "Let Windows manage my default printer". Fine with me,
but not accepted by our customers.
I have also seen that Microsoft has changed registry keys that handles default printer (also mentioned in this forum):
[With the release of server-2012 and up (2016, 2019), Microsoft changed
the location of terminal-server default printer from:
"HKEY_CURRENT_USER\SOFTWARE\Microsoft\Terminal Server
Client\DefaultPrinter"
to:
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Windows\SessionDefaultDevices\<session>\Device".]
Is this issue a bug in PowerBuilder or is the solution to change some settings on the server or?
/Leif
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.