You can install the Security Center SDK from a separate package instead of using the full Security Center installation package. If you are using this separate package, be aware that the silent SDK installation options are slightly different from those of Security Center.
Command syntax
The syntax for running the setup in silent mode is:
setup.exe /debuglog<setupLog> /s /v"/qn /l*v <msiLog> <SDK_options>"setup.exeis the setup program found in the root folder of the SDK installation package.<setupLog>is the path to the setup log file. The folder path must exist. The setup program will not create it.<msiLog>is the path to the MIS log file. The folder path must exist. The setup program will not create it.<SDK_options>are the Security Center SDK options.An option follows the
<option>=<value>syntax, where<option>is written in all caps. No space is allowed on either side of the equal sign (=). If the value contains spaces, the value must be included between double quotes.
SDK options
The following table describes the SDK options.
| SDK option | Description |
|---|---|
AGREETOLICENSE |
Indicate that you agree with our software license agreement. IMPORTANT: The only accepted value is
Yes. If omitted, the
installation will fail.EXAMPLE:
|
CREATE_FIREWALL_RULES |
Add the installed Security Center
applications to the Windows Firewall exceptions list. Accepted values are 0 and 1.
EXAMPLE: |
INSTALLDIR |
Specify the folder where the SDK package is installed. The default is
|
Sample command line
setup.exe /debuglog"C:\Users\Public\prereqinstall.log"
/s /v"/qn /l*v "C:\Users\Public\sdkmsi.log"
AGREETOLICENSE=Yes CREATE_FIREWALL_RULES=0 INSTALLDIR="C:\NewFolder""