Users Guide
Scenario 2: Conguration management
A company plans to standardize the client platform and manage each system through its lifecycle. As part of this eort, the company
acquires a suite of tools, and plans to automate the deployment of a new client operating system using the Preboot Execution Environment
(PXE).
The challenge is to modify the BIOS password in the BIOS of each client computer without manually visiting the desktop. With Dell
Command | Monitor installed on each client system, the IT department of the company has several options for remotely modifying the boot
order. The OpenManage Essentials (OME) is a management console that can be integrated with Dell command | Monitor and used to
monitor BIOS settings remotely on all enterprise client systems. Another option is to write a script (CIM, WinRM/WSMAN/PowerShell/
WMIC) that changes the BIOS setting. The script can be remotely delivered over the network and run on each client system.
For more information on Dell Command | Monitor, see Dell Command | Monitor Reference Guide at dell.com/
dellclientcommandsuitemanuals.
For more information on Dell Command | Monitor, see Dell Command | Monitor Reference Guide.
Standardized congurations can provide signicant cost savings for companies of all sizes. Many organizations deploy standardized client
systems, but few manage the system conguration throughout the life of the computer. With Dell Command | Monitor installed on each
client system, the IT department can lock down Legacy ports to prevent the use of unauthorized peripherals, or enable Wake On LAN
(WOL) to revive the system from a sleep state during non-peak hours to perform systems management tasks.
Scenario 3: Health monitoring
A user receives read error messages while trying to access certain les on the client-system hard drive. The user reboots the system and
the les now appear to be accessible. The user disregards the initial problem because it appears to have resolved itself. Meanwhile, Dell
Command | Monitor queries the hard drive with the problem for a predicted failure and passes a Self-Monitoring, Analysis and Reporting
Technology (SMART) alert to the management console. It also displays the SMART error to the local user. The alert indicated that several
read/write errors are occurring in the hard drive. The IT department of the company recommended that the user must make a backup of
critical data les immediately. A service technician is dispatched with a replacement drive.
The hard drive is replaced before it fails, preventing user downtime, a help desk call, and a technician trip to the desktop to diagnose the
problem.
Monitoring system alerts through operating system Event
Viewer, Syslog, or CIM indication
Dell Command | Monitor supports monitoring events through the following procedures:
• Pulling the log through CIM class DCIM_LogEntry.
• Monitoring CIM indication through DCIM_AlertIndication class.
• (only for Dell Command | Monitor for Windows) Monitoring events through Simple Network Management Protocol (SNMP) and
Windows event viewer.
• (only for Dell Command | Monitor for Linux) Monitoring through Syslog.
For more information on Dell Command | Monitor, see Dell Command | Monitor Reference Guide at dell.com/
dellclientcommandsuitemanuals.
For more information on Dell Command | Monitor, see Dell Command | Monitor Reference Guide.
Scenario 4: Proles
NOTE
: DMTF proles are implemented for Dell Command | Monitor for Windows only.
User scenarios 13