Systems Management Server 2.0
An interactive guide to centralized management for Windows 2000-based systems.
Introduction to SMS 2.0
Microsoft Systems Management Server (SMS) 2.0 was a powerful enterprise-level management solution designed to help IT professionals manage and maintain computer systems across an organization. With Service Pack 2, it became an indispensable tool for large Windows 2000 deployments.
Its primary goal was to reduce the total cost of ownership (TCO) by automating routine administrative tasks and providing a comprehensive view of the network's assets through features like inventory, software distribution, and remote control.
Typical Client Environment
Illustrative client mix in a typical Windows 2000-era SMS deployment.
Figure 1.0: Microsoft Systems Management Server Product Box Art
Interactive Architecture
Explore the components and their interactions in a typical SMS deployment.
Figure 2.0: Typical Microsoft SMS Implementation Diagram
Hover over a component above to see its description.
Core Features
Explore the key functionalities of Systems Management Server 2.0.
Hardware & Software Inventory
SMS 2.0 excelled at collecting detailed data from clients, providing a comprehensive understanding of network assets. This was critical for asset management, license compliance, and planning upgrades.
How It Works:
- • Hardware Inventory Agent: Collects system specifications like CPU, memory, disk space, and OS details.
- • Software Inventory Agent: Scans for installed applications, executables, and Windows Installer packages to gather version and usage information.
- • Data Flow: Data is sent to the Management Point, processed, and stored in the SMS site database for reporting.
Typical Use Case:
Identifying all Windows 2000 Professional workstations with less than 256MB of RAM to schedule a memory upgrade project.
Software Distribution & Installation
One of SMS's most powerful features was its ability to reliably deploy software to large numbers of computers, including applications, updates, and OS upgrades.
Deployment Process:
-
1
Create Package
Define source files and programs (e.g., `setup.exe` with silent install parameters).
-
2
Create Advertisement
Link the package to a target collection of computers and set a deployment schedule.
-
3
Distribute Content
Copy the package content to one or more Distribution Points.
-
4
Client Execution
Clients poll for advertisements, download the package from a DP, and run the installation.
Figure 2.1: SMS Administrator Console - Packages Node (Illustrates Distribution Point creation)
Software Metering
SMS 2.0 could monitor software usage on client computers, helping organizations enforce license compliance and identify underutilized software.
How It Works:
- • Rule Definition: Administrators define rules to monitor specific executables.
- • Usage Tracking: The Software Metering Agent tracks when these applications are launched, for how long they are used, and by whom.
- • Reporting: Usage data is reported to the site database, enabling comprehensive reports on peak usage, total usage, and active users.
Typical Use Case:
Ensuring that the number of concurrent users for a specialized line-of-business application does not exceed the purchased license count.
Remote Control
SMS provided robust remote control tools, allowing IT support staff to troubleshoot client computers without being physically present, significantly improving resolution times.
Key Features:
- • Full Desktop Control: Take over the client's screen, keyboard, and mouse.
- • Remote Chat: Communicate directly with the user during a session.
- • File Transfer: Securely copy files to and from the remote computer.
- • Remote Reboot: Restart the client machine.
Typical Use Case:
A helpdesk technician remotely diagnosing and fixing a printer configuration issue on a user's Windows 2000 workstation.
Figure 4.1: Systems Management Server Setup Wizard - Remote Tools Installation Option
Management & Best Practices
Key considerations for maintaining a healthy SMS 2.0 environment.
Installation Overview
- Prepare Environment: Ensure Windows 2000 Server is installed and configured optimally.
- Install SQL Server: A dedicated Microsoft SQL Server instance is crucial for the SMS site database.
- Run SMS Setup: Execute the SMS 2.0 setup program from the installation media.
- Configure Site Settings: Define your SMS site code, assign site system roles (Management Points, Distribution Points), and set up boundaries.
- Apply Service Packs: Crucially, install SMS 2.0 Service Pack 2 (or later) for full Windows 2000 compatibility and feature enhancements.
- Install Client Agents: Deploy the necessary SMS client agents to all target Windows 2000 machines for management.
Prerequisites & Best Practices:
SMS 2.0 typically required Microsoft SQL Server 7.0 or SQL Server 2000. It is recommended to install the SMS Site Server on a dedicated Windows 2000 Server, preferably as a member server rather than a domain controller for performance and security isolation. Ensure Internet Information Services (IIS) is installed for Management Point functionality, as it hosts the client communication interfaces.
Client Deployment:
Common client deployment methods include Client Push Installation (which requires proper network discovery and security permissions), logon script installation, and manual installation for smaller environments or troubleshooting. Service Pack 2 for SMS 2.0 was vital for robust Windows 2000 client support, including improvements to Windows Installer integration and Group Policy-based client assignment.
Maintenance Overview
- Database Backups: Implement a regular, robust backup schedule for the SQL Server SMS database to prevent data loss.
- Database Optimization: Perform periodic re-indexing and integrity checks on the SMS database for optimal performance.
- Monitor Site Health: Regularly check SMS site system components and client health status messages via the SMS Administrator Console.
- Review Logs: Periodically check SMS server and client logs for any errors, warnings, or anomalies that may indicate issues.
- Disk Space Management: Actively monitor disk space on all site servers, Management Points, and Distribution Points to prevent outages.
SQL Maintenance Examples:
Utilize SQL Server Agent jobs to automate tasks such as `DBCC CHECKDB` for database integrity, `REINDEX` commands for fragmented indexes, and transaction log backups to ensure quick recovery and prevent log file bloat. Regular archival of old status messages and discovery data can also help manage database size.
Key Log Files:
Important log files to monitor include `site.log` (SMS Site Server activity), `ccm.log` (Client Component Manager on clients), and `advert.log` (advertisement processing on clients). The Windows Event Viewer on both server and client machines also provides crucial diagnostic information.
Performance Counters:
Use Windows Performance Monitor (PerfMon) to track SMS-specific performance objects and counters, such as "SMS_SITE_BACKLOG" or "SMS_CLIENT_HEALTH," in addition to general SQL Server and operating system performance metrics.
Security Overview
- Limit Admin Access: Grant SMS administrative permissions only to authorized personnel following the principle of least privilege.
- Secure WMI: Ensure proper security permissions on the Windows Management Instrumentation (WMI) namespace that the SMS Provider utilizes.
- Use Strong Passwords: Mandate and enforce strong, complex passwords for all SMS service accounts and administrative accounts.
- Regularly Patch: Keep the Windows 2000 Server operating system and SQL Server instance patched with the latest security updates.
- Firewall Configuration: Configure network firewalls to allow only necessary SMS communication ports while restricting all others.
SMS Admins Group:
The `SMS Admins` local group (or domain local group on a DC) is created during SMS installation and is granted the necessary WMI permissions (`Enable Account`, `Remote Enable`) on the `Root\SMS` and `Root\SMS\Site_XXX` namespaces. Users needing access to the SMS Administrator Console must be members of this group.
Service Account Permissions:
SMS utilizes various service accounts. Ensure these accounts are granted only the minimum necessary permissions on file shares, SQL Server, and Active Directory to perform their specific roles (e.g., network access account for client push, SMS_Executive service account).
Firewall Ports:
Common ports required for SMS communication include TCP/445 (SMB), TCP/135 (RPC Endpoint Mapper), dynamic RPC ports (1024-5000 on Windows 2000), TCP/1433 (SQL Server), and potentially TCP/80 (HTTP) or TCP/443 (HTTPS) for Management Points and Distribution Points that use web-based communication.
Conclusion
Microsoft SMS 2.0 was a cornerstone for IT management in Windows 2000 environments. It provided a robust set of tools for centralized control over assets, streamlining operations and reducing administrative overhead. Though succeeded by Configuration Manager, SMS 2.0 laid the groundwork for modern endpoint management.