Software Deployment

Actually I'm also having to work up a deployment method for a couple hundred installs. It's some kind of Wise or InstallShield installer but no way to get the full MSI from it. The only option available is /VERYSILENT which simply makes the entire install silent (I assume it asks for activation later). I'm going to contact them and see how to get it to at least activate from command line, whether during install or otherwise. If they aren't helpful, and I kind of doubt they will be, the only solution is to have it auto fill the activation via GUI automation like AutoII, but that would be so ghetto so that's my absolute last resort.

I have tried a before/after snapshot packaging method but the activation really does bind to the hardware, so when you deploy it comes back.

I'll keep everyone updated of my final solution.

Wrappers generally extracts the MSI(s) and then executes them so; enable the Windows Installer policy "DisableMSI", execute the wrapper and when prompted about MSI prevention fetch the MSI(s).

Looks like this setup does not use a main MSI.
If you try to make a snapshot you might want to install the supporting MSI's as prereqs to avoid that they show up in your snapshot.

Okay I talked to tech support at InfoMap and despite their crappy limited installer they were actually quite helpful. SO! Here was my solution:

Installation:
1) Contact InfoMap and tell them your company policy does now allow users to register software. They will then provide you with a version of the installer that does not require user registration during activation. HOWEVER, this modified version also no longer seems to support the silent install switch of /VERYSILENT.

2) I created a Prism package to deploy the core files/services (use your snapshot packager of choice or scripted method to address the installer GUI)

Activation:
1) Under the "Information Mapping\FS Pro 4.0" Program Files folder, create a "License.txt" file containing nothing but your license number. Also under the same folder, if you need proxy settings for activation, create a "ProxySettings.txt" file with the format port-server (ex. 8080-proxy.company.net). The GUI for the proxy settings in the activation window also creates this file if you enter them manually, so you can see the structure for more complex proxy set-ups if needed. I included both these files into my Prism package for deployment.

2) I wrote an AutoIt script to manually run ControlActivation.exe (which now automatically has the license number and proxy info entered from the files above) and then procede with automating the activation process. I also wrote an AutoIT script to handle de-activation when uninstalling FS Pro 4 to correctly increment the license count available. You can see I just did a super generic error handling, nothing fancy; just something better than not knowing it wasn't successful.

AutoIt Scripts:

Activation:

Opt("TrayIconHide", 1)

Run ("C:\Program Files\Information Mapping\FS Pro 4.0\ControlActivation.exe")

WinWait ("FS Pro 4.0","",5)
WinActivate ("FS Pro 4.0")
ControlClick ("FS Pro 4.0","","[NAME:optActivate]")
WinActivate ("FS Pro 4.0")
ControlClick ("FS Pro 4.0","","[NAME:btnContinue]")
WinActivate ("FS Pro 4.0")
ControlClick ("FS Pro 4.0","","[NAME:btnActivate]")
WinWait ("FS Pro 4.0","Successful Activation",5)
WinActivate ("FS Pro 4.0")
$ExitClick = ControlClick ("FS Pro 4.0","","[NAME:btnCancel]")
If $ExitClick = 0 Then
MsgBox (4144,"Activation Error","A problem occurred with FS Pro activation!")
Exit
EndIf


De-activation:

Opt("TrayIconHide", 1)

Run ("C:\Program Files\Information Mapping\FS Pro 4.0\ControlActivation.exe")

WinWait ("FS Pro 4.0","",5)
WinActivate ("FS Pro 4.0")
ControlClick ("FS Pro 4.0","","[NAME:optDeactivateYes]")
WinActivate ("FS Pro 4.0")
ControlClick ("FS Pro 4.0","","[NAME:btnContinue]")
WinWait ("Information","",5)
WinActivate ("Information")
$ExitClick = ControlClick ("Information","","[CLASS:Button; INSTANCE:1]")
If $ExitClick = 0 Then
MsgBox (4144,"De-activation Error","A problem occurred with FS Pro de-activation!")
Exit
EndIf


P.S. And yes, you need all the WinActivate's to keep the window in focus properly to make it work consistently.