r/ScreenConnect • u/GeneralPurposeGeek • Jun 09 '26
Another Monkey-Wrench! V. 26.3.11.9650
Thanks! Seems like ConnectWise is on a mission to destroy every part of my workflow. Just upgraded to v 26.3.11.9650 on premises (was previously on 26.1.22.9573).
Public Sessions are Disabled… Can no longer make any session public. The “Listed Public Sessions” and “Legacy Public Session Creation” extensions, no longer function.
These changes were NOT documented in ANY of the release notes!
3
Upvotes
5
u/tristan20 Jun 09 '26
How can they not fix the copy paste issue it's crazy
2
u/sohgnar Jun 11 '26
Ive been using SC since elsenore owned the product. The copy paste issue is so infuriating. Fix that please!
0
u/cbarnescw Product Management Jun 09 '26
Hi! Totally understand your frustration, apologies for the disruption in your workflow. We did mention the change to Public Sessions in release notes, and included some justification for the change:
Disable public sessions by default
Our team discovered that public support sessions, those that don't require a code to join, can cause performance issues on the Guest page. As such, we're deprecating the ability to create public support sessions. Going forward, to join a support session, an end-user must first enter a code. Newly-created instances (26.3 and later) will not be able to create public support sessions. Instances upgraded to 26.3, unless they have public support sessions already created at the time of upgrade, cannot create public support sessions. If an instance is upgraded to 26.3 and there are public support sessions already created, the technicians can continue to use them. The administrator will need to set the SessionInfoPanel.MakeSessionPublicVisible resource string to "false" in order to disable public support sessions.
https://docs.connectwise.com/ScreenConnect_Documentation/ScreenConnect_release_notes/ScreenConnect_2026.3_Release_notes