• Replies 7 replies
  • Subscribers 336 subscribers
  • Views 56 views
  • Users 0 members are here
Related

Remote Box Office Via Terminal Services

Jeanne DeVore
$organization
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
Parents
  • $organization

    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

     

Reply
  • $organization

    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

     

Children
No Data