Users Guide

User scenarios

This chapter describes the various user scenarios of Command | Monitor.

You can use Command | Monitor for:

• Asset management

• Configuration management

• Health monitoring

• 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 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 determine the systems that can be upgraded to Windows latest versions.

You can also get asset inventory through script or any Windows Management Instrumentation (WMI)

command line.

SCCM integration

You can integrate SCCM with Command | Monitor by:

• Using the MOF file within Command | Monitor install package, which contains all the 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