Users Guide
Table Of Contents
- Dell Command | Monitor Version 10.2.1 User's Guide
- Introduction to Dell Command | Monitor 10.2.1
- Windows SMM Security Mitigations Table (WSMT) Compliance
- Standards and protocols for Dell Command | Monitor 10.2.1
- Use case scenarios using Dell Command | Monitor 10.2.1
- Using Dell Command | Monitor 10.2.1
- Polling interval setting
- RAID status reporting
- Monitoring the Dell client systems
- Application log for Dell Command | Monitor for Linux
- Detecting advance format drives
- Boot configurations
- Changing the system settings
- Managing Dell client systems locally using Dell Command | Monitor 10.2.1
- Managing Dell client systems remotely using Dell Command | Monitor 10.2.1
- Frequently asked questions for Dell Command | Monitor 10.2.1
- Troubleshooting steps using Dell Command | Monitor 10.2.1
- Unable to remotely connect to Windows Management Instrumentation
- Installation failure on systems running Windows
- BIOS setting enumeration value appears as 1
- Hapi installation fails due to the dependency of libsmbios
- CIM resources not available
- Unable to execute the commands using DCM on the systems running Ubuntu Core 16
- Third-party licenses
- Other documents you may need
- Contacting Dell
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
4
Use case scenarios using Dell Command | Monitor 10.2.1 9