Fluke Networks Linkware 8.1

Fluke Networks Linkware 8.1 is an MSI install in an InstallAware execuatable wrapper.

The MSI extracts out into the temp folder when the exe is run and the exe launches the MSI with a partiular command line.

The MSI is totally non-standard, probably due to the InstallAware type of generation.

The exe does support the /s switch which makes the installation silent with defaults however the driver installation part of the install which is DPINST driven prompts to user to trust drivers from the Fluke Networks vendor.  This prompt can be worked around by obtaining the registry key which is written when the "Always Trust drivers from this vendor" tick box is clicked.  It is a binary registry entry created here
HKLM\SOFTWARE\Microsoft\SystemCertificates\TrustedPublisher\Certificates\97A2CBA2763CAD7B8B214B4BE53ABE56380747FB

If this value is written into the registry before the exe /s is launched the installation will be fully silent.

Finally the exe is not SCCM compatible because it fails to run properly under the system account.

It is possible to use psexec.exe to remotely run the install under an admin account on the target machine.  Copy the install files to the target first then run

psexec.exe \\machinename <path to batch file>

A batch file can manage the installation of the regkey (reg.exe import of a reg file), launch the exe /s and then delete unwanted shortcuts (uninstall)

The uninstall procedure can be silent with the following batch file

C:\ProgramData\{AF40D181-8A8C-4CE5-99C4-8E2EF44E493F}\setup.exe /s REMOVE=TRUE
rd /s /q "%ProgramData%\Microsoft\Windows\Start Menu\Programs\Fluke Networks"

IBM Websphere MQ Explorer 7.5.0.2 - install MSI special command line requirements.

The websphere MQ Explorer 7.5.0.2 MSI installation requires some parameters to be supplied via an ini file.  This ini file is specified on the command line using the USEINI parameter.

msiexec /i "IBM Websphere MQ.msi" transforms=<name> USEINI=<path> /qn

/qn or /q must be used so that the MSI is run with no user interface at all.

important: the USEINI path must be a full and absolute and not relative.  Putting the ini file in the same folder as the MSI/MST and using USEINI=myfile.ini will NOT work.

UNC paths will work.

http://pic.dhe.ibm.com/infocenter/wmqv7/v7r5/topic/com.ibm.mq.ins.doc/q009040_.htm

Application Startup

In addition to the normal startup places such as registry run keys and startup folders.  Some applications may also startup by creating entries in the task scheduler with a trigger of "At log on of any user"

sysnative

Occationally you'll need to run 64-bit things from SCCM which may try to initialise them in a 32-bit way and cause problems and errors.  One way to get round this is to use the sysnative value.  This enables 64-bit programs to be correctly initialised even from the 32-bit SCCM client.

e.g.
C:\windows\sysnative\DISM.EXE  parameters

The above command will enable the Windows features on a 64-bit build to be configured via an command to a 32-bit SCCM client.