Export (0) Print
Expand All

Unattended Setup Overview

Applies To: System Center Configuration Manager 2007, System Center Configuration Manager 2007 R2, System Center Configuration Manager 2007 R3, System Center Configuration Manager 2007 SP1, System Center Configuration Manager 2007 SP2

You can run Configuration Manager Setup unattended by supplying setup.exe with an initialization file using the /script setup command-line option. Unattended setup is supported only for new installations of Microsoft System Center Configuration Manager 2007 primary sites, secondary sites, and Configuration Manager consoles.

To use the /script setup command-line option, you must create an initialization file and specify the initialization file name after the /script setup command-line option. The name of the file is unimportant as long as it has the .ini file name extension. When referencing the setup initialization file from the command line, you must give the full path to the file. For example, if your setup initialization file is named setup.ini and it is stored in the C:\setup directory, your command line would be:

setup /script c:\setup\setup.ini.

The setup initialization file supplies the same kind of information that the Configuration Manager Setup Wizard prompts for during attended installations, except that there are no default settings; all values must be specified for the setup keys that apply to the type of installation you are performing.

noteNote
This document describes how to use a separate instruction file to automate Configuration Manager 2007 Setup. For information about command-line options available when running Configuration Manager 2007 Setup, see Setup Command Line Options.

The scripted installation initialization file contains section names, key names, and values. Required section key names vary depending on the installation type you are scripting. The order of the keys within sections, and the order of sections within the file, is not important. The keys are not case sensitive; some data is case sensitive as indicated in the following tables. When supplying values for keys, the name of the key should be followed by an equals sign (=) and the value for the key.

The following tables describe each of the setup initialization file keys, their corresponding values, whether or not they are required, which type of installation they are used for, and a short description of the key:

For examples of unattended Setup initialization files, see Scripted Installation Examples.

Unattended Setup Initialization File Keys

Unattended Setup Initialization File Keys for the [Identification] Section

 

Key Name Required Values Installation Type Description

Action 

Yes

InstallPrimarySite

Primary site

Installs a primary site

 

 

InstallAdminUI

InstallAdminUI

Installs a Configuration Manager console

 

 

InstallSecondarySite

Secondary site

Installs a secondary site

Unattended Setup Initialization File Keys for the [Options] Section

 

Key Name Required Values Installation Type Description

ProductID

Yes

 

Primary site

ConfigMgr console

xxxxx-xxxxx-xxxxx-xxxxx-xxxxx format.

PrerequisiteComp

Yes

0 or 1 (0 for no, 1 for yes)

Primary site

Secondary site

Indicates whether or not updated client prerequisite files have already been downloaded.

PrerequisitePath

Yes

<path to files>

Primary site

Secondary site

Path to either the location of pre-downloaded updated client prerequisite files or where to store files to be downloaded.

SiteCode

Yes

 

Primary site

Secondary site

Three alpha-numeric characters that will uniquely identify the site in your hierarchy.

SiteName

Yes

 

Primary site

Secondary site

Description for this site.

ParentSiteCode

Yes

Secondary site

ConfigMgr console 

Site code of the parent site of the secondary site to be installed.

ParentSiteServer

Yes

Secondary site

Server name of the parent site of the secondary site to be installed.

AddressType

Yes

MS_ASYNC_RAS

MS_ISDN_RAS

MS_LAN

MS_SNA_RAS

MS_X25_RAS

Secondary site

Specifies the type of address to be used as the default address to the parent site.

LanUser

No

Secondary site

The account name for the Standard Sender account to be used at this site.

LanUserPassword

No

Secondary site

The password for the account specified for LanUser.

RasUser

No

Secondary site

The account name for the RAS Sender account to be used at this site.

RasUserDomain

No

Secondary site, if installing a RAS Sender

The domain in which the RasUser account was created.

RasUserPassword

No

Secondary site, if installing a RAS Sender

The password for the account specified for RasUser.

RasPhoneBook

No

Secondary site, if installing a RAS Sender

A RAS phone book name for the RAS Sender to use.

SMSInstallDir

Yes

 

Primary site

Secondary site

ConfigMgr console

Directory to install the Configuration Manager program files.

ManagementPoint

No1

 

Primary site

Server name of the computer to be used as the default management point for this site.

ImportantImportant
The server name must be in upper case.

DistributionPoint

No

0 or 1 (0 for no, 1 for yes)

Primary site

Secondary site

Specifies whether or not to install a distribution point on the site server during setup.

SDKServer

Yes

 

Primary site

Computer to install the SMS Provider on for primary site installations and the computer name hosting the SMS Provider for ConfigMgr console installations.

ImportantImportant
The server name must be in upper case.

ClientAgents2

No

SINV

Primary site

Software inventory client agent.

 

No

HINV

Primary site

Hardware inventory client agent.

 

No

ADPROG

Primary site

Advertised programs client agent.

 

No

NAP

Primary site

Network Access Protection (NAP) client agent.

 

No

SUM

Primary site

Software update management client agent.

 

No

SWM

Primary site

Software metering client agent.

 

No

DCM

Primary site

Desired configuration management client agent.

 

No

RT

Primary site

Remote tools client agent.

SiteSecurityMode

No3

Native

Primary site

Installs the site in native mode.

 

No

Mixed

Primary site

Installs the site in mixed mode.

Port

No

[user defined custom port]

Primary site

Specifies if the site will use a custom TCP/IP port. If the SiteSecurityMode option is set to Native, the port specified will be set to https. If SiteSecurityMode option is set to Mixed, the port specified will be set to http.

SiteServerSignCert

Yes4

 

Primary site

Site server signing certificate thumbprint (spaces must be removed if you are copy and pasting the thumbprint from the certificate properties).

1 If this setting is not provided for unattended primary site installations, the site will not have a management point installed when setup completes and will be unable to manage clients until a management point is installed.

2If the ClientAgents key is omitted, default Setup client agent settings are used (all client agents are enabled except for NAP). This setting is used to enable less client agents than are enabled by default as part of Configuration Manager Setup. When using the ClientAgents key to enable multiple client agent settings during an unattended Setup, each client agent value should be separated by a comma. For example, ClientAgents=SINV,HINV,ADPROG,NAP,SUM,SWM,DCM,RT.

3 The site will be installed in mixed mode if this key is not specified.

4 This key is required only if the SiteSecurityMode key is set to native mode.

Unattended Setup Initialization File Keys for the [SQLConfigOptions] Section

 

Key Name Required Values Installation Type Description

SQLServerName 

Yes

 

Primary site

The name of the server, or clustered instance name, running SQL Server that will host the site database.

ImportantImportant
The server name must be in upper case.

CreateSQLDevice

Yes

0 or 1 (0 for no, 1 for yes)

Primary site

Indicates whether or not Setup should create the database.

DatabaseName

Yes

<site database name>

Primary site

The name of the SQL Server database to create or use to install the primary site database.

See Also

For additional information, see Configuration Manager 2007 Information and Support.
To contact the documentation team, email SMSdocs@microsoft.com.
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2015 Microsoft