Subscribe to Windows IT Pro
May 01, 1999 12:00 AM

Systems Management Server 2.0 Client Features

Windows IT Pro
InstantDoc ID #5189
Rating: (0)

Software Metering. SMS 2.0's Software Metering client agent runs on a client computer and reports software activity to the SMS License Server service to control or simply monitor software usage. (The SMS License Server service isn't related to the NT License Logging service.) You define settings in the metering database to configure this client agent. Unlike SMS 2.0's other client agents, Software Metering runs only on 32-bit Windows OSs (i.e., Win2K, NT, and Win9x).

SMS Software Metering supports callback queuing. If a user attempts to run software that the maximum number of client computers are already using, the Software Metering client agent places the request to use the software in a queue. When the software becomes available, the agent notifies the user. This feature is optional and requires extra processing on the site system running the License Server service.

Mobile computing users can take advantage of SMS Software Metering by checking out software before disconnecting from the network. The software license then belongs to the mobile user until a particular amount of time passes (which you can configure) or the user checks the software back in. This system also supports license balancing if you have multiple SMS License Server site systems. Screen 7 illustrates use of the SMS Software Metering program to configure a product for licensing.

Event to Trap Translator. The Event to Trap Translator client agent converts Win2K and NT events that you specify in SMS into SNMP traps. You can then forward these traps to a network-management system that provides SNMP-based network monitoring and analysis. In this way, SMS can augment the data that a network-management system such as HP OpenView receives.

No Stones Unturned
Microsoft was thorough in updating SMS. Three additional improvements are Network Monitor, Network Trace, and Health Monitor.

SMS's improved Network Monitor includes the Monitor Control tool, which you use to continually monitor your network for unauthorized access or significant network events (e.g., an IP router failure). You can then use Network Monitor Experts to analyze the packets you capture, and you can determine, for example, the average server response time for servers on a network segment. You can also use Network Monitor to monitor network traffic on remote segments.

SMS's new Network Trace utility helps you determine whether your site servers and other SMS site systems are operational. You use this feature to create a site view of your network and the SMS site systems connected to it.

Health Monitor provides a Microsoft Management Console (MMC) snap-in for centralized monitoring of Win2K and NT client computers running the Health Monitor client agent. Health Monitor can monitor hardware and Microsoft BackOffice activity.

SMS 2.0 fixes many of the problems that turned network administrators away from SMS as a systems-management solution. Resource discovery extends SMS's reach, and enhanced client agents provide improved capability. If you're already using SMS 1.2, SMS 2.0's ability to work with the previous version makes migration smooth. SMS 2.0 has been a long time coming, but it's worth the wait.

Related Content:

ARTICLE TOOLS

Comments
  • Frank Regan
    13 years ago
    Aug 09, 1999

    After reading Ethan Wilansky’s “Systems Management Server 2.0 Client Features” (May), I started a Microsoft Systems Management Server (SMS) test environment. I can’t get network discovery to find my static IP machines. The machines are running SNMP, and they’re set to accept from any SNMP host. When I run network discovery, it finds the router and the SMS system but not my statically assigned Windows NT and Windows 95 workstations. As soon as I switch these machines to DHCP and have SMS use DHCP, network discovery finds these machines.
    On one of the SMS newsgroups, I read that the static IP detection feature is broken and that Microsoft will fix the problem soon either through a hotfix or Service Pack 1—–SP1, but Microsoft has yet to confirm this statement. I’ve looked at the Microsoft article “SMS: Clients with Static IP Addresses Not Network Discovered” (http://support.microsoft.com/support/kb/articles/Q201/7/81.asp), but the fixes the article lists have not worked for me.

    —–Frank Regan



    I’ve not had any problems finding these devices using either the static IP address of the devices or the SNMP community name, but I saw the post you refer to in the SMS public newsgroups. Throughout the beta process, no one found this bug. I suppose most of us used DHCP in conjunction with SNMP community and SNMP IP address discovery. You’ve brought up an important issue with the release version of SMS. I’m sure Microsoft will address this problem in the first service pack.

    --Ethan Wilansky

You must log on before posting a comment.

Are you a new visitor? Register Here

advertisement

advertisement

Windows is a trademark of the Microsoft group of companies. Windows IT Pro is used by Penton Media Inc. under license from owner.