Has anybody found any drawbacks to using AD integration?
Ha! No news is good news, I guess.
We're not there yet, but one issue is that any user must be set to AD or Tessitura authentication: you can't use both. I _believe_ TNEW has a workaround, but I think there may be some issues when it comes to other utilities that are accessed via browsers.
We are testing V15 right now.
I've been using AD authentication since December.
I like it.
A user must have a default login group in Security. (Not clear that users can change their default Login Group themselves.)
That is the group that the Tessitura Client Logs you in as, and TNew Logs you in as.
So if you need Tnew Admin Access, your default login group will have to have this Access in order for you to get into the TNew Admin Screens
If you change Groups a lot this may not be an ideal situation for you. However, if you are almost always in a single Login Group it's nice.
If you have to change your login group you can go to the File Menu and use the Relogin option.
--Tom
For what it's worth, the rollout went pretty well! We have two users that have had problems with the integration, but another 40 or so for whom it has been seamless. I recommend you roll out in your test environment and go through your users and see what happens before going live. You will take care of most of your headaches that way first, stuff like .net being up to date and all that.
We upgraded two weeks ago to version 15. We have several users who use more than ONE security group and they still found it's easier to get logged into the default security group and then ReLogin into a different security group. TNEW and On-the-go require a new login (RAMP credentials in our case). We'all are liking it.