Microsoft's Systems Management Server helps bring the anarchy of multiple-vendor networks under centralized control
Ethan Wilansky
Intelligently managing networked computers has become difficult and complex. One complicating factor is the plethora of management tools that use different OSes and front ends. Each management application is configured separately and often uses proprietary data collection, remote control, and software distribution.
Microsoft seeks to resolve these problems with SMS (Systems Management Server), a suite of network management utilities. Using Microsoft's Windows NT Server and Windows NT SQL Server as its underlying OS and database, respectively, SMS provides four major management functions: hardware and software inventorying; electronic software distribu
tion; shared application management; and remote-control and network monitoring.
SMS is an integrated set of node-level tools that use industry-standard methods for managing the network. It distinguishes itself from the competition by using the NT SQL Server database as its foundation. This means, for example, that when a network manager defines a software update procedure that executes only on a client if CPU or disk space is adequate, the client's characteristics are determined by querying the NT SQL Server database.
SMS provides an open environment to support three of the most popular NOSes (network operating systems), Novell NetWare 3.1x and 4.x (in bindery emulation mode only), IBM's LAN Server 3.0 and 3.1, and Microsoft LAN Manager 2.1 and higher. This open systems philosophy extends to data collection and reporting via ODBC (Open Database Connectivity), DMI, and SNMP. Client OSes--such as Mac System 7, OS/2 2.x, MS-DOS 5.x or higher, and the Microsoft Windows family--are supported for vary
ing degrees of systems management (for details, see the table "
SMS-Supported Operating Systems
"). NT's support of such popular industry protocols as TCP/IP, IPX, SNA (Systems Network Architecture), RAS (Remote Access Service), and NetBEUI lets SMS use any of these protocols for data gathering, management, and distribution.
To operate SMS, you need NT Server ($699) and NT SQL Server ($999). The CPU, disk, and RAM requirements depend on the number of workstations and on how dispersed--from a single segment LAN to many routed WANs--the network is.
For our tests, we ran SMS on five NetWare log-on servers. Two of these were located at our Bethesda, Maryland, test site, and the other three were accessed remotely across a frame-relay link. Of the three remote servers, two were connected via 256-KB lines, and one was on a 56-KB line. Clients were dispersed throughout the local and remote sites and ran a variety of OSes, including Windows 3.1, MS-DOS 5.0 or higher, WFW (Windows fo
r Workgroups) 3.11, Mac System 7, and OS/2 2.1. Last, but not least, we ran SMS on two NT servers, one of which functioned as the central site server.
Building on a Strong Foundation
SMS uses a format called MIF (management information file), developed by the DMTF (Desktop Management Task Force), for collecting inventory information about the hardware on the network. It also uses SNMP services for monitoring SMS servers from a network management station, such as Hewlett-Packard's OpenView. In addition, IBM's NetView network management software can receive SMS status information if an NT server is running Microsoft SNA Server.
Inventory Management
Inventory data collection
underlies all SMS's key operations. At the central or primary site servers, you decide the schedule and frequency of inventory collection for managed sites. Constant updates to the SMS database keep the inventory current, regardless of whether clients ha
ve been added or reconfigured. The inventory can encompass such items as hardware disk type, names of workstation boot files, installed software, and BIOS revision dates.
SMS provides a sophisticated query function that lets you use stored inventory information to complete a selective software upgrade through SMS, to document the network, or to trigger an alert condition in the event log. You can also save defined queries for future use.
We found the inventory function to be the most robust and well-designed SMS component. However, the data we collected was sometimes incomplete. For example, our database contained no mention of the SCSI controller on a Tricord ES5000 server running NetWare 3.12. The reason is that SMS uses standard NetWare APIs to collect information from NetWare servers, and those APIs report only NetWare volume (not disk controller) information, the OS version, and other server information tracked by the NOS.
In addition, on some stations at the Bethesda, Atlanta, and S
an Francisco test sites, the SMS boot-configuration component didn't run because other batch procedures executed commands that dumped users out of their boot files before the SMS agent TSRs could run. After we reconfigured the batch routines, the agents ran fine.
Electronic Software Distribution and Management
Maintaining a hardware inventory is hard enough; add ESD (electronic software distribution) and software management, and you have a nightmare. To help with this management headache, SMS provides a robust and highly configurable set of software distribution and tracking tools.
From a central or primary site server (both of which can function as a multisite hub, although only the former sits atop the hierarchy), you can create a
package
(a type of SMS component) that defines how an application you want to distribute will be installed, executed, or tracked for inventory.
For configuring packages, SMS uses PDFs (package definition files), which consist
of scripts for setting up Microsoft OSes, (e.g., MS-DOS, Windows, and NT) and Microsoft applications, such as Excel 5 and Word 6. Also included is a run-time version of Microsoft Test for running precompiled scripts. (Compiling your own scripts requires the retail version of Microsoft Test, which is not included with SMS.)
Each package provides the information necessary for running a task. Its own delivery, however, is handled through a
job
, which is analogous to addressing and carrying a letter to a mailbox for delivery.
Overall, the package component is slick, but its run-time version of Microsoft Test for script compiling leaves something to be desired. We found using a third-party scripting language like WinApps Installer was the quickest and easiest alternative.
For software installation to execute, the client must have available a PCM (package command manager). Microsoft provides PCMs for computers running MS-DOS 5.0 or higher, Windows 3.x, WFW, NT, and Mac System 7. Curren
tly, there are no PCMs for OS/2 or Unix systems. However, you can run the Windows PCM from an OS/2 Windows shell. At this writing, Digital Equipment was shipping beta versions of a Unix client for SMS. Also, because Mac System 7 doesn't support running applications from the network, you can't share server-based applications.
Shared application management, a main function of SMS, can be used to distribute software to any server in the SMS environment. When setting up shared applications on a server, it's important to make the applications easily accessible to users. For Windows 3.x and NT clients, you can use SMS's PGC (Program Group Control) utility to make application icons appear on each client workstation.
Unfortunately, DOS, Windows 3.x, and NT are the only platforms that can take full advantage of PGC's automation features. If you use a third-party Windows shell or OS/2, you must also use a third-party icon management utility to centrally manage each desktop.
Remote-Access Uti
lities and Network Monitoring
For real-time user support, SMS offers three functions: a diagnostic utility for viewing client configurations, network monitoring for collecting raw data frames or packets while troubleshooting network problems, and remote control (also called help desk). The diagnostic utility lets you, for example, view the device drivers loaded on a DOS workstation. On a Windows station, it lets you see the local heap space used for the GDI (Graphical Device Interface). Network monitoring lets you set network alert triggers for executing any program or task. For remote-control and diagnostic support, SMS can access clients running DOS, Windows, and WFW. Surprisingly, SMS does not support NT or Macintosh clients for diagnostic or help desk functions.
The host and viewing station must have the same protocols bound to the NIC (network interface card) for these remote facilities to function. The administrator monitors the DOS, Windows, or WFW client via a LAN or RAS conne
ction.
Network monitoring also requires either a promiscuous-mode NIC at the monitoring site (i.e., a NIC that receives all frames on the network) or a connection to a remote network monitoring agent running a promiscuous-mode NIC. A wide variety of LAN and WAN protocols running RAS are supported for SMS network monitoring.
SMS remote control doesn't work with OS/2, NT, and Mac clients, although NT support is expected by year's end, and Microsoft is considering adding native OS/2 and Mac support.
A Complex Route to Simplification
SMS is not for administrators who want a simple solution to network management. It's a complex product that demands careful planning before you can implement it.
That said, Microsoft has created a powerful suite of network management tools. When taken individually, SMS's management components are above average. Its distribution mechanisms and client support are superior to those of any product on the market, but they aren't what di
stinguishes SMS from its competitors. SMS really shines as a total network management platform. Its multiprotocol and multi-NOS support are unmatched.
PRODUCT INFORMATION
Systems Management Server $649 per server
($39.95 per client; prices are estimated retail)
Microsoft Corp.
Redmond, WA
(800) 426-9400
(206) 882-8080
fax: (206) 936-7329
MS-DOS WINDOWS MAC
5.X OR WINDOWS FOR WINDOWS SYSTEM OS/2
HIGHER 3.1 WORKGROUPS NT 7 2.X
Client services
Inventory management X X X X X X
Remote control X X X O O O
Network monitoring* X X X X X X
Client
diagnostic utility X X X X O O
Shared applications X X X X O X**
Software distribution X X X X X X
Server types***
Central site O O O X**** O O
Primary site O O O X**** O O
Distribution O O O X O O
Log-on O O O X O O
Helper O O O X O O
Note:
Table information doesn't include NOSes;
X = yes;
O = no.
*
Limited monitoring is possible on any client with a supported protocol,
but only Windows NT and Windows for Workgroups support full,
agent-based monitoring.
**
Although you can run shared applications from a server, SMS cannot
handle client configu
ration and icon setup on the Presentation
Manager desktop.
***
Distribution and log-on servers can also run Novell NetWare 3.x
and 4.x, Microsoft LAN Manager, and IBM's LAN Server.
****
Only Windows NT Server can act as a central or primary site server.
screen_link (63 Kbytes)
Systems Management Server stores network inventory data in an NT SQL Server database. Here, a database report highlights the disk configuration of a node on the network.
Ethan Wilansky is a Maryland-based network integration consultant and instructor for Microsoft and NetWare networking products. He can be reached on the Internet at
ewilan@clark.net
or on BIX c/o "editors."
The Benefits of Recentralization
