Client Features Flowcharts
Client features provide SMS 2.0 functionality to client computers rather than site systems. SMS provides each client feature using client agents that run on the client and deliver the client side of each feature’s functionality. You enable and configure client features at the site level using the SMS Administrator console, and these settings affect every client within the site.
When SMS installs clients, the client agents that provide the features you have enabled (such as software distribution) are installed along with the base client components. If you do not enable client features before client installation, you can also enable them after the client has been installed. In that case, the related client agent is installed on each client after you enable the feature.
This chapter contains the component flowcharts for both the client-side and server-side of features that use SMS client agents. This chapter includes the following flowcharts:
- Hardware Inventory: 32-Bit Client
- Hardware Inventory: 16-Bit Client
- Software Inventory: 32-Bit Client
- Software Inventory: 16-Bit Client
- Software Distribution: Windows NT Client
- Software Distribution: Windows 9x Client
- Software Distribution: 16-Bit Client
- Software Metering: Processing an Offline Log File
- Status Message: Client Component
- Remote Tools: Client Agent Installation
Before you use the tips and flowcharts in this chapter, you should be familiar with the information presented in the following chapters of the SMS 2.0 Administrator’s Guide:
- Chapter 10, “Collecting Hardware and Software Inventory”
- Chapter 12, “Distributing Software”
- Chapter 14, “Metering Software”
- Chapter 15, “Supporting Remote Users and Clients”
- Chapter 20, “Understanding the SMS Status System”
You should also become familiar with the flowchart introductory material in Chapter 16, “Introducing the SMS 2.0 Flowcharts.”
Note Several flowcharts in this chapter include information that applies to all SMS-supported versions of Microsoft Windows. You should interpret the names of log files and executables listed with xx in their name, for instance, Licclixx.log, to reflect the version of Windows installed on the client computer. For example, if you are looking at this log on a Windows 2000 or Windows NT client, the log will be named LiccliNT.log. Client agent executable files are named in a similar fashion. For example, the software metering agent is called LiccliNT.exe on a Windows 2000 or Windows NT client, and Liccli95.exe on Windows 95 or Windows 98 computers.