Oh okay that makes sense, then there is no reason to hit CTRL+F at all! Even better.

The .MSI installer can be made to run unattended an silent. e.g.

msiexec.exe /i ScreenConnect.ClientSetup.msi /quiet /qn

And you can even open the MSI up using ORCA and customize to your heart's content.

All software management product (Group policy software installation, SCCM, PDQ Deploy, etc.) can install ScreenConnect silently and remotely. Heck I just deployed it to my entire client base using remote commands in Nagios.

I strongly DISAGREE with ScreenConnect fumbling around trying to add "deployment" capabilities to their software. You see this in countless "enterprise" antivirus products that try to add features to "scan" the network and find your PCs to remotely install their agent via some sort of control panel that they provide. It's almost always error-prone and convoluted, it bloats the software and muddies the water because now you're using more than one tool to deploy software in your organization. That's awful.

ScreenConnect is a remote assistance / remote control product. It's lean and clean. Their responsibility should be to ensure that their software can be installed silently and unattended with all the various options configurable, and then it is up to you to use whatever software management product you like to deploy the software into your organization.