B
Brett Sadler
Guest
Hello,
Hopefully someone can point me in the right direction with the issues I'm
having and that I explain this in an understandable manner.
We have a TS server that we have for our Accounting (Dynamics 9) department
only. Currently, we have it setup through client registry settings so that
they have only their default printer connecting through to the RDP session.
This works fine. However, it was constantly defaulting to the client
printer, as opposed to being only just available. I realize this is by
design.
Since only one person has a local printer, under the RDP connection
properties on the Client Settings tab, I turned off the "Use connection
settings from user settings" box, left drives and printers at logon checked,
but unchecked the auto default to main client printer.
The reason I took this route is due to the client printers not having the
ability to print double sided since not all of the printer properties are
available. Two of our accounting people NEED this functionality as part of
their job. To try to get around this issue, we setup policy so they received
network printers.
Now we are having two problems:
1. The user with the client printer can't set her local printer as default
after she logs in and have it persist through so the next time she logs in it
remains the default printer
2. The double sided print settings for our other two users on the network
printer won't persist through another login, so when they make change to
double sided (duplex) printing, and then log out for the day, when they log
back in to TS server, it has reverted back to the single sided printing.
Does this look like a printer policy issue where the printers are being
re-pushed at every login, overwriting settings? Or is this an issue with the
TS client? Thank you in advance!
Hopefully someone can point me in the right direction with the issues I'm
having and that I explain this in an understandable manner.
We have a TS server that we have for our Accounting (Dynamics 9) department
only. Currently, we have it setup through client registry settings so that
they have only their default printer connecting through to the RDP session.
This works fine. However, it was constantly defaulting to the client
printer, as opposed to being only just available. I realize this is by
design.
Since only one person has a local printer, under the RDP connection
properties on the Client Settings tab, I turned off the "Use connection
settings from user settings" box, left drives and printers at logon checked,
but unchecked the auto default to main client printer.
The reason I took this route is due to the client printers not having the
ability to print double sided since not all of the printer properties are
available. Two of our accounting people NEED this functionality as part of
their job. To try to get around this issue, we setup policy so they received
network printers.
Now we are having two problems:
1. The user with the client printer can't set her local printer as default
after she logs in and have it persist through so the next time she logs in it
remains the default printer
2. The double sided print settings for our other two users on the network
printer won't persist through another login, so when they make change to
double sided (duplex) printing, and then log out for the day, when they log
back in to TS server, it has reverted back to the single sided printing.
Does this look like a printer policy issue where the printers are being
re-pushed at every login, overwriting settings? Or is this an issue with the
TS client? Thank you in advance!