 | Recommended: Click Here to Update All of Your PCs Outdated Drivers |
Planning for SMS
Systems Management Server (SMS) Review
SMS 2.0 is a systems management tool that administrators can utilize to centrally control a variety of network environments. Before you can plan your SMS deployment and implement SMS, you need to understand the main functions of SMS, as well as the different SMS components.
The main functions of SMS are listed here:
- Resource discovery: Before you can use the SMS Administrator console to manage network resources, SMS has to first discover the network resource that you want to manage. Network resources that SMS can discover and add to the SMS database are listed here:
- Client computers, IP hosts, routers, switches, hubs, other site systems, file and print servers, global groups and domain users, and other networking devices that have IP addresses.
Typical information discovered on resources includes:
- NetBIOS name of a computer
- IP address of a computer or other networking device
- IP subnet of a computer
- MAC address
- Operating system
- SMS unique identifier
- Domain information
- User name information
- Hardware and software inventory: Inventory collection is categorized as follows:
- Hardware inventory: Involves collecting data on the hardware properties of installed client computer hardware:
- Disk model
- Processor type and speed
- Firmware manufacturer and version
- Capacity
- Free space
- Amount of RAM
- Monitor type and resolution
The Hardware Inventory Client Agent collects the actual hardware properties information from the client.
- Hardware inventory: Involves collecting data on the hardware properties of installed client computer hardware:
- Software inventory: The Software Inventory Client Agent collects the following types of information:
- Filename
- File version
- File size
- Product name
- Product version
- Product language
- Date/time when the file was created.
- Software distribution: SMS software distribution is used to perform the following functions:
- Install software on SMS client computers from a network distribution share.
- Remove software on SMS client computers.
- Copy software on SMS client computers.
- Perform maintenance tasks.
The typical tasks for distributing packages are listed here:
- Specify the client access points (CAPs) for the package.
- Specify the distribution points for the package.
- Create the necessary collections.
- Collect the necessary source files, installation scripts etc.
- Create the SMS package.
- Define one program for the package. This is the minimum requirement. You can define multiple programs for a package.
- Advertise the programs to one or multiple collections.
- Distribute the package to the specified distribution points.
- Run the program being advertised on the client.
- Software metering: The SMS software metering feature was introduced with SMS 2.0, to enable administrators to perform the following functions:
- Monitor how applications are being utilized by the SMS clients.
- Specify restrictions on applications based on permissions or on time of day.
- Track license usage.
- Recognize when unauthorized applications are being utilized.
You can use software metering in either of the following modes:
- In offline mode, software usage is tracked without enforcing software compliance.
- In online mode, software usage is tracked, together with the enforcement of software compliance.
- Network Analysis: The main administration tasks which you can perform using Network Monitor are summarized below:
- You can capture frames directly from the network which you are monitoring.
- You can configure capture filters to specify the type of information which should be captured by Network Monitor.
- You can view captured frames immediately once the capture is complete, or at some later stage.
- You can filter captured frames by creating display filters. This allows you to find specific information in a capture.
- You can create triggers if you want certain actions performed when the content of a packet(s) match a predefined condition.
- You can edit captured frames and pass them on.
- You can capture frames from a remote computer.
The features listed below are solely available when the full Network Monitor version of SMS 2.0 is utilized:
- Capture frames from a remote computer.
- Edit captured frames and pass them on.
- Resolve device names to MAC addresses.
- You can also determine which user who is consuming the most bandwidth
- The protocol that is consuming the most bandwidth
- The devices which are routers
Network Monitor in SMS 2.0 includes experts and monitors:
- The Network Monitor experts analysis tools assist with analyzing the captured network data.
- Network Monitor monitors are monitor tools used to capture frames for monitoring specific network traffic patterns.
- Remote Tools: SMS remote tools enable administrators to control remote client computers. The Remote Tools set provides the following features:
- Remote control
- Remote reboot
- Remote chat
- Remote execute
- File transfer
- Windows diagnostics
- DOS diagnostics
- Ping test
With SMS 2.0 Remote Tools are categorized as follows:
- Remote Diagnostics: Provides the capabilities listed here:
- Control a client computer’s mouse and keyboard
- Execute a program
- Copy files
- Reboot
- View the configuration settings of client computers.
- Remote Functions: Indicates whether the SMS administrator or the local user manages the level of access of the administrator.
The SMS components are briefly reviewed here:
- SMS site: A SMS site specifies the computers, networking hardware, users and groups, and all resources which will be managed through SMS. The SMS environment is made up of one or multiple SMS sites. You define a SMS site based on IP subnet address. An SMS site consists of the following SMS components: SMS site server, SMS site systems, and SMS clients and resources. The structure that links multiple sites together is called a hierarchy. The hierarchy is created by linking sites together so that parent-child relationships can be formed. A parent site is a SMS site that contains one or multiple additional site beneath it. A child site is a SMS site that has a parent site residing over it in the hierarchy. There are also two different types of sites that assist in organizing the administration of the SMS environment, namely a primary site and a secondary site
- SMS site server: This is the Windows server on which SMS 2.0 is installed and running. The SMS site server is the main access point between the SMS database and administrators. The SMS server manages the SMS site and component attributes. The SMS site server must be installed on a domain controller or on a member server. It cannot be installed on a stand-alone server.
- SMS site system: This is a Windows server that carries out one of multiple SMS roles for the SMS site. When installing SMS, the default configuration is that all SMS roles are installed on an SMS site server.
The SMS roles are:
- Logon points: This is a SMS site system that is the initial connection point between a SMS site and client computer. Functions performed by logon point include the collection of discovery information on the client, determines the site assignment of the client and passes the client a list of client access points (CAPs).
- Client access points (CAPs): This is a SMS site system that operates as the exchange point between SMS clients and the SMS site server. At the CAP; inventory, and status information and discovery information is gathered. Advertisement information can be retrieved from the CAP.
- Distribution points: This is a SMS site system that installs the following components which deal with running a package at a SMS client computer: Package files, Programs, and Scripts.
- Software metering servers: This is a SMS site system which enables administrators to perform a number of management activities: Grant/deny licenses for applications running on an SMS client; Monitor and track application usage on SMS clients; and Restrict application usage on SMS clients.
- SMS client:This is a computer running a Microsoft operating system listed below. A SMS client is installed through the SMS client component software, and is assigned to a SMS site.
- Microsoft Windows Server 2003, Windows XP Professional, Microsoft Windows 2000, Microsoft Windows NT 4.0, Microsoft Windows NT 3.51, Service Pack 5 or above, Microsoft Windows 98 and Microsoft Windows 95
The tasks listed below are common tasks which need to be performed in the SMS design phase:
- Determine the site boundaries: Determine the servers and client computers that make up the site. Remember to exclude unreliable network connections. Remember that an SMS site has nine different site system roles that each has its own operating system, RAM, microprocessor and hard disk requirements.
- Determine the site hierarchy: After the site boundaries are determined, you have to determine how sites connect to one another. The central site and its physical location have to be identified. The child sites and their physical locations have to be identified.
- Determine the site types: You also have to decide whether a site is a primary site or a secondary site. Another factor to include would be whether site systems are going to be configured on the remote network.
- Determine the SMS deployment strategy: This task involves planning how SMS is going to be deployed in the network, the manner in which resources are discovered, the client installation methods that will be utilized, and the client agents which will be installed.
Documenting the Existing Network
A network which is well managed and designed should have documentation on the components and networking aspects listed here:
- Physical network structure: Information included here should entail:
- Cabling
- Routers
- Nodes connecting client computers and servers
- Line speeds
- Speed and throughput of links.
- Protocols
- Network segmentation
The information collected on the existing network structure has an impact on how you place SMS sites and site systems.
- Network protocols: For SMS 2.0, either IP or IPX is required.
- Network traffic characteristics: You should be aware of the traffic patterns that exist on each network segment.
- Mainframe and minicomputer hardware and operating systems
- Microcomputer server hardware and operating systems
- All computer hardware and operating systems.
- Configuration of hardware and operating systems
- Information on NetWare directory services and bindery logon server.
- Configuration in the NetWare environment
- Installed application software
- Application software configurations.
- Location and configuration information on all scripts
- User and group information.
Assessing the Existing Network Infrastructure
To plan your SMS environment, you need to have information available on what computers support the network and how these computers support your network. Planning SMS deployment is a tedious process because it involves collecting information on the computers, domain controllers and servers within the network.
It is recommended that you minimally collect the information listed below on each domain controller and server relevant to the SMS deployment:
- Microprocessor type
- Microprocessor speed
- RAM capacity
- Disk or array controller characteristics
- Configuration of disk or array controller
- Devices, including information on:
- Size
- Drive model and types
- Megabytes of cache
- Software applications hosted in each drive
- Network topology
- WAN connection characteristics.
Selecting a Site Hierarchy
Before you can design the site hierarchy, you need to select the servers and client computers that will form the site.
With regard to determining the site boundaries for your SMS design, consider the following important factors:
- A site is determined by resource boundaries which consider either IP subnets or IPX networks.
- A SMS site should not span an unreliable network connection.
- After you have gathered all the necessary information on your existing network infrastructure, you should use this information to determine the following:
- Whether the entire network will be one site.
- Whether there will be more than one site.
- Whether sites will be divided, based on geographic location.
- Whether all servers will be included in the site.
- Which site system roles would the different computers have
- Which computers can be used for site systems
A few factors that you should consider when you are designing the SMS site structure are discussed below:
- The physical network structure and the requirements of the organization will determine whether a flat and wide hierarchy or a steep and narrow hierarchy will be employed. A flat and wide hierarchy has multiple site servers with fewer clients. A steep and narrow hierarchy on the other hand has fewer servers and numerous clients.
- With a flat hierarchy, managing and maintaining the site database is simpler.
- The more levels within your hierarchy, the more time needed for configuration modifications to move up/move down the hierarchy.
- The time restraint with regard to site failures is another factor that needs to be considered. With a flat and wide hierarchy, the loss of connectivity with a site server would have less of a negative influence on the entire SMS hierarchy as would be the case with a steep and narrow hierarchy. With a steep and narrow hierarchy, the loss of a site server that contains numerous child sites would have a bigger impact on the entire site system.
- The expected traffic volumes between the sites in the hierarchy affects the network links which connect the sites within hierarchy.
- The sites that have to communicate over WAN connections have an impact on the maintenance costs of your SMS design as well.
Selecting SMS Features
Each SMS feature that you plan to use has a different set of hardware requirements. These hardware requirements should be included when you plan the following:
- Site systems
- Site system roles
- Load
- Placement
To assist you with this task, the SMS features together with their specific hardware requirements are listed here:
- Hardware and software inventory; consider the following hardware requirements:
- Additional disk space is required for the SMS site database server.
- Additional bandwidth is required on the site server at the site and parent sites. This is due to the inventory cycles.
- Software distribution; consider the following hardware requirements:
- This SMS feature needs disk space on distribution points.
- There should be enough bandwidth between the clients and the distribution points.
- Software distribution creates status messages that need to be processed as well.
- Software metering; consider the following hardware requirements:
- Sufficient processing resources on the software metering database server.
- Adequate enough number of computers to carry out the software metering server role.
- A SQL Server database.
- Network analysis; consider the following hardware requirements:
- For Network Monitor, the Network Monitor Agent must be deployed on a computer in every subnet that needs to be monitored.
- For HealthMon, the HealthMon Agent must be deployed on each computer that needs to be monitored.
- Remote Tools; consider the following hardware requirements:
- Sufficient network bandwidth.
- Remote SMS Administrator consoles.
- SMS Installer scripts; consider the following hardware requirements:
- Disk space on the site server.
- Sufficient and memory processing resources on the site server.
The supported SMS site server languages are listed below:
- English
- French
- German
- Japanese
- Korean
- Simplified Chinese
- Traditional Chinese
Determining the Number of Objects for Site Server Processing
Object in the case of SMS refers to the components which SMS uses to store client and server data, move client and server data, and which are stored in the SMS site database. The different SMS features which are used create different types of objects.
The common types of objects are:
- Discovery data records (DDRs)
- Management Information Format (MIF) files
- Software inventory files
- Status VarFiles
The number of objects which the site servers have to process has an impact on the hardware requirements of the SMS site systems. You can though specify the number of objects which are generated by the SMS components.
The objects created by specific SMS features are listed here:
- The Logon discovery method creates one DDR for each user logon.
- All other SMS discovery methods create one DDR for each resource.
- The Heartbeat discovery creates one DDR for each heartbeat interval.
- Software distribution creates 3 status messages for a new advertisement, and creates 2 status messages for each existing advertisement.
- Hardware inventory creates one MIF file and one status message for each inventory interval.
- Software inventory creates one .sic or .sid file and one status message for each inventory interval.
Determining Server Resource Requirements
When networks are fairly large, there are many site systems used to support the SMS functions:
- Site database server
- Primary site server
- Secondary site server
- Component servers
- Logon point
- Client access point (CAP)
- Software metering server
- Software metering database server
- Distribution point
Within the SMS design, these site system roles can be assigned to the site server or it can be assigned to any other computer that forms part of the site hierarchy. Planning of site system roles should be done with thoroughness and great care.
There are a number of factors that should be considered, including:
- For the site database server; SMS is reliant on the SQL Server and its database. All SMS services in a primary site utilize SQL Server to update and manage the site database. The performance of SMS is therefore directly impacted by the performance of SQL Server. Here, SMS performance would be determined by the following factors:
- SQL Server performance.
- SQL Server hardware capacity.
- SQL Server configuration settings.
- Network access between the site database server and the site server.
- SMS Provider location.
The best possible performance is assured for SMS if SQL Server is installed solely for SMS. In addition to this, SMS performance is also maximized when the SMS site database and the computer for the SMS site server role exists on the same computer. The performance of SMS is also enhanced if the data and log devices reside on separate physical drives or on RAID arrays.
It is recommended that you install SQL Server on a separate computer to the site server when the following conditions apply:
- A dedicated computer cannot be used for the site server and SQL Server.
- There is a fast reliable network connection between the site server computer and the site database computer.
- SQL Server manages other databases.
- The site runs mainly as a software distribution service.
You can run numerous SMS databases on one SQL Server under the following conditions:
- To centrally manage your SMS and SQL Server databases.
- There is one copy of SQL Server for both the site database and software metering database.
- The database requirements can be distributed because SQL Servers is being underutilized.
- For the primary site servers; consider the following important factors:
- Installing Windows, SMS and SQL Server on the same disk would typically depreciate performance, unless the logical disk is a RAID implementation. The site server running SMS must have a minimum of 1 GB disk space. For packages, you would need roughly four times the amount of disk space.
- For large SMS sites that have multiple site systems and subsites, you need to ensure that the CPU does not become a processing bottleneck. You need to ensure that you have sufficient processing power when the site server runs SQL Server.
- It is recommended that you monitor the Committed Bytes and Memory Page Reads/sec counters in Performance Monitor to ensure that you have sufficient RAM. If you constantly have a high Committed Bytes counter, you should consider increasing the RAM.
- For secondary site servers; consider the following:
- Because secondary site servers have no subsites or SQL Server databases, the RAM requirement is 64 MB.
- The system files use roughly 40 MB of disk space on secondary site servers.
- For component site servers; consider the following:
- You need 2 MB of RAM for component servers.
- If component servers are being used for sending packages, you should ensure that you have adequate disk space for compressed packages.
- For client access points (CAPs); you would need additional CAPs when your existing CAPs have a heavy load. Remember that the CAPs processes all objects created by SMS client processes, and also host most of the client components. Therefore, when you deploy SMS, the CAP is usually under a heavy load. Once SMS is installed, the CAP processes objects created by SMS client activity and passes objects transmitted from clients to the site server.
There are a few SMS components that are known to place a load on a CAP:
- Hardware inventory
- Software inventory
- Advertisements
- Status messages
To improve performance, you should have at least two CAPS within a site.
- For distribution points; consider the following:
- Distribution points need sufficient disk capacity to obtain packages.
- Distribution points need both fast and reliable access to client computers.
- The load placed on distribution points is determined by the number of packages specified for distribution and the size of the packages being distributed.
- For clients that utilize NetWare, one NetWare server is needed to perform the distribution point role in a site.
To improve distribution point performance and availability:
- Deploy at least two distribution points in a site.
- To control the processing load placed on distribution points, you should place and schedule software distribution.
- For software metering servers; consider the following:
- You need at least one or more software metering servers if you plan to use the SMS software metering feature in a site.
- You should consider the traffic volumes created by user logon events and application start and shutdown events to determine how many software metering servers are required.
- Consider the mode that the software metering clients will use as well. In offline mode, software usage is tracked without enforcing software compliance. In online mode, software usage is tracked with the enforcement of software compliance.
If online mode is being used, consider the following additional factors:
- In online mode, a software metering server handles a fewer number of users than in offline mode.
- Network traffic volumes increase because of the instant reporting of the client agent to the particular software metering server.
- The load of the software metering server is directly impacted by the demand for licenses from clients.
Understanding Client Activity Generated by SMS
When it comes to client activity, the enabling and running of the SMS components affects how much client activity is generated. This basically means that the interval configured for the SMS components to run affects the SMS client activity cycles performed.
The common SMS client activity cycles performed are listed here:
- Heartbeat Discovery: The Heartbeat Discovery method rediscovers already discovered network computers. The purpose of Heartbeat Discovery it to ensure that the DDRs for computers remain updated or current in the SMS database. By default, Heartbeat Discovery is enabled, and you can use the SMS Administrator console to configure the Heartbeat Discovery method. It is though only active on those computers that have SMS clients installed. The default configuration is that Heartbeat Discovery results in each client generating one DDR per week. Heartbeat Discovery therefore does not really impact clients and network performance.
- Hardware and software inventory: Because hardware and software inventory collects data on the hardware properties of installed client computer hardware, and the Software Inventory Client Agent collects information on files and products; it is obvious that the inventory collection process is a processor intensive activity.
The aspects of inventory collection which affect client processors are listed here:
- Frequency at which inventory collection occurs.
- The quantity of data collected during inventory collection.
- Software metering data collection and reporting: The mode that you use for software metering affects how much activity is generated. In offline mode, software usage is tracked without enforcing software compliance. In online mode, software usage is tracked with the enforcement of software compliance. The default mode for software metering is offline mode, which creates less network traffic than online mode.
- Software distribution – new advertisement polling: Clients only poll for new advertisements each 60 minutes by default. This makes SMS clients polling for new advertisements not a processor intensive activity.
Determining Network Bandwidth
Network bandwidth can become a performance bottleneck in a SMS site. You can use tools such as Network Monitor to determine and monitor utilization on network segments. Network utilization should consistently be under 40 percent.
You should monitor the activities listed below when monitoring network bandwidth utilization. These activities generally generate network traffic:
- Discovery data
- Site configuration changes
- Collection updates
- Remote tool sessions
To solve network bandwidth bottlenecks, consider the following strategies:
- Use virtual LANs and switches
- Upgrade network components
- Relocate servers
SMS Site Server Hardware and Software Installation Requirements
The hardware installation requirements listed below are a guideline for a typical site server deployment which has to support the main SMS functions, and roughly one hundred computers:
- The production site server should be a computer specified on the Windows NT/Windows 2000 Server/Windows Server 2003 Hardware Compatibility List (HCL).
- SMS, Windows NT/Windows 2000/Windows Server 2003, and SQL Server run on computers which include CISC based x86 or RISC based Alpha CPUs. The hardware requirements for the two systems differ to some extent.
- One Pentium 133 processor is required to run a site server
- 64 MB of RAM is the minimum RAM requirement for a site server which contains a dedicated SQL Server. 128 MB of RAM should be assigned for a site server that supports about 100 client computers.
- Approximately 500 MB of disk space is typically required for a Windows NT Server version 4.0 (SP4), SQL Server version 7.0 and a SMS site server installation. The size of the site database and software metering database are excluded from figure though. Packages require additional hard disk space.
The software requirements are relevant to each site server installation.
- Site servers have to be installed on Windows NT Server version 4.0 (SP4), Windows NT Server version 4.0 Enterprise Edition, or Windows 2000 Server or Windows Server 2003.
- The disk partition used for the SMS source files must be NTFS formatted partitions.
- Internet Explorer 4.01 or above has to be installed to use the SMS Administrator console and the help features.
|
Bookmark Planning for SMS
