Offline Installer no longer working with 5.5.x

In 5.4 we could install SimpleHelp on a windows PC by using a command like:
Remote-Access-windows64-offline.exe /S /NAME=“AUTODETECT” /HOST=http://

Now that we are on 5.5.2, there is no way to get the Remote-Access-windows64-offline.exe file - we can only find the PACK file (Remote Support-windows64-offline-exe.pack)

Anyone have any idea on how to install via command line on ver 5.5.2 ?

That should still work.

An alternative you can do is on the technician access tab, create a new installer app with the pre-configured settings you want, including silent install.
Click download and then run it as you normally would, either Command line, deployment tool, or GUI.

Yup - never thought of that. Thank you - that should work.

We still have the ability to download the offline installer on our 5.2.2 install…

Same as we always did…

Yes, I see those, but for some strange reason those don’t work to install silently through the command line.
Using Darrell_Swafford’s alternative solution above seems to work.

Strange, we use a powershell script that takes the beginning of the computer name (which is set per location, like GB- or GBR- or GCM- etc… and it added the device into the group by the name, so all devices with GB- are in the GB group etc… and it still installs silently, we are also using a SMA called Kace that pushes the install and installs as “system” so maybe the reason it is still silent for us is because it is running as system…

Hi all, we’ve had a similar issue since upgrading to 5.5.1. When running the offline installer from the command line mentioned in the original post, it now launches the Remote Access Service window and requires you to manually click the start service button. This also means a user must be logged in when running silently or the service will never start. Previous versions didn’t do this.

I’ve used the method Darrell_Swafford suggested above and it still does the same thing, however using the Mass Deploy option works. That’s ok when you can connect directly to the machine, not so helpful when it’s off network or part of an automated deployment :frowning: