ScreenConnect Control On-Premises vs Cloud for Legacy Partners

Software & Web Applications
1

As a longtime ScreenConnect Legacy Partner (customer), this past week has consumed my time and workload devotion to our on-premises deployment for access to our local systems. With the new code-signing certificate requirement for the On-Premises community and setting up Azure Key Vault, it’s been a hurdle to determine if migrating to the cloud offering is the right path moving forward. We use SC Control for unattended access to our systems and for various maintenance tasks. I am not using the Premium Technician license; however, I can see some great benefits to that tier.

We are a nonprofit that operates our systems on-premises and continues to invest in the infrastructure that supports the tech needs of our campus.

Today, I am teetering on the fence of going to Cloud as long as we can continue to benefit from the Legacy Partner discounts. Talking to sales this week has been non-existent, given the volume of responses to the news of code-signing and temporary cloud migration.

My question for Tom and everyone here is:
What will I lose as a Legacy On-Premises partner going to their cloud product?

I want to be a good steward of the organization’s donor giving as well as my time over the management of these systems. I have read the article here, and I will say that I know we can still use SC Control locally/internally when the internet is down (which is practically rare on a Dedicated Enterprise service with SLA) given we have a loopback configured on the firewall.
The certificates for my webserver host and the new code-signing come out to $613 with discounts. I have no clue what Azure Key Vault Premium and the transactions would come out to since we install the SC client on roughly 50 systems. If anyone wants to share how that works, please do. I can’t get answers from ConnectWise support. I would leverage the Microsoft Azure Grant afforded to nonprofits if I go the route of staying On-Premises and performing our own code-signing.

I am new to the LTS Forums so I look forward to hearing from everyone, and Tom, too! (Been following for 5 years or so - love the channel and tips!) - Thanks!

2

We still use the on prem version and are doing the code signing so I am not really sure what would be lost other than what that article references

On-prem infrastructure offers **complete control and data sovereignty

And of course subject to their financial whims of raising the price whenever they see an opportunity to do so.

4

We’re also a nonprofit running On-Prem and recently had to dive into the code-signing changes. Biggest trade-off going Cloud is losing full control over infrastructure and data but you gain simplicity, especially with updates and certs. If your Legacy Partner pricing carries over (sales confirmed it for us), it’s not a bad move if your internet is reliable. That said, we’re sticking with On-Prem for now and using Azure Key Vault standard to handle code-signing automation. The Microsoft grant definitely helps. Here’s a helpful link on Azure Key Vault if you’re going that route: https://learn.microsoft.com/en-us/azure/key-vault/general/overview. I hope it helps!