is anyone using Tessitura Sync for file distribution? I'm having such a bad time with it on terminal server. It does not run at all if i am logged in as a user(it will run if i log in as an admin). I keep getting "Access Denied" each time I click on the icon to start Tessitura. The same icon and path works fine on my regular systems (XP, WIN7, and WIN 10) as a user.
I am using TessituraSync for file distribution and installation, but I treat our terminal server as a special case. I only have the users use the Sync shortcut to launch tessitura when I do not have direct control over their filesystem. In the case of terminal services, when I can change the Tessitura application directory at will, I make that part of my client upgrade workflow when doing Tessitura updates.
For this, I actually launch TessituraSync from the tessitura share, but all it's doing could be accomplished by a simple batch script--just a file compare and sync. Then the Terminal Services users have shortcuts on their desktops for the local client executable and their personal INI file.
That's sort of what I am doing right now. The actual tessitura executable is on the local C drive. The ini is in their roaming profile. The tessync shortcut runs from the tessitura distribution server and does the file check/update if needed. Then it starts the local client. But the launcher itself keeps giving me an access denied error.
Same issue here. I gave up using Tessitura Sync on our terminal servers long ago. Now I just copy files manually off hours when I know no one is using it.
Fortunately, that's not a big deal and is rarely necessary (save a hotfix or upgrade situation). If we're putting out a new report, I can just copy over our local pbl anytime. But we copy the pbl manually.