Windows Server 2016/Default and virtual printer issue
Hi everyone,
I have a server (windows server 2016) configured to run applications.
Every end-user connects to this server in order to run an specific software (desktop app). Within that software the user can use the option to "prints" documents. The first issue here is that those documents had barcodes. If I do a preview of the document using the app everything looks good, but once I want to print it, the barcodes are missed.
So, what I've done is to install "PrimoPDF" and tell the user to select that printer to save the documents with the barcodes. Works so good! But,
Second and main issue is that if I set a default printer to be a "Physical printer" and the user goes to the app and try to print the document, selecting "PrimoPDF", the document goes to the physical printer and not to the virtual one (PrimoPDF). For example, in "Devices and Printers", I have a LaserJet printer as my default printer. And have install also PrimoPdf, a virtual printer. Within the software if I want to print the document, then select the virtual one from the list cause I don't want to print in papers, but it goes to the physical printer.
This escenario does no happens with a previous version of Windows Server 2016. It also does not happen on Windows 7 and Windows 10. It takes the one that the user selects. I was doing a reaserch on this subject and I found this link/pages on Technet: https://social.technet.microsoft.com/Forums/en-US/785cbcc6-4f0b-4d88-b12f-2b1d89b85a44/remoteapp-default-printer-redirection-not-working-in-server-2016?forum=winserverTS
But I think is not exactly my scenario.
Had anyone of you seen/heard of this?
Additional information.
Application: Desktop Application (build in vb6 and vb.net)
Connection: RemoteApp (end-users can connect remotely to the application, located in windows server 2016).
If i didn't make myself clear, please let me know, so I can explain better!
Thank you,
Regards
I have a server (windows server 2016) configured to run applications.
Every end-user connects to this server in order to run an specific software (desktop app). Within that software the user can use the option to "prints" documents. The first issue here is that those documents had barcodes. If I do a preview of the document using the app everything looks good, but once I want to print it, the barcodes are missed.
So, what I've done is to install "PrimoPDF" and tell the user to select that printer to save the documents with the barcodes. Works so good! But,
Second and main issue is that if I set a default printer to be a "Physical printer" and the user goes to the app and try to print the document, selecting "PrimoPDF", the document goes to the physical printer and not to the virtual one (PrimoPDF). For example, in "Devices and Printers", I have a LaserJet printer as my default printer. And have install also PrimoPdf, a virtual printer. Within the software if I want to print the document, then select the virtual one from the list cause I don't want to print in papers, but it goes to the physical printer.
This escenario does no happens with a previous version of Windows Server 2016. It also does not happen on Windows 7 and Windows 10. It takes the one that the user selects. I was doing a reaserch on this subject and I found this link/pages on Technet: https://social.technet.microsoft.com/Forums/en-US/785cbcc6-4f0b-4d88-b12f-2b1d89b85a44/remoteapp-default-printer-redirection-not-working-in-server-2016?forum=winserverTS
But I think is not exactly my scenario.
Had anyone of you seen/heard of this?
Additional information.
Application: Desktop Application (build in vb6 and vb.net)
Connection: RemoteApp (end-users can connect remotely to the application, located in windows server 2016).
If i didn't make myself clear, please let me know, so I can explain better!
Thank you,
Regards
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Marking this as Answer.
Thank you Andrew!
Thank you Andrew!
ASKER
I think that your recomendation would be something good that I can scalate internally to resolve this detail.
Thank you so much for your comments.
I will continue working on my research cause this seems to be something that could be related to the enviroment of Window server 2016.
I'll let you know if something new happens!
Thank you,