Running an Unattended Setup
You can create an SMS Setup initialization file to run an unattended setup. Specify this file when using the Setup command /script option. This file supplies the same kind of information that the SMS Setup Wizard prompts for, 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 using.
Caution
- All accounts and passwords are listed in the Setup.ini file. It is important that you restrict unauthorized access by manually setting the permissions on this file after you have created it.
Tables 15.4 through 15.6 describe each of the setup keys in an SMS Setup initialization file and their corresponding values. Each key description specifies the type of installation that requires that key.
The order of the keys within sections, and the order of sections within the file, is not important. Also, the keys and data are not case-sensitive.
The SMS Setup initialization file contains four sections. Each of the following tables describes the keys in one of the sections:
Table 15.4: [Identification] section
Table 15.5: [Options] section
Table 15.6: [SQLConfigOptions] section
For an example of an SMS initialization file, see the "Example of an SMS Initialization File" section later in this chapter.
Table 15.4 SMS Setup Initialization File Keys for the [Identification] Section
Key |
Description |
Used in this type of installation |
Action |
InstallAdminUI. Installs only the SMS Administrator console. InstallPrimarySite. Installs a primary site. InstallSecondarySite. Installs a secondary site. |
All |
Table 15.5 SMS Setup Initialization File Keys for the [Options] Section
Key |
Description |
Used in this type of installation |
|---|---|---|
AddressType |
Specifies that one of the following types of addresses is to be used as the default address to the secondary site from its parent site: MS_ASYNC_RAS. For RAS communication over an asynchronous line. MS_ISDN_RAS. For RAS communication over an ISDN line. MS_LAN. For communication over a LAN, and over a WAN when routers connect multiple LANs. MS_SNA_RAS. For RAS communication over an SNA link. MS_X25_RAS. For RAS communication over an X.25 line. |
Secondary |
AllClientOptionsOn |
Enables all client agents and options. |
Primary |
FullName |
The name of a person under whom this product will be registered. (This is the same as the Name field on the Product Registration page of the SMS Setup Wizard.) |
All |
LanUser |
The account name for the Standard Sender account to be used at this site. |
Secondary |
LanUserPassword |
The password for the account specified for LanUser. |
Secondary |
NumberOfAdminUI |
Specifies the maximum number of SMS Administrator consoles that the site can have running simultaneously. A good number is 5. |
Primary |
NumOfClients |
Specifies the maximum number of clients that the site can simultaneously support. |
Primary and secondary |
OptionalUnits |
Specifies one or more of the following SMS components, in a comma-separated list (no spaces): Remote Control (called Remote Tools in the SMS Setup Wizard): Allows the administrator to control remote computers over the network. The remote computer's desktop is displayed on your screen, allowing you to run its programs, examine its logs, and restart. Scripts (called Package Automation Scripts in the SMS Setup Wizard): Ready-made scripts to automate the installation and configuration of many popular software programs. |
Primary and secondary |
OrgName |
The organization name under which this product will be registered. (This is the same as the Organization field on the Product Registration page of the SMS Setup Wizard.) |
All |
ParentSiteCode |
Specifies the site code of the site that will be the new secondary site's parent site. |
Secondary |
ParentSiteServer |
Specifies the network name of the site server of the new secondary site's parent site. |
Secondary |
ProductID |
The 10-digit key from the yellow sticker on the SMS CD case. |
All |
RasUser |
The account name for the RAS Sender account to be used at this site. |
Secondary |
RasUserDomain |
The domain in which the RasUser account was created. |
Secondary, if installing a RAS Sender |
RasUserPassword |
The password for the account specified for RasUser. |
Secondary, if installing a RAS Sender |
RasPhoneBook |
A RAS phone book name for the RAS Sender to use. |
Secondary, if installing a RAS Sender |
SDKServer |
Specifies a server where the SMS Provider will be installed. |
Primary |
SecurityMode |
Specifies the security mode: Advanced: This mode relies on using the local system context to run services and the computer accounts to communicate between servers. With advanced security, the user accounts are not applicable. Standard: On the site server, SMS services run under a user-specified service account. |
Primary |
ServiceAccount |
Specifies a user account to be used as the SMS Service account at this site. |
Primary and secondary |
ServiceAccountDomain |
The domain in which the SMS Service account was created. |
Primary and secondary |
ServiceAccountPassword |
The password for the SMS Service account. |
Primary and secondary |
SiteCode |
Three characters that will be the new site's site code. |
Primary and secondary |
SiteDomain |
The domain containing the site server. |
Primary and secondary |
SiteName |
The new site's name (with a 50 character limit). |
Primary and secondary |
Table 15.6 SMS Setup initialization file keys for the [SQLConfigOptions] section
Key |
Description |
Used in this type of installation |
|---|---|---|
AutoConfigSqlConnections |
1 to automatically configure SQL Server connections, 0 to not automatically configure. |
Primary |
DatabaseName |
A name for the SMS site database, such as SMS_ABC. (SMS_<site code> is a good choice if you have more than one site.) If you choose to have SMS Setup install SQL Server for you, SMS Setup specifies the database name. This is because SQL Server is considered as a dedicated SQL Server for SMS. |
Primary |
NumberOfSqlConnections |
The number of simultaneous connections that your SMS site database can have. A recommended number is 75. |
Primary |
SQLLoginID |
A SQL Server account for accessing the SMS site database. This account must already exist (SMS Setup does not create it) and have SQL Server system administrator (sa) permissions. |
Primary |
SQLLoginPassword |
The password for the account specified for SQLLoginID. |
Primary |
SQLServerName |
The name of the computer running the instance of SQL Server that contains the SMS site database for this site. |
Primary |
SQLServerVersion |
The version of SQL Server that will contain the SMS site database. Additionally, the version of SQL Server that will be installed by SMS Setup if 1 was specified for InstallSQLServer in the [Options] section. |
Primary |
UseSQLIntegrated Security |
1 to have SMS use Windows authentication mode when accessing the SMS site database, 0 to not use it. |
Primary |
Example of an SMS Initialization File
The following is an example of an SMS initialization file.
[Identification] Action=InstallPrimarySite [Options] FullName=Sam Woodman OrgName=Microsoft ProductID=123-4567890 SiteCode=FIN SiteName=Finance SiteDomain=Seattle SecurityMode=Standard ServiceAccount=smsadmin ServiceAccountDomain=Seattle ServiceAccountPassword=Animal$Cracker27 NumOfClients=100 OptionalUnits=Remote Control SMSInstallDir=D:\SMS InstallSQLServer=0 NumberOfAdminUI=5 SDKServer=Rainy [SQLConfigOptions] SQLServerName=Rainy SQLServerVersion=7.0 UseSQLIntegratedSecurity=0 SQLLoginID=sa SQLLoginPassword=Harpo&Chico CreateSQLDevice=1 DatabaseName=SMS_FIN DatabaseDevice=SMSdata_FIN LogDevice=SMSlog_FIN SQLDevicePath=F:\MSSQL\SMSDATA NumberOfSqlConnections=75 AutoConfigSqlConnections=1
For More Information
Did you find this information useful? Please send your suggestions and comments about the documentation to smsdocs@microsoft.com.