Here is what I'm dealing with:
Tom has printer-A installed on his local machine. Tom terminal services into a core style 2003 server. There is a logon script that adds a networked printer-B. All is well and Tom can print to both printers.
Tom then executes a batch file that does a runas administrator for Program-A. Everything inside program-A works except when he goes to print, he only sees "Printer-A from session1" but can't print to it.
(also, tom logs into the local pc as labuser, and then logs
in as Tom to the ts)
The program has to be ran by the domain administrator account, no way around that, it's designed to be like that (silly i know)
any ideas?
Tom has printer-A installed on his local machine. Tom terminal services into a core style 2003 server. There is a logon script that adds a networked printer-B. All is well and Tom can print to both printers.
Tom then executes a batch file that does a runas administrator for Program-A. Everything inside program-A works except when he goes to print, he only sees "Printer-A from session1" but can't print to it.
(also, tom logs into the local pc as labuser, and then logs
in as Tom to the ts)
The program has to be ran by the domain administrator account, no way around that, it's designed to be like that (silly i know)
any ideas?