I just installed the 25.4.16 screenconnect for On-Premise. I was previously on 25.2... I just noticed that the connecting user gets a download of a ZIP file instead of an EXE file when Joining with a code. Is that a new intended change? I can't find it in the release notes. Can we change it?
Installed v25.4.25.9314 on prem which reports incorrectly as 25.4.25.9313
Main issue is no reinstall\upgrades as Webroot has flagged it as infected
Infection List:
SCREENCONNECT.CLIENT.EXE, W32.Malware.Gen, %programfiles(x86)%\screenconnect\bin\
SCREENCONNECT.CLIENTSETUP.EXE, W32.Malware.Gen, %programfiles(x86)%\screenconnect\bin\
Did you obtain a code signing cert and set it up in the new code signing extension? The new on-prem version is no longer signed so that would one reason it would get flagged.
Did you obtain a code signing cert and set it up in the new code signing extension? The new on-prem version is no longer signed so that would one reason it would get flagged.
That would be a no
I though the real changes were happening on Monday
Maybe a warning needed or did I miss it
We ended up spinning up a rustdesk server. There's some features I'll miss but at least it's functional. SC has been completely broken and every "patch" has just made things worse.
Migrated to the the cloud trial. That went smoothly.
No ability to customize backgrounds, banner or anything that brands our instance as far as I can see.
Chat support sitting at 99+ so getting any answers basically not available currently - not suprising since this is deadline day.
The entire experience has been frustrating beyond belief - entirely disrupted our ability to support clients and wasted countless hours - days actually resolving alternate solutions.
We've basically decided to move to Zoho for the interim and maybe forever. Months left on our current subscription with SC. In my view SC should provide the cloud until the current on-prem licence expires as a bare minimum to retain clients who are undoubtedly just as angry as we are. Limiting to a 14 day trial and then asking for payment beyond that would be adding insult to injury after inflicting this pain on long term clients.
Nightmare. And a loss of a family weekend. Been on this since Friday evening. Cannot any support , Configure azure cert is just a spinning save circle. lack of sleep and patience's on top of spending $1k for a 3 year code signing cert. Good for Screenconnect to be in a position to make this an opportunity to sell us a cloud service that we really did not want to use. Amazingly expensive experience . I have lost faith in SC.
SC should extend at least 1 year to the cloud as compensation for this fiasco. Yep - days of wasted time, Cost of code signing cert. Maybe they don't have many on-prem users. Regardless we are moving on unless they extend somethng significant to compensate for the days of wasted time.
We decided to move to the SC cloud just to get things going again. No other products match the features for the price.
They offer a migration extension to move unattended to the cloud. However, according to the migration doc, it says the versions need to match. My new cloud account is version 25.4.20. Our on-prem account is version 25.4.16. I cannot get 25.4.20 for on-prem and the cloud account won’t let me upgrade to 25.4.25 (which is available for on-prem). Not sure what to do.
Also, in testing the new cloud instance, it is downloading the ZIP file for the support client. We definitely don’t want that.
And, we use Duo for our on-prem 2FA. We added it to the cloud instance and it doesn't work.
This whole thing is off the rails.
We decided to move to the SC cloud just to get things going again. No other products match the features for the price.
They offer a migration extension to move unattended to the cloud. However, according to the migration doc, it says the versions need to match. My new cloud account is version 25.4.20. Our on-prem account is version 25.4.16. I cannot get 25.4.20 for on-prem and the cloud account won’t let me upgrade to 25.4.25 (which is available for on-prem). Not sure what to do.
Also, in testing the new cloud instance, it is downloading the ZIP file for the support client. We definitely don’t want that.
And, we use Duo for our on-prem 2FA. We added it to the cloud instance and it doesn't work.
This whole thing is off the rails.
We made same decision and are still on cloud trial
Detest the dark theme
Our on prem is 25.4.25 cloud trial is 25.4.20
migration basically succeeded, no internal users, roles or support sessions made it over
Agents seem to come across as they check in with on-prem and are usable in both
MFA wise I copied the details from the on-prem OTP section to cloud and it works for us
we are looking to go with the Legacy Concurrent Session Cloud Migration Offer once I get clarification on whether we get time credited for balance of on-prem lic time
HTH
I am glad to report that Version 25.4.25.9314 is now rolling out in the cloud, so the zip file is gone. I can speak for the entire ScreenConnect team when I say that we appreciate your patience; this was always intended as a stop gap fix while we could work on a more permanent solution.
The auto upgrades will take several days to hit each instance, so if you want to manually upgrade your cloud instance you can follow these instructions
Upgrade a cloud instance - ConnectWise