Checkpoints

[Previous] [Next]

If you've read this chapter carefully, you've already compiled a list of potential problems regarding client installation. The most obvious sources of error occur in four areas:

• Be sure that an appropriate client installation method or methods have been enabled and properly configured. It would be a good idea to review all your clients (servers and workstations) to determine whether your enabled installation method actually "hits" all your clients. For example, a logon installation method may not be appropriate for installing SMS on Windows NT servers at which administrators rarely or never log on locally.
• Be sure that the client can actually be assigned to your SMS site by confirming the site boundaries. Remember that SMS uses not only the subnet address of the client, but also its subnet mask to determine a client's site assignment.
• Be sure that you have enough free disk space on the client to complete installation of all enabled client components. Recall that you may need anywhere from 14 MB to 20 MB of disk space. And, of course, this should not be your last 14 or 20 MB of available disk space.
• Be sure that whatever client installation account you are using—the SMS Service account or your own designated SMS Client Remote Installation account—has local administrative rights on the client.

The Microsoft Systems Management Server 2.0 Resource Guide

If at all possible, you should obtain the Microsoft Systems Management Server 2.0 Resource Guide. This guide is part of the Microsoft BackOffice 4.5 Resource Kit available from Microsoft Press. It is also included as part of the Microsoft Tech Net CD subscription and other partner programs with Microsoft. The Microsoft BackOffice 4.5 Resource Kit contains several utilities that can facilitate your management of SMS clients in your site, including the following:

• Client Cleaner tool (20CliCln.bat) Removes all SMS 2.0 components from the client
• Client Utilities tool (Cliutils.exe) Lets you start, stop, and schedule processes on the client
• Set Client Event tool (SetEvnt.exe) Enables you to initiate components based on events—in particular, to trigger a CCIM maintenance cycle
• Set Preferred Distribution Point and CAP tool (PrefServ.exe) Enables you to designate a preferred distribution point or CAP for each client.