Hi,
We are about to roll out windows 7 and was wondering how does Tessitura capture machine name in TX_machine_location table?
The reason I want to understand this process is to we want user to be able to run application right after its installed and shouldn't have to see "This machine does not have assigned location".
The way I want to approach this is to have a SQL trigger to run stored procedure to update TX_machine_location avoiding to display that annoying message to user.
Has anyone worked on this or has any other way to achieve what we want to?
Many Thanks,
--Monic
Hi Monic
Why not just add all the new machine names to the table in advance? Easy enough to script that, or just add them manually if there aren’t that many. Certainly much easier than trying to do it with a trigger.
Tess won’t automatically add the machine name into the table until someone tries to connect for the first time.
________________________________Ken McSwain
Systems and Technology Manager
Australian Chamber Orchestra
ken.mcswain@aco.com.au
Ph +61 2 8274 3833 :: Mob +61 418 659 360 :: Fax +61 2 8274 3801
PO Box R21, Royal Exchange NSW 1225
2 East Circular Quay, Sydney NSW 2000
From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Monic VermaSent: Friday, 23 September 2011 09:54To: Ken McSwainSubject: [Tessitura Ticketing Forum] Capturing machine name
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing 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!
I'm with Ken. It's much easier. Whenever we roll out new PCs (or newly upgraded ones), we just enter the machine names into the table before we distribute the computers to staff. If you've got hundreds of computers I recommend scripting it, presuming you know what the machine names are. If it's not so many, you can just enter it directly in the system tables module.
I built a report that supervisors have access to that they can run anytime that one of the users gets the error. All that the report does is run the following query.
UPDATE TX_MACHINE_LOCATION
SET location = 1 WHERE location IS null
Once you get the error, Tessitura put the name in the table already and all you need to do is set the location.
Marty Jones
Director of Information Services
Omaha Performing Arts 1200 Douglas Street
Omaha, Nebraska 68102
P 402.661.8469
Marty.Jones@omahaperformingarts.org
www.omahaperformingarts.org
For tickets, call Ticket Omaha at 402.345.0606
Hi Beth,
Thank you for your valuable suggestion.
I think we will get machine names forehand and that will give us time to import it to Tessitura and then script to assign machine location would do the rest.
Hope all goes smoothly.
Thanks again,
From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Beth HawrylukSent: Saturday, 24 September 2011 2:32 AMTo: Monic VermaSubject: Re: [Tessitura Ticketing Forum] Capturing machine name
We have been going through this process over the last few weeks. Luckily, we've done it as a slow rollout so it hasn't been too bad. Basically, our IT guy sets up the computer and one of the first things he does is opens the Tess application so it gets the location not assigned error. Then he either calls or emails me the computer number(s) and I assign the location.... hopefully before the other employee needs in there! It's not a perfect solution (or what you asked for) but it's worked for us. I'm pretty sure that you can manually enter the computer names into the system table. If that interests you. I haven't tried it myself so I'm not sure if it works as nicely as I imagine it will.
From: Monic Verma <bounce-monicverma6276@tessituranetwork.com>Sent: 9/22/2011 6:51:45 PM
I've just imported all our PC names into Tessitura with the addition of adding the appropriate location already applied as part of the import.
Oh - the joy of importing............!