Setup Configuration Files
Applies To: Forefront Endpoint Protection
Setup configuration files are XML files that can contain the following items:
A common parameters section
One or more sections which correspond to a Forefront Endpoint Protection server role
This topic describes these sections and their corresponding parameters.
Important
If any mandatory sections or parameters are not specified, Setup fails and an error is logged in the setup log file. For more information about setup log files, see Validating the Installation.
Sections
The following table describes the sections that can be specified in a setup configuration file.
Section name | Advanced topology option | Required? | Description |
---|---|---|---|
FepCommon |
Not applicable |
Mandatory |
This section contains parameters that are common to all installations. |
FepSiteServer |
Configuration Manager Site Server FEP 2010 Extension |
Optional |
Specifying this section instructs Setup to install the FEP site server extension. This section does not contain any parameters. |
FepReportingRole |
FEP 2010 Reporting and Alerts |
Optional |
Specifying this section instructs Setup to install the FEP reporting and alerts role. This section contains mandatory parameters for configuring the role. For more information, see "FepReportingRole" later. |
FepConsoleExtension |
Configuration Manager Console Extension for FEP 2010 |
Optional |
Specifying this section instructs Setup to install the FEP console extension. This section does not contain any parameters. |
FepCommon
The following table describes the parameters that can be defined in the FepCommon section of a setup configuration file.
Parameter name | Required? | Description |
---|---|---|
Organization |
Mandatory |
The name of the organization that owns the Microsoft Forefront Endpoint Protection license. |
UserName |
Mandatory |
The name of a user who performs the installation. |
ProductKey |
Mandatory |
Specify the product key that corresponds to the version of FEP you are installing. The following list shows the supported values:
|
AcceptEula |
Mandatory |
For installation to succeed, you must accept the End User License Agreement by setting this parameter to True. |
MuOptin |
Mandatory |
If you want Microsoft Updates to keep your installation up-to-date, set this parameter to True. |
SqmOptin |
Mandatory |
If you want to participate in the Customer Experience Improvement Program, set this parameter to True. |
SpyNetOptin |
Mandatory |
Specifies the Microsoft SpyNet membership level. The following list shows the supported values:
|
InstallDir |
Optional |
The root folder for the installation. The default path is %ProgramFiles%. |
FepSiteServer
This section does not contain any parameters.
FepReportingRole
The following table describes the parameters that can be defined in the FepReportingRole section of a setup configuration file.
Parameter name | Required? | Description |
---|---|---|
SCCMSiteServer |
Optional/Mandatory |
When installing on a computer that is not the Configuration Manager site server, this parameter is mandatory and must contain the name of the site server. |
FepDbName |
Optional |
Specifies the name of the FEP auxiliary database that resides on the same SQL Server computer and instance as the Configuration Manager database. The default database name is FEPDB_XXX, where XXX is the Configuration Manager site code. |
FepReportingDbServerName |
Optional |
Specifies the name of the SQL Server computer to use for the FEP reporting database. The default value is the name of the SQL Server computer used for the Configuration Manager database. |
FepReportingDbInstanceName |
Optional |
Specifies the name of the SQL Server instance for the FEP reporting database. The default value is the name of the SQL Server instance used for the Configuration Manager database. |
FepReportingDbName |
Optional |
Specifies the name of the FEP reporting database. The default database name is FEPDW_XXX, where XXX is the Configuration Manager site code. |
FepReportingDbAllowReuse |
Optional |
Specify this parameter to reuse an existing FEP reporting database. If you specify this parameter, you must use the original database name and verify that it exists on the specified SQL Server instance on the specified SQL Server computer. |
FepReportUrl |
Optional |
The management URL of the SQL Server Reporting Services in the following format: https:// <ReportingServer> /Reportserver where <ReportingServer> is the name of the computer running SQL Server Reporting Services. The <ReportingServer> for the default value is determined in the following order:
|
FepReportUsername |
Mandatory |
The user name that is used by SQL Server Reporting Services to connect to the FEP reporting database. |
FepReportPassword |
Mandatory |
The password that corresponds to the user name specified in the FepReportUsername parameter. Important Because the password is stored in plain text, it is recommended that you set a temporary password for this user account during installation. This will also require the manual changing of the password in the report data source. This can be performed using the SQL Server Reporting Services web interface. |
FepConsoleExtension
This section does not contain any parameters.
Examples
The following are examples of configuration files that correspond to the following installation options:
Basic topology
Basic with remote reporting database
Basic Topology Option
The following is the setup configuration file that corresponds to the actions performed when installing using basic setup.
<UnAttend xmlns:xsi="https://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="https://www.w3.org/2001/XMLSchema">
<FepCommon>
<Organization>Contoso Pharmaceuticals</Organization>
<UserName>Corbin, Jim</UserName>
<ProductKey>03082-270-0001260-04309</ProductKey>
<AcceptEula>true</AcceptEula>
<MuOptin>true</MuOptin>
<SqmOptin>true</SqmOptin>
<SpyNetOptin>Basic</SpyNetOptin>
</FepCommon>
<FepSiteServer />
<FepConsoleExtension />
<FepReportingRole>
<FepReportUsername>contoso\jcorbin</FepReportUsername>
<FepReportPassword>TemporaryReportPassword</FepReportPassword>
</FepReportingRole>
</UnAttend>
Basic with a Remote Reporting Database Option
The following is the setup configuration file that corresponds to the actions performed when installing using basic setup with a remote reporting database.
<UnAttend xmlns:xsi="https://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="https://www.w3.org/2001/XMLSchema">
<FepCommon>
<Organization>Contoso Pharmaceuticals</Organization>
<UserName>Corbin, Jim</UserName>
<ProductKey>03082-270-0001260-04309</ProductKey>
<AcceptEula>true</AcceptEula>
<MuOptin>true</MuOptin>
<SqmOptin>true</SqmOptin>
<SpyNetOptin>Basic</SpyNetOptin>
</FepCommon>
<FepSiteServer />
<FepConsoleExtension />
<FepReportingRole>
<!-—It is recommended that you add the Site Code to database names in order to avoid database name conflicts -->
<FepDbName>MyDb_CON</FepDbName>
<FepReportingDbServerName>ReportingServer.contoso.com</FepReportingDbServerName>
<FepReportingDbInstanceName>MyNamedInstance</FepReportingDbInstanceName>
<FepReportUrl>https://SrsServer.contoso.com/ReportServer</FepReportUrl>
<FepReportingDbName>MyDw_CON</FepReportingDbName>
<FepReportUsername>contoso\jcorbin</FepReportUsername>
<FepReportPassword>TemporaryReportPassword</FepReportPassword>
</FepReportingRole>
</UnAttend>