I have clients that use the remote printing feature of ScreenConnect daily, but after updating to v19.0, remote printing now needs to be toggled manually each time the host connects. I would like it if once remote printing is enabled then it stays active even after the host disconnects, unless disabled manually.
We have come to rely on that being on automatically. We have a number of clients that are frustrated now because they have to remember to turn printing on each time. It would be nice to be able to choose what state the session should start in.
please add print lock function what is existed already on local's printers properties but via remote printing session is not accessible
when you use printer Lanier mp 4054 pcl 6 locally "Lock print" function works fine, but when you do 'screenconnect remote printing', you see your printer, you can print, but that function gets lost, only basic printer settings are here. It created chaos - all print jobs got messed up between office users, clients delayed, what is not good for business, plus, actually it's a big MINUS, privacy gets broken. Please fix it A.S.A.P.
If we use LogMeIn service - all printer's options and setting are translated, so there is no difference between locally and/or remotely printed job. But with you guys, it doesn't work and you positioning your product as the best.
See below, "lock print" accessible locally:
And see below, it's gets lost if the same printer connected for remote print (see how much you got lost!):
and yes, users very upset that after every reconnect they have to turn on again "Allow remote printing" again and again.
Definitely would like to have an option to keep it automatically on have some sort of plugin to have it activated on certain users only
please add print lock function what is existed already on local's printers properties but via remote printing session is not accessible
when you use printer Lanier mp 4054 pcl 6 locally "Lock print" function works fine, but when you do 'screenconnect remote printing', you see your printer, you can print, but that function gets lost, only basic printer settings are here. It created chaos - all print jobs got messed up between office users, clients delayed, what is not good for business, plus, actually it's a big MINUS, privacy gets broken. Please fix it A.S.A.P.
If we use LogMeIn service - all printer's options and setting are translated, so there is no difference between locally and/or remotely printed job. But with you guys, it doesn't work and you positioning your product as the best.
See below, "lock print" accessible locally:
And see below, it's gets lost if the same printer connected for remote print (see how much you got lost!):
and yes, users very upset that after every reconnect they have to turn on again "Allow remote printing" again and again.
in your second photo . if you goto the advanced tab . then change the driver from pcl5 to the driver of your printer in the drop down . then click ok . you will see same as your first photo .
but for some reason screen connect does not remember and you have to do it each time you reconnect to machine ..
pain .
Agreed, we need a way to keep remote printing active all the time for certain users.
Agreed, we need a way to keep remote printing active all the time for certain users.
There is a setting for this already depending what version your server is on in the Advanced Configuration Editor extension. Once you install it you go to Admin > Advanced > Web Configuration > Settings. You will see a checkbox to have remote printing default to always being on.
There is a setting for this already depending what version your server is on in the Advanced Configuration Editor extension. Once you install it you go to Admin > Advanced > Web Configuration > Settings. You will see a checkbox to have remote printing default to always being on.
Jake, we need to be able to activate this only for certain users. Your recommendation turns it on for all users all the time.
Perhaps there could be a role assigned to certain users that would automatically enable remote printing for only the users with that role applied.
This is also a change that I would really like to see come back. This is how it behaved in the old version, at least an option to change the behavior would be sufficient.