Hey frands.
Has anyone explored using Windows Virtual Desktop as a remote and/or disaster recovery solution? If so, have you found it successful with a self-hosted instance of Tessitura? I would love to hear from you! Feel free to reply to this post or reach out to me directly at enash@2st.com.
Thanks so much!
Thanks for the quick replies, Scott Trapani and Mike Tiernan! How do your VDI instances handle the Tessitura .ini file for each users' Tessitura defaults? From my understanding of the Windows VDI, each session could live on any one of multiple host servers depending on the size of the environment. The users' profile is stored in terms of their default desktop views, but I'm curious how the Tessitura defaults would save to that user's profile. We're currently setup with a GPO that saves a local instance of Tessitura to the user's personal computer. If the user's personal computer keeps changing (in terms of host VMs), how can I get the local .ini file to stick to each individual user's VDI instance?
Additional question regarding cloud hosting - How/where are your file server(s) hosted? We're looking at Azure File Storage vs. Sharepoint, but are concerned about some of Marketing's massive files and egress traffic to load those files, as well as general performance speeds.
Thoughts?
P.S. Larry Becker and Eugene Karyakin, you might find this thread useful as well. Any updates you can provide on your end with Windows VDI?
For our call center and BO staff we use persistent desktops so they get the same machine everytime. WHen it comes to our Citrix servers themselves (multi sessions) we have their Tess shortcut point to s specific tessitura.ini which has their settings saved. We don't have lots that require this setup lucky for us.