• Main Menu
  • Understanding Systems Management Server (SMS)


    Systems Management Server (SMS) Overview

    SMS 2.0 is a Microsoft BackOffice systems management tool that can both operate in and manage an assortment of network environments. Systems Management Server (SMS) enables network environments and network resources to be centrally controlled. The core control point or center of Systems Management Server is the SMS Administrator console. This is a snap-in to the Microsoft Management Console (MMC). The industry standard for Web-Based Enterprise Management (WBEM) is the core of SMS data collection and presentation.

    The main functions of SMS are listed here:

    • Resource discovery
    • Hardware and software inventory
    • Software distribution
    • Software metering
    • Network Analysis
    • Remote support through the Remote Tools feature

    The SMS Administrator console is used to access and initiate these SMS 2.0 functions. A process known as resource discovery must be performed first to find computers, network hardware, and groups and users.

    The main SMS components are listed here:

    • SMS site: A SMS site specifies the computers, other 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.Understanding Systems Management Server (SMS)

    An SMS site consists of the following SMS components

    • SMS site server
    • SMS site systems
    • 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:

    • Parent site: This is a SMS site that contains one or multiple additional site beneath it.
    • Child site: This 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:

    • Primary site
    • 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 includes:
      • Collection of discovery information on the client.
      • Determines the site assignment of the client.
      • Pass 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
      • 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.
      • 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, an 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
      • Microsoft Windows 95

    Understanding the Resource Discovery Methods

    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. SMS 2.0 still considers computer clients as being one of the main resources that needs to be discovered and then added to the SMS database.

    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 servers
    • Print servers
    • Global groups
    • Domain users
    • All other networking devices that have IP addresses

    When SMS discovers a network resource, a record for that particular resource, called a discovery data record (DDR), is created and then included in the SMS database. The specific information discovered on a particular resource is determined by the nature of the resource.

    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

    There are seven methods that can be used to discover network resources. These resource discovery methods are discussed below:

    • Site system discovery; includes the following two discovery methods:
      • Windows NT Server Discovery
      • NetWare Bindery Server Discovery

      These discovery methods automatically create discovery records for the servers that are assigned one of the site system roles (logon point, client access point, distribution point). The site system discovery methods are automatically started by the WINNT Server Discovery Agent and the NetWare Bindery Server Discovery Agent SMS threads. This basically means that you cannot configure the site system discovery method through the SMS Administrator console.

    • Logon discovery; includes the following two discovery methods:
      • Windows Networking Logon Discovery
      • NetWare Bindery Logon Discovery
      • NetWare NDS Logon Discovery

      The Windows Networking Logon Discovery methods create discovery records for each resource supported by SMS that logs on to the network. The NetWare Bindery and NetWare NDS Logon Discovery methods create discovery records for NetWare client resources.
      With the logon discovery method, you use the SMS Administrator console to perform the following tasks:

      • Assign logon points.
      • Enable the logon process through changing the logon scripts of the users.

      With logon discovery, the discovery data record (DDR) contains the information listed here. The exact information included is determined by the type of client.

      • SMS unique identifier
      • NetBIOS name
      • IP addresses and IP subnets
      • IPX addresses and IPX network numbers.
      • MAC addresses
      • Resource domain
      • Operating system name
      • Last logon user name
    • Windows NT User Account discovery: This method deals with discovering domain user accounts and then adding the information to the SMS database. When you configure this discovery method in the SMS Administrator console, you can specify which domain should be utilized to discover the information. A DDR is created for each user account that is discovered.
    • Windows NT User Group Discovery: This method deals with discovering domain global group accounts and then adding the information to the SMS database. Whn you configure this discovery method in the SMS Administrator console, you can specify which domain should be utilized to discover the information. A DDR is created for each group account that is discovered.
    • Network Discovery: The Network Discovery method can find the following:
      • Domain controllers
      • Routers
      • Computers
      • Subnets
      • DHCP servers
      • SNMP enabled devices’ IP addresses
      • SNMP community strings
      • Network addresses
      • Numerous devices on the network

      Before a DDR can be generated, the Network Discovery method has to have IP address and subnet mask information.

    • 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.
    • Manual Discovery: If you need to manually create a DDR for a specific client, then you can use the Manual Discovery method.

    Understanding Client Installation Methods

    As seen in the previous section of this Article, there are different resource discovery methods. So too are there different client installation methods. While the client installation processes differ somewhat, the underlying tasks performed are still the same:

    • Bootstrap
    • Discovery
    • Assignment
    • Installation

    The client agents that can be installed and enabled on SMS client are listed here:

    • Advertised Programs Client Agent
    • Hardware Inventory Client Agent
    • Event to Trap Translator Client Agent
    • Software Inventory Client Agent
    • Software Metering Client Agent
    • Remote Tools Client Agent

    The different client installation methods are listed below:

    • Logon client installation method; includes the following logon client installation types:
      • Windows Networking Logon Client Installation
      • NetWare Bindery Logon Client Installation
      • NetWare NDS Logon Client Installation
    • Windows NT Remote Client Installation
    • Manual client installation

    The above client installation methods are used to install client agents. You can perform client installation before a computer resource is discovered. A logon discovery method is associated with a client installation method. To install a client agent, a user needs to be logged on to the network at computer. This is the case for all methods other than the Windows NT Remote Client Installation method.

    Hardware and Software Inventory Overview

    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

      You can configure which hardware properties information should be collected by SMS. The Hardware Inventory Client Agent or simply Hardware Inventory Agent collects the actual hardware properties information from the client. The hardware inventory is stored in the SMS database. When it comes to a secondary site server, you can also enable the Hardware Inventory Client Agent on a secondary site server. The secondary site server would then pass hardware inventory information to its associated primary site, and it is then eventually added to the SMS database.

    • Software inventory: Includes the following components:
      • Inventory collection; collects and writes file statistical information to the site database. /li>
      • File collection; locates the inventoried files in a directory on the SMS site server. Administrators can access the information by using the SMS Administrator console.

      The Software Inventory Client Agent, also called Software Inventory Agent, runs automatically on the client based on how the schedule for collecting information is defined. 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 Overview

    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.

    For a SMS client computer to receive packages:

    • The SMS client computer must have the Advertised Programs Client Agent installed.
    • The SMS client computer must be a member of a collection.

    The typical tasks for distributing packages are listed here:

    • Specify the 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.

    Using SMS to install software on SMS client computers from a network distribution share involves the following process:

    • You have to create a SMS package that includes the location of the source files and the package definition file (.pdf). The package definition file includes the information that would be needed to create the SMS package. The SMS package includes command-line executables as well. These executables runs on the SMS client computers to manage how the SMS package executes.
    • You then have to distribute the SMS package to the distribution points that you have identified.
    • Lastly, you have to create an SMS advertisement that will inform the SMS clients on the available software.

    The package definition file (PDF) includes the information needed for the following:

    • Create the software distribution package for an application.
    • Create the programs in the software distribution package.

    With SMS 2.0, the Definition Wizard and Distribute Software Wizard contain the PDFs. The Distribute Software Wizard is used to provide the information on distributing the software. When executing the Distribute Software Wizard, you have to select which package should be distributed. This involves selecting the Create new package from a definition option and then specifying the PDF that should be imported.

    The Definition Wizard is used to create the package and program. Using the Create Package from Definition Wizard involves the steps listed here:

    • Create the package source files.
    • Create a package for the application by using the PDF and the Create Package from Definition Wizard.
    • Define the distribution points for the package.
    • Advertise the program(s) of the package to clients.

    SMS Software Metering Overview

    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:

    • Offline mode: In offline mode, software usage is tracked without enforcing software compliance. The characteristics of offline mode are:
      • Tracks applications running on client computers.
      • Programs not intended to be monitored are excluded.
      • Prevents applications from being used, based on the computer name, or user account or group account.
      • Uses software usage data to generate usage data reports.
    • Online mode: In online mode, software usage is tracked with the enforcement of software compliance. The characteristics of online mode are:
      • Tracks applications running on client computers.
      • Programs not intended to be monitored are excluded.
      • Prevents applications from being used, based on the computer name, or user account or group account.
      • Prevents applications from being used when there is no authorization.
      • Includes support for software license check-in and check-out for remote users.
      • Assesses and balances license usage in sites and between sites.
      • Includes a callback queue feature that allows users to utilize an application once a license becomes available.
      • Uses software usage data to generate usage data reports.

    The following components are involved in the software metering process:

    • Site server: This is the place where you configure the components that support software metering, and specify which applications are included or excluded from the software metering process. The site server is also where you specify how many licenses are available, and the balancing of license information.
    • Software metering server: The software metering server performs the following functions:
      • Obtains configuration information from the site server.
      • Obtains license information from the site server.
      • Maintains and stores software usage information received by client agents.
      • Replies to client requests for application access and licenses.
    • Software metering database server: Used to store software metering information. The software metering database server is a separate database to the SMS database. To view information in the software metering database server, you need to use the Software Metering tool.
    • SMS client running the Software Metering Client Agent: Clients that have the Software Metering Client Agent installed participate in the software metering process. The Software Metering Client Agent is configured by means of the site server.

      The main functions of the Software Metering Client Agent are listed here:

      • Pass software usage information to the software metering database server.
      • Request licenses for clients.
      • Update component information on the client.

    Network Analysis Overview

    The tool which you can utilize to both monitor and log network activity as it occurs on the network is Network Monitor. You can use the information obtained from Network Monitor to optimize network traffic as well. Network Monitor stems directly from the Windows NT Network Monitor. Network Monitor is included with Windows Server 2003 and with SMS 2.0 .

    The key 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.

    There are two versions of Network Monitor available:

    • The basic Network Monitor version which is included with Windows Server 2003.
    • The full Network Monitor version which is included with Microsoft Systems Management Server (SMS).

    With the full version of Network Monitor included with SMS 2.0, you can monitor network activity and capture frames on all devices on the network segment. 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 the following information:
      • The 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:

    • Network Monitor experts: These are analysis tools that assist with analyzing the captured network data. The different Network Monitor experts are:
      • Average Server Response Time; this expert determines the average time taken by each server to reply to a request.
      • Property Distribution; calculates the protocol statistics for a protocol property in a capture session.
      • Protocol Coalesce Tool; for a transaction that was fragmented, this expert combines the frames to form a new capture file.
      • Protocol Distribution; determines which protocols created the majority of the traffic in a capture.
      • TCP Retransmit; indicates those TCP frames which were transmitted multiple times during a capture session.
      • Top Users; determines which senders and receivers created the majority of the traffic in a capture.
    • Network Monitor monitors: These are monitor tools used to capture frames for monitoring specific network traffic patterns. The different Network Monitor experts are:
      • ICMP Redirect Monitor; this monitor creates events whenever Internet Control Message Protocol (ICMP) frames are redirected by:
        • A router not authorized to redirect the frames
        • A router incorrectly configured.
      • IP Range Monitor; creates an event when a frame’s IP address is not within a valid address range. The IP address is basically unauthorized.
      • IP Router Monitor; creates an event when a particular IP router fails.
      • IPX Router Monitor; creates an event when a particular IPX router fails.
      • Rogue Monitor; creates an event when an unauthorized DHCP server or WINS server is detected on the network.
      • Security Monitor; creates an event when there are unauthorized users capturing frames through Network Monitor.
      • SyncAttack Monitor; monitors the network for all suspicious connections made to servers on the network.

    SMS Remote Tools Overview

    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.

    Remote tools can be installed on the following components when you run SMS 2.0 Setup

    • SMS primary site
    • SMS secondary site
    • On a Windows server as a SMS Administrator console

    Before clients can use Remote Tools, the following requirements have to be met:

    • Remote access to the client must be allowed.
    • The client must be a SMS client.
    • The client must have the Remote Tools Agent must be installed. The Remote Tools Agent must be enabled/running.
    • The SMS Administrator console computer and the SMS client must use the same protocol:

    SMS 2.0 Tools Overview

    The SMS 2.0 tools have been categorized into a number of broad categories. While there are some tools that can be included in more then one category, the tool falls within the category which best matches the actual tool.

    The main factors considered to categorize the various SMS 2.0 tools are listed here:

    • Installation considerations for installing the tool.
    • Purpose or function of the SMS tool.
    • Area which the tool deals with or services.

    When you install SMS tools, you can install the tools based on category. This essentially enables you to simultaneously install the entire set of tools within the specific category.

    The SMS tool categories are:

    • System Setup Tools; includes the following system setup SMS tools:
      • Administrator Console Setup (v20Admin.ini, v20Admin.sms): Used to install the SMS 2.0 Administrator console on a computer that is not the site server.

        To use the Administrator Console Setup tool, you have to perform the following process:

        • Create a disk image of the SMS 2.0 compact disc.
        • Locate the disk image on a package source directory.
        • Copy V20Admin.ini to the SMSSetupBin directory of the package source directory which was created.
        • Use v20Admin.sms as the PDF and the created package source directory to create software distribution package.
        • Create an advertisement for the specific package
        • Indicate which computers the SMS 2.0 Administrator console should be installed for.
        • The package will then install SMS 2.0 Administrator console for these computers.
      • Client Preload (CliStage.ipf): Used to install SMS client software on the computer prior to the particular computer being added to a SMS site.
      • Query Backup and Restore (QryEdit.exe): Used to back up SMS queries and restore SMS queries. The Query Backup and Restore tool can be used to export a query from one SMS site and then import the query to a different SMS site. The tool though only works for user defined queries. You cannot use the Query Backup and Restore tool on the default SMS 2.0 queries.
    • Site Maintenance and Administration Tools; includes the following site maintenance and administration SMS tools:
      • Delete Group Class (DelGrp.exe): Used to delete a group class and its associated tables from the SMS site database.
      • License Reports (LicenseReports.mdb): Used to access the data in the software metering database and create reports which utilize this data.
      • Load Site Boundary (SiteBndy.exe): Used to load site boundaries through the usage of a text file. Therefore, before the Load Site Boundary tool can be utilized, you have to create a text file that contains the list of site boundaries which should be loaded. The default configuration is that all site boundaries defined in the text file are added to the existing site boundaries.
      • Load Network Discovery (NDiscLdr.exe): Used to load network resources for Network Discovery through a text file. Once again, to use the Load Network Discovery tool, you first have to create a text file that contains the network resources which should be loaded. You can define the following resources:
        • Subnets
        • Domain
        • DHPC servers
        • SNMP devices.
      • Make Collection (Makecoll.exe): Used to create a new collection from a text file of either NeBIOS computer names or IP addresses. Before you can use the Make Collection tool, you have to create a text file that includes the list of NetBIOS computer names or IP addresses for the new collection.
      • Preferred Server (Localsvr.exe, SetSMSsvr.exe): LocalSvr.exe is used to query the SMS site database for the network abstraction layer (NAL) paths of distribution point groups and client access points (CAPs). The SetSMSSvr.exe tool is used to locate the paths in the client registry, to indicate to the client what the preferred distribution point groups and CAPs are.
      • Query Extract (SMSExtract.xlt, SMSExtract.xls, SMSExtract.mdb): Used to extract SMS query results into a Microsoft Excel workbook or Microsoft Access table.
      • Site Utilities (Preinst.exe): Used to perform the following functions:
        • Stop SMS services at a SMS site.
        • Identify problems or issues in a site.
        • Repair a SMS site.
    • Client Maintenance Tools; includes the following client maintenance SMS tools:
      • APM Spy (APMSpy.exe): A command-line tool installed and executed on the client to view internal Advertised Program Manager data for a client in a format which can be read.
      • Client Cleaner (20CliCln.bat): Used to remove a SMS 2.0 client and its associated SMS client components.
      • Client Utilities (Cliutils.exe): Used to perform the following functions on a SMS client:
        • Start a SMS client component.
        • Stop a SMS client component.
        • Specify a Start Cycle event for a particular SMS client component.
        • Register an application to be started by the client launchers.
        • Display schedule information for a client component
      • Process Viewer (Pview95.exe): Used to display information on processes on the local or remote Windows computers using a GUI.
      • Set Client Event Tool (SetEvnt.exe): Used to initiate client component events on a SMS client. The Client Event tool forces the Client Configuration Installation Manager (CCIM) and Copy Queue to cycle on the client, by default. You can though specify other client component events as well.
      • Set Preferred Distribution Point and CAP Tool (PrefServ.exe): Used to define the preferred distribution point and CAP for the SMS client.
      • Set New ID Tool (Newuid.exe): Used to allocate a unique SMS identifier (ID) to the client.
      • Zap (Zap.exe): Used to delete a file which cannot be deleted or which is in use.
    • Log File, Schedule File, and Error Code Tools; includes the following SMS tools:
      • Convert Schedule and Read Schedule Tools (SchedCnv.exe and ReadSche.exe): Used for troubleshooting purposes, to display schedule string in a format which can be read.
      • Dump Error Messages (Error32.exe) : Used to display error messages for Win32 error codes.
      • Dump Scheduler Data (DumpSend.exe): Used to display data from a Scheduler send request (.srq) file.
      • Log Span (LogSpan.exe): Used to view SMS log file activity for a specified time period.
      • NAL Logging (Turn_on_nal.reg): Used to enable/disable NAL logging on the SMS server or on the SMS client. It is recommended that you disable NAL logging after the information was retrieved so that the log file size can be decreased again.
      • SMS Trace and Tracer (Smstrace.exe, Tracer.exe): Used to view log file data as it is added to the log file. The SMS Trace and Tracer tools can be installed on the SMS server or SMS client. Before you can use the tools though, you have to enable logging in the SMS Service Manager.
    • Discovery and Inventory Tools; includes the following discovery and inventory SMS tools:
      • Dump Discovery Data (Discdump.exe): Used to obtain network discovery information from the local client discovery data record (DDR).
      • Inventory Synchronizer (InvSyncexe): Used to pass a hardware inventory resynchronization or software inventory resynchronization request to a client.
      • MIF Checker (MIFCheck.exe): Used for the following purposes:
        • Display the Management Information Format (MIF) file in a format that can be read.
        • Verify the MIF file’s syntax.
        • Report MIF file syntax errors and semantic errors.
        • Parse a MIF file.
      • MIF Form Generator and MIF Entry (Mifgen.exe, Mifwin.exe): Used to extend the client’s computer inventory to contain further information. This is done through the creation of custom groups for storing the additional information.
      • MOF Manager (MofMan.exe): Used to modify the hardware classes and attributes collected for hardware inventory.
      • Software Inventory Viewer (SinvView.exe): Used to for the following purposes:
        • Display and view data processed through the SMS Software Inventory Processor.
        • View data from full inventory files.
        • View data from delta inventory files.
        • View data from the software inventory history file.
      • Software Distribution Tools; includes the following software distribution SMS tools:
        • Advertisement Info (AdvInfo.exe) : Used to display the header information contained in a package file or an advertised programs offer file, including the following:
          • Name
          • Version
          • Package ID.
          • Language
          • MIF file information
          • Disk space requirements
          • Command line for the executable file
        • Configure Client Desktop (SetStart.exe): Used to configure a program shortcut on the Start menu or desktop of the client.
        • Delete PDF (DeletPDF.exe): Used to remove package definition files (PDFs) from a SMS site database.
        • Make CAP (MakeCAP.exe): Used to assign a client access point (CAP) role to a specific server.
        • Make Distribution Point (MakeDist.exe): Used to assign a distribution point role to a specific server.
        • Make Distribution Point Group (MakeDPG.exe): Used to create a distribution point group by using a text file.
        • PDF Wizard (Pdfwiz.exe): Used to create a PDF from a package ID.
        • Test Application (TestApp.exe): Used for the testing of software distribution packages.
      • Remote Control Tools; includes the following remote control SMS tools:
        • Remote Control Settings (RCCliopt.exe): Used to configure the following parameters for a remote client:
          • Default protocol
          • Lana number
          • Specify the Update Enabled setting to enable/disable multisite Remote Control security settings.
        • Set NIC Tool (Multinic.exe): Used to configure the network interface card (NIC) a client binds to.
        • Stop Remote Control (StopRC.exe): Used to stop the Remote Control Client Agent running on a client that uses a RAS account to connect to the network.
      • Scalability Tools; includes the following scalability SMS tools:
        • Site Properties Manager (SMSSPMan.exe): Used to create a hierarchy of sites. The tool allows you to import/export site properties using a GUI. The GUI enables you to easily copy site properties configuration from one site to another site.
        • SMS Console Load Simulation (UILoad.exe): Used to simulate the effect of running multiple SMS Administrator consoles concurrently on a computer. The tool enables you to determine what the load will be on a SMS site when multiple SMS Administrator consoles are being utilized.
        • SMS Object Generator (SMSObgn.exe, SMSObldr.exe): For testing system performance, the SMS Object Generator tool is used to generate data which reflects the actual/expected load on a SMS site
      • SMS 1.2 Interoperability Tools: includes the following interoperability SMS tools:
        • Add/Remove 1.2 Console (V12Admi.ipf): Use this tool to add/remove the SMS 1.2 Administrator console from a computer which currently has the SMS 2.0 Administrator console installed.
        • PGC Migration Wizard (SMS_MPGC.exe): Used to upgrade the PGC application from SMS 1.2 to SMS 2.0.

    Got Something To Say:

    Your email address will not be published. Required fields are marked *

    One comment
    1. Dendy

      5 May, 2011 at 3:42 am

      What’s the command prompt for accessing the SMS Properties in client side ?

      Reply
    Microsoft SMS
    } 108 queries in 0.440 seconds.