We are migrating to Windows Installer so all of our customers currently have our application installed with Inno Setup.
To help them install, we use the 'File Search' to identify what is already installed. We then use VBScript to set the FeatureRequestState (shown below). If the user is not running using the UI sequence (SILENT_INSTALL = "Y") then we call the VBScript in the "InstallExecuteSequence.InstallInitialize" event.
If Session.Property("HAVE_ADMIN_CLIENT") <> "" Then
Session.FeatureRequestState("Admin") = msiInstallStateLocal
Else
Session.FeatureRequestState("Admin") = msiInstallStateAbsent
End If
This works fine when the installer is run using msiexec and the /qb option but it is not working when the it is installed using (Active Directory) GPO. We are told the customer pushes the MSI installer and forces a reboot at which time the installer is run by Windows.
We can run the installer from a folder anywhre so it is not related to the location of the installer.
Brian
FOLLOW US
Get the latest news in Application Packaging