Dell Command | Monitor is designed for Dell Enterprise Client systems, Dell IoT Gateway systems, as well as for Dell Embedded PCs.
With Dell Command | Monitor, system administrators can remotely manage assets, monitor system health, and inventory deployed systems in an enterprise.
NOTE: Dell Command | Monitor was formerly Dell OpenManage Client Instrumentation (OMCI). After the OMCI version 8.2.1, OMCI is rebranded as Dell Command | Monitor.Dell Command | Monitor interfaces with leading enterprise management consoles that support industry standards. This approach helps to ensure that Dell systems can be managed by a broad array of existing enterprise management tools. It also interfaces with the Dell Integration Suite for System Center 2012, Dell KACE K1000 Management Appliance, Dell OpenManage Essentials and our Client Management Pack for System Center Operations Manager (SCOM). Finally, tight integration with Windows Management Instrumentation (WMI) allows customers to take advantage of the rich scripting capabilities for collecting information and customizing system settings. This product is provided at no additional charge to Dell customers.
The latest version of Dell Command | Monitor is v9.3.
Installing Dell Command | Monitor
Installing Dell Command | Monitor manually is pretty simple. Just download the latest version (links above) and install with administrative rights.
To perform an unattended installation to be used with your favorite software distribution tool, perform the following steps:
Download Dell Command | Monitor v9.1 for Windows 32-bit (released 07/29/2015)
Download Dell Command | Monitor v9.1 for Windows 64-bit (released 07/29/2015)
Dell Command | Monitor v9.1 Documentation
Check if a BIOS password is set
I strongly discourage the use of this software. It has caused thousands of crashes (Windows Error Reports) on our workstations. After escalating this case to Dell and waiting for a YEAR to not get a resolution we are removing this software from our environment. If you search online you will see lots of reports about dsm_sa_datamgr64.exe application faults. This software is not stable and will have unknown affects on your clients.
DSM SA Data Manager service is failing to start due to the following error. Installation is the fresh Windows 10, all available updates installed, OptiPlex 9020. Works fine on Latitude E7450. Any thoughts?
Faulting application name: dsm_sa_datamgr64.exe, version: 22.214.171.124, time stamp: 0x5583c54b
Faulting module name: MSVCR100.dll, version: 10.0.40219.325, time stamp: 0x4df2bcac
Exception code: 0xc0000417
Fault offset: 0x0000000000070468
Faulting process id: 0x25c
Faulting application start time: 0x01d15cecf7209d44
Faulting application path: C:\Program Files\Dell\Command Monitor\dataeng\bin\dsm_sa_datamgr64.exe
Faulting module path: C:\WINDOWS\SYSTEM32\MSVCR100.dll
Report Id: 21016e15-3832-4e90-9ba3-bfaa6c52ae53
Faulting package full name:
Faulting package-relative application ID:
the dev team wasn't able to reproduce this error. Please open a support ticket to pursue it further.
Hello Warren, after plenty of tests I have found out that AMD graphics card driver is the problem. Although I don't know what exactly is causing it. Can you check this with dev team again, please?
Hello. Is there any update on this? I have e7440, e7450 model laptops and want to deploy Monitor but now I'm scared.
You say this is related to AMD graphics cards, how did you come to that conclusion? What model computers do you have? Do you have any laptop models that I use and have you had issues? Thanks.
It's related to AMD driver. AMD driver during installation makes some changes, which we can't find. Service DSM SA Data Manager then can't be started because it fails.
MSIexec command to silently deploy DCM with SNMP enabled:
msiexec.exe /i Command_Monitor_x64.msi ADDLOCAL=Core,Hapi,EnableSNMP /qn
I successfully discovered a Dell Latitude laptop which shows with a green check mark in the "Clients" area. The wifi NIC shows as expected in the system inventory, however, the wifi NIC is also separated out as a separate device in the "Unknown" area, and has a gray question mark on it. I can delete this wifi NIC device but it's re-added with every re-discovery of the same system. Does anybody know how to get around this so the wifi NIC isn't separated out?
Is there ever going to be a fix for the DSM Data Manager service crash issue with AMD Radeon Cards?
The driver dcdbas64.sys does not appear to be compatible with Windows 10 Device Guard Code Integrity (HVCI) as reported by the Microsoft readiness tool www.microsoft.com/.../details.aspx
Is this a known issue?
Is there any way with this software to suppress a specific alert? I have an alert ID 2359. disk is not supplied by authorized hardware manufacturer. I certainly don't care at all about that, but it continually shows the alert...
Please post your query in Enterprise-Client Forum
DCM Dev team will take it forward from there.
DCIM_Battery is bringing value 5 (which means battery is OK) on the HealthState property even when it's not.
I have a test computer here (e7440 - Windows 8.1) that is reporting the following:
battery 1: good batery, working fine, reporting 5. (OK)
battery 2: completelly bad battery (LED flashes with "Fatal Battery Fail" and windows shows a red X on the battery) - DCIM_Battery brings nothing (I'd expect it to bring something, but that's ok, it's workable since it's a laptop and has no battery identified by WMI I could point it as an error)
battery 3: bad battery (LED flashes with "Fatal Battery Fail"), but windows recognizes it 84% charged. When you remove the AC power the battery doesn't work and PC goes off. This battery has a 5 for HealthState, even with the computer LED flashing as "Fatal Battery Fail" - refer System Battery/Charge LED on www.dell.com/.../checking-notebook---laptop-battery-health-status-on-dell-systems
To me, it doesn't make sense to have a sensor telling me there's a problem with the battery (on both cases 2 and 3) and this is not being captured by Dell Command Monitor.
So, in the end even if we fix the first issue in the Management Pack we still have the second. And I really need the second one to be fixed...