Your comments

Just by renaming the machine from the GUI. I thought this just worked - perhaps I'm wrong. I'd need to test to be sure.

In fairness, SC deals with a machine being renamed OK - and fairly quickly.  Reinstalls of the OS / SC aren't deduplicated though. This should probably be a controllable option, which defaults to deduplicating but can be set to still operate the old way. 

Max, I wish I had a suggestion for HA, but I don't have anything in my toolbox that I'd trust. Don't quote me on this - but I think I've seen it written that it's possible to change SC to another DB engine like PostgreSQL, but it's not supported. As you want HA, I'd assume you'll be wanting to stay within support from CW. 

I also had a database die because I tried to export the auditing reports.  Dead, server gone, toasted.  

Insert Coin To Start Game.   That server was allowing our support desk to service our clients. That was a fun couple of days - NOT!  As I recall, support's response was to tell us to start again with a fresh install and not be stupid enough to try and export the auditing logs again. 

I'm looking forward to hearing from Mike how querying the DB causing complete loss of the DB is not a DB engine issue.  There seems to be a disconnect between how he thinks the DB engine behaves and what you, we, and SC support have seen in real life. 

For the record - I'm not in favour of MS SQL due to license / limitations, and MySQL needs careful backup / restore handling due to lack of VSS support (as we found out on our LabTech DB) though I expect that is true of all / most of the open source options. 

Mike - I have to disagree. Extended auditing was operationally useless for us, and support have told us the reason for this is excessive SQLite DB size. When we restarted the server, it took over an hour for SC to become usable and even then it was slow for three more hours. IMO SQLite is not suited to anything like 200GB.  It's suitable for more like 200MB. Regardless of the maximum size listed on - that doesn't mean it's a good idea to use it at that scale.  The lack of caching being one obvious problem (relying on OS FS cache is not as performant as a DB engine taking nGB of RAM away from the OS and dedicating it to the DB table cache).  Another is the single writer limitation.   

While certainly SQLite makes the system easy to deploy and work with, and while you may say you don't have issues running it at scale it's very clear that many customers do have issues running it at scale (or at least think they do).  If you're SURE all these issues aren't related to the DB engine, perhaps you'd like to explain what is causing them and how to resolve them, because support have told us it's a DB scaling issue?

As a workaround  - Ask them if they'll accept you removing its entry from Add Remove Programs so "users" don't see it as installed and try to remove it. Nuke the registry to remove the entry for it. 

For the record - Here's a repost of how this can be set up, and some more info / code.

However this is not (as I understand it) currently "supported" by ConnectWise - though that will be discussed. 
Credit to Scott Linak @ CW for jumping on this when I asked, and the above repo. :-) 

I asked, and apparently this will now be discussed in ScreenConnect (CWC) support meeting tomorrow. The case for this is understood. 

For our use case, we'd nee a GUI option to opt out of this for a connection to a session.  For example tech is starting a process in user space on a server that will run for 14 hours, and tech needs to disconnect and reconnect tomorrow to check on it. If there's no option to opt out of this when they disconnect it would log them off and kill their task. This would make this useless to us as we couldn't enable it. 

It sounds more like you need a better RMM than InTune.  If you want to script this, it should be possible to use a script to make API calls to identify machines and move them to a group (or whatever you want to do about it).

Guys - we know this works well because we know CW use it themselves.  Please can you just make this supported in the main release. We know not all customers are going to be able to use it but many will.