Users Guide

Use case scenarios using Dell Command |
Monitor 10.2.1
This chapter describes the various user scenarios of Dell Command | Monitor.
You can use Dell Command | Monitor for:
• Asset management
• Configuration management
• Health monitoring
• Profiles
Topics:
• Scenario 1: Asset management
• Scenario 2: Configuration management
• Scenario 3: Health monitoring
• Scenario 4: Profiles
Scenario 1: Asset management
A company that uses many Dell systems was not able to maintain accurate inventory information because of changes in the business and
IT staff. The Chief Information Officer (CIO), requests a plan for identifying the systems that can be upgraded to Microsoft Windows
latest versions. This requires an assessment of the deployed systems to determine the size, scope, and financial impact of such a project.
The information collection involves a significant effort. Deploying IT staff to each client system is expensive, in terms of man-hours and
end-user interruptions.
Using Dell Command | Monitor on each Dell system, the IT manager can quickly collect information remotely. Using tools such as Microsoft
System Center Configuration Manager (SCCM), the IT manager queries each client system over the network and collects information
such as CPU type and speed, memory size, hard-drive capacity, BIOS version, and current operating system version. Once the information
is collected, it can be analyzed to identify the systems that can be upgraded to Windows latest versions.
You can also get asset inventory through WSMAN/WinRM command line or any using any CIM client command line.
SCCM integration
You can integrate SCCM with Dell Command | Monitor for Windows by:
• Using the MOF file within Dell Command | Monitor install package, which contains all the Dell Command | Monitor classes and
importing to ConfigMgr
The MOF is located at:
C:\Program Files\Dell\Command_Monitor\ssa\omacim\OMCI_SMS_DEF.mof
• Extending asset reporting capabilities using collections
Scenario 2: Configuration management
A company plans to standardize the client platform and manage each system through its lifecycle. As part of this effort, 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.
4
Use case scenarios using Dell Command | Monitor 10.2.1 9