1322 MSIEXEC - Installing SecureDoc using the .msi installer, with flags - describedMSIEXEC - Installing SecureDoc using the .msi installer, with flags - described

Prev Next

The pre-requisites before installing SecureDoc using the MSI installer are:

1) Windows 4.5 Installer
2) Microsoft Visual C++ 2008 Redistributable Package (9.0.30729.6161)

The command to run the MSI:

msiexec -i SDSetupSilent.msi /qn

/qn = No UI (totally silent)
 

NOTE: for a basic quick result, the following example provides a workable simple installation scenario:

Msiexec /i SecureDoc_64.msi /qn /l*v C:\installlog.log SETUPEXEDIR="<path where msi and SDProfile.spf reside>"

You can take out the / l*v and the log file if you don’t want the logs.

 

NOTE: The setupexedir is needed, to provide the path/location where the SES Client installer config files reside, as well as the .msi file itself


FURTHER OPTIONS:

Microsoft Windows Installer.

Syntax
Install
MSIEXEC /i package options

Uninstall
MSIEXEC /x package options

Advertise to current user
MSIEXEC /ju package options [/t Transform_List | /g LanguageID]

Advertise to all users
MSIEXEC /jm package options [/t Transform_List | /g LanguageID]

Administrative install - install on the network.
MSIEXEC /a package

Apply a patch to an installed Admin image
MSIEXEC /p patchPKG /a package 

 

ALLUSERS or MSIRMSHUTDOWN Properties

msiexec SecureDoc_XX.msi /qn /l*v %TEMP%\SDSetupSilent.log ALLUSERS=2 MSIRMSHUTDOWN=2


Options:
/fp fix - replace missing files
/fo fix - replace Older files
/fe fix - replace older or Equal date files
/fd fix - replace Different version files
/fc fix - replace files based on Checksum differences
/fa fix - replace All files
/fu fix - rewrite HKCU registry
/fm fix - rewrite HKLM registry
/fs fix - recreate shortcuts
/fv fix - rewrite local cache from source
/l* Logfile Log Everything (not Verbose)
/l*v Logfile Log Everything Verbose
/lv Logfile Log Verbose
/le Logfile Log All error messages
/lw Logfile Log Non-fatal warnings
/li Logfile Log Status messages
/la Logfile Log Startup actions
/lr Logfile Log Actions
/lu Logfile Log User requests
/lc Logfile Log User Interface (UI) parameters
/lm Logfile Log memory use
/lp Logfile Log Terminal properties
/l+ Logfile Append to an existing log file.
/l! Logfile Clear an existing log file.
/q , /qn No UI.
/qb Basic UI.
/qb! Basic UI with no cancel button.
/qr Reduced UI. A modal dialog box is displayed at the end of the install.
/qf Full UI. A modal dialog box is displayed at the end of the install.
/qn+ No UI. However, a modal dialog box is displayed at the end of the installation.
/qb+ Basic UI. A modal dialog box is displayed at the end of the installation. If you cancel the installation, a modal dialog box is not displayed.
/qb- Basic UI with no modal dialog boxes.
/y module Register a DLL - only use for registry information that cannot be added using the registry tables of the .msi file.
/z module UnRegister a DLL - only use for registry information that cannot be removed using the registry tables of the .msi file.

Windows installer versions

Windows NT can support version 1.1 or version 1.2 (No longer supported by SecureDoc, included only for completeness)
Windows 2K includes version 1.1 (No longer supported by SecureDoc, included only for completeness)
Windows XP Sp1 /Server 2003 include version 2.0
Windows XP SP2 includes version 3.0

Updates to msiexec can be downloaded from MSDN.

DO NOT use the domain controller Sysvol folder as a Windows Installer installation point, doing so may result in the following error when you attempt to run the Windows Installer (.msi) package:

This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package.

This is because the Sysvol folder is created with the SHI1005_FLAGS_RESTRICT_EXCLUSIVE_OPENS attribute, which prevents it from being exclusively locked by Windows Installer. Having locked files on a SYSVOL would create Active Directory directory service synchronization problems.