So I did my research and it looks like i will need to implement a vb script to fix the ini file so that each connection via RDP has a unique hostname. The problem is how do I update the tx machine location at the same time? I have 400 users who work remotely and locally. I can't imagine having to sit here and manually create TX locations for each user. Thanks
Hi John
In our terminal services environment we don't have the host name specified and we only have to add the server name to TX_MACHINE_LOCATION. What we do is copy the Tessitura_Local.ini file to each users profile so when you setup the Tessitura short cut it points to that location using the %username% windows short cut.
So the target is set to T:\Startup\Tessitura_Start.bat "C:\users\%username%\tessitura_local.ini
Hope that helps and if you need any more information let me know.
Thanks
Nick
Hi Nick, thanks for your input. Do you have the usernames in the TX_ machine location or just terminal server name?
From what I understand having just the terminal server name doesn't really because Tessitura will see multiple connections from 1 location instead of many unique locations.
We haven't done this so just an idea. You could put an "after insert" trigger on the TX_Machine table to update 'location' to 1 where location is null.
It would mean anyone that attempted to connect would get a failure first time, then would be allowed to login after that (possibly a security issue?)