This one’s a real pain because of how little information is out there. For what I describe below, I’m basing it on an installation of a Hosted Screenconect (Connectwise Control) version 20.9.799.7542 on a domain-joined Windows Server 2016. Your mileage may vary, but the fundamentals of this issue should hold across servers and platforms.
ScreenConnect, a remote access tool, allows you to host a server that enables remote support of client computers. Many of the best features of this software relate to giving you control over deployment and hosting. This would seem like the perfect fit for Amazon’s cloud server infrastructure. If what you wanted to do is run it on a lower-cost AMI (Amazon Machine Image) free-tier micro instance, here’s how to do that.
All users running Logmein Free options on mobile and desktop tools will receive a notification that they’ll have to upgrade to the “Pro” version or lose access within 7 days. Naturally, Logmein puts a spin on this, mentioning that they’ve offered the free product for 10 years, but many users are angry.
If you’re a remote control user, you’re likely familiar with the two-step process of opening a port, creating a gateway server and connecting. This keeps your need to open the network to a minimum while allowing access to all systems internally. Why don’t we have an open source equivalent to this kind of tool?
This week I received the email that informed me that Logmein would no longer allow access to more than 10 computers, so I decided to look at ways to get around this restriction.