screenconnect migrating from Windows to CentOS7
-
I am about to setup a CentOS 7 to install sc and migrate our existing windows setup to this. Setup will be based on the instructions from @scottalanmiller https://mangolassi.it/topic/3997/installing-screenconnect-on-centos-7/20
Hope there are no issues with CentOS7 on SC as of now
Along with that, planning to enable 2FA for all instances and the cloud login as well
-
We moved to Fedora 27. Newer components, slightly better performance.
-
Unless there are no serious performance issues, i think i will go ahead with centos for now
-
@ambarishrh said in screenconnect migrating from Windows to CentOS7:
Unless there are no serious performance issues, i think i will go ahead with centos for now
No serious issues. But zero benefits. Fedora is better in general, and better specifically.
-
I was able to setup SC on linux and migrate all settings, clients etc to the new server. Facing issues with the mail settings. Using O365, the same works on windows server, but on Linux, when i try to send test mail, i get the error "Message could not be sent."
Telnet to smtp.office365.com on port 587 gets connected. Not sure what could be causing this issue. Anyone know how to check the logs to get more info?
-
@ambarishrh said in screenconnect migrating from Windows to CentOS7:
I was able to setup SC on linux and migrate all settings, clients etc to the new server. Facing issues with the mail settings. Using O365, the same works on windows server, but on Linux, when i try to send test mail, i get the error "Message could not be sent."
Telnet to smtp.office365.com on port 587 gets connected. Not sure what could be causing this issue. Anyone know how to check the logs to get more info?
Did you make an IP based connector in O365 for this?
-
@jaredbusch said in screenconnect migrating from Windows to CentOS7:
@ambarishrh said in screenconnect migrating from Windows to CentOS7:
I was able to setup SC on linux and migrate all settings, clients etc to the new server. Facing issues with the mail settings. Using O365, the same works on windows server, but on Linux, when i try to send test mail, i get the error "Message could not be sent."
Telnet to smtp.office365.com on port 587 gets connected. Not sure what could be causing this issue. Anyone know how to check the logs to get more info?
Did you make an IP based connector in O365 for this?
Not really, just used an account with credentials. As mentioned, the same works fine on the windows installation without any problems
-
@ambarishrh said in screenconnect migrating from Windows to CentOS7:
@jaredbusch said in screenconnect migrating from Windows to CentOS7:
@ambarishrh said in screenconnect migrating from Windows to CentOS7:
I was able to setup SC on linux and migrate all settings, clients etc to the new server. Facing issues with the mail settings. Using O365, the same works on windows server, but on Linux, when i try to send test mail, i get the error "Message could not be sent."
Telnet to smtp.office365.com on port 587 gets connected. Not sure what could be causing this issue. Anyone know how to check the logs to get more info?
Did you make an IP based connector in O365 for this?
Not really, just used an account with credentials. As mentioned, the same works fine on the windows installation without any problems
When I click send test mail I could see the firewall logs the traffic but no emails on my inbox and the message not sent shows up on sc.
-
@ambarishrh said in screenconnect migrating from Windows to CentOS7:
@ambarishrh said in screenconnect migrating from Windows to CentOS7:
@jaredbusch said in screenconnect migrating from Windows to CentOS7:
@ambarishrh said in screenconnect migrating from Windows to CentOS7:
I was able to setup SC on linux and migrate all settings, clients etc to the new server. Facing issues with the mail settings. Using O365, the same works on windows server, but on Linux, when i try to send test mail, i get the error "Message could not be sent."
Telnet to smtp.office365.com on port 587 gets connected. Not sure what could be causing this issue. Anyone know how to check the logs to get more info?
Did you make an IP based connector in O365 for this?
Not really, just used an account with credentials. As mentioned, the same works fine on the windows installation without any problems
When I click send test mail I could see the firewall logs the traffic but no emails on my inbox and the message not sent shows up on sc.
I do not send directly to O365. I send to a postfix relay. But I could send it direct because I have a connector made.
Only reason I do not send direct is that I block all outbound port 25 at the firewall except for the postfix relay IP.
-
During SC support sessions they gave me some information:
-
There is an issue with the certificates in the Mono server if you are using Gmail, suspecting the same for O365. Suggested fix for this is to upgrade to 6.5 but on the site that is not a stable release.
-
SC normally recommend using Windows for the server if you will have 10-15+ active sessions for performance reasons
Should i reconsider moving to Linux server, when the product owner recommends to stay with Windows? We do have 10-15+ sessions usually.
-
-
@ambarishrh said in screenconnect migrating from Windows to CentOS7:
Should i reconsider moving to Linux server, when the product owner recommends to stay with Windows? We do have 10-15+ sessions usually.
You have to look at the big picture. Windows might be "faster" than Linux for .NET right now, but you already chose CentOS instead of Fedora which is also recommended for better performance as it has newer libraries, like for Mono performance. So if this was of concern, moving to Fedora would have been a sure thing already. Next is cost, even if Windows is faster, is it faster "for the same money?" My guess is "not even close".
We've not seen performance issues in a long time. Current SC on current Fedora has been exceptionally good.
-
@ambarishrh said in screenconnect migrating from Windows to CentOS7:
Should i reconsider moving to Linux server, when the product owner recommends to stay with Windows?
Should also note, the vendor chose to use .NET for their server and much of their software is utter garbage; their reliability in decision making around these things is already highly suspect.
