Hi Jeanne,
A couple of questions:
Are you using a remote app or RDP?
Are your user ini files pointing to the master ini file? Our user ini files look like this:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[sqlca]Hostname=tsheleheMasterIniFilePath="X:\startup\tessitura_production_master.ini"
[Login]logid=tshelehe[Frame]State=MaximizedWidth=4736Height=3120X=23Y=12[TicketPrinter]Default=Benedum Center Phone Room
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
And then our master ini has the data connection string and default paths for the client files and the reports, but it does not declare the host name again. I wonder if you've got a default host name in your master ini file?
Jeanne- We've done this a few years ago. Our Patron Services Manager Terry Breedlove (tbreedlove@sfsymphony.org) would be the guy to ask about implementation.
Kara
We’re using Windows Remote Desktop Connection (all XP machines).
My user ini files look identical to yours, minus the logid line, as I don’t want a specific login to have to be tied to a machine (we’ll be having different ticket agents logging in).
And there’s no change to the master ini file.
Jeanne
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Nancy Sheleheda Sent: Tuesday, March 29, 2011 12:58 PM To: Jeanne DeVore Subject: Re: [Tessitura Technical Forum] Remote Box Office Via Terminal Services
[sqlca] Hostname=tshelehe MasterIniFilePath="X:\startup\tessitura_production_master.ini"
[Login] logid=tshelehe [Frame] State=Maximized Width=4736 Height=3120 X=23 Y=12 [TicketPrinter] Default=Benedum Center Phone Room
From: Jeanne DeVore <bounce-jeannedevore2565@tessituranetwork.com> Sent: 3/29/2011 12:45:38 PM
I'm in desperate need to speak with someone who's doing this and can help me with the setup. My understanding is to create separate .ini files for each user, reflecting a hostname that equals the username, and to refer to them in the shortcuts. And then to create locations for each user in the tx_machine_location table. I've done this, but when I go into Tessitura, using the shortcut I modified, pointing to the .ini file I modified, it still logs me into the Terminal machine and not to the new host I thought I told it to go to. My big issue is that I can't get Tessitura to see my shared printer, even though my Terminal session can see the printer just fine. When I go into Tools/Preferences there's no ticket printer available in default printers. I'm desperate, because my remote box office has to go live this evening and right now I've only got 2 of the 4 machines working correctly. Thanks! Jeanne DeVore Technology Manager Chicago Shakespeare Theater jdevore@chicagoshakes.com 312 595-5603 www.chicagoshakes.com This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
Our ticket agents aren't tied to a specific machine, so I don't think the logid has anything to do with that. Our phone room and window associates switch positions all the time.
We finally got this part sorted (who knew that Windows 2008 required the .ini file to be in the root of c:?), but still can’t get my remote Tessitura instances to speak to my shared printer. It’s a single Boca connected to one machine, shared. All the workstations see the printer, all the Remote instances see the printer. Tessitura doesn’t recognize that there’s a ticket printer connected.
If I have to take 4 Bocas to my remote location I may cry….
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Nancy Sheleheda Sent: Tuesday, March 29, 2011 3:13 PM To: Jeanne DeVore Subject: RE: [Tessitura Technical Forum] Remote Box Office Via Terminal Services
From: Jeanne DeVore <bounce-jeannedevore2565@tessituranetwork.com> Sent: 3/29/2011 1:40:32 PM
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
Hi Jeanne
We were having some weird things happening with printers in RDP sessions, until we added this setting (I think) in t_defaults:
PRINTER LIST METHOD
This is an internal setting which controls the method used to read the Window printer list. If an n_powerprinter system error is received on startup, it may help to add this setting with a value of PW. Alternately individual workstations can be controlled by adding this entry to the [Defaults] section of the local ini file: PRINTER_LIST_METHOD=PW
Although it doesn’t sound like your problem, it could be worth trying. Our problem was to do with printers “crossing” from one session to another, so it didn’t match this description either.
Ken McSwainBusiness Solutions Manager
T 02 9250 7876 F 02 9251 7821 M 0418 659 360
Sydney Opera House Bennelong Point
GPO Box 4274 Sydney NSW 2001 AUSTRALIA
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Jeanne DeVoreSent: Wednesday, 30 March 2011 07:24To: Ken McSwainSubject: RE: [Tessitura Technical Forum] Remote Box Office Via Terminal Services
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Nancy ShelehedaSent: Tuesday, March 29, 2011 3:13 PMTo: Jeanne DeVoreSubject: RE: [Tessitura Technical Forum] Remote Box Office Via Terminal Services
From: Jeanne DeVore <bounce-jeannedevore2565@tessituranetwork.com>Sent: 3/29/2011 1:40:32 PM
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Nancy ShelehedaSent: Tuesday, March 29, 2011 12:58 PMTo: Jeanne DeVoreSubject: Re: [Tessitura Technical Forum] Remote Box Office Via Terminal Services
From: Jeanne DeVore <bounce-jeannedevore2565@tessituranetwork.com>Sent: 3/29/2011 12:45:38 PM
I'm in desperate need to speak with someone who's doing this and can help me with the setup. My understanding is to create separate .ini files for each user, reflecting a hostname that equals the username, and to refer to them in the shortcuts. And then to create locations for each user in the tx_machine_location table. I've done this, but when I go into Tessitura, using the shortcut I modified, pointing to the .ini file I modified, it still logs me into the Terminal machine and not to the new host I thought I told it to go to.My big issue is that I can't get Tessitura to see my shared printer, even though my Terminal session can see the printer just fine. When I go into Tools/Preferences there's no ticket printer available in default printers.I'm desperate, because my remote box office has to go live this evening and right now I've only got 2 of the 4 machines working correctly.Thanks!Jeanne DeVoreTechnology ManagerChicago Shakespeare Theaterjdevore@chicagoshakes.com312 595-5603www.chicagoshakes.comThis message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
Please consider the environment before printing this email.=====This message is intended for the addressee(s) named and may contain confidential information.If you are not the intended recipient, please delete it and notify the sender.Views expressed in this email are those of the individual sender and are not necessarily the views of the Sydney Opera House Trust=====
We did finally get this working, and I thought I’d tell how we did it, if ever anyone runs into the same situation.
Turns out the “generic / text only” driver that the Bocas use doesn’t play well with Terminal Services 2008’s “Easy Print” functionality, which in theory is supposed to eliminate the need for additional printer drivers. Easy Print is enabled by default through Group Policies, so I had to go in and disable that. Once I did, all my laptops could speak to my printers over the network and all has gone swimmingly since.
Thanks, everyone, for your assistance and suggestions.
Jeanne DeVore Technology Manager Chicago Shakespeare Theater jdevore@chicagoshakes.com 312 595-5603 www.chicagoshakes.com