hit counter script
Dell OPENMANAGE 7.6 User Manual
Dell OPENMANAGE 7.6 User Manual

Dell OPENMANAGE 7.6 User Manual

Dell computer accessories user manual
Table of Contents

Advertisement

Dell™ OpenManage™
Client Instrumentation Version 7.6
User's Guide

Advertisement

Table of Contents
loading

Summary of Contents for Dell OPENMANAGE 7.6

  • Page 1 Dell™ OpenManage™ Client Instrumentation Version 7.6 User’s Guide...
  • Page 2 Trademarks used in this text: Dell, the DELL logo, OpenManage, Latitude, OptiPlex, and Dell Precision are trademarks of Dell Inc.; Intel is a trademark of Intel Corporation in the U.S. and other countries; Altiris is a registered trademark of Altiris Inc.; Microsoft, Windows, and Windows Vista are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries.
  • Page 3: Table Of Contents

    What's New Supported Operating Systems Latest Updates Other Dell Documents You Might Need Other Resources Which Might Be Of Interest Obtaining Technical Assistance ......
  • Page 4 Windows Management Instrumentation WMI Overview WMI Security Retrieving Dell Information With SMS 2.0 WMI Scripts Contents ........
  • Page 5 Alerts ......Overview ......ASF Alerting .
  • Page 6 Glossary ......Index ....... Contents...
  • Page 7: Introduction

    Dell client systems. OMCI enables Dell client systems to be managed using the Common Information Model (CIM) standard. CIM reduces your total cost of ownership, improves security, and provides a holistic approach to managing all devices in the enterprise, including clients, servers, storage, network, and software devices.
  • Page 8: Wmi Overview

    • The CIM data model abstracts and describes all elements in a network environment. The CIM schema provides the actual data model descriptions and arranges the network into a series of managed objects, all interrelated and broadly classified. • The CIM schema is defined by the Managed Object Format (MOF) file, which provides a standardized model for describing management information between clients in a management system.
  • Page 9: Omci Architecture

    CIMOM. • Dell WMI provider — Lies beneath the CIMOM and contains two CIM providers which register with the CIMOM. When the CIMOM receives a request for information, it routes the request to the appropriate provider.
  • Page 10 The WMI application layer makes the request over the network to the CIMOM (in the Dell WMI provider layer) on the client system. The CIMOM routes the request to the appropriate WMI provider, which, in turn, routes the request through the data router layer to the disk data provider in the data provider layer.
  • Page 11: Features

    Dell LegacySelect 2.0 Support LegacySelect allows a network administrator to selectively enable or disable legacy components in a Dell system. It is a BIOS you control the level of legacy technology your varied workgroups require. LegacySelect 2.0 supports the ability to enable or disable ports, including USB, PCI slots, and disk drives.
  • Page 12: Remote Boot Device Select

    Access privileges are enforced by distributed component object model (DCOM) security and the CIMOM. Event Reporting OMCI detects events on Dell systems and can alert the local user and network administrator to potential failures, configuration changes, and chassis intrusions. These events are displayed by a system management application program such as IT Assistant.
  • Page 13: Remote Shutdown

    For more information on this standard and its specifications, see the Intel website at www.intel.com. What's New The following are new updates to OMCI 7.6: • Support for new platforms: Support for new Dell Latitude Dell OptiPlex and Dell Precision ™, •...
  • Page 14: Supported Operating Systems

    Latest Updates For the latest update information about OMCI, see the readme file located in the installation directory. The default installation path for a typical installation of OMCI is C:\Program Files\Dell\OpenManage\Client. Introduction ® Business x86 (32-bit) and x64 (64-bit) versions...
  • Page 15: Other Dell Documents You Might Need

    The Dell Client Configuration Utility User’s Guide provides information on how to obtain or configure BIOS settings. You can restart or shut down the system or flash the BIOS with Dell Client Configuration Utility. The utility creates an executable that can be run as a standalone package or used with software deployment tools to execute remotely across an enterprise.
  • Page 16 Introduction...
  • Page 17: Installing Dell™ Openmanage

    This means that you must be authenticated on the client system as a user who is a member of the Administrators group, typically the Administrator. The target system must be a Dell system with SMBIOS version 2.3 or later. Otherwise, the OMCI 7.6 installer will exit without installing OMCI.
  • Page 18: User Account Control In Windows Vista

    OMCI 6.x on it. Ensure that you uninstall OMCI 6.x before installing OMCI 7.6. OMCI version 7.2 and later can be installed only on Dell systems running the Windows operating systems listed in the "Supported Operating Systems"...
  • Page 19: Local Installation

    Installing the Client 1 Click Download Now to download the installation file (for example, r118302_a00.exe) from the Dell Support website at support.dell.com. When the File Download window appears, save the file. The installation file contains the components for the following languages: English, French, German, Spanish, Simplified Chinese, and Japanese.
  • Page 20: Uninstalling The Client

    3 From the Add/Remove Programs dialog box, select OMCI and click Remove. 4 Follow the instructions on the screen. NOTE: In Windows Vista, use the Programs and Features icon on the Control Panel for installing or uninstalling OMCI. Installing Dell™ OpenManage™ Client Instrumentation...
  • Page 21: Silent Installation

    /s /v"/qn INSTALLDIR=<destination>" where <destination> is the custom directory and INSTALLDIR must be in uppercase. For example, the following command line installs OMCI with all components in silent mode under the directory c:\destination: setup.exe /s /v"/qn INSTALLDIR=c:\destination" Installing Dell™ OpenManage™ Client Instrumentation...
  • Page 22: Upgrading The Client In Silent Mode

    /X{73F1BDB7-11E1-11D5-9DC6-00C04F2FC33B} For all 64-bit Windows installations: msiexec.exe /X{09ADA709-10D2-4C38-807C-7B84F696F6CE} To uninstall the client instrumentation with the installation program in silent mode, run the following command from the directory containing the installation program: setup.exe /s /x /v/qn Installing Dell™ OpenManage™ Client Instrumentation...
  • Page 23: Administrative Installation

    <Network Location> is the path to the server image. NOTE: For information on using the server image to deploy OMCI, see the documentation for the application program that you are using as your deployment agent. Installing Dell™ OpenManage™ Client Instrumentation...
  • Page 24 Installing Dell™ OpenManage™ Client Instrumentation...
  • Page 25: Windows Management

    Web-Based Enterprise Management (WBEM) effort. It is implemented on Microsoft Windows platforms. There are two components to WMI. In the Dell™ OpenManage™ Client Instrumentation (OMCI) architecture (see Figure 1-1), both the components are represented by the Microsoft WMI Object Manager. The first component is the Common Information Model (CIM) Object Manager (CIMOM), which is the interface and manipulation point for CIM objects and information.
  • Page 26: Retrieving Dell Information With Sms 2.0

    2.0 can only retrieve information from the root\cimv2 namespace. OMCI provides information in the root\dellomci namespace. However, to make certain key attributes available to SMS, OMCI duplicates them in the root\cimv2 namespace. For Dell systems running OMCI, you can import the following system attributes into SMS 2.0: •...
  • Page 27 To retrieve these Dell attributes, edit the sms_def.mof file available on the SMS server in the sms\inboxes\clifiles.src\hinv directory. Add the following lines to the end of the sms_def.mof file: [SMS_Report(TRUE), SMS_Group_Name("Dell Summary"), ResID(7000),ResDLL("dellwmi.dll"), SMS_Class_ID("Dell|Summary|1.0")] class Dell_System_Summary : SMS_Class_Template [SMS_Report(TRUE), read: ToInstance ToSubClass] string SystemVendor;...
  • Page 28: Wmi Scripts

    instance of __InstanceProviderRegistration Provider = $Q; SupportsGet = TRUE; SupportsPut = TRUE; SupportsDelete = TRUE; SupportsEnumeration = TRUE; QuerySupportLevels = {"WQL:UnarySelect"}; instance of __MethodProviderRegistration Provider = $Q; [Dynamic, Provider ("DellWMI")] class Dell_System_Summary [read, key] uint32 DellInstanceID; [read, write] string AssetTag; [read] datetime BIOSDate;...
  • Page 29 NOTICE: The sample scripts are provided as examples only, and have not been tested, nor are warranted in any way by Dell; Dell disclaims any liability in connection therewith. Dell provides no technical support with regard to such scripting. For more information on WMI scripting, see the applicable Microsoft documentation.
  • Page 30 Windows Management Instrumentation...
  • Page 31: Alerts

    Alerts are generated when a system’s state of interest changes. There are two basic types of alerting: local alerting to the current computer user and remote alerting to a management application. Dell™ OpenManage™ Client Instrumentation (OMCI) handles both types of alerting.
  • Page 32: Asf Alerting

    Platform Event Trap (PET) when an event occurs. Where applicable, OMCI notifies the local user of the alert. For information on which PET a specific model of Dell system supports, see the system's Setup Guide.
  • Page 33 You are also provided with an option to receive either a single alert or a limited number of alerts of the occurrence of an event, of a given type. You can mask out specific events and can generate single alert messages for only those events. The Dell_IndicationStaticValues class has the MaxNTEventLogNotifications, MaxDisplayNotifications, and the OccurrencesCount properties, which control the number of notices of each alert condition that are sent to the NT...
  • Page 34 The following properties in the Dell_Configuration class allows you to control the notices sent to the NT event log and to the local display based on the severity of the event: • GlobalNTEventLogSeverityLevel: Controls the notice to the NT event log based on the severity level of the event •...
  • Page 35 The lowest WMI severity level that OMCI sends is WARNING_DEGRADED and the highest is CRITICAL. The severities of OMCI 7.x events are listed in Table 4-1. OMCI sends local alerting and remote alerting for all the listed events. Table 4-1. Events Polled by OMCI 7.x OMCI Event (Windows Event Log Number) FanProbe...
  • Page 36 Table 4-1. Events Polled by OMCI 7.x (continued) OMCI Event (Windows Event Log Number) DiskCapacity (105) EccMemory (1403) MemorySizeChanged Alerts Description One of the hard drives is running out of free space. In OMCI 7.0, only one user-defined threshold is used.
  • Page 37 Table 4-1. Events Polled by OMCI 7.x (continued) OMCI Event (Windows Event Log Number) MemorySizeIncreased (103) MemorySizeDecreased (104) NumberOfDisksDecreased (102) NumberOfDisksIncreased (101) NumberOfProcessorsDecre ased (107) NumberOfProcessorsIncre ased (106) Smart (108) ChassisIntrusion (1253) TemperatureProbe (1054) VoltageProbe (1153) The event is specific to OMCI 7.0. The event is specific to OMCI 7.1 and later versions.
  • Page 38 Alerts...
  • Page 39: Component Descriptions

    Component Descriptions Table 5-1 lists the Dell™ instrumentation components, their functions, their default installation locations, and other relevant information. NOTICE: Changing or deleting component files may cause Dell™ OpenManage™ Client Instrumentation (OMCI) to become unusable. NOTE: %ProgramFiles% is a variable that refers to the path to the Program Files directory.
  • Page 40 Component Descriptions Functional Information Component that retrieves data from the system management basic input/output system (SMBIOS) data tables and reads and writes Dell system data into the BIOS through system management interrupts (SMIs) and the CMOS. Instrumentation Access Provider (IAP); component that queries the iap_routing_data.htm file for...
  • Page 41 Component Interconnect (PCI) devices, PCI-PCI bridges, and PCI- Card bus bridges present in a system. Lists most of the PCI devices in the industry. Dell specific PCI device list. Data-provider DLL that provides system-specific information not available through other data-provider DLLs.
  • Page 42 Table 5-1. Instrumentation Component Information (continued) Component Default Location or File Name Indication %ProgramFiles%\Dell\Open Consumer Manage\ Client\IndiCons.dll Indication %ProgramFiles%\Dell\Open Provider Manage\ Client\IndiProv.dll CIM-IAP %ProgramFiles%\Dell\Open Data Routing Manage\ File Client\cim_iap_data.htm CIM-Win32 %ProgramFiles%\Dell\Open Data Routing Manage\ File Client\cim_win32_data.htm Component Descriptions Functional Information DLL that subscribes to the CIMOM for indications of interest.
  • Page 43 Table 5-1. Instrumentation Component Information (continued) Component Default Location or File Name DSMBIOS %ProgramFiles%\Dell\Open Data Routing Manage\ File Client\dsmbios_data.htm IAP Data %ProgramFiles%\Dell\Open Routing File Manage\ Client\iap_routing_data.htm Dell OMCI %ProgramFiles%\Dell\Open Namespace Manage\ Client\Mofs\ Create MOF DellOMCI_NamespaceCreat e.mof Dell OMCI %ProgramFiles%\Dell\Open Windows Manage\ Preparation Client\Mofs\DellOMCI_Win Prep.mof...
  • Page 44 Table 5-1. Instrumentation Component Information (continued) Component Default Location or File Name Dell %ProgramFiles%\Dell\Open Instantiation Manage\ Client\Mofs\DellOMCI_Inst ant.mof CIM v26 LT %ProgramFiles%\Dell\Open Manage\ Client\Mofs\cim26lt.mfl Dell OMCI %ProgramFiles%\Dell\Open Manage\ Client\Mofs\dellomci.mfl (Installed only for non-English OMCI installations) Dell Event %ProgramFiles%\Dell\Open Manage\ Client\Mofs\dellevent.mof Dell Event %ProgramFiles%\Dell\Open Manage\ Client\Mofs\dellevent.mfl...
  • Page 45: Troubleshooting

    • Use either Dell™ OpenManage™ IT Assistant or system setup on the client system to verify that Wakeup on LAN is enabled. See your Dell system documentation for detailed information. • Ensure that the correct Network Interface Card (NIC) driver is installed.
  • Page 46 • If both the server and the client system are in a domain, perform the following steps: – Verify that the domain administrator account has administrator privileges for both systems. – If you are using IT Assistant on the server system, run the IT Assistant ConfigServices utility (configservices.exe found in the /bin directory of the IT Assistant installation directory).
  • Page 47 WMI CIM Studio: – Install WMI tools along with CIM Studio on the local system and install Dell OMCI on the remote system. – Configure the system’s firewall accordingly for WMI Remote Connectivity. For example, open the TCP ports 135 and 445 in Windows Firewall.
  • Page 48: Installation Problems

    If you are unable to complete installation of OMCI, check the following: • You must have administrative rights on the target system. • The target system must be a Dell system with SMBIOS version 2.3 or later. • The system must be running the Microsoft Windows operating systems listed in the Supported Operating Systems "...
  • Page 49: A Sample Scripts And Bios Settings

    '*** This sample script is provided as an example '***only, and has not been tested, nor is '***warranted in any way by Dell; Dell disclaims any '*** liability in connection therewith. Dell provides '***no technical support with regard to such '***scripting.
  • Page 50 '*** Declare variables Dim strNameSpace Dim strComputerName Dim strClassName Dim strKeyValue Dim objInstance Dim strPropName Dim strPropValue '*** Check that the right executable was used to run '***the script and that all parameters were passed. If (LCase(Right(WScript.FullName, 11)) = "wscript.exe" ) Or _ (Wscript.Arguments.Count < 1) Then Call Usage() WScript.Quit...
  • Page 51: Disable Desktop Messages For All Alerts

    '*** Set the value of ChassisIntrusionStatus to'5' '***("Clear") '***Set the new value for the property and save the instance objInstance.Properties_.Item(strPropName).Value = 5 objInstance.Put_ '*** If any errors occurred, let the user know. If Err.Number <> 0 Then WScript.Echo "Clearing Chassis Intrusion Status failed."...
  • Page 52 '*** This sample script is provided as an example '***only, and has not been tested, nor is warranted in '***any way by Dell; Dell disclaims any liability in '***connection therewith. Dell provides no technical '***support with regard to such scripting. For more '***information on WMI scripting, refer to applicable '***Microsoft documentation.
  • Page 53 '*** Initialize variables strNameSpace = "root/Dellomci" strComputerName = WScript.Arguments(0) strClassName = "Dell_IndicationStaticValues" strPropName = "MaxDisplayNotifications" '*** Establish a connection to the DellOMCI namespace Set objWMIService = GetObject("winmgmts:{impersonationLevel=impersonate," &_ "AuthenticationLevel=pktprivacy}\\" & strComputerName & "\" &_ strNameSpace) '*** Retrieve the instances of '***Dell_IndicationStaticValues class (there should be 16 instances –...
  • Page 54: Remote System Shutdown

    & _ "cscript.exe /nologo SampleDisableAlertMessages.vbs <systemname>" WScript.Echo strMessage End Sub Remote System Shutdown Below is a sample VBScript that will shut down a Dell™ OMCI client remotely. '**************************************************** '*** Name: SampleShutdown.vbs '*** Purpose: To shut down a Dell™ OMCI client.
  • Page 55 '*** Check that the right executable was used to run the script '*** and that all parameters were passed If (LCase(Right(WScript.FullName, 11)) = "wscript.exe" ) Or _ (Wscript.Arguments.Count < 1) Then Call Usage() WScript.Quit End If '*** Initialize variables strNameSpace = "root/Dellomci" strComputerName = WScript.Arguments(0) strClassName = "Dell_Configuration"...
  • Page 56: Remote System Restart

    "cscript.exe //nologo SampleShutdown.vbs <systemname>" WScript.Echo strMessage End Sub Remote System Restart Below is a sample VBScript that will restart a Dell OMCI client remotely. '**************************************************** '*** Name: SampleRestart.vbs '*** Purpose: To restart a Dell OMCI client. '*** Usage: cscript.exe //nologo SampleRestart.vbs <systemname>...
  • Page 57 Dim objInstance Dim ObjOutParam Dim strMethod '*** Check that the right executable was used to run the script '*** and that all parameters were passed If (LCase(Right(WScript.FullName, 11)) = "wscript.exe" ) Or _ (Wscript.Arguments.Count < 1) Then Call Usage() WScript.Quit End If '*** Initialize variables strNameSpace = "root/Dellomci"...
  • Page 58: Remote Bios Update

    "cscript.exe //nologo SampleRestart.vbs <systemname>" WScript.Echo strMessage End Sub Remote BIOS Update Below is a sample VBScript that will flash the BIOS of a Dell OMCI client remotely. '**************************************************** '*** Name: SampleFlash.vbs '*** Purpose: To flash the BIOS of a Dell OMCI client.
  • Page 59 '*** Declare variables Dim strNameSpace Dim strComputerName Dim strClassName Dim strPropValue Dim objInstance Dim ObjOutParam Dim strMethod Dim objMethod Dim objClass Dim objInParam '*** Check that the right executable was used to run the script '*** and that all parameters were passed If (LCase(Right(WScript.FullName, 11)) = "wscript.exe"...
  • Page 60 '*** Set the In parameter of the method to the URL of BIOS header file Set objInParam = objMethod.inParameters.SpawnInstance_() objInParam.sUrl = WScript.Arguments(1) '*** Execute the method Set ObjOutParam = objClass.ExecMethod_(strMethod, objInParam) '*** Let the user know whether the method returned success or not '*** Note: if return value is 0, it does not mean the system's BIOS has...
  • Page 61: Enabling Pxe Boot On The Next Reboot

    Enabling PXE Boot on the Next Reboot Below is a sample VBScript that will force a Dell OMCI client to boot to PXE on next reboot. '**************************************************** '*** Name: SampleForcePXE.vbs '*** Purpose: To force a Dell OMCI client to boot to PXE on next reboot.
  • Page 62 (Wscript.Arguments.Count < 1) Then Call Usage() WScript.Quit End If '*** Initialize variables strNameSpace = "root/Dellomci" strComputerName = WScript.Arguments(0) strClassName = "Dell_Configuration" strKeyValue = "Configuration" strPropName = "ForcePXEOnNextBoot" '*** Retrieve the instance of Dell_Configuration class (there should '*** only be 1 instance). Set objInstance = GetObject("WinMgmts:{impersonationLevel= impersonate}//"...
  • Page 63: Enabling Wakeup On Lan

    <systemname>" WScript.Echo strMessage End Sub Enabling Wakeup on LAN Below is a sample VBScript that will enable Wakeup On LAN on a Dell OMCI client. '**************************************************** '*** Name: SampleWuOLEnable.vbs '*** Purpose: To enable Wakeup On LAN on a Dell OMCI client.
  • Page 64 Dim strComputerName Dim strClassName Dim strKeyValue Dim objInstance Dim strPropName Dim strPropValue '*** Check that the right executable was used to run the script '*** and that all parameters were passed If (LCase(Right(WScript.FullName, 11)) = "wscript.exe" ) Or _ (Wscript.Arguments.Count < 1) Then Call Usage() WScript.Quit End If...
  • Page 65: Retrieving Service Tag, Asset Tag, And Bios Revision

    '*** Usage: cscript.exe //nologo SampleSystemSummary.vbs <systemname> '*** '*** This sample script is provided as an example only, and has not been '*** tested, nor is warranted in any way by Dell; Dell WScript.Echo "Enabling WakeUp On Lan Sample Scripts and BIOS Settings...
  • Page 66 '*** liability in connection therewith. Dell provides no technical '*** support with regard to such scripting. For more information on WMI '*** scripting, refer to applicable Microsoft documentation. '**************************************************** Option Explicit '*** Declare variables Dim strNameSpace Dim strComputerName...
  • Page 67 WHERE " & _ strKeyName & "=" & Chr(34) & strComputerName & Chr(34) '*** Retrieve instances of Dell_Configuration class (there should only '*** be 1 instance). Set colInstances = GetObject("WinMgmts:{impersonationLevel= impersonate}//"&_ strComputerName & "/" & strNameSpace).ExecQuery(strWQLQuery, "WQL", NULL) '*** Use only first instance to retrieve asset tag, service tag, and BIOS '*** version For Each objInstance in colInstances...
  • Page 68: Changing Bios Password

    "cscript.exe //nologo SampleSystemSummary.vbs <systemname>" WScript.Echo strMessage End Sub Changing BIOS Password Below is a sample VBScript that will change the BIOS password on a Dell OMCI client. '**************************************************** '*** Name: SampleBIOSPwd.vbs '*** Purpose: To change the BIOS password on a Dell OMCI client.
  • Page 69 Dim strPropName Dim strPwd '*** Check that the right executable was used to run the script '*** and that all parameters were passed If (LCase(Right(WScript.FullName, 11)) <> "cscript.exe" ) Or _ (Wscript.Arguments.Count < 2) Then Call Usage() WScript.Quit End If '*** Initialize variables strNameSpace = "root/Dellomci"...
  • Page 70: Bios Settings Supported In Omci 7.6

    "<old pwd> space <new pwd>" & Chr(34) WScript.Echo strMessage End Sub BIOS Settings Supported in OMCI 7.6 NOTE: Not all of the below listed BIOS settings are supported on all Dell systems. The BIOS settings supported in OMCI 7.6 are: • AmbientLightSensor* •...
  • Page 71 • Hyperthreading NOTE: On some Dell systems, the Hyperthreading property in the Dell_SMBIOSSettings class displays Enabled or Disabled even if the installed processor does not support hyperthreading technology. In this case, the Hyperthreading property, instead of hyperthreading, may toggle the multi- core capability on and off.
  • Page 72 • MonitorToggling* • MultiCore NOTE: On some Dell systems, the MultiCore property in the Dell_SMBIOSSettings class displays Enabled or Disabled even if the installed processor does not support multi-core technology. In this case, the MultiCore property is actually disabled. •...
  • Page 73 • PrimaryVideo • RadioTransmission • Safe USB* • SATADIPM* • SecondaryParallelATAMaster • SecondaryParallelATASlave • SerialATAChannel1 • SerialATAChannel2 • SerialATAChannel3 • SerialATAChannel4 • SerialATAChannel5 • SerialATAChannel6 • SerialATAChannel7 • SerialATAChannel8 • SerialCommunication* • SerialPort1Configuration • SerialPort2Configuration • SERRDMIMessage* • SetCMOSToDefault* • SingleByteECCLogging* •...
  • Page 74 BIOS settings added in OMCI 7.6 are marked with an asterisk (*). NOTE: See the Dell OpenManage Client Instrumentation Reference Guide on the Dell Support website at support.dell.com for detailed information on OMCI classes, properties, and their descriptions. Sample Scripts and BIOS Settings...
  • Page 75 Glossary The following list defines or identifies technical terms, abbreviations, and acronyms used in this guide. Abbreviation for Alert Standard Format—Defines remote control and alerting interfaces for operating system absent environments. BIOS Acronym for basic input/output system. BIOS refers to the software code run by a system when first powered on.
  • Page 76 Abbreviation for command line interface. A CLI displays a prompt, the user types a command on the keyboard and terminates the command (usually with the Enter key), and the system executes the command, providing textual output. CMOS CMOS which stands for complementary metal oxide semiconductor, is a major class of integrated circuits.
  • Page 77 Abbreviation for Dynamic Link Library which is Microsoft's implementation of the shared library concept in the Microsoft Windows operating systems. These libraries usually have the file extension DLL, OCX (for libraries containing ActiveX controls), or DRV (for legacy system drivers). The file formats for DLLs are the same as for Windows EXE files—Portable Executable (PE) for 32 Windows, and New Executable (NE) for 16 bit Windows.
  • Page 78 CIM classes and instances. Compilation of MOF files provides developers and administrators with a simple and fast technique for modifying the CIM Repository. OMCC Abbreviation for Dell OpenManage Client Connector. OMCC is a one ™ ™...
  • Page 79 SMART Acronym for Self Monitoring, Analysis, and Reporting Technology, which is a monitoring system for system hard disks to detect and report on various indicators of reliability, in the hope of anticipating failures. SMART warns an user or the system administrator of an impending drive failure while time remains to take preventive action, such as copying the data to a replacement device.
  • Page 80 to diagnose and upgrade a remote system while the user of that system continues working on other tasks. It also allows software upgrades in the background or during scheduled hours. Abbreviation for Windows Management Instrumentation which is a set of extensions to the Windows Driver Model that provides an operating system interface through which instrumented components can provide information and notification.
  • Page 81 COM, 25 Computer management console, 26 Data, 8 data provider, 9 data router, 9 DCOM, 12, 45 ddisks.dll, 39 Dell event MOF, 44 Dell instantiation MOF, 44 Dell OMCI MOF, 43 dellWMI.dll, 39 DEvents.dll, 41 DMTF, 31 dpccard.dll, 41 dpci.dll, 41 dsmbios.dll, 40...
  • Page 82 JScript, 28 language, specifying, 19, 21 LegacySelect, 11 MOF, 8 OMCI, 7, 9 architecture, 9 BIOS tokens, 14, 70 data sources, 8 features, 11 omci.sys, 40 schema, 8 supported operating systems, 14 PET, 32 Index server image, using, 23 silent installation complete, 21 custom, 21 SMART, 12...
  • Page 83 WMI, 7-8, 25, 34, 49 alerting, 32 application layer, 9 control, 26 overview, 8 provider, 9 repository, 25 sample script examples, 49 scripts, 28 security, 25 severity levels, 34 Index...
  • Page 84 Index...

This manual is also suitable for:

Openmanage client instrumentation 7.6

Table of Contents

Save PDF