Must have botched something, will look into it, all other parts should work just fine.
I tested this on a separate machine with a clean install. Works good. I wasn't able to get "patch installer" function to work for me. I used "patch system".
Everything was working smoothly.
I backed up my production install to be safe and upgraded without a hitch.
Many Thanks!
Finally got around to playing with the patcher a bit more. I downloaded that latest stable linux installer then copied the patched files from my windows installation to overwrite the files contained in the "screenconnect" folder of the linux installer. Then I just ran the upgrade process as normal on my Debian box all seems fine.
Great work Arlecho all seems well
2.0.2.0
- Fix custom directories
Download
https://mega.nz/#!wg9lzSzK!RnqjBpHUH1hFB...LmSrIRy3Ak
asgh43ui56kmtnrabt3217yuehjrnd
Notices
- Patch the installer before installing to prevent leaking your information
- Linux can be patched, just copy the files over to a windows machine and select the directory!
- "External Accessibility Check", "Version Check" and "Browser URL Check" will now always fail!
- Installing/updating extensions could theoretically be spotted by Connectwise as they are downloaded directly from their servers!
- License no longer displays (not required/possible anymore)
- Please do not post thanks and other posts that do not contribute (the mods don't like them and it clutters the thread)
- Hosts file editing no longer required
@Arlecho
I ran the new patcher (v2.0.2.0) on the installer msi. After using it to update an existing Windows installation, I can no longer connect to clients and I get the following error:
Code:
Status
Waiting for an available license...
Your installation has reached the limit of concurrent sessions it is allowed, or you've reached a licensing restriction. This will continue to try to reconnect until a license is available.
I had to run the patcher directly on the server and use the
Patch System button in order to get the server up and running, again.
So... What is the
Patch Installer button supposed to do? It seems patching the installer doesn't do anything and patching the files on the system is still necessary.
With the new patcher, are we now supposed to perform both steps (
Patch Installer and then
Patch System)?
The patch installer patches the msi so it doesn't autostart the services, this stops any and all callbacks to their servers untill the patch system has been used and all other callbacks have been eliminated.
The patch installer is optional though highly recommended in order to stay safe.
(Jul 15, 2019, 10:43 am)Arlecho Wrote: [ -> ]The patch installer patches the msi so it doesn't autostart the services, this stops any and all callbacks to their servers untill the patch system has been used and all other callbacks have been eliminated.
The patch installer is optional though highly recommended in order to stay safe.
Thanks! Makes sense to me now.
Is it safe to use ConnectWise View Integration Extension? Or is there an self hosted version for ConnectWise View ?
I backed up my production install to be safe and upgraded. I patched the installer then the system after install. Everything seems to be working OK except the version check gives an error and is blank. I did it multiple times with both 2.0.1.0 and 2.0.2.0. Is this OK and I should leave it alone or could there be other problems?
Rectified the statement about the version check, just killing it is easier and more future proof then patching that file.