| Planning
|
Design a Microsoft
Systems Management Server (SMS) site; plan
for various elements.
- Identify location of resources.
- Identify types of resources, which consist
of computers, printers, routers, users, and user
groups.
- Choose features of SMS to be implemented.
- Identify hardware and software requirements
for site systems.
|
Design an SMS site
hierarchy.
- Identify the number of sites needed, based
on considerations that include number and types
of resources, network connectivity, and
international issues such as language.
- Identify the number of layers needed, based
on considerations that include number and types
of resources, network connectivity, and
international issues such as
language.
|
Plan a security
strategy for SMS servers.
- Implement appropriate SMS accounts.
- Implement access permissions for varying
levels of SMS administration.
|
Plan the
interoperability or upgrade for various
situations.
- Plan the interoperability of a mixed
SMS 1.2 and SMS 2.0 site.
- Plan the upgrade of an SMS 1.2 site to
an SMS 2.0 site.
|
| Installation and Configuration |
Install, configure,
and modify a primary site server.
- Use Express Setup and Custom Setup.
- Configure the Microsoft Windows NTŪ
Server computer that will be the site server.
- Set up Microsoft SQL Server™ during SMS
Setup.
- Use a remote SQL Server.
- Shut down, reset, and restart the current
installation.
- Change the user name and password of the SMS
service account.
- Change the SQL Server information.
- Remove SMS.
- Install new SMS components.
|
Install a secondary
site server.
- Perform the installation from the CD-ROM.
- Perform a network installation by using
files from the network or the CD-ROM.
|
Configure site system
roles.
- Configure component servers.
- Configure logon points.
- Configure distribution points.
- Configure client access points.
- Configure software metering servers.
- Configure the SMS Administrator
console.
|
Configure a site
hierarchy.
- Configure site addresses.
- Add and configure senders, which consist of
Standard, Courier, and RAS.
- Implement parent-child relationships.
- Remove a site from the site
hierarchy.
|
| Configuring and Managing Resources
|
Configure software
and hardware inventory collection for a site.
- Enable and configure hardware inventory
collection.
- Enable and configure software inventory
files to be scanned and collected.
|
Manage inventory
data.
- View inventory data, including history.
- Use the SMS Administrator console to manage
inventory data.
- Customize inventory data.
|
Distribute software.
- Use SMS Installer to produce installation
executable files.
- Create a query to locate target computers.
- Create a collection of target computers.
- Create a package, program, and advertisement
to distribute software.
- Monitor the software distribution process by
using status messages.
- Use the SMS client software to run or
install a program on a client computer.
- Remove advertised software from distribution
points.
|
Configure and use
software metering.
- Configure software metering servers and
client components.
- Add products to be licensed.
- Configure licensing options.
- Exclude products from being metered.
- Meter software.
- Manage software metering data.
- Generate reports and graphs.
|
| Integration and Interoperability |
Install and configure
an SMS client computer.
- Discover client computers.
- Configure client installation methods for
client computers.
- Run the client computer installation.
- Identify changes made to client computers.
|
Install and configure
remote utilities on client computers.
- Configure Remote Tools Client Agent at the
site server.
- Configure Remote Tools settings at the
client computer.
- Configure protocols on client computers.
- Use diagnostic utilities for client
computers.
- Use Remote Tools.
|
| Install and configure
Windows NT Event to SNMP Trap translator. |
| Install and configure
Health Monitor to monitor Windows NT Server
computers. |
| Monitoring and Optimization |
| Identify changes to a
site server after SMS installation. Types of site
servers are domain controllers, non-domain
controllers, and secondary site servers. |
Monitor SMS status
messages.
- Configure status messages.
- Configure and use SMS Status Message Viewer.
- Configure and use SMS logs to monitor SMS
process activity.
|
Monitor the progress
of SMS functions.
- Monitor the progress of client installation.
- Monitor the progress of inventory
collection.
- Monitor the progress of software
distribution.
- Monitor the progress of remote control.
- Monitor the progress of software
metering.
|
Use SMS utilities to
monitor SMS functions.
- Use the Windows NT Event Viewer to view
SMS error messages.
- Use the Status Message Viewer to monitor SMS
components and processes.
- Use Network Monitor to view and filter
network traffic.
- Use Network Trace to trace the SMS network.
- Use SMS Trace to track and view log
files.
|
| Optimize SQL Server
for SMS. |
| Optimize sender
network utilization. |
Monitor the SMS
database.
- Configure SMS database maintenance tasks.
- Back up and restore the site
database.
|
| Back up an SMS site.
|
| Troubleshooting |
| Choose the
appropriate diagnostic tool. |
Diagnose and resolve
installation problems in SMS site systems.
- Diagnose and resolve installation problems
involving the primary site server.
- Diagnose and resolve installation problems
involving the secondary site server.
- Diagnose and resolve installation problems
involving client access points, distribution
points, logon points, and component
servers.
|
| Diagnose and resolve
installation problems involving client computers.
|
| Diagnose and resolve
problems involving software distribution. |
| Diagnose and resolve
problems involving inventory collection. |
| Diagnose and resolve
problems involving remote control. |
| Diagnose and resolve
problems involving software metering. |
| Diagnose and resolve
problems involving SNMP integration. |
Restore an SMS site.
- Restore a SQL Server.
- Restore a site server.
- Restore logon points, client access points,
and distribution points.
|
| Diagnose and resolve
problems involving site-to-site communication. |
