• How to run a nested *.exe relative to the calling *.msi
• What are the differences between patching, update and upgrade with MSI
• Which UI Level Im running
• How to Add a Printer
• How to run a classID from Explorer / InternetExplorer
• Custom Action to manipulate DirectoryTable
• Custom Action to Add Line to logfile from Custom Action
• Return last / free position in Enumerated Regkey and submit to MSI
• HKCU RegKey in Citrix Server
• Resolve SourceDir Property
• Custom Action: Delete Folder given by Property
• Launch Condition Windows XP SP2 or Windows 2000 Sp4 or Server 2003 or newer

How to run a nested *.exe relative to the calling *.msi ([SOURCEDIR]setup.exe)

• Define a Property as "placeholder" to store Path in it --> _SDEXE 

Table:Properties

• Create a Custom Action "CA_SETPROP" (immediate Execute, call VBS embedded)
• Create a Custom Action "CA_SILENT" (defered, System, Synchronous)

Table:Custom Action

• Give that Stuff the proper Conditions and Sequence in 

Table: InstallExecuteSequence

What are the differences between patching, update and upgrade with MSI?

Which UI Level I'm running?

To detemine the user-interface level being used by a running installation,create conditions that test the value of the UILevel property.
The UILevel property contains the value

I.e. to create a CA that should run only during a completely silent installation, you can schedule the action with the condition UILevel=2.

Keep in mind that actions in the User Interface sequence will be skipped for anything other than a completely silent installation, irrespective of any conditions associated with them!

Instead using msiexec.exe, you can launch an MSI package from VBScript using the InstallProduct method of the MSI Automation interface; you can set the UI level for an installation launched from VBScript code by setting the UILevel property of the Installer object before calling InstallProduct.

Set oMSI = CreateObject("WindowsInstaller.Installer")
' set the UI level to basic
oMSI.UILevel = 3
' launch the installer
oMSI.InstallProduct "C:\Source\MyApp\MyApp.msi", ""
' clean up used ObjectVars
Set oMSI = Nothing

Note, however, than you cannot change the user-interface of a running installation (that is, inside a custom action).

How to Add a Printer

If OS > W2k you can call printui.dll to install a printer and its driver, example:
rundll32.exe printui.dll,PrintUIEntry /if /b "HP LaserJet III" /f%windir%\inf\ntprint.inf /r "lpt1:" /m "HP LaserJet III"
Installs Printer HP LaserJet III on port lpt1 using HP LaserJet III driver .
rundll32.exe printui.dll,PrintUIEntry /? for help file.
Run the executable rundll32.exe in a custom action with the rest of the syntax as the command line.
I have found that if you want to add the printer and its driver you need to have the port already existing. To add the port you can use the follwoing VB script, but you will need to install prnadmin.dll, comes with WIN2k resource kit, with your install. Substitute PORT Name with the port you desire to add.

Set oPort = CreateObject("Port.Port.1")
Set oMaster = CreateObject("PrintMaster.PrintMaster.1")
oPort.PortName = "PORT Name"
oPort.PortType=3
on error resume next
oMaster.PortAdd oPort

How to run a classID from Explorer / InternetExplorer

eg. Publishing on Windows Terminal Server / Citrix

iexplore.exe ::{ClassGUID}
explorer.exe ::{ClassGUID}

Where to place Custom Action to manipulate Directory Table

The Directory Table will be resoluted during the "CostFinalize" Action
To manipulate Directory Table Entries ensure that You place Your type 51 Custom Action after that InstallExecuteSequence entry.

Add Line to logfile from Custom Action

If You need to add a Line of text to the MSI-Logfile within Your custom action

 VBS:

Return last / free position in Enumerated Regkey and submit to MSI

VBS code to add as Custom Action, with session.property transaction

just a sample, You have to optimize ;-)

HKCU RegKey in Citrix Server

just put them in HKLM\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\TerminalServer\Install

Resolve SourceDir Property

make use of ResolveSource in InstallExecuteSequence

Custom Action: Delete Folder given by Property

'(C) by Wolfgang Zerzawy
' use as Custom Action Type 102
' Use Condition in Install Execute Sequence: REMOVE~="ALL"
Option Explicit
Dim WshShell,SystemFolder,Fso,strFolder, strFile, ret
' ensure that You dont Use "Root-Folders" ! e.g. C:\Programme -- that would be fatal!
strFolder = GetAProperty("DATADIR")
strFolder = Left(strFolder,Len(strFolder)-1)
On error resume next
'Environment variable reading
set WshShell = CreateObject("WScript.Shell")
set Fso=createobject("scripting.filesystemobject")

If Fso.FolderExists(strFolder) Then
ret = Fso.DeleteFolder (strFolder,True)
MsgBox strFolder & " deleted with ErrorLevel" & ret & ". Let's go further"
AddLogFile strFolder & " deleted with ErrorLevel" & ret & ". Let's go further"
Else
AddLogFile strFolder & " could not be deleted. Either not Present or something else ... --> not really an error"
End if

Set WshShell = Nothing
Set fso = Nothing


' Getting a Property
Function GetAProperty (PROPERTYNAME)
dim szStringVal
szStringVal = Session.Property(PROPERTYNAME)
GetAProperty = szStringVal
End Function

Sub AddLogFile (LogText)
const msiMessageTypeInfo = &H04000000
set LogText = Session.Installer.CreateRecord(2)
LogText.StringData(1) = "ZA_CustomAction"
LogText.StringData(2) = LogText
Session.Message msiMessageTypeInfo, LogText
End Sub
 

Launch Condition Windows XP SP2 or Windows 2000 Sp4 or Server 2003 or newer

(c) by Wolfgang Zerzawy 07-Mai-08 12:11