We needed to keep the same user interface, but would have liked to have been able to use just the one printer and programmatically set duplex on or off. The application would then switch the default printer in Windows to the appropriate printer, depending on the user choice and duplex requirement. Actually a third would be needed to allow the user to keep custom settings for their own preferences. The way this problem used to be handled is to install two printers, one set to always print single-sided and another to always print double-sided. This is a story of how we solved this issue. getting the documents to print double-sided.

One issue that we have with it is Duplex printing, i.e.

This way, I can go to our engineering team and ask why these particular settings/values in the LTSR branch differ from the CR branch.I have been working on a program that prints any document you provide to it, as long as there is an application installed on your computer that can handle that document. Are there registry keys or values the application is looking for that are present in VDA 1912 sessions that are not present in VDA 2003 sessions? This is the level of information we need from the application vendor. “The goal is to have the vendor explain what their application is looking for to enumerate a printer in their application. Below is what Citrix would be looking for on the call. So right now we have our VDAs working on the LTSR version (1912) but we are unable to upgrade to the latest VDA versions starting with 2003. Is there any other information that could be provided that may be helpful to them? I saw in another thread The PB run-time just calls the equivalent 'Enumprinters' command API in the O/S ( ). Here is the information they are looking for and I was hoping someone could help answer this as to how PB is looking for the printers. One clientis still having an issue and has been working with Citrix directly but was hoping for some guidance as per a request from Citrix to have a phone call. We then found an option in Citrix that tells the application to start without waiting for default printers, we turned this off which causes a minimal delay but the default printers were now available. At the time we tried to implement a suggestion found here by adding an option that our application would call an extra windows printer API when opening to determine which default printer to use but that didn't seem to help. We recently upgraded to PB 2019 and had some complaints from our users in the Citrix environment where their default printer was not being set correctly.

Windows api enumprintersw