Jump to content

[How To]: Outpost Firewall Pro 2.5.365


SiMoNsAyS

Recommended Posts


This what is tried

extracted outpost setup to directory and clicked outpost.exe

it threw an error messsage with

1. install.exe /u

2. restart

3. install.exe

4. restart

5 run outpost.exe

when i did that and clicked on outpost i got outpost running fine in the systemtray.

so i think scripting autoit to do above actions 1,2,3 and 4 would be enough

infact 2-restart step can be skipped and still the outpost would work i think

There are also a lot of ini files in the directory which can be used to configure outpost.... like logging etc

one other thing if /u stands for uninstalling then what happens when insall.exe is executed? are there anymore switches?

i'll check it in detail when i go home :)

Link to comment
Share on other sites

theres only one restart...

its not necessary to restart unless you want to launch outpost.

most of us restart anyway after installing all our applications either in in runonce ex or guirunonce. after that restart outpost will work fin.

Link to comment
Share on other sites

Is the first post, the way I should try this? I'm new to Unattended installions and getting along pretty well so far.

How do you do that AutoIt stuff? From what I read from the first post it says something about in the AutoIt directory. So does this mean I have to download it? If so, where can I get it?

Also that .zip at the end of the post, is that a working version that reg's outpost? I would like to try to compile one on my own, but this is probably the last resort.

Link to comment
Share on other sites

  • 3 weeks later...

hi all,

i've made a new autoit script from scratch that automates that silent installation of outpost firewall pro 2.5.xxx... i tried not to use the sleep (delay) command since it may add some inconsistency with fast or slow pc's.

here's my autoit script

Run(@HomeDrive&"\Others\outpost\OutpostProInstall.exe /s")

WinWait("Create New Configuration")
ControlClick ("Create New Configuration", "", "Button5")

WinWait("Configuration Wizard")
$e= ControlCommand("Configuration Wizard", "", "Button5", "IsEnabled", "")
While $e=0
$e= ControlCommand("Configuration Wizard", "", "Button5", "IsEnabled", "")
WEnd
ControlClick ("Configuration Wizard", "", "Button5")

$c= ControlCommand("Configuration Wizard", "", "Button8", "IsVisible", "")
While $c=0
$c= ControlCommand("Configuration Wizard", "", "Button8", "IsVisible", "")
WEnd
ControlClick ("Configuration Wizard", "", "Button8")

WinWait("Install", "This system must be restarted to complete the installation. Click the OK button to restart this computer. Press Cancel to return to Windows without restarting.")
ControlClick("Install", "This system must be restarted to complete the installation. Click the OK button to restart this computer. Press Cancel to return to Windows without restarting.", "Button3")

ProcessWaitClose("OutpostProInstall.exe")

DirCreate(@ProgramsDir&"\Agnitum")
DirCopy  (@HomeDrive&"\Agnitum", @ProgramsDir&"\Agnitum", 1)
DirRemove(@HomeDrive&"\Agnitum", 1)

RunWait("REGEDIT /S "&@HomeDrive&"\Others\outpost\register.reg")

so, without the delay command, this script will be as responsive between a slow and a fast pc. what this script does is it checks if buttons are clickable/visible or not, as in the case of outpost installation, some buttons starts up unclickable yet during the progress of the installation on the same window... this script monitors it.

also, during the testing, i've found a way on cutting back much of the time outpost pro installs and the lines of the script as well... i just dunno if this one will install outpost properly...

here's the alternative script:

Run(@HomeDrive&"\Others\outpost\OutpostProInstall.exe /s")
ControlClick ("Configuration Wizard", "", "Button6")

WinWait("Install", "This system must be restarted to complete the installation. Click the OK button to restart this computer. Press Cancel to return to Windows without restarting.")
ControlClick("Install", "This system must be restarted to complete the installation. Click the OK button to restart this computer. Press Cancel to return to Windows without restarting.", "Button3")

ProcessWaitClose("OutpostProInstall.exe")

DirCreate(@ProgramsDir&"\Agnitum")
DirCopy  (@HomeDrive&"\Agnitum", @ProgramsDir&"\Agnitum", 1)
DirRemove(@HomeDrive&"\Agnitum", 1)

RunWait("REGEDIT /S "&@HomeDrive&"\Others\outpost\register.reg")

with that does compared to the first script is that this time, the installation finishes even at the first part of the wizard.

Anyways, the folder \Others\outpost is just a sample location i used, you can set it anywhere you placed the outpost installer and the registry file.

The registry file pre-contains the registration key of my outpost. You may use yours. Remember, when placing the registration key for ourpost to the registry file, just place the entire keys in one line like so... (example)

if the registration key is like this...

ABCD
EFGH
IJKL
MNOP

you should enter the key to the registry file like this...

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Agnitum\Outpost Firewall]
"Key"="ABCDEFGHIJKLMNOP"

hope this clears some things.

Link to comment
Share on other sites

  • 2 weeks later...
  • 1 month later...

i install oupost 2.5.370.370 silent with winxp sp2. After installation computer reboot's and when begin registration outpost with AutoIt script:

; AutoIt Version: 3.0.102
; Language: English
; Platform: Win9x / NT / XP
; Author:  SiMoNsAyS aka Bio]-[aZaRD
; Script Function: Registrar Agnitum Outpost Pro Firewall 2.5
Sleep(90000)
Opt("TrayIconDebug", 1)
Opt("WinTitleMatchMode", 2)
BlockInput(1)
Run("Notepad.exe")
WinWaitActive(" - ","")
Send("{LALT}{DOWN}{DOWN}{ENTER}")
Send("%SYSTEMDRIVE%\Serial.txt{ENTER}")
WinWaitActive("Serial.txt","",5)
Send("^a")
Send("^c")
Send("{LALT}{UP}{UP}{ENTER}")
Run("outpost.exe /register")
WinWaitActive("Outpost Firewall Pro Registration")
WinActivate("Outpost Firewall Pro Registration")
Send("D")
WinWaitActive("Enter code")
WinActivate("Enter code")
Send("^v")
Send("{ENTER}")
WinWaitActive("Outpost Firewall Pro")
WinActivate("Outpost Firewall Pro")
Send("{ENTER}")

DirRemove (@HomeDrive&"\Install", 1)
FileDelete (@HomeDrive&"\Serial.txt")

EXIT

but after copying serial from serial.txt and closing serial.txt nothing to happened, explorer not running - no icons and taskbar, but in task manager process outpost is present.

This script locate in program files in outpost folder with other outpost files.

Link to comment
Share on other sites

I try his script, but outpost not register after that.

I solve my problem changing some string in script, but after reboot when registration done (flash window "thank you for registration") starting explorer, desktop and icons i run outpost and his NOT registerd :)

What should i do now?

Link to comment
Share on other sites

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Agnitum\Outpost Firewall]
"Key"="----"

Will register it for you insted using the autoit script. ;)

BTW that prolly means your serial is blacklisted in the newest build.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...