Chapter 6. IBM System Management Tools
to the network and respond with a signal that allows the network to gain control of the client and prevents
the local operating system from loading.
LCCM will then query the client for vital product data through its Systems Management BIOS and Wired
for Management/DMI features. LCCM creates a client profile as part of an Individual Client Details record
and database with this information (e.g., machine type and serial number, disk, memory size,
graphics/video chipset, MAC address, BIOS level and more.)
If the PC is equipped with Asset ID, as are select models of IBM client system PCs and IntelliStations,
LCCM can also recover any information that has been recorded about the user. Asset ID allows an
administrator using a radio-frequency handheld unit to record information to a system EEPROM without
even opening the system's packing carton.
Otherwise, LCCM assigns a default name to the client during the scan, and can optionally prompt the end
user to enter personal information such as his location, department and phone number, etc.. If a user is
not present, this request will automatically time-out. The data collected is entered automatically into the
Individual Client Details record.
Flashing the CMOS or BIOS
The LCCM administrator can use the information gathered from the client to review its CMOS settings and
BIOS level. In some cases, these may need to be changed to ensure consistency across the enterprise
or to conform to corporate policies.
Since LCCM gains control of the system before the local operating system was booted, LCCM allows
administrators to remotely perform low-level maintenance tasks, like flashing the BIOS, that need to occur
during the preboot state. The only alternatives are to involve the end user or send a technician to each
client. LCCM is complementary to postboot management tools, which need a local operating system
running, such as DMI browsers or software change management programs.
Installing Software
Next, the network administrator uses the information that LCCM has gathered about the client to
determine the end user's software requirements, including operating system and applications. (When
Asset ID is used, this step can be simplified by recording the end user's software profile to the system
EEPROM.)
The software can come from one of two sources: a compressed software "image" that includes a copy of
all of the software needed by the local client, or from installation files located on a file server. In either
case, the software can be downloaded to the client without intervention by the user or the administrator.
LCCM New Client Scenario
1. LCCM Administrator starts scanning the network for new PCs
2. 2 PCs found. LCCM displays PC serial #, captures and associates vital product data, etc.
3. LCCM creates Individual Client Details notebook for new clients
4. Administrator assigns clients to software profiles
Administrator examines level of BIOS
Elects to update BIOS and distribute a different image to each PC-one used by Marketing, one by
Accounting, using Hybrid RPL
Schedules the update to occur on Saturday at 7:00 am and to use Wake on LAN to turn on the
PC Saturday morning, 7:00 am
5. Server awakens the new client PCs with Wake on LAN PC uses alternate boot sequence to boot to
server, proceses job, sends message to server when done
44
Technical Information Manual