Introduction
This document will provide information about command line installation Note that these instructions are ONLY for installation on the Windows platform.
They are as well sometimes partially used in deployment tools
Commands
Sometimes we hand out installation command lines like this:
SecureDoc_64.exe /s /v" /qn /norestart /l*v \"C:\Logs\SDSetup.log\" MSIRMSHUTDOWN=2 SDREBOOT=\"NO\" SDPROMPTRESTART=\"NO\" ALLUSERS=2"
SecureDoc_64.exe /s /v" /qn /norestart /l*v %TEMP%\SDSetupSilent.log ALLUSERS=2 MSIRMSHUTDOWN=2 SDREBOOT="NO" SDPROMPTRESTART="NO" ALLUSERS=2 CHECK_ATA=0"
SecureDoc_64.exe /s /v" /qn /l*v %TEMP% ALLUSERS=2 SETUPEXEDIR="C:\SDinstall" MSIRMSHUTDOWN=2 SDREBOOT="NO" SDPROMPTRESTART="NO" REBOOT=ReallySuppress
Explanation
Sometimes customers ask what the meaning of all that is:
/s = silent is to tell setup.exe to run silent
/v" is to pass parameters to MSI (so you have to wrap it in quotes) -> The end of the line is always "
/l*v = location of file with verbose logging
/norestart = No Restart
/v" = s to pass parameters to MSI (so you have to wrap it in quotes)
/qn = MSI parameter that causes everything but setup.exe to be silent. This sets the user interface level to zero.
SDREBOOT = will instruct InstallShield to not reboot machine upon package installation finished.
SDPROMPTRESTART = prompts a question to user if he would like to restart the system or not. The values are YES or NO
SDWaitReboot will stop the installshield, and the goal is to not start SDForm immediately ... Rather wait till next time, initiated by SDService, upon loading time
ALLUSERS Sets the installation level of the program: ALLUSERS=1 (per machine) and ALLUSERS=2 (per user)
MSIRMSHUTDOWN=2 = Processes or services currently using files affected by the update will not be shut down unless they have all been registered for a restart. If a process or service has not been registered for a restart, no processes or services will be shut down.
REBOOT=ReallySuppress = Forces or suppresses a restart. (Force, Suppress, ReallySuppress
SETUPEXEDIR="C:\SDinstall" = SETUPEXEDIR is a property that contains the path to Setup.exe
further SD defined properties:
"SUPPORTDIR"
"SDPROMPTRESTARTFORCE": [ 0 | 1 ] used only when Macfee SafeBoot is found installed, whether force to restart device
"STANDALONE": [ 1 | 0 ] internal logic, to control SD client deployed as standalone or enterprise (remote package)
"SDIsUserAdmin"
"SDREBOOT": [ NO | YES ] whether suppress the reboot
"SDPROMPTRESTART": [ YES| NO ] instead of suppress reboot, whether showing 2 min message asking the user reboot or not
"SD_SHUTDOWN": [ 0 | 1 ] on device with OPAL SED boot disk, enforce device shutdown, instead of restart
"SDSILENTUNINSTALL": [ 0 | 1 ] silent un-installation
"SDSERVICERUNEXE": [ STRING ] for remote package, by default, SDService launches SDForm.exe, to start initial client registration.
"CHECKEDRIVE": [ YES | NO ] check whether bitLocker is deployed on TCG OPAL boot disk as eDrive
"BITLOCKERENABLED": [ 0 | 1 ] checking whether bitLocker protection is on already, to device deploy client as RMO or SDBM
"CHECK_ATA": [ 0 | 1 ] whether checking ATA security enabled or not
"SDPROGRESS": [ 0 | 1 ] suppress message progress pop-up
INTERNALLY USAGE ONLY:
"SDUPDATE": [internal use only] before deployment, checking whether BL installed already, to decide case of fresh deployment or upgrade
"SDOLDVERSION": [internal use only] retrieved from the registry value of "SDVersion"
"ISACTIONPROP1": [ internal debug use only ]
"IS_MAJOR_UPGRADE": [ internal debug use only ]
"REMOVE": [ internal use only ] [ ALL | … ] for automation unit testing of installshield
"BITLOCKERSETUP": [ internal use only ] detecting whether BitLocker is supported and enabled (protection is on)
"SDShortcutFoler": [ internal use only ] to delete the Container Encryption short cut from the start menu
"FOUNDFVEVOLSYS": [ internal use only ] to check whether bitLocker driver (fevvol.sys) installed
"HPPTINSTALLDIR": [ internal use only ] to detect whether SD HPPT installed or not …
"WININSTALLERVER": [ internal use only ] to check windows installer 4.5 - minimal required
"INSTALLDIR": [ internal use only ] used in standalone update to check the compatibility of any existing SecureDoc (e.g. HPSecureDoc)
"SDPACKAGETYPE": [ internal use only ] detecting old way (assuming SDJob.bat & install.dbk exists under c root) vs new way of SD client deployment
Microsoft MSI Property reference
Article Document
Title
Information about command line installation
URL Name
Information-about-command-line-installation