Customizations no longer supported from next version of ScreenConnect
So ScreenConnect will no longer support certain customizations from the next version onwards.
HOWEVER, the list includes resources that are actual sentences in English. My customers do not speak English and so we currently use a translation extension.
So my question is: Will the change mean the translation extension no longer applies to these resources?
I mean these resources in particular:
UnderControlBannerTextFormat | Your computer is being controlled by {0} | The message in the small banner that appears on an end-user's screen when connected. |
ConsentHostConsentButtonText | Consent to Control | Button to consent to a connection |
ConsentHostRefuseButtonText | Refuse Control | Button to refuse a connection |
GuestWelcomePanel.Message | Welcome to our online remote support and collaboration portal. The following options allow you to connect to a session. | Welcome message on the Guest page |
EDIT: I tried the new v25.4.25 and I can confirm the translation no longer applies.
Please realize that there are people who use ScreenConnect outside the English-speaking world. Please don't leave us behind.
We need to revert the recent changes to ScreenConnect that removed the option to hide the tray icon and branding options.
It is causing unnecessary noise and extra workload from our customers.
They are seeing the icon, do not recognise it, and are either raising tickets or uninstalling the agent completely.
This has led to devices needing reauditing, especially in restricted environments where any unexpected change is flagged.
We now have to explain a change we did not authorise and were not warned about.
You have also removed the ability to brand the support page, which is another step backwards.
These changes do nothing to protect end users from malicious access. All they do is punish paying customers who are using the product as intended.
If security is the concern, put a paywall or verification process in place for the abuse cases. Do not push out broad restrictions that impact everyone.
Delaying branding options by six months or adding an approval step would make more sense than removing functionality and giving us no control.
Find the actual problem and fix that. Do not take a blanket approach that wastes time, damages trust, and puts more pressure on our support teams.