The site control file provides a record of site configuration parameters. Each primary and secondary site has a unique master site control file (SITECTRL.CT0) located in the SMS\SITE.SRV\SITECFG.BOX directory. This file defines the site properties, including information such as the type of site, SMS service and SQL Server accounts, SMS domains and logon servers, SMS services and components, and specific site configuration options, such as inventory scanning intervals and SMS Client Setup options.
When site properties are modified, the Hierarchy Manager creates a temporary site control file (*.CT1), which is read by the Site Configuration Manager. The Site Configuration Manager overwrites SITECTRL.CT0 with the information in *.CT1 and creates another file named *.CT2, which is used to update the database.
The site control file begins with a line indicating the SMS build number and the syntax version number. For example:
SITE CONTROL FILE [786][1.08]
Additional sections then are used to define specific site properties. Section names in the site control file are typically grouped with a BEGIN and an END statement. For example, the following section defines the File Definition:
BEGIN_FILE_DEFINITION <2> <Setup-based site creation> <SKZ> <SKZ> <837492602> <1> END_FILE_DEFINITION
The following sections and entries are in the site control file:
These sections and entries are described in the following sections. In addition, a sample site control file is included in "Sample Site Control File" later in this chapter.
Provides information about the site control file.
File Type
The file type for site control can be one of the following:
File type | Description |
Actual (1) | Refers to a version of the site control file that contains the actual status of the site after completing the most recent changes. Such a file usually has a .CT2 extension. |
Proposed (2) | Refers to site control files that contain proposed changes for the site. These files have a .CT1 extension and are used by the Site Configuration Manager as a basis for reconfiguring the site. |
New site (3) | Used by SMS Setup to instruct Site Configuration Manager to begin creating a new site, either locally or remotely. |
Transactions (4) | Contains specific one-time instructions for the Site Configuration Manager. These files initiate changes to the site hierarchy. |
Local transactions (5) | Used by the Site Configuration Manager, Hierarchy Manager, and SMS Setup to pass along site upgrade or removal instructions within a site. |
Comment
The description of the operation that generated the file. For example:
Setup-based site creation
Target site
The site code for the site being modified.
Originating Site
The site code for the site that originated the site modifications.
GMT time stamp
The file creation time (using Greenwich Mean Time).
Posted/Not Posted
A value of 1 (posted) indicates that the file is used internally by the Hierarchy Manager. A 0 indicates no handling by the Hierarchy Manager.
A list of one-time transactions, usually a set of instructions to the Hierarchy Manager or Site Configuration Manager. If the file type is transactions only, this section will be the only other entry in the file. If there are no transactions to be done, this section is not present.
Transactions have the following format:
TRANSACTION<TransactionType><PersistentFlag><DWORDValue><String1><String2>
The TransactionType field is described in the following sections. The PersistentFlag field is used to indicate whether the transaction applies to all transactions or only to this transaction. The remaining 3 fields are data fields for the transactions.
The following transaction types are possible:
Change@
Transaction sent to change the SMS Service Account and password.
SqlChange@
Transaction sent to change the SQL Server account and password.
InactiveDomains, InactiveServers, InactiveComponents, InactiveSenders
These transactions are used by the Site Configuration Manager to report inactive items. A count of inactive items is displayed in the SMS Administrator; Windows NT and SMS events are also generated for each inactive item.
The first string in these transactions is a comma-separated list of up to 20 items. The second string is blank. The DWORD parameter gives a total count of inactive items of this type. For example:
TRANSACTION InactiveDomains<0><2><DomainX,DomainY><>
DeinstallSite
Transaction sent to the Site Configuration Manager to remove the site from the site hierarchy.
InitiateDeinstall
Transaction sent to the Hierarchy Manager to initiate the removal of a site from the site hierarchy.
InitiateUpgrade
Transaction sent to the Hierarchy Manager to initiate a site upgrade.
DeinstallSiteAck
Transaction sent by the Site Configuration Manager to indicate that it has successfully removed a site from the site hierarchy.
Shutdown
Transaction sent to the Site Configuration Manager to shut down (stop and remove) all SMS services in the site.
ShutdownAck
Transaction sent by the Site Configuration Manager when shutdown is completed.
Upgrade
Transaction sent to the Site Configuration Manager to upgrade files for SMS services at the site.
DeleteSite
Transaction sent whenever a site needs to be deleted from the site hierarchy in all parent site databases. Each Hierarchy Manager forwards this to its parent site until the top of the tree is reached. The site is deleted only if the parent site code matches.
SyncParentDetach
Transaction used by the Hierarchy Manager to synchronize a detachment from a parent site.
ParentDetach
Transaction forwarded up the site hierarchy to detach from a parent site.
Heartbeat
Transaction sent in a site control file every 24 hours.
RequestNewSCFile
Transaction sent when the Site Configuration Manager detects no master site control file (SITECTRL.CT0).
TriggerWatchdog
Transaction that causes the Site Configuration Manager to do a watchdog cycle.
TriggerWatchdogHeartbeat
Transaction that causes the Site Configuration Manager to do a watchdog cycle and write a CT2 status file with a heartbeat transaction.
TriggerUserGroupMIF
Transaction that causes the Site Configuration Manager to do a watchdog cycle and write a user group MIF file.
TriggerLogonScriptConfig
Transaction that causes the Site Configuration Manager to do a watchdog cycle and modify logon scripts as specified by the Automatically Configure Logon Scripts setting.
LogEventForBootstrap
This transaction causes the Hierarchy Manager to log an event on behalf of the Bootstrap service.
SMSBaseID
Transaction sent by the Site Configuration Manager to log the last used SMS ID range from a previous SMS installation (if applicable).
NoEnumeration
Transaction sent to the Site Configuration Manager to suppress the enumeration of user groups.
Describes SMS account and configuration information.
SiteType
Defined by the following values:
Site Type | Value |
9 | Secondary site |
6 | Primary site |
Site code
A three-character code that the SMS system uses to identify the site. The site code for any site must be unique across the SMS system. It is not case sensitive.
Parent site code
A three-character code that the SMS system uses to identify the parent site. This field is blank if the site does not have a parent site.
Site server
The name of the site server.
Site server domain
The Windows NT domain to which the site server belongs.
Site name
The name of the site.
Installation directory at the site
The path and directory name containing SMS files.
Service account domain name
The name of the domain that contains the SMS service account.
Service account name
The encrypted name for the SMS Service Account.
Password
The encrypted password for the SMS Service Account.
Public encryption key
The security mechanism used by SMS.
SQLServer name
The location of the SQL Server database that services the site.
SQL Login account
The encrypted login account for the SQL Server.
SQL Login password
The encrypted password for the SQL login account.
SQL database name
The name of the SQL Server database specified during SMS Setup.
SQL public encryption key
The security mechanism for SQL Server operations.
User name
The name the user entered during SMS Setup.
Organization
The name of the organization that the user entered during SMS Setup.
Properties are various configurations used by different components. Property definitions include the property name followed two optional strings and a mandatory DWORD integer. (The DWORD value is 0 if there is no flag.) The following example uses two strings but no flag:
PROPERTY <User And Organization><AlexanderSeth><Siblings Inc><0>
Site Server Platform
The hardware platform (Intel, MIPs, RISC, and so on) of the site server. For example:
<Site Server Platform><INTEL X86><><0>
Site Server Language
The language platform of the site server (English, French, and so on). For example:
<Site Server Language><english><><0>
Last Valid @
The most recently known valid service password. The encrypted user name and password are defined by the first and second strings, respectively. The DWORD parameter contains the time stamp when the user name and password were created.
Last Valid SQL @
The last valid password for the SQL Server. The encrypted user name and password are defined by the first and second strings, respectively. The DWORD parameter contains the time stamp when the user name and password were created.
Hardware Scan/Software Scan
Two separate properties that define the frequency at which hardware and software scans occur. The frequency is defined using one of the following values:
Value | Scan frequency |
1 (always) | A scan occurs each time a log on occurs. |
2 (daily) | A scan occurs at most once a day. |
3 (interval) | The property HardwareScanInterval (or SoftwareScanInterval) is also defined, and a scan occurs at most once during that interval. |
Hardware Scan Interval/Software Scan Interval
Two separate properties that define the scan interval (in days).
User and Organization
The user name and company name specified during the site installation. For example:
<User And Organization><SaraElizabeth><Siblings Inc><0>
SNA Local Address
Defines the local LU alias for the SNA Sender. For example:
<SNA Local Address><MYLU1234><><0>
Note
When creating an LU alias for use with the SNA Sender, do not use numerals in the first position; numerals are allowed in positions 2 through 8 only.
Service Response
Indicates the monitoring mode for the SMS services. The faster the response rate, the heavier the system load. The following values are possible:
Value | Monitoring mode |
1 | Test (1 minute) |
2 | Fast (5 minutes) |
3 | Medium (15 minutes) |
4 | Slow (30 minutes) |
Slow Net Strategy
Specifies how SMS clients at the site report their inventory when they have a slow communications link to their SMS logon server. This setting applies to all clients in the site. The following values are possible:
Value | Meaning |
1 | Clients always report their inventory to the SMS logon server, even if the Inventory Agent detects a slow network. |
2 | The Inventory Agent prompts the user if it detects a slow network. A message box requests permission for Inventory Agent to scan the client and report any inventory changes to the SMS logon server. |
3 | The Inventory Agent does not scan when it detects a slow network. |
Client Config Manager On Servers
Specifies where the Client Configuration Manager service is running. The following values are possible:
Flag | Meaning |
0x00000001 | The Client Configuration Manager is automatically installed on the site server. |
0x00000002 | The Client Configuration Manager is automatically installed on all SMS logon servers (if there is an agent for that type of server). |
0x00000004 | The Client Configuration Manager is automatically installed on all helper servers. |
Package Command Manager on Servers
Specifies where the Package Command Manager service is running. The following values are possible:
Flag | Meaning |
0x00000001 | The Package Command Manager is automatically installed on the site server. |
0x00000002 | The Package Command Manager is automatically installed on all SMS logon servers (if there is an agent for that type of server). |
0x00000004 | The Package Command Manager is automatically installed on all helper servers. |
Inventory Agent On Servers
Specifies where the Inventory Agent service is running. The following values are possible:
Flag | Meaning |
0x00000001 | The Inventory Agent is automatically installed on the site server. |
0x00000002 | The Inventory Agent is automatically installed on all SMS logon servers (if there is an agent for that type of server). |
0x00000004 | The Inventory Agent is automatically installed on all helper servers. |
PCM Polling
Specifies, in minutes, how frequently the Package Command Manager checks for new packages. This DWORD value applies to all clients but it can be overridden at an individual client through the Package Command Manager user interface.
LogonScripts
Indicates whether SMS is configured to alter logon scripts automatically. The following values are possible:
Flag | Meaning |
0x00000000 | Do not automatically configure workstation logon scripts. |
0x00000001 | The Automatically Configure Workstation Logon Scripts option is enabled. |
0x00000002 | When existing logon scripts are automatically configured, SMS adds them at the bottom of the script. |
Client Installation
Indicates whether SMS modifies the AUTOEXEC.BAT file on clients. The following values are possible:
Flag | Meaning |
0x00000001 | Install Package Command Manager. |
0x00000002 | Automatically start Package Command Manager. |
0x00000008 | Install Program Group Control. |
0x00000010 | Automatically start Program Group Control. |
0x00000020 | Install Help Desk. |
0x00000040 | Automatically start Help Desk. |
0x00000100 | Install MIF Entry. |
0x00000200 | Automatically start MIF Entry. |
Version
The version of SMS software specified by SMS Setup. For example:
<version><549><><0>
Default Package Server
Always set to Default Package Server.
Account Checking
Indicates whether SMS should attempt to validate the SMS Service Account before using it to install the SMS services. This property is currently used by SMS Setup only. The following values are possible:
Value | Meaning |
1 | Account checking is enabled for the site. |
0 | Account checking is disabled. |
Remote Control Install Video Driver
Indicates whether or not to install support for the IDIS_NT.DLL remote control video driver.
Value | Meaning |
0 | Do not install support for the remote control video driver. |
1 | Install support for the remote control video driver. |
Remote Control Command Line
Indicates the remote control command line to run on Windows NT clients. This command line lets you specify the default protocol and Lana number to be used on the clients.
GlobalUserGroupEnum
Indicates whether user group enumeration will be performed. The following values are possible:
Flag | Meaning |
0x00000000 | Enumerate the user groups. |
0x00000001 | Do not enumerate the user groups. |
Contains miscellaneous information about the site.
DOMAINTYPE
Supported domain types.
ADRSTRFMT
Supported sender address string types.
SoftwareUnits
Currently installed software units.
Remote Control Permitted Viewers
List of users and user groups that can remotely control Windows NT computers in the site.
Remote Control Supported Video Drivers
List of video adapters supported for accelerated screen transfer mode (valid only for computer running Windows NT).
NET_PROVIDERS
List of network provider types in the site. May include sub-lists.
Desktop Services
List of services installed on SMS logon servers.
Logon Script Files
A list of files used by the SMS logon script.
TrapFilter number
A description of each SNMP trap filter that has been defined in the site.
Describes each SMS domain that participates in the site hierarchy.
Domain name
The name of the SMS domain.
Domain type
Specifies either Windows NT, LAN Manager, or NetWare.
Autoenumerate SMS logon servers
A 1 indicates that SMS is configured to autoenumerate SMS logon servers. A 2 indicates a user-defined list of servers and is followed by the SMS logon server list.
Logon server
SMS logon servers in the domain.
Contains information about the site addresses. The format of the address string is:
ADDRESS <Originating Site Code><Destination Site Code><Sender Type><Address string format><Address String>
The sender type can be LAN Sender, SNA Sender, or RAS Sender. The address string format also refers to a sender type.
The address string begins with a number that indicates how many address characters are to be read in the rest of the string that follows. Most of the address string is encrypted because it contains passwords.
An Outbox entry exists for each defined sender. The format of the outbox string is:
OUTBOX <Outboxname><Drive><Address string format><Schedule string> <CreateFlag><Server name>
Various types of auxiliary servers are specified in this section. The format for the server string is:
SERVER <Server name><Server type><Flags><Install drive letter>
Describes each of the Windows NT services (or their subcomponents) required by SMS.
Installation flags
The following table lists and describes the service installation flags.
Service | Flag | Description |
INSTALL | 0x00000001 | Install this component. |
LOCALSYSACCT | 0x00000002 | If this is a service, install it on the SMS logon server as a system account (instead of the SMS Service Account). |
STARTSERVICE | 0x00000004 | Start this component if it is stopped. |
SETREGISTRY | 0x00000008 | Configure the initial SMS registry values for this component. |
EXE | 0x00000010 | Not currently used. |
LITERALPATH | 0x00000020 | The file ID for this component is a full path to the executable file instead of an ID in the system map file. |
PRIMARYSITE | 0x00000040 | Install this component if the site is a primary site. |
SECONDARYSITE | 0x00000080 | Install this component if the site is a secondary site. |
AUTOSTART | 0x00000100 | If this is a service, install it to start automatically during system startup. |
SENDER | 0x00000200 | This component is a sender. |
OPTIONALSVC | 0x00000400 | This component is optional at this site. |
AS_THREAD | 0x00000800 | This component runs under the control of SMS Executive. |
DONTSTOPSVC | 0x00001000 | This service is not stopped or removed during a site shutdown or site removal. |
Service or thread name
The name of the service or component, such as SMS_EXECUTIVE or SMS_DESPOOLER.
File ID of the service or subcomponent
This ID is used to look up the list of file names in the system map file to determine the executable files (EXEs and DLLs) for this component.
Server on which to install the component
The name of the site server or a helper server where this component should be installed.
Drive on which to install the service
The drive letter to which the executable files are copied when the component is installed on the server named in the preceding entry.
Describes the senders in use at the site. Senders are similar to components but have special characteristics, such as the type of address format they support and the outboxes they monitor.
Installation flags
See the Installation flags entry in "COMPONENT," earlier in this chapter.
Address string format type
The type of address format that this sender understands and, therefore, the type of outbox it uses. For example, MS_LAN_SENDER.
File ID of the sender
This ID is used to look up the list of file names in the system map file to determine the executable files (EXEs and DLLs) for the sender.
Drive on which to install
The drive letter where the executable files are copied to when the sender is installed on the server named in the next entry.
Server on which to install
The name of the site server or helper server where this sender should be installed.
Sender name
The name of the sender. For example, SMS_LAN_SENDER.
Outbox
The outbox the sender is monitoring.