Jump to content

Silent commandline install


Recommended Posts

To my knowledge Immunet doesn't have any downloadable install command line scripts available to the general public. Then again, there is the option of writing your own install scripts if you're tech. savvy enough. How the install scripts are to be configured I have no available info regarding that unfortunately. 

There are still a couple of other options at your disposal too.

The ClamAV source code that Immunet uses has that ability. In fact ClamAV has to be configured and run using only command line scripts as it doesn't have a traditional User Interface. Like Immunet ClamAV's open sourced codes are free to use. Here's a link for the ClamAV source codes if you would like to give that a try instead of using Immunet. https://www.clamav.net/downloads

Another option would be to use Immunet's enterprise version called 'Secure Endpoints' (formally called AMP for Endpoints). Although not freeware like Immunet it does have the ability to deploy on multiple endpoints simultaneously. https://www.cisco.com/c/en/us/products/security/amp-for-endpoints/index.html

Best wishes, Ritchie...

Link to comment
Share on other sites

Many generic Windows installers can be called from the "run" dialogue (SUPER + R) or from the command prompt with the "/silent" option. It's generally undocumented and support is not universal, but it sometimes works. So, if the Immunet installer is called "setup.exe" and resides in the root of drive D:, you'd hit SUPER+R, and type "D:\setup.exe /silent" in the box, then hit enter/OK.

Other commandline options that may get you what you want: /silentinstall or /verysilent or /y

I've not tried any of the above but I've seen and used them for various other installers.

I'm fairly certain Chocolatey makes use of this trick for most installers, so you may want to see if you can find Immunet's NuGet install script on Chocolatey's web site to see how it calls Immunet's installer.

To deploy this on another machine, you'd have a .bat file calling the installer with the correct commandline option, and run that instead of running the installer directly.

This does of course sound a bit like you might be managing some sort of commercial deployment, so if this is the case then AMP will suit your needs better and is of course licenced and supported for such scenarios. Sometimes it's worse to use the wrong tool for the job than to just not do the job at all. If something's worth doing, it's worth doing right. If you're doing this for an organisation, just get AMP.

  • Like 1
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in

Sign In Now

  • Create New...