Hello Kirsten,

Unfortunately no, creating a support session with the default name of the session the same as the join code is not what i'm referring to.  All that did was create a bunch of support sessions, still all named "Untitled Session" with a join code of "Untitled Session". So I still end up with duplicate session names and less secure join codes (all the same).

Currently today, we have random 6 digit join numerical codes when creating new support / meeting sessions and I want to keep it that way.  What would suffice, is if I could either:

I would LOVE to see more customizable Database Maintenance Plan Actions (and schedule options) including more variables similar to what session groups have.  For example, "Support: Delete Host and Guest connections where session name = "Untitled Session" and no host (and or guest) activity for xx minutes/hours/days.  This would be especially important after the version 6.3 was released.  I'm now having to manually delete 20+ support sessions a day named "Untitled Session" because employees aren't scrolling down past the legit existing support sessions to delete them.

I agree,  I can't disable TLS 1.0 and 1.1 on our instance until these items are fixed. ETA?

Hmm, I updated to version 6.2.12963.6312 and I'm still not seeing those options.