Microsoft's Systems Management Server (SMS) is an extremely powerful product to help network administrators control an organization's entire network. SMS is designed to help administer large enterprise-wide networks, but is flexible enough to maintain
even small networks. It is extremely versatile, being able to handle networks with a wide variety of configurations.
However, with this power SMS requires careful planning and an understanding of the network's configuration to be the most effective. Planning how your SMS sites are arranged helps to implement an effective SMS strategy. SMS takes advantage of features
found in Windows NT and uses another BackOffice product, SQL Server, for its record keeping. SMS can be used on a single server in an organization, or SMS tasks can be divided between different servers.
In this chapter, you will learn the following:
When corporations first started using computers, those computers were typically mainframe computers. These large machines were housed in special rooms, and terminals scattered throughout the office were connected to these mainframes. The actual
processing of the mainframe was handled by the central computer, not the terminals. All administrative control was also handled at the central computer.
Later, personal computers were introduced and adopted by companies. Initially, most PCs were not connected to each other, but now, networks have been created to connect the individual personal computers in an office together. A personal computer
network, however, is managed differently from a mainframe configuration. Each personal computer has the ability to process and store user information. Furthermore, users can often share individual resources, such as printers and directories, on that
machine.
Personal computers and additional hardware are often purchased from different manufacturers and can have many different operating systems. The modern network administrator has to deal with a large number of personal computer types, computer peripherals,
and operating systems. Additionally, the network administrator has to do a lot of record keeping of how the networked systems are configured. A dramatic change from the older mainframe-computing scenario!
Fortunately, Microsoft Systems Management Server is designed to help a network administrator take back some control over the network. SMS is flexible enough to help administration of different-sized networks, from small networks all the way to
enterprise networks. SMS can also view and access Novell NetWare and LAN Manager servers incorporated with a Windows NT network. SMS can take advantage of wide-area network links and remote access links to further extend the management reach of the network
administrator.
SMS provides a large array of features to help the network administrator control the network. SMS is also very versatile in its configuration to better serve the needs of different network designs. It takes advantage of Windows NT and BackOffice
features, such as using SQL Server as its information store. SMS tasks can also be distributed on other servers in the network to reduce the load on one server. Conversely, SMS can run on a single server for smaller network environments.
SMS provides some of the following features to help network administrators control the network:
The primary program the administrator will use is the SMS Administrator program, which provides the user interface between the administrator and the SMS services. Figure 34.1 shows the SMS Administrator program running on a Windows NT computer.
FIGURE 34.1. The SMS Administrator.
One of the most daunting tasks for a network administrator is trying to keep up with each user's computer configuration. Although a network administrator may easily remember that Bill in accounting has an Intel 486 machine and Jill in Engineering has a
Pentium, the IRQ settings for the network adapter in either computer are a bit harder to remember. Even on small networks, most administrators usually write down important hardware settings. In environments with very large networks, hardware record keeping
is vital.
SMS makes the important job of hardware record keeping a lot easier. When a computer joins an SMS site, hardware information is recorded about that computer. SMS stores a wide variety of hardware information, including items such as the following:
Systems Management Server also enables custom information to be added to the inventory list. SMS does this by using the Desktop Management Task Force's (DMTF) file format known as a Management Information File (MIF). An MIF is simply an ASCII text file
with a standardized structure and format. SMS uses graphical forms to fill in the necessary information into the MIF file. SMS also provides a MIF form creator to enable the administrator to create user MIF forms.
MIF forms enable users the ability to fill in custom information when their machine is inventoried by the SMS server. This custom information can include information such as the building where the computer is located, the phone extension of the computer
user, or the department of the computer user. Forms can also have text, number, or list fields to store custom information. SMS provides a sample MIF form for use with SMS.
The user fills out the form, and the data is collected on the next hardware inventory. If SMS collects data from the login script, the next hardware inventory will be run the next time the hardware inventory agent is run, usually by a login script when
the user logs into the network.. Otherwise, the user may have to run the hardware inventory manually. Figure 34.2 shows a MIF form displayed on a client computer.
FIGURE 34.2. The MIF form displayed on a client computer.
The SMS Administrator program is used to view MIF form data. The MIF form information for that user is shown in the computer properties of the SMS Sites window. This example shows a sample MIF form with information. Figure 34.3 shows the MIF form
information displayed in the SMS Administrator program.
FIGURE 34.3. The MIF form information displayed in the SMS Administrator program.
SMS provides a default MIF form with the SMS program. This form, the User Information MIF form, is automatically collected with the inventory when a computer first connects to an SMS site. This form contains the following information: name, e-mail
address, phone number, department, building, and office. The User Information form can be used without modification, or it can be modified using the SMS MIF Form Generator.
SMS enables the network administrator to inventory software on network machines by a method called auditing. SMS auditing can be used to find individual files based on criteria set by the SMS administrator. This is useful in trying to find how
many users have a particular file on their system, such as WINWORD.EXE. SMS contains a predefined package rule file, also known as a RUL, that audits many popular types of user applications. You can also create a custom package rule file to
inventory other software applications. A package is then created to run on workstations on the network and report back the audited information. The SMS Administrator program then shows the software audit in the properties for that computer.
When software auditing is used, the computer's property sheet will show the software that was found. This is a useful feature for determining how many copies of a particular program are stored throughout the network. When software auditing is used, the
computer's property sheet shows the software that was found.
Figure 34.4 shows the SMS Administrator program with audited software information.
FIGURE 34.4. The SMS Administrator program with audited software information.
Although an inventory of software can be performed by SMS, it should not be confused with software metering. Software metering refers to a type of process on a server that actively monitors how many users are currently using a program. This type of process is used to help large sites to properly use license agreements of a software package. The SMS software inventory records only actual files on a computer; it does not check actual usage.
Another strong feature of Systems Management Server is the ability to distribute software across the network. The software distribution feature of SMS is very versatile, allowing automated setup options and both mandatory and expiring distributions.
Previously, most administrators had two options for installing software on networked computers: take the application's disks or CD-ROM to each individual machine and run the setup program, or create a network share and instruct the user to install the
program off the share. The first method was very time-consuming, and the second relied on the expertise of the user to configure the software correctly.
Systems Management Server's ability to deliver software across the network and allowing automated setups help the software-distribution process become more efficient. As with other features of SMS, larger organizations or organizations with remote
computers may find this ability more useful. SMS can be used to distribute both optional and mandatory software packages. Mandatory packages are useful when a network administrator wants all the network users to install a software program. SMS also can set
expiration dates for software distributed over the network. This means that if the software distributed by SMS is not installed by a certain date, the software is no longer available for installation.
SMS makes software distribution very convenient, but always be sure when using SMS to distribute software, that you understand and comply with the license agreement of the software. Many companies, including Microsoft, are very specific about licensing agreements and will enforce them.
One of the advantages of using a networked personal computer is the ability to run programs either from the personal computer or over the network from a server. Running programs from a central server provides many advantages to a company. When a new
version of an application is released, it can be installed once on a server and all of the clients using that program can run the updated version. Also, the storage and processing requirements for client machines are not as large as clients that do not run
programs from the server. However, some of this advantage is offset by the increased storage and processing requirements of the server running these applications.
SMS provides the ability to better manage network-based applications. Typically, the network administrator or the computer user had to manually connect to the share to run the program. SMS allows the automatic installation of shared programs over the
network, similar to the distribution of other software. Program group control is also available for controlling the program groups used for network applications. This feature is available only for computers that use Program Manager, such as Windows 3.1
machines.
Another important aspect of maintaining a network is understanding how data moves between network nodes and ensuring that the network traffic load does not become too large. SMS uses a program called Network Monitor that enables a network administrator
to watch data traffic on the network. The SMS Network Monitor captures all of the frames, also known as packets, on the network. The captured frames are graphically displayed on the Network Monitor screen. You can filter frames to narrow the information to
specific data. You can also transmit frames from the Network Monitor computer for diagnostic testing of the network. Triggers based on buffer space or pattern matching can also be defined.
SMS also enables you to watch the network information between the SMS computer and another network computer, using the computer's property window in the SMS Administrator program. This is the standard Network Monitor program with a filter applied to
monitor the network traffic of only that particular computer. All of the features and items found in the Network Monitor program are available when it is used from the SMS Administrator program to view a specific computer.
The SMS Network Monitor provides detailed information about the network and its performance. Network Monitor captures all of the frames transmitted on the network so the administrator can monitor the data flow of the network. Figure 34.5 shows an
example of network monitoring under SMS.
FIGURE 34.5. An example of network monitoring under SMS.
Of course, the primary purpose of a computer network is to give users the tools to help them accomplish their everyday tasks. With any type of machine, problems do occur. Most users on the network aren't knowledgeable of the internal workings of
computer hardware and software and require assistance in fixing these computer problems. The situation is sometimes further complicated by the user not knowing how to effectively describe the problem to the administrator.
Systems Management Server provides the administrator with utilities designed to help a user by allowing remote administration of a network computer. The administrator can see exactly what is occurring on the screen of a user's computers and can perform
all of the on-screen tasks as if they were sitting directly at that computer. Although this feature may not be as useful for a network contained in a single building, it is handy for administrators who have to handle network users on the opposite end of
the country!
The Remote Control feature of SMS is a powerful tool for providing support to network users. Especially in geographically dispersed network configurations, the Remote Control feature saves time and trouble for an administrator who would otherwise have
to be physically at that workstation. Figure 34.6 shows an example of the SMS Remote Control function being used to remotely view and control a client on the network.
FIGURE 34.6. An example of the SMS Remote Control function being used to remotely view and control a client on the network.
On-screen viewing of a network computer isn't the only remote help feature found in SMS. An administrator can also do a remote reboot of a computer or execute a program on the remote machine. An SMS administrator can also view dynamic configuration and
memory information that isn't stored in the SMS database of a remote computer. All of these remote functions enable the SMS administrator to provide better support to remote network users.
Many third-party programs exist that integrate and extend the features found in Microsoft SMS. Some examples include the following:
Many of these products add support for vendor-specific platforms, whereas others extend the ability of SMS by incorporating new features for systems SMS already supports. With these packages, you can build on SMS's already strong management functions.
SMS uses a site-based organizational structure. An SMS site is used to organize the different networks of an organization into logical units. This structure is known as a site hierarchy. SMS uses the site hierarchy to better help the network
administrators manage the different networks they control. Understanding the SMS site structure and how it relates to Windows NT domains and your network configuration is important to a successful implementation of SMS.
An SMS site is simply an organizational structure using logical groupings of computers and networks. For instance, a company that has many small regional offices of less than 20 computers may want to put those regional offices into a single site so one
central administrator can remotely handle network functions from one location. Also, a very large company with large offices worldwide may want to organize each office into a single site so a network administrator can handle the individual network needs of
that office.
SMS sites are based primarily on how the network is to be managed. SMS has two distinct types of sites: primary sites and secondary sites. A primary site has its own SQL Server database, in which all information about that site is stored.
A secondary site does not have its own SQL database, but rather it is linked with a primary site that records information about the secondary site. A primary site is designed to administer itself and any secondary sites that report SMS information to its
SQL database. A secondary site does not have the SMS administration tools available; it is managed by the primary site to which it reports.
Primary sites also can be linked to other primary sites. For example, a primary site in a regional office, with its own network administrator, can be linked to a primary site at the corporate headquarters. This enables a site to be managed by both a
network administrator at that site or a network administrator in the parent site. In this type of site configuration, the topmost site in the SMS site hierarchy is called the central site.
With the different levels in the SMS site structure, an organization has a lot of flexibility in organizing the site structure. Two companies with very similar network organizations may use two completely different types of site layouts. Determining the
SMS sites depends on the administrative needs of a company for its network structure.
Windows NT Server uses domains to logically group network computers together. SMS sites also logically group network computers together; however, SMS sites do not always correspond with the Windows NT domain structure. It is possible to have many
different Windows NT domains in a single site. Conversely, it is possible to have many SMS sites in a single Windows NT domain.
Most administrators new to SMS may at first find this very confusing, but the SMS site structure is based on different requirements than the Windows NT domain structure. The Windows NT domain structure is based on the needs of resource-sharing for
network users, whereas the SMS site structure is based on the needs of administrators to manage the network. The requirements for Windows NT domains and SMS sites vary from organization to organization, so the two may not match each other. However, some
organizations may have Windows NT domains and SMS sites arranged in the same structure.
With the number of different site configurations available, how does an organization decide how to set up an SMS site structure? Understanding the current network configuration and planning how to manage that network is the key. SMS is designed to be
flexible in its configuration, but when implemented, constant changing of that structure is not recommended. Be sure to plan how the network is to be managed, the number of resources available at each planned site, and the command structure of the
organization.
Be sure to think about how your network is currently configured, and also what future changes will occur to the network. Although you probably can not foresee all the future changes, having an idea will help to ensure that the SMS structure can grow
without causing problems. Computer networks change and grow as new technology is introduced or a company expands its operations.
Take a look at some examples of SMS site structures. The first example is the simplest. There is a single Windows NT Domain for an office of 35 networked computers. A single Windows NT Server provides all of the network services. The SQL Server and SMS
are installed on the single Windows NT Server, and only one site is used. It is a primary site because it uses the SQL Server, and it is also the central site. A network administrator, or group of network administrators, controls all of the
network-management functions.
The second example includes an office in New York, another in Chicago, and a third in Los Angeles. Each office uses its own Windows NT domain. For example, the New York office has a single domain called the New_York domain. Each domain trusts the other
two, enabling user accounts to access resources on each domain.. Each office has a SQL Server and a network administrator, so the company has decided to make the SMS site structure follow the Windows NT domain structure. For example, the New York office is
set up as the New York site. Each site is a primary site using its respective SQL Server.
Another organization has a single office, but is very large. Each department uses a Windows NT domain to help control departmental computing resources. Even though there are multiple domains, there is a central staff of network administrators for the
entire company. In this case, the company has decided to set up a single SMS site to handle the entire organization to allow the network administrators better control of the network.
The final example is a company that has a single Windows NT domain with multiple SMS sites. A Chicago-based company is located in a single building, but on different floors. A single Windows NT domain is used for the resource sharing and user
administration of the company. However, a network administrator is available on each floor. The company decides to divide the SMS site structure for each floor. Each network administrator has a single site to control within a single domain. Communication
can occur between sites, so the different network administrators can have access to those other sites.
As mentioned previously, SMS utilizes both Windows NT Server and SQL Server for its proper operation. For networks that have multiple sites, there may be different types of SMS servers. Furthermore, for networks that have a lot of users or heavy network
traffic, individual functions of SMS can be divided among computers, known as helper servers. SMS requires or uses the following types of servers:
When discussing servers, many people may be confused about the difference between software servers and actual physical server machines. A physical computer can be a file and print server, an authentication server, SQL Server, and a primary or secondary SMS site server. In certain instances, software servers may be divided among many different computers. The term server is used in this chapter to describe an individual software system, not a physical machine.
As mentioned previously, SMS requires a SQL Server to store the acquired information into a database. A dedicated SMS database is created in SQL Server when SMS is installed. The central site and all primary sites require a SQL database in each site.
Secondary SMS sites do not have a SQL database at that site, rather the parent site stores the information.
The SQL Server used in a site may be dedicated to SMS information or it may be used for the sites other client-server database needs. SMS usually does not place very heavy demands on SQL Server, so the SQL Server is often available for other database
tasks. A SQL Server must be installed and configured before SMS is installed. The SQL Server may either be located on the same physical computer as the SMS computer or they may be two different machines on the network.
Primary site servers are usually the most common site servers in an SMS configuration. In every organization using SMS, at least one primary site server is required. The primary site server has its own SQL Server database and SMS administration tools.
Primary sites are installed using the distribution media—typically a CD-ROM or server-based network installation.
A primary site can have either primary or secondary sites below it. A primary site that contains sites below it can also administer those sites. If a primary site is the highest level of the site hierarchy, then it is known as the central site
server.
Secondary site servers are used when a site is to be controlled by a parent primary site. No SQL Server is used at that site, and no SMS administration tools are installed there. Secondary sites can be installed directly by the primary site server,
without the need for the distribution media. A secondary site may not have any other sites below it.
A logon server is a server that processes user logon requests and stores the user login scripts. It is added to the SMS site through the SMS Administrator program. It holds temporary SMS inventory data obtained through the client inventory agent. The
data is then transferred to the SMS server to be stored in the SQL database. Logon servers may also act as distribution servers and may either be the same computer as the SMS server or other computers on the network.
A distribution server is used to send packages from the SMS server to client computers on the network. A distribution servers receives packages from the SMS server, then sends the packages to the appropriate clients. It also acts as a location for
shared network applications. Distribution servers can also be logon servers.
Most of the components of SMS are Windows NT Services. In large networks, a single SMS server may become overburdened. To help reduce this load, helper servers may be used to handle certain SMS tasks. Helper servers help move information between sites
and are also known as senders. Three types of senders are supported: LAN senders, RAS senders, and SNA senders. Helper servers must also be logon servers.
The majority of SMS functionality takes place at the site server. SMS uses Windows NT Services for the background work and the SMS Administrator program for interaction with the network administrator. Other SMS programs (such as the SMS Security
Manager, MIF Form Creator, and Network Monitor) provide other server-based components to help the administrator.
Almost all of the functions provided by SMS are handled through Windows NT services. These services automatically run in the background performing the information-gathering and software-distribution functions of SMS. Because they run in the background,
other processing can be done on the Windows NT server while these functions are being performed. SMS runs some of the following services in the background:
These services are displayed from the Windows NT Control Panel using the Services item. As noted, the SMS Executive is composed of many different components. These individual components can be viewed from a program known as the SMS Service Manager.
The SMS Service Manager enables you to see the SMS services being run on a site, logon, or helper server (see Figure 34.7). You can also stop or pause any services that are currently running. Conversely, you can start or continue any services that have
been stopped or paused. You may also start or stop tracing options for a particular service and set the location of the trace log filename. The SMS Service Manager can view services on either the local computer or any other SMS computer on the network. The
SMS Service Manager enables you to view the available SMS services being run on the Windows NT machine. It also enables you to start, stop, and pause an SMS service. Tracing options can be turned on or off as well.
FIGURE 34.7. The SMS Service Manager.
The primary tool used by a network administrator to schedule SMS tasks is the SMS Administrator program. This program does not actually do the distribution work of SMS, which is handled by the SMS services, but rather allows an administrator to view the
information collected by SMS and to create and schedule distribution packages and jobs. The SMS Administrator program also enables the administrator to schedule queries and alerts and to see the results of each.
The SMS Administrator also handles some of the SMS site-creation tasks, including the creation of secondary sites. The Sites window is used with the New command to create secondary sites. The Site Properties page shows information about the selected
site configuration and enables the administrator to make changes to the site. The Site Properties page also enables computers to be added to the site and enables the selection of a parent primary site for the selected site.
The SMS Administrator program enables a network administrator to view the collected SMS information, perform queries to find certain network information, create software distribution packages, and schedule SMS jobs. Figure 34.8 shows the SMS
Administrator program with a sample site listed.
FIGURE 34.8. The SMS Administrator program with a sample site listed.
SMS distributes software to network computers by using packages and jobs. An SMS package defines the properties of the software. Packages can have three distinct purposes. You can define a package to obtain inventory information, install software on a
client machine, or to install a shared network application. Packages can be manually created by the administrator or predefined package definition files, also known as PDFs, can be used. The SMS program contains predefined PDF files for the
installation of a wide variety of existing programs. Some examples include the following:
Many of Microsoft's new products also may have .PDF files on the distribution media for that program. For example, .PDF files are available on the Windows 95 and Windows 4.0 CD-ROMs for distributing those applications using SMS. These .PDF files contain
the information about the application's configuration. .PDF files simply provide the information rather than require the administrator to input the information manually. Using .PDF file to better understand package creation is a good way to learn how to
create SMS packages.
The Microsoft World Wide Web site periodically updates PDF files for releases of new products. You can access the Microsoft Web site at: http://www.microsoft.com.
An SMS job actually handles the delivery of the SMS package across the network. An SMS job controls items such as the delivery time, which computers will receive the package, and which distribution servers to use. Jobs can be can be
made available to users, be made mandatory, or expire after a certain date.
Jobs run as a background task on Windows NT machines and, therefore, take some time to be distributed throughout the network. The speed of the links between the SMS server and the final destination path also affect the speed in which jobs deliver their
packages. Jobs can also have three different priorities: high, medium, and low. By default, most SMS jobs are given a low priority and may take a while to deliver packages to their destination.
On computers that have Program Manager running, standardized program groups can be created for network applications. These program groups contain any network-based programs the administrator wants to add. This way, Windows 3.1 clients and Windows NT
3.5x clients can have a program group automatically created for them containing the specified network applications. This feature helps to ensure a consistent grouping of network applications throughout the organization.
Queries enable the network administrator to search and find computers on the network that meet certain criteria. For instance, a network administrator may want to distribute software across the network to client machines. However, the program can run
only on computers with 8M or more of physical memory. Rather than send the software to all of the computers on the network, it is more practical to send the software only to machines with 8M or more of RAM installed. The administrator can query all the
computers in the SMS database for those machines and send the software only to them.
The queries can be stored for future use, making them available even when the network changes. An SMS group type, known as a machine group, can be created based on query results. This makes it easier to view and distribute packages to those
machines. By using queries and machine groups together, the administrator is able to quickly access the machines that meet certain specifications.
Queries are ideal before installing new software on network workstations. You can use a query to find out which computers on the network have the required processor, memory, and storage space for an application. The results of this query can be saved into an SMS machine group and distributed directly to this group.
One of the key requirements for keeping a network running smoothly is detecting potential problems. SMS Alerts make this job easier by providing warnings about potential trouble spots. Alerts use queries to find certain information; when the alert
detects a certain condition, and alert event is triggered. When an alert event occurs, it can set to perform any of the following actions:
Any item that can be used in a query can be used for an SMS alert. However, many items that can be used in a query are not appropriate for alerts. One query that is predefined in SMS is querying machines for nearly full disk space. This query is well
suited for an alert.
Many times the network administrator will have to check the performance of the network infrastructure. SMS provides monitoring features to help the administrator view the data traffic on the network or between two stations. The SMS Network Monitor,
found in the Systems Management Server group, enables the administrator to view all of the packets moving across the network. The Network Monitor shows a multipaned display containing a variety of network information. It shows items such as the percentage
of network utilization, the frames per second, the network address packet senders, the type of packet being sent, and the total statistics for the network. You can also view network information in a report view after the session has been captured.
The Network Monitor program provides other features like filtering. Filtering enables the administrator to determine which type of packets should be monitored. The Network Monitor also allows triggers, based on either buffer space or pattern matching,
that can stop the capture or run a command-line program. You can also select which network to monitor if multiple types of network connections are available, such as a remote access connection to an Ethernet network.
The Network Monitor item located in the SMS Administrator uses a filter to view information about only a particular computer. It provides the same display and features as the Network Monitor item in the Systems Management Server group, but it provides
network information about the selected machine. This is useful if you want to see how a particular computer is utilizing the network and don't want to manually create a filter.
Before the SMS Administrator can monitor network connections, the Network Monitor Agent has to be installed from the Windows NT Control Panel. When SMS is installed, it checks to see if it has been configured. If it hasn't, then it gives the user the option of installing it. However, the user installing the software can still choose not to install the Network Monitor Agent. When this occurs, the Network Monitor Agent has to be added in the Network item in Control Panel. If you are using version 1.0 or 1.1 of SMS, the network adapter must be able to operate in a mode known as promiscuous mode. This does not apply to SMS version 1.2. Check the documentation or contact the manufacturer to determine whether your network adapter can support this mode.
The other component to SMS is the client component. Certain programs are installed when a computer connects to an SMS server. These components handle the actual information about the computer and send a file with the information to the SMS server. Also,
client software is installed to enable the user to run SMS packages that are sent from the SMS server. Finally, help desk functions are available to operating systems in which the SMS administrator can connect to the client computer when trying to
troubleshoot computer problems.
SMS can support the following operating systems on client computers:
The client inventory agent collects hardware and other inventory information when the client connects to the network. The data is stored in a file and transmitted to the SMS server. The SMS server processes the information and sends the data to the SQL
database. Inventory agents are typically run from a user's login script, or they can be run as part of the manual installation of a client to an SMS site.
The Package Command Manager is the client program that handles the receipt and execution of SMS packages. The Package Command Manager receives SMS packages sent from a distribution server. The packages can then be executed by the Package Command
Manager. If the package is an optional package, the user can run it manually. If the package is a mandatory package, the Package Command Manager will display a message indicating that the package is mandatory when the mandatory date is reached. It will
also give the user the option to run the package immediately or wait five minutes for the user to save any work before the package runs.
The Package Command Manager also keeps track of executed packages run on the client machine. Keeping track of these packages enables the package to be reinstalled in case the original installation becomes corrupted. Package Command Manager also enables
packages to be archived for later use. Folders are used to store the pending, archived, and executed packages. After a package is executed, it automatically is moved from the Pending folder to the Executed folder.
The Package Command Manager receives incoming SMS packages and allows the user to execute the SMS package. Figure 34.9 shows an example of the SMS Package Command Manager on a client computer.
FIGURE 34.9. An example of the SMS Package Command Manager on a client computer.
The Program Groups window enables you to standarize the program groups for network applications. This allows for a consistent user interface when accessing applications run from a network server. When a user logs into the network SMS verifies the
existance and format of the program group and, if needed, makes any changes to the groups listed in the Program Groups window of the SMS Administrator program.
Program groups enable the SMS administrator to create a standard program group that all network users have for shared network applications. Figure 34.10 shows the properties of a program group created in the SMS Administrator program.
FIGURE 34.10. The properties of a program group created in the SMS Administrator program.
Program group control is only available for clients that use Program Manager. Therefore, it is not able to control groups for Windows 95, MS-DOS, IBM OS/2, or Apple Macintosh computers.
Probably some of the strongest tools that SMS provides for client troubleshooting and maintenance are the help desk options. The help desk options enable the SMS administrator to control certain parts of the client machine via the SMS Administrator
program. This is especially useful if the client is geographically separate from the rest of the network. The network administrator uses the SMS to find the computer and send a message to the client asking for permission to access that computer. After the
client gives permission to access the computer, the administrator can then access the machine as if he or she were sitting directly in front of it.
Help desk options are not available for all of the supported SMS clients. Only MS-DOS, Windows 3.1, Windows for Workgroups 3.11, and Windows 95 computers can be accessed through the SMS help desk options. SMS can not be used to access Apple Macintosh,
or OS/2 computers. SMS version 1.2 allows help desk options to be used to remotely control Windows NT clients. Versions 1.0 and 1.1 of SMS do not allow Windows NT computers to be remotely controlled. However, those versions allow access to certain
administrative tools and the Windows NT diagnostic tool on Windows NT clients.
The Help Desk item in the SMS Administrator program enables the administrator to access a client workstation and perform certain tasks over the network. This enables the administrator the ability to provide assistance to a user without physically being
at the client computer. Figure 34.11 shows the help desk options located in the SMS Administrator program.
FIGURE 34.11. The help desk options located in the SMS Administrator program.
SMS enables the following functions to be performed using the help desk utilities:
FIGURE 34.12. An example of a remote computer being controlled by the SMS Remote Control function.
FIGURE 34.13. An example of the Remote Chat function.
FIGURE 34.14. An example of the Remote Diagnostic Information function when used for a remote machine.
With the powerful nature of the SMS remote control abilities, many network administrators will obviously be concerned about misuse or security problems with someone taking control of another computer. The SMS client must be running the Remote Control client program before the computer can be accessed. Also, before anyone else can control the computer, a dialog will be displayed to the client asking if remote control access is allowed. This helps to prevent unauthorized remote control access of client computers.
Microsoft Systems Management Server provides a wealth of tools to help a network administrator take control of a network. Whether it is a small network with only a few computers or a large network that is geographically dispersed, SMS is flexible and
powerful enough to ease the burden of some of the network administrator's most important jobs. SMS builds on Windows NT's management features, and it utilizes another component of the BackOffice package: SQL Server.
With the right planning and site layout, SMS can be used to properly manage multiple networks with many network administrators. SMS provides strong client support, allowing remote control and other supporting functions to MS-DOS, Windows 3.1, and Windows 95 computers. The features of SMS are very powerful, and the next few chapters explore these features even further.
