I'm pretty sure I've seen this topic touched upon before, but I am curious if anyone has come up with anything new...
When logging onto a Terminal Server session (in this case via Remote App) to run Tessitura, the user’s local printer is re-directed to the TS sessions with a session “tag” added to the name of the printer e.g. “Tessitura BOCA (redirected 2)”. Given the tag changes for each TS session, trying to set the default printer in the INI file is a bit difficult. It would be nice to find a way other than the user setting their printer preferences each time they log in.
Any creative solutions out there?
Kris
Hi Kris,
Our whole ticket office uses terminal server logins but they each have their own local .ini file as the target for their tessitura shortcut.We don't seem to have the problem you are talking about.Is this possibly the solution to your printer problem?
target example:
T:\Startup\Tessitura_Start.bat "C:\Documents and Settings\rrowell\Application Data\Tessitura\tessitura_live.ini
Hi Ryan,
We use user specific .ini files as well. Our problem seems to be related to printer redirection. Since Tess is used via Terminal Services in a number of different box offices, the BOCA printers are attached to the local workstations. The user prints to that local ticket printer via terminal server printer re-direction. The problem is the name of the windows printer changes (“session xx” is added to the end) whenever the user logs into the Terminal Server. Since the name of the printer changes, it no longer matches up to the one listed in the .ini file...
-Kris
We don't use TS here but why don't you just share the printer on the local workstation and then use that share in Terminal Server to print back to it. That way the name would stay consistent.
-Rich
That could be a good solution, though the user might still need to re-select the printer when moving from workstation to workstation (since the Terminal Server wouldn't be able to have two shared print queues with the same name).
The only other idea I had was to try to do this through a login script that would grab the name of the re-directed BOCA printer in the TS session via WMI and then right that name to the user's ini file...