[How To]: Outpost Firewall Pro 2.5.365

[ironside]

Agnitum Outpost Pro 3.0.543.431

They seem to have changed the installer in this version, Does anyone know how to install it silently ?

Thanks in advance

[SiMoNsAyS]

yep, some1 needs to start working on a new script

i personally find this latest version full of bugs

[WotC]

3.0 uses an inno based setup script, so:

/sp- /verysilent /norestart

helps to install. nevertheless the **** config wizard pops up afterwards. this application is really troublesome. if not for the cool features it provides i would replace it!

the config wizards even pops up after adding the path to the configfile to the registry :-(

[SiMoNsAyS]

untested: what about using /sp- /verysilent /norestart, then once the wizard pops up use "pskill.exe outpost.exe" to finish the process and finally import during uA the config files?

[WotC]

the processname is still outpostinstall.exe :-(, so the only way to achieve this is via autoit - i hate auto it scripts....

maybe the pid changes, dunno... have to check it...

nevertheless, here's an autoit script that worked in a VM, although u get the config screen after the first reboot. however, this might be circumvented when u add the path to the configfile to the registry as u mentioned - i'll try that tomorrow...

this script is tested with version 3.0.543.431

Opt("TrayIconDebug", 1)
Opt("WinTitleMatchMode", 3)
BlockInput(1)

Run("OutpostProInstall.exe /sp- /verysilent /norestart")

;Cancel configuration Wizard
WinWaitActive("Configuration Wizard")
WinActivate("Configuration Wizard")
ControlClick("Configuration Wizard", "", "Button7")

;Confirm exit
WinWait("Outpost Firewall Pro")
ControlClick ("Outpost Firewall Pro", "", "Button1")

btw: has anybody tried the office version of outpost firewall? it should be easier to get it installed automatically, though much more expensive :-(

Edited September 30, 2005 by WotC

[WotC]

update:

adding the following to the registry works - no config screen after a reboot. just the "whats new screen" - working on that though...

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Agnitum\Outpost Firewall\General]
"ICMP"=dword:00000000
"AutoUpdate"=dword:00000000
"EnableNetstatLogging"=dword:00000001
"EnableNetstatReporting"=dword:00000000
"SendRulesAtStartup"=dword:00000001
"ConfigFileName"="c:\\Outpost.cfg"


[HKEY_LOCAL_MACHINE\SOFTWARE\Agnitum\Outpost Firewall\Window]
"MinimizeOnClose"=dword:00000001
"MinimizeToTray"=dword:00000001

edit: i think the "whats new" can be cancelled as mentioned above... its just not history.txt but history.en in the ini file...

history.en=1c5bf93/69706b00

Edited September 30, 2005 by WotC

[WotC]

Using the AutoIT script, merging the regfile into the registry BEFORE a reboot and copying the outpost ini to the install folder is a) silently and B) prevents the popup after the install... i tried it in a vm - so if anyone wants to give it a real-machine test....

[WhatsNew]
history.en=1c5bf93/69706b00

This is what i THINK is important in the ini file...