The SYSTEM.MAP file lists the platforms, languages, directories, and files that SMS can use. It tells SMS Setup which directories to create for specific language IDs and platforms. SMS Setup uses the SYSTEM.MAP file to copy files and directories from the Microsoft Systems Management Server version 1.2 compact disc to the site server disk. The Maintenance Manager uses the SYSTEM.MAP file to create copy-list files; these files are used to specify the files that should be copied to clients. Copy-list files are copied to each type of client that SMS supports.
The SYSTEM.MAP file is located in the SMSSETUP directory on the Microsoft Systems Management Server version 1.2 compact disc. For an installed site, it is located in the SMS root directory on the site server. Because the SYSTEM.MAP file is used by SMS to control site configuration, this file should not be modified.
The SYSTEM.MAP file contains the following sections:
These sections provide mappings from one or more items to a single keyword; for instance, the following IDList maps the substrings that can be used to indicate the Intel x86 platform:
IDLIST "INTEL X86" = "386", "486", "PENTIUM", "X86"
The sections in the SYSTEM.MAP file are described next.
Platforms
List of supported platforms (CPU architectures). SMS 1.2 supports Intel, DEC Alpha, MIPS, and Macintosh platforms. This is indicated in the following line which appears in the SYSTEM.MAP file for the U.S. English version of SMS 1.2:
PLATFORMS = "INTEL X86", "DEC ALPHA", "MIPS R4000", "MAC 68000"
Copylists
Each entry indicates a client group for which files must be copied. For instance, in the following COPYLISTS section, the WIN95:PCM entry indicates the copy-list to be used to copy files to a Windows 95 client if the Package Command Manager is to be installed.
The COPYLISTS entry from the SMS version 1.2 SYSTEM.MAP file follows:
COPYLISTS = "DOS:STANDARD", "DOS:PCM", "DOS:REMOTE_CONTROL",
"DOS:REMOTE_CONTROL_386", "DOS:REMOTE_CONTROL_NETWARE",
"DOS:REMOTE_CONTROL_LANMAN", "DOS:MIFENTRY", "WIN16:STANDARD",
"WIN16:PCM", "WIN16:APPCONTROL", "WIN16:REMOTE_CONTROL",
"WIN16:REMOTE_CONTROL_386", "WIN16:REMOTE_CONTROL_NETWARE",
"WIN16:REMOTE_CONTROL_LANMAN", "WIN16:MIFENTRY", "WIN95:APPCONTROL",
"WIN95:STANDARD", "WIN95:PCM", "WIN95:REMOTE_CONTROL",
"WIN95:REMOTE_CONTROL_386", "WIN95:REMOTE_CONTROL_NETWARE",
"WIN95:REMOTE_CONTROL_LANMAN", "WIN95:MIFENTRY", "WIN95:LANMAN",
"WIN95:NETWARE", "OS2:STANDARD", "OS2:PCM", "OS2:MIFENTRY",
"WINNT:REMOTE_CONTROL", "WINNT:STANDARD", "WINNT:PCM",
"WINNT:APPCONTROL", "WINNT:MIFENTRY", "WIN16:LANMAN",
"WIN16:NETWARE", "DOS:LANMAN", "DOS:NETWARE", "WINNT:LANMAN"
Languages
List of languages supported by this version of SMS. For example, the following line is included in the SYSTEM.MAP file for the U.S. English version of SMS 1.2:
LANGUAGES = "ENGLISH"
Units
List of the valid installable software units for this version of SMS. This information is used by SMS Setup to properly configure the site. The UNITS entry from the SMS version 1.2 SYSTEM.MAP file follows:
UNITS = "ALPHA SERVER", "MIPS SERVER", "INTEL SERVER", "INTEL CLIENT", "ALPHA CLIENT",
"MIPS CLIENT", "MACINTOSH CLIENT", "SCRIPTS", "INTEL SMS ADMINISTRATOR",
"ALPHA SMS ADMINISTRATOR", "MIPS SMS ADMINISTRATOR", "INTEL NETWORK MONITOR",
"ALPHA NETWORK MONITOR", "MIPS NETWORK MONITOR"
IDList
Define new associations to be used by the SMS system. For instance, IDLists define the default platforms, languages, CPU identifiers, directories, allowable installation or upgrade options, and so on. A sampling of the IDLists that appear in the SMS version 1.2 SYSTEM.MAP file follows:
IDLIST "BUILDNUMBER" = "786" IDLIST "SPNUMBER" = "" IDLIST "SYSMAPVERSION" = "786", "FINAL", "SMS V1.2", "FULL" IDLIST "SMSVERSIONINFO" = "V1.2", "712" IDLIST "LANGUAGE_DEFAULT" = "ENGLISH" IDLIST "PLATFORM_DEFAULT" = "INTEL X86" IDLIST "PERMITTED_UPGRADES" = "479:479", "521:531", "531:786" IDLIST "INTEL X86" = "386", "486", "PENTIUM", "X86" IDLIST "DEC ALPHA" = "ALPHA", "DEC", "DIGITAL" IDLIST "MIPS R4000" = "R4000", "R4400", "MIPS", "RPC 44", "ARCSBIOS" IDLIST "MAC 68000" = "MAC", "APPLE", "68000" IDLIST "PLATFORM_DIRECTORY" = "INTEL X86=X86.BIN", "DEC ALPHA=ALPHA.BIN", "MIPS R4000=MIPS.BIN", "MAC 68000=MAC.BIN"
Service
Defines how to install the SMS services. The Service sections use the BEGIN and END keywords. They also use the FLAGS, MAIN, and SUBCOMPONENT keywords, as follows:
· The FLAGS keyword is used to indicate how the service should be installed and configured. See the following table to interpret the Flag bits.
· The MAIN keyword is used to indicate the primary executable file associated with the service or component.
· The SUBCOMPONENT keyword is used to indicate the secondary executable files associated with the service or component.
The following is an example of the Service entry for the SMS service, SMS_ASYNC_RAS_SENDER.
SERVICE "SMS_ASYNC_RAS_SENDER"
BEGIN
FLAGS = 3789
MAIN "SENDER.DLL"
SUBCOMPONENT "CONNRAS.DLL"
END
The following table lists the service flag bits.
Service | Flag | Description |
INSTALL | 0x00000001 | Installs this component. |
LOCALSYSACCT | 0x00000002 | If this is a service, installs it on the SMS logon server as a system account instead of the SMS Service Account. |
STARTSERVICE | 0x00000004 | Starts this component if it is stopped. |
SETREGISTRY | 0x00000008 | Configures 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 | Installs this component if the site is a primary site. |
SECONDARYSITE | 0x00000080 | Installs this component if the site is a secondary site. |
AUTOSTART | 0x00000100 | If this is a service, installs it to start 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 the SMS Executive. |
DONTSTOPSVC | 0x00001000 | This service is not stopped or removed during a site shutdown or site removal. |
Package
Defines how to install the SMS services on SMS logon servers and Windows NT-based clients. The Package section uses the BEGIN and END keywords. It also uses the FLAGS, MAIN, and SUBCOMPONENT keywords (see the preceding section for a description of how these keywords are used).
An example follows:
PACKAGE "SMS_INVENTORY_AGENT_NT"
BEGIN
FLAGS = 0
MAIN "INVWIN32.EXE"
END
Directories
The remainder of the SYSTEM.MAP file consists of directories and files that must be created or installed on the site server. The directories and files are installed based on the microprocessor architecture platform, language, and software installable units specified in the section. For instance, the following section creates the PRIMSITE.SRV\AUDIT directory, and installs the files AUDIT.RUL and RUL2CFG.BAT in the directory:
DIRECTORY "PRIMSITE.SRV\AUDIT"
PLATFORM "" LANGUAGE "" SOURCE "COMMON\INTNL" FLAGS = 42
UNIT = "SCRIPTS"
BEGIN
"AUDIT.RUL", SIZE(1, 1033292, 1033292), "AUDIT.RUL", "AUDIT.RU_", REMOTE=NO, COPYLISTS(), COMPRESS=NO, FLAGS = 1
"RUL2CFG.BAT", SIZE(1, 991, 991), "RUL2CFG.BAT", "RUL2CFG.BA_", REMOTE=NO, COPYLISTS(), COMPRESS=NO, FLAGS = 1
END