ConnectWiseControl.ClientSetup.sh: line 237: InstallPackageFile: command not found

The script attempts to determine what package manager is native to the target system [determinePackageType()], and then prefixes the function named in the call with rpm, pkg or deb. As Arch is none of the above, no prefix is added to the InstallPackageFile function call and it fails.

If we could bypass that process and simply drop binaries and scripts where they belong, is there a chance it would run on Arch? I reverted my main desktop OS back to Mint just so I can keep ScreenConnect running on it. I may, if I ever find the time, try copying the pieces over and see what happens.

If we could bypass that process and simply drop binaries and scripts where they belong, is there a chance it would run on Arch? I reverted my main desktop OS back to Mint just so I can keep ScreenConnect running on it. I may, if I ever find the time, try copying the pieces over and see what happens.

In theory yes, as long as Java was installed on the machine. You could just copy over the installation location /opt/screenconnect-xxx from a separate Linux guest onto this machine and then place the startup script found at /etc/init.d/screenconnect-xxx

You would have to modify the SessionID found at /opt/screenconnect-xxx/ClientLaunchParameters.txt after copying it over so that the new Guest calls back with a unique primary key. To my knowledge the SessionID is the S parameter and a Guid, so just modify one letter or number to a different letter or number (within the S= parameter).

You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.