How can I do a silent installation?
Starting with FCS Express v7.16.0035, FCS Express will support command-line silent installations that can be run by the System Administrators.
To perform the silent installations, the following parameters are supported:
- /SILENT
- the installation wizard and background windows are not displayed, but the installation progress window is.
- /VERYSILENT
- the installation wizard, background windows, and installation progress windows are not displayed.
To run installations using the /SILENT or /VERYSILENT parameters, the following parameter will need to be included:
- /ACCEPTPRIVACYPOLICY
- accepts the privacy policy and end-user licensing agreement prior to installation.
For example, after calling the directory for where the installer is located, set the installer name with the appropriate parameter, plus /ACCEPTPRIVACYPOLICY:
The installation will occur, either silently or very silently, in the default location as defined by the installer.
For uninstallation, FCS Express writes the uninstaller to the same folder where the application executables are installed. As a result, a call to the installation folder will need to be made before calling the uninstaller package, unins000.exe.
For example:
cd C:\Program Files\De Novo Software\FCS Express 7 Research Edition
followed by:
C:\Program Files\De Novo Software\FCS Express 7 Research Edition>unins000.exe /SILENT
or
C:\Program Files\De Novo Software\FCS Express 7 Research Edition>unins000.exe /VERYSILENT
The following parameters can also be used during installation in conjunction with the /SILENT and /VERYSILENT parameters
| /LOG | Creates a log file in the user's TEMP directory detailing file installation and [Run] actions taken during the installation process.
/LOG can also be used during uninstallation. The log file is created with a unique name based on the current date. It will not overwrite or append to existing files. |
| /LOG="filename" | Also creates a log file, however, the fixed pathway and filename can be defined in the "filename" variable.
Please note that "filename" needs a legitimate pathway and filename with extension. For example, /LOG="C:\Users\Public\Documents\logfile.txt" will create a log file called logfile.txt in the folder C:\Users\Public\Documents. If a log file with the specified name already exists in the given location, the file will be overwritten. If the file cannot be created, for example, due to a lack of Read/Write permissions or if the pathway is inaccessible, the Setup will abort with an error message. |
| /NOCANCEL | Prevents the user from canceling during the installation process, by disabling the Cancel button and ignoring clicks on the Close button. |
| /NORESTART | Prevents Setup from restarting the system following a successful installation, or after a Preparing to Install failure that requests a restart. |
| /CLOSEAPPLICATIONS | Instructs Setup to close applications using files that need to be updated by Setup if possible. |
| /NOCLOSEAPPLICATIONS | Prevents Setup from closing applications using files that need to be updated by Setup.
If /CLOSEAPPLICATIONS was also used, this command line parameter is ignored. |
| /FORCECLOSEAPPLICATIONS | Instructs Setup to force close when closing applications. |
| /NOFORCECLOSEAPPLICATIONS | Prevents Setup from force closing when closing applications.
If /FORCECLOSEAPPLICATIONS was also used, this command line parameter is ignored. |
| /LOGCLOSEAPPLICATIONS | Instructs Setup to create extra logging when closing applications for debugging purposes. |
| /RESTARTAPPLICATIONS | Instructs Setup to restart applications if possible. |
| /NORESTARTAPPLICATIONS | Prevents Setup from restarting applications.
If /RESTARTAPPLICATIONS was also used, this command line parameter is ignored. |
