Installing ScreenConnect on CentOS 7
-
Yes, you certainly could. I would look at the Dev3 option, 2GB with Linux. We've run into a bug and getting SC support to take a gander at it. Will let you know the results soon. We suspect that it might be that CentOS 7 is too new, but don't want to rebuild until they tell us that they know what the issue might be.
-
Ended up being minor. SC has a known bug that they are addressing. As it stands, you have to do a reboot after installing the license file, then all is well. Pretty minor, but you have to know to do that.
-
I've been on ScreenConnect for a year I love it.
Mine is on a Windows Server 2012 R2 VM inside a Windows DataCenter 2012 R2 host.
I really need to get it moved to Linux. Been on my list for a while. Guess I'll spin up a new CentOS 7 install tonight and do this.
Then I get to figure out how to migrate my data!
-
@GregoryHall runs it on 2012 R2 as well. We are going to be doing some tests going between Windows and Linux, good time to learn
-
I've never looked at ScreenConnect, but did just get the bill for LogMeIn so it's time to look at other options.
Scott,
Let's assuming I buy a Dev3 box from C@C do I need something like Pertino to connect this server to all of my clients? or do the clients happily connect via the internet to the SC server? ala LMI? -
@Dashrender said:
Let's assuming I buy a Dev3 box from C@C do I need something like Pertino to connect this server to all of my clients? or do the clients happily connect via the internet to the SC server? ala LMI?
You have choices.
First is the no agent mode. Just send them to your URL and they make their own session.
Second, you can make the session for them and they get an email with a link.
Third, you can install the access agent.
-
@Dashrender The only issue with the access client is you have 100% access to that machine as long as it is on the internet. No client approval required to connect.
Obviously, I do not have everyone's passwords, so that mitigates, but it CAN be a concern depending on the client.
There are so add-ons for ScreenConnect that I have not really looked into. Also Security permissions can be VERY finely tuned.
-
@JaredBusch said:
@Dashrender The only issue with the access client is you have 100% access to that machine as long as it is on the internet. No client approval required to connect.
Obviously, I do not have everyone's passwords, so that mitigates, but it CAN be a concern depending on the client.
There are so add-ons for ScreenConnect that I have not really looked into. Also Security permissions can be VERY finely tuned.
Awesome - I have access 100% of the time with LMI so this wouldn't be any different from that. But the additional abilities for other users who I don't have the agent deployed to sound great.
Thanks.
-
@Dashrender said:
I've never looked at ScreenConnect, but did just get the bill for LogMeIn so it's time to look at other options.
Scott,
Let's assuming I buy a Dev3 box from C@C do I need something like Pertino to connect this server to all of my clients? or do the clients happily connect via the internet to the SC server? ala LMI?ScreenConnect is like LMI, no need for a separate VPN.
-
@JaredBusch
When you mentioned putting SC on CentOS - are you thinking Cloud@Cost? -
@g.jacobse not right now, but only because I have my own infrastructure collocated in a datacenter.
-
@g.jacobse said:
@JaredBusch
When you mentioned putting SC on CentOS - are you thinking Cloud@Cost?My plan is to do this next week.
-
Got to love a one line install!
-
@Aaron-Studer always a nice feature.
-
I love screenconnect, used it for 3-4 years for simple remote support at my last company that offered "remote support" to the public.
Have now implemented it here now instead of Teamviewer.
