Terminal Server Easy Print - printing half size

[BigRBTrout]

I've got one terminal server S2022.
The few users connect via RDP from Win 10 workstations.
I've got an app that's written in VB and old that several users access. It's old enough that it doesn't work on some Win 10/11 machines. Not sure how I got it to work on S2022.
We're using Easy Print.
When printing through the app in RDP, it prints 4.25" X 11". No matter how the printer is set up locally.
I can't remove Easy Print.

I'm not sure how to solve this one.

 

[COLGeek]

To be clear, please link to "Easy Print". There are a couple things called this.

 

[BigRBTrout]

Microsoft remote desktop easy print.

How to setup Remote Desktop Easy Print setting in Windows 2019. - Microsoft Q&A

In Windows 2016 our client printers are redirected without issues .All local printers are redirected and the Remote Desktop Easy Print is taken as default driver. The client is used to log into windows 2019 terminal server but the printers are not…

learn.microsoft.com

 

[Ralston18]

PCL?

Make and model printer?

My thought is that the VB app may be generating control codes that the printer is directly responding to or (oppositely) ignoring and perhaps defaulting to the 4.25"x11" page size.

https://www.pclviewer.com/resources/reference/

Do you remember doing anything involving VB or PCL when the problem was fixed before? S2022?

 

[BigRBTrout]

Any of my printers. Kyocera or HP doesn't matter.
TaskAlfa 5003
HP M4001

I didn't do anything to VB or PCL. The program is written in VB but made into an .exe and I don't have access to any of the programming.

 

[Ralston18]

Do I understand correctly that the reduction of printing size to 4.25" x 11.00" occurs on multiple makes and models of printers?

And the correct print size should be 8.5" x 11.00" ?

Is it possible to set up/connect a printer directly to one of the systems hosting that VB app?

Objective being to determine if the printed output is the correct size.

And correct on some systems but not others....

Then discover some difference(s) that could be the culprit.

= = = =

Anyway, I did some"research" (aka Google") and found the following link regarding printmanagement.msc

https://www.techtarget.com/searchen...ws-11-Print-Management-can-fix-printer-issues

Also of interest:

https://theitbros.com/remote-desktop-easy-print/

Overall, I started with "remote printer redirection" and then attempted to narrow or otherwise filter down the responses.

However, not sure about all of the details involved and most likely you will be able to revise the search criteria to be more applicable to your environment and the printing problem.

Could be possible that you find something that triggers your memory regarding the previous fix via S2022.

 

[BigRBTrout]

Do I understand correctly that the reduction of printing size to 4.25" x 11.00" occurs on multiple makes and models of printers? Yup


And the correct print size should be 8.5" x 11.00" ? Yup

Is it possible to set up/connect a printer directly to one of the systems hosting that VB app? Done this already. Makes no difference.

The only difference I've noticed is that logged in as admin, it prints perfectly. I can't make all users admins.

 

[Ralston18]

Regarding:

"The only difference I've noticed is that logged in as admin, it prints perfectly. I can't make all users admins."

That is really interesting....

Agree: not everyone can be or should be "admins".

But the log in "level" certainly suggests some issue with permissions.

Try to discover as much as you can about an admin user who can print perfectly versus a user who can not print perfectly.

Delve into GPO.

One way may be via Powershell: do you or anyone else have any knowledge of Powershell?

For example:

https://www.itechtics.com/gpo-report-powershell/

Objective being to discover some difference that allows admins to print perfectly while non-admins cannot.

Without any compromising of protective admin rights.

 

[BigRBTrout]

I set the 2 users that have to run the app as admins. The good thing is they'll never know or know what to do with it. It's a band aid until I (or we) can figure this out.
Good suggestion on Powershell. I've been using it for years, not extensively, but enough to be scary. 😉

I'll see what I can find out......

Happy Thanksgiving.