Signing Installer & Agent
Since ConnectWise removed theming from ScreenConnect due to security concerns, we’ve lost the ability to brand the agent and installer—something many MSPs and IT teams relied on for a consistent user experience.
Right now:
-
ConnectWise signs the agent
-
We sign the installer (if we want)
-
Theming is no longer supported
The original concern was valid—customized agents could be used maliciously without any verification. But a better solution would be:
-
Let us theme the installer and agent again
-
Require partners to sign both the installer and agent with their own valid code-signing cert
-
Optionally use an org validation key to enforce secure theming
Why this Matters
-
Security: Requiring code-signing of both the agent and installer by the partner mitigates the original risk of tampered or spoofed deployments.
-
Brand Trust: End users see software signed by their actual IT provider or company, restoring trust in remote support sessions.
-
Compliance: Enterprises with strict software verification policies can deploy ScreenConnect in a compliant and more secure way.
-
Customer Experience: Theming allows MSPs and internal IT to deliver a seamless, branded support experience.
Hoping this can be considered—it solves the security issue without removing legitimate functionality.