Windows 2012 RDP Printer Issue
HELLO ALL...
We're having a major issue with RDP (Terminal Services) on a Windows 2012 Server. We have *not* previously had such problem(s) with Windows 2008 R2 (nor with any earlier Windows Server O/S Editions). I'll try to explain.
The issue is that on Terminal Services 2012, the RE-DIRECTED PRINTERS PROPERTIES are NOT being pulled from the local workstation. We cannot change those properties of the redirected printers ON Terminal Server...and the options are all GREYED OUT. Easy Print is, apparently, disabled by design here.
Because this is part of a Point of Sale WAN (Wide Area Network), we *MUST* be able to either (a) administer such printer's properties on the Terminal Server box, or (b) have ALL the properties' "Configuration Settings" honored by the Terminal Server...when the workstation (and therefore, the printer) is authenticated to the Terminal Server. Things like "cut codes" and "cash drawer popping" and so forth, as set in stone here (on the local workstation)...and all hell breaks loose otherwise.
We appreciate any assistance/guidance/direct
We're having a major issue with RDP (Terminal Services) on a Windows 2012 Server. We have *not* previously had such problem(s) with Windows 2008 R2 (nor with any earlier Windows Server O/S Editions). I'll try to explain.
The issue is that on Terminal Services 2012, the RE-DIRECTED PRINTERS PROPERTIES are NOT being pulled from the local workstation. We cannot change those properties of the redirected printers ON Terminal Server...and the options are all GREYED OUT. Easy Print is, apparently, disabled by design here.
Because this is part of a Point of Sale WAN (Wide Area Network), we *MUST* be able to either (a) administer such printer's properties on the Terminal Server box, or (b) have ALL the properties' "Configuration Settings" honored by the Terminal Server...when the workstation (and therefore, the printer) is authenticated to the Terminal Server. Things like "cut codes" and "cash drawer popping" and so forth, as set in stone here (on the local workstation)...and all hell breaks loose otherwise.
We appreciate any assistance/guidance/direct
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
hdhondt
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.