| In SMS 1.2 | In SMS 2.0 | Notes |
|---|---|---|
| Any network administrator can log on to SMS Administrator. | Anyone can open the SMS Administrator console, but the features available to each user are limited by the permissions assigned to each Windows NT user name. | You cannot pass access to SMS features to
unauthorized users by telling them a password.
Authorized users have one less password to remember. |
| You perform specific SMS tasks by opening task-specific windows from Windows Start. | You perform specific SMS tasks by navigating to different items on the SMS console tree. | |
| Each site consists of one or more Windows NT domains. | Each site contains one or more IP subnets or IPX segments. | Site boundaries are not constrained by Windows NT
domain structure.
You can adjust site boundaries at any time. It is possible for site boundaries to overlap. |
| Site servers must be Windows NT domain controllers. | Site servers can be any computer running Windows NT Server 4.0, Service Pack 4 or later. | You can dedicate a standalone server to act as your SMS site server — there's no need to add to domain controller workloads. |
| Resources are recognized only after SMS client software installation is complete. | SMS 2.0 discovers resources in a separate step before they are assigned to a site and before client software installation. | SMS 2.0 resources can be anything with an IP or IPX address (such as routers and printers) as well as Windows NT users and user groups. |
| You can organize resources into machine groups (static lists of clients). | You can organize resources into collections, which can consist of any type of resource — either static or dynamic — in the site. | Static collections are similar to SMS 1.2 machine groups. Dynamic collections are based on queries that SMS evaluates on a regular schedule. |
| You create queries in the Query Properties dialog box in the Queries window. | You list and view queries by navigating to Queries in the SMS Administrator console and you create or modify queries in Query Builder. | SMS 2.0 database structure is different than that of SMS 1.2, so SMS 1.2 queries do not work in SMS 2.0. |
| Many SMS tasks such as inventory occur in an MS-DOS window when the client logs on. | Most tasks occur in the background on the client according to a schedule that you set. | Logon time is faster, and SMS client-side tasks rarely disrupt the end user. |
| In Windows 95 and Windows NT clients, SMS 1.2 client components appear under Programs in the Start menu. | Users working at Windows 95 and Windows NT clients are generally unaware of SMS operation. However, exceptions such as advertised programs announcing their availability to the client or a remote control session in progress do occur. | In Windows 95 and Windows NT clients, control panel
applets provide users access to advertised programs and
configurable client settings.
You can control client settings to make status icons available on the system tray. For example, a status icon can show when programs are available to the client. |
| SMS 1.2 client components appear in a special, 16-bit client program group. | The 16-bit client user interface is much the same
as it was in SMS 1.2. There is a new 32-bit client user interface
that provides more functionality.
In SMS 2.0, Advertised Programs Client Agent replaces Program Control Manager. SMS 2.0 no longer supports MIF Editor. |
|
| You must install SQL Server 6.x before you install SMS 1.2. | You must use SQL Server 6.5 Service Pack 4 or later for the SMS site database. You can install a dedicated copy of SQL Server 6.5 on the site server during the SMS 2.0 setup process. | If you want to maintain the SMS site database on a computer other than the site server, you must set up SQL Server on that computer before you install SMS 2.0. |
| New feature | Express Setup is best suited to smaller or relatively simple installations. | The setup option you choose determines whether features such as client setup methods and inventory are enabled. In general, if you use Express Setup, features are enabled by default and if you use Custom Setup, these features are disabled. |
| Your choices of optional components are limited to client and server components supported on various platforms, the SMS Administrator, Network Monitor, and login scripts. | You can choose from optional components such as Network Monitor, Crystal Reports, Remote Control, and Software Metering. | SMS 2.0 installs platform-specific files automatically. |
| You install secondary sites only from the parent site, and you send all required files to the secondary site over the network. | You install secondary sites from the parent site as in earlier versions of SMS or in one of two additional ways: initiating the installation at the parent and completing it by using files at the secondary site or running the entire installation from the Systems Management Server 2.0 compact disc at the secondary site. | The method you choose will depend on available network bandwidth and whether someone at the secondary site can run SMS Setup locally or from the compact disc. |
| You install client software by running the Smsls.bat or Runsms.bat files from the potential client. The installation is run by a login script or explicitly by the end user. | You can configure your site to install SMS 2.0 client software on any Windows NT computer, even if no one is logged on to it. | You can install clients by running the SMSman.exe from the potential client, either explicitly or from a login script. These client setup methods are now extended to NetWare clients. |
Related Topics
