Dell OpenManage Client Instrumentation Version 8.0 User’s ... · WMI security can be configured using the WMI Control available in the Computer Management console under the Services

Dell OpenManageClient Instrumentation Version 8.0

User’s Guide

Notes and Cautions NOTE: A NOTE indicates important information that helps you make better use of

your computer.

CAUTION: A CAUTION indicates potential damage to hardware or loss of data if instructions are not followed.

____________________

Information in this document is subject to change without notice.© 2010 Dell Inc. All rights reserved.

Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.

Trademarks used in this text: Dell™, the DELL logo, and OpenManage™ are trademarks of Dell Inc. Microsoft®, Windows®, Windows Server® and Windows Vista® are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries.

Other trademarks and trade names may be used in this publication to refer to either the entities claiming the marks and names or their products. Dell Inc. disclaims any proprietary interest in trademarks and trade names other than its own.

September 2010

Contents

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5

OMCI Overview . . . . . . . . . . . . . . . . . . . . . . 5

Features . . . . . . . . . . . . . . . . . . . . . . . . . . 7

What's New in this Release . . . . . . . . . . . . . . . . 9

Standards and Protocols Used in OMCI. . . . . . . . . 10

Data Sources Used for OMCI . . . . . . . . . . . . . . 12

Other Documents You May Need . . . . . . . . . . . . 13

Obtaining Technical Assistance . . . . . . . . . . . . 13

2 Installing, Upgrading, and Uninstalling OpenManage Client Instrumentation . . . 15

Installation Pre-requisites. . . . . . . . . . . . . . . . 16

User Account Control in Windows Vista and Windows 7 . . . . . . . . . . . . . . . . . . . . . 16

GUI Installation, Uninstallation, and Upgrading OMCI Using DUP . . . . . . . . . . . . . . . 17

GUI Installation, Uninstallation, and Upgrading OMCI Using .msi File . . . . . . . . . . . . 19

Silent or CLI Installation and Upgrading Using DUP File . . . . . . . . . . . . . . . . . . . . . . 20

Contents 3

Silent or CLI Installation, Uninstallation, and Upgrading OMCI Using .msi File. . . . . . . . . . . . . 21

3 Troubleshooting . . . . . . . . . . . . . . . . . . . 25

Unable to Remotely Connect to WMI . . . . . . . . . . 25

Installation Failure . . . . . . . . . . . . . . . . . . . . 28

4 Contents

1IntroductionThe Dell OpenManage Client Instrumentation (OMCI) software enables remote management application programs to access the client’s system information, monitor the status, or change the state: shutting it down remotely. Through standard interfaces, OMCI exposes key system parameters allowing administrators to manage inventory, monitor system health, and gather information on deployed Dell client systems.

This document provides an overview of OMCI and its various features. It also provides information on installing, upgrading, and uninstalling OMCI.

OMCI OverviewOMCI 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 manage all devices in the enterprise, including clients, servers, storage, network, and software devices.

OMCI can also be accessed through Web Services for Management Standards (WSMAN).

OMCI contains the underlying driver set that collects system information from a number of different sources on the client computer, including the BIOS, CMOS, System Management BIOS (SMBIOS), System Management Interface (SMI), operating system, APIs, DLLs, and registry settings. OMCI exposes these information through the CIM Object Manager (CIMOM) interface of the Windows Management Instrumentation (WMI) stack.

Thus, OMCI enables IT administrators to remotely collect asset information, modify CMOS settings, receive proactive notification of potential fault conditions, and get alerts to potential security breaches.

Introduction 5

OMCI is used to gather asset inventory from the system including BIOS settings through CIM implementation. It can be integrated into a console such as Microsoft System Center Configuration Manager by directly accessing the CIM information, through an integration with DCM, or through other console vendors who have implemented OMCI integration. Additionally, custom scripts can be created to target key areas of interest at the administrator’s discretion. These scripts can be used to monitor inventory, BIOS settings, and system health.

OMCI ArchitectureOMCI data provider collects the system information data and stores the information in the proprietary XML format. The data manager is a service that loads these providers based on request. OMCI CIM provider layer abstracts the interface to different CIMOM implementations. The input is a combination of XML and XSL data in proprietary form while the output is a CIM object instance based on Management Profiles. Then, WSMAN, which serves as the channel protocol, requests the data from CIMOM and transmits it to the console.

The OMCI architecture has several layers that are integrated with the Microsoft WMI stack:

• WMI application layer — Consists of management applications such as Dell Client Manager and other standards-based management tools, and WMI applications such as: Microsoft SMS, LANDesk, and WMI Tools. The applications in this layer are consumers of the system's management data supplied by OMCI. These applications request client information and alerts through WSMAN/CIM Object Manager (CIMOM). For more information about WMI and CIMOM, see "Standards and Protocols Used in OMCI" on page 10.

• OMCI CIM Provider — Lies beneath the CIMOM and contains two CIM providers, which is registered with the CIMOM:

– The instance/method provider implements an interface that enables utility operations such as create, delete, modify, and query.

– The indication provider implements an interface for WMI indications (or events).

When the CIMOM receives a request for information, it routes the request to the appropriate provider. Both Dell and Microsoft providers

6 Introduction

exist in this layer, and they provide information on system devices. The providers send management application requests from the CIMOM to the data router.

• OMCI Data Manager — A service that loads data provider based on request from the upper layer.

• Data Provider — Collects system information like hardware, drivers, and operating system data, and stores them in the proprietary XML format.

For example, a management console in the WMI application layer requests the available processor information on a client system. The WMI application layer makes the request over the network to the CIMOM on the client system. The CIMOM passes the request to the OMCI CIM provider and data manager. The data manager loads the corresponding data provider, which gets the information and stores it in a proprietary format. The information is then returned (through the same path in reverse) to the management console.

FeaturesThe key features of OMCI are:

• CIM 2.17 Schema Support

• BIOS Configuration

• WMI Security

• Event Reporting

• Remote Shutdown

• Access to System Information using WMI-CIM Protocol and WSMAN

• Compilation of Detailed Asset Information

• Remote Wake-Up Configurability

• Remote Modification of System Settings

• Monitoring of System Health and Reports Status

CIM 2.17 Schema SupportOMCI conforms to the CIM 2.17 Schema, and includes two WMI providers: Dell WMI Indication Provider/Polling Agent and Dell WMI Instance/Method Provider.

Introduction 7

BIOS ConfigurationOMCI provides the ability to perform configuration of a system’s BIOS, including management of its boot order.

WMI SecurityWMI provides for user authentication before granting access to CIM data and methods. Access privileges are enforced by Distributed Component Object Model (DCOM) security and CIMOM. Access, whether full or limited, can be granted to users on per-namespace basis. There is no class implementation or property-level security. By default, users who are members of the administrators group have full local and remote access to WMI.

WMI security can be configured using the WMI Control available in the Computer Management console under the Services and Applications section. Right-click WMI Control, and then click Properties. You can configure namespace-specific security from the Security tab. WMI Control can also be executed from the Start menu or the command prompt,by running wmimgmt.msc.

Event ReportingOMCI 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 Dell Client Manager (DCM).

Remote ShutdownOMCI supports remote system shutdown and restart.

Access to System Information using WMI-CIM Protocol and WSMANOMCI provides access to system information such as BIOS revision and System Model through WMI using CIM. The WSMAN protocol can also be used to access this information through WMI.

Compilation of Detailed Asset InformationOMCI provides access to detailed inventory information such as processors, PCI devices, and batteries.

8 Introduction

Remote Wake-Up ConfigurabilityOMCI supports configuration of remote wake-up settings. Remote wake-up is a function of the client system and Network Interface Card (NIC).

Remote Modification of System SettingsOMCI allows IT administrators the ability to retrieve and set Dell business client BIOS settings such as USB port configuration, boot order, and NIC settings.

Monitoring of System Health and Reports StatusOMCI monitors the system health such as fan status and reports the status of such through NT event log entries and CIM events.

What's New in this Release• Supports access of the classes and properties of the new namespace at -

"root/dcim/sysman," through Dell Common Information Model (DCIM). The classes and properties of the 7.x version (legacy namespace) can be accessed at - "root/dellomci."

• Supports access of specific HW asset information and HW alert information through CIM/WSMAN.

• Supports access through the existing protocols such as HTTPS.

• Supports the usage of the interoperability namespace, "root/interop," to search for profiles implemented in the current version.

– Supports usage of the profile, "RegisteredProfiles," to search for registered profiles.

– Supports usage of the profile, "ReferenceProfiles," to search for other references to a particular profile.

Introduction 9

Standards and Protocols Used in OMCIOMCI uses WMI and enables WSMAN protocols.

CIM and WMI Technology OverviewThe Distributed Management Task Force (DMTF) is the industry-recognized standards body that leads the development, adoption, unification of management standards (including CIM, and ASF), and initiatives for desktop, enterprise, and Internet environments.

CIM

The CIM, created by the Desktop Management Task Force (DMTF) as part of the Web-based Enterprise Management (WBEM) initiative, provides a unified view of physical and logical objects in the managed environment.

The following are important CIM details:

• CIM is an object-oriented data model for describing management information. CIM describes the way the data is organized, not necessarily the transport model used to transport the data. The most prevalent transport method is the Microsoft Windows Management Instrumentation (WMI).

• CIM-capable management applications gather information from a variety of CIM objects and devices, including client and server systems, network infrastructure devices, and applications.

• The CIM specification details mapping techniques for improved compatibility with other management protocols.

• 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. The MOF file is not bound to a particular implementation, and it allows the interchange of management information between many different management systems and clients.

10 Introduction

WMI

Microsoft Windows Management Instrumentation (WMI) is Microsoft's implementation of the Web-based Enterprise Management (WBEM) effort. It is implemented on the Microsoft Windows platforms. WMI supports CIM and Microsoft specific CIM extensions.

WMI includes:

• A powerful set of native services such as query-based information retrieval and event notification.

• Extensive scripting capabilities via the Windows Scripting Host (WSH).

• The CIMOM, which is the interface and manipulation point for CIM objects and information.

• The repository, where CIMOM stores management data.

In the OMCI architecture, CIMOM and the repository are represented by the Microsoft WMI Object Manager. The CIMOM is the interface and manipulation point for CIM objects and information. It acts as a facilitator in gathering information and manipulating object properties. Microsoft has implemented this component as the Windows management (winmgmt) service. The CIMOM is a software middle layer that mediates interactions between high-level management applications and the lower levels of instrumentation, such as OMCI and other providers. The CIMOM ensures that data supplied by providers is presented to management applications in a uniform and provider-independent way. The CIMOM does this, in part, by using the Component Object Model (COM) Application Programming Interface (API) for communication with providers and management applications.

The repository is a binary file where the CIMOM stores management data. Such data includes information from the compiled Managed Object Format (MOF) file(s), including the CIM class definitions, properties, qualifiers, and hierarchical relationships. Instance data, as it becomes available, is also stored here.

WMI provides a scripting interface. Using VBScript or JScript, you can write scripts that connect to WMI services locally or remotely, retrieve information, or execute methods. Because OMCI is implemented through WMI, most OMCI tasks can be scripted. This section provides sample VBScript scripts as

Introduction 11

examples only. For the sample scripts, see the Dell OpenManage Client Instrumentation Reference Guide available on the Dell support web site at support.dell.com/manuals.

NOTE: To connect remotely to WMI services, you must have administrative rights for both the local and remote systems.

For more information about WMI, see the Microsoft website.

WSMANThe WS-Management Protocol is a DMTF open standard defining a Simple Object Access Protocol (SOAP)-based protocol for managing servers, devices, applications, and Web services. It uses data from CIMOM to facilitate the management.

WSMAN is a protocol that provides an abstraction layer to access the CIM information OMCI provides through WMI. The reason is that the console can use WSMAN to communicate to in-band or out-of-band systems to gather asset inventory and to set information or run methods. In the in-band part, the WSMAN layer also abstracts the operating system present underneath. Thus, there is no need for the console to know the operating system it is communicating with. For example, Windows or Linux. It uses the same commands. However, OMCI does not require WSMAN and OMCI does not directly enable WSMAN as it is only a protocol.

For more information about WS-Management from the DMTF, see: dmtf.org/standards/wsman/

For more information about enabling WS-Management based management of WMI on a Windows system, see: msdn.microsoft.com/en-us/library/aa384426%28v=VS.85%29.aspx

Data Sources Used for OMCIOMCI collects system information from a number of different sources on the client systems including the BIOS, CMOS, System Management BIOS (SMBIOS), System Management Interface (SMI), operating system, Application Programming Interfaces (APIs), Dynamic Link Libraries (DLLs), and registry settings. OMCI exposes this information through the CIMOM interface of the WMI stack and enables IT administrators to remotely collect asset information, modify CMOS settings, receive proactive notification of potential fault conditions, and gets alerts to potential security breaches.

12 Introduction

OMCI uses a variety of data sources that resides on the client system, and they are:

• Microsoft Win32 WMI providers

• SMBIOS

• Operating system registry

• Operating system Application Programming Interfaces (APIs)

• WMI repository Supported Operating Systems

OMCI is supported on the Microsoft Windows operating systems. For the list of operating systems, see the readme available on the Dell support site at support.dell.com/manuals.

Other Documents You May NeedIn addition to this User's Guide, you can access the following guides available on the Dell Support website at support.dell.com/manuals. On the Manuals page, click SoftwareSystems Management. Select the appropriate product link on the right side to access the documents.

• The Dell OpenManage Client Instrumentation Reference Guide provides detailed information on all OMCI classes, properties, and their descriptions.

• The Dell Client Solution (DCS) that includes Dell-specific hardware and BIOS inventory information, helps configure and update BIOS, supports remote shutdown and remote wakeup, and provides hardware health monitoring.

• The Glossary provides information about the terms used in this document.

Obtaining Technical AssistanceIf at any time you do not understand a procedure described in this guide, or if your product does not perform as expected, different types of help are available. For more information see "Getting Help" in your system's Setup Guide.

Additionally, Dell Enterprise Training and Certification is available; see dell.com/training for more information. This service may not be offered in all locations.

Introduction 13

14 Introduction

2Installing, Upgrading, and Uninstalling OpenManage Client InstrumentationDell OpenManage Client Instrumentation (OMCI) can be installed using Graphical User Interface (GUI) also known as the OMCI installation wizard, or remotely through a silent installation using the Command Line Interface (CLI). The OMCI installation file is available as a Dell Update Package (DUP) on the Dell support website at support.dell.com.

NOTE: Separate installation programs exist for Windows 64-bit Edition operating systems.

• GUI Installation: You can install OMCI using DUP or .msi file, extracted from the DUP. The OMCI installation wizard allows you to install the complete package or perform a custom installation of specific components required for a particular environment. For more information, see "GUI Installation, Uninstallation, and Upgrading OMCI Using DUP" on page 17 and "GUI Installation, Uninstallation, and Upgrading OMCI Using .msi File" on page 19.

• Silent/CLI Installation: OMCI provides a series of command-line switches for silent installation. This allows you to remotely install OMCI using a software distribution tool with no end-user interaction. You can use the .msi file or DUP to deploy OMCI to client computers on a network by using a login script, Windows system policies, or other methods.

For more information, see "Silent or CLI Installation and Upgrading OMCI Using DUP File" on page 20 and "Silent or CLI Installation, Uninstallation, and Upgrading OMCI Using .msi File" on page 21.

Installing, Upgrading, and Uninstalling OpenManage Client Instrumentation 15

OMCI installs a WMI provider, two services and a driver. WMI utilizes COM as the communication interfaces with providers. The services provide OMCI access to the system for events and data retrieval. OMCI also installs a driver. The driver is used for secure communication with BIOS and other low level system resources. OMCI does not itself support any type of remote access; therefore it does not require any specific network interfaces to be enabled. Remote access to OMCI may be accomplished using the remote access protocols supported by WMI.

Installation Pre-requisitesBefore installing OMCI, ensure the following:

• You must have administrative rights on the client system. 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 8.0 installer exits without installing OMCI.

• The system must be running the Microsoft Windows operating systems listed in the readme.

• For Windows XP 64-bit operating systems, .NET Framework 3.5 SP1 or later must be installed.

User Account Control in Windows Vista and Windows 7During OMCI installation or uninstallation, Windows Vista and Windows 7 prompts the user for administrator authorization, depending on the privileges of the user. You must provide the administrator password for installing or uninstalling OMCI if you have standard account privileges, since OMCI installation and uninstallation need administrative privileges. Even when you are logged in as a member of the Administrators group (except the Administrator account), User Account Control (UAC) prompts you to give your consent to allow the installation or uninstallation. For more information about UAC, see the Microsoft website.

NOTE: Only users with administrator privileges can connect to the standard or legacy namespace.

16 Installing, Upgrading, and Uninstalling OpenManage Client Instrumentation

NOTE: Since the user experience is configurable with the Security Policy Manager snap-in (secpol.msc) and with Group Policy, there are multiple UAC user experiences. The configuration choices made in your environment will affect the prompts and dialogs seen by standard users, administrators, or both. The specific behavior of the UAC elevation prompt is dependent upon the Security Policy setting.

GUI Installation, Uninstallation, and Upgrading OMCI Using DUPYou can install OMCI locally using the DUP, downloaded from support.dell.com to your local directory.

Installing OMCI Using DUP1 Double-click the Dell OpenManage Client Instrumentation

Update Package you downloaded from support.dell.com.

The Dell OpenManage Client Instrumentation screen is displayed with details such as supported devices, supported operating systems, fixes, and enhancements.

2 Click Install.

The Welcome to the InstallShield Wizard for Dell OpenManage Client Instrumentation window appears. You can install OMCI 8.0 in English, French, German, Japanese, Spanish, and Simplified Chinese.

3 Click Next.

The License Agreement window appears. Select the option, "I accept the terms in the license agreement."

4 Click Next.

The Setup Type window appears.

5 Choose the installation type by clicking one of the following options:

• Typical — Installs the Standards-based Instrumentation, using the default directory. This option is selected by default.

• Custom — Enables you to install specific program features such as the OMCI 7.x compatibility mode or Standards-based Instrumentation options, and specify the installation directory. It also allows you to install the legacy namespace.


The OMCI 7.x compatibility mode provides a subset of the classes available in the namespace, "root/DellOMCI." This namespace is in read-only mode.

The Standards-based Instrumentation provides instrumentation available in the "root/DCIM/sysman." This namespace complies with the DMTF DASH standards.

6 Select the Typical option and click Next.

The Ready to Install the Program window appears. If the option Custom is selected, the Custom Setup window is displayed, allowing you to select specific program features, and also specify the directory in which you want to install OMCI. Click Next.

7 Click Install to begin the installation.

The Installing Dell OpenManage Client Instrumentation window appears. A progress bar indicates the installation status. When the installation is completed, the InstallShield Wizard Completed window appears.

8 Click Finish. The Dell OpenManage Client Instrumentation screen appears.

9 Click Finish to complete the installation.

Upgrading OMCI Using DUP1 Double-click the DUP you downloaded from support.dell.com.

The Dell OpenManage Client Instrumentation screen appears with details such as supported devices, supported operating systems, fixes, and enhancements.

2 Click Install. The following message appears:

"The setup will perform an upgrade of OMCI. Do you want to continue?"

3 Click Yes and follow the instructions on the screen.

NOTE: While upgrading OMCI 7.x, the compatibility mode is installed by default.

4 After upgrading, restart the system.


Uninstalling OMCI Using Control Panel1 Go to Start Settings Control Panel.

2 Select Add/Remove Programs. The Add/Remove Programs window is displayed.

3 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 uninstalling OMCI.

GUI Installation, Uninstallation, and Upgrading OMCI Using .msi FileYou can perform a local installation using the omci.msi file extracted from the OMCI DUP. Download the OMCI DUP from support.dell.com to your local directory and extract the omci.msi file. By default, the omci.msi file is extracted to the folder:<SystemDrive>:\Dell\Drives\sysman\om_app_win_r275106

The installation file contains the components for the following languages: English, French, German, Spanish, Simplified Chinese, and Japanese. It can be installed only on systems running the Windows operating systems.

Installing OMCI Using .msi File1 Double-click the omci.msi file. The Welcome to the InstallShield Wizard

for Dell OpenManage Client Instrumentation wizard appears.

2 Click Next.

The License Agreement window appears. Select the option, "I accept the terms in the license agreement."

3 Perform the steps 5 through step 9 described in the section, "Installing OMCI Using DUP" on page 17.

NOTE: Users and local administrators must elevate their privileges before running the .msi file for installation.


Upgrading OMCI Using .msi File1 Double-click the omci.msi file.

2 Follow the instructions on the screen to upgrade the application.

Uninstalling OMCI Using .msi File1 Double-click the omci.msi file.

The Welcome to the InstallShield Wizard for Dell OpenManage Client Instrumentation window appears.

2 Click Next.

The Program Maintenance window appears.

3 Select the Remove option and click Next.

The Remove the Program window appears.

4 Click Remove. The following message appears:

"Do you want to allow the following program to remove software from this computer?"

5 Click Yes.

The Uninstalling Dell OpenManage Client Instrumentation window appears.

After the application is uninstalled, the InstallShield Wizard Complete window appears.

6 Click Finish to complete the uninstallation process.

Silent or CLI Installation and Upgrading OMCI Using DUP FileTo perform a silent installation of OMCI with default settings using the DUP, you can invoke the DUP executable with the /s option. This will install perform a typical installation, into the default directory, using the default operating system language (if supported).

To perform a silent upgrade of OMCI using the DUP, you can invoke the DUP executable with the /s option.


NOTE: Only typical OMCI installation or upgrading OMCI in silent mode from the DUP is supported.

Silent or CLI Installation, Uninstallation, and Upgrading OMCI Using .msi File

Installing the Client in Silent ModeIn the silent mode (no dialog boxes appear), you can perform complete and custom installations.

NOTE: When typing commands, enter spaces exactly as shown in the examples in this section.

Performing a Complete Installation in Silent ModeTo perform a silent unattended installation of OMCI with all components in the default directory:

For 32-bit Windows operating systems:

msiexec /i omcix86.msi /qn



where .msi is the installation executable file for OMCI.

To install OMCI only with the standard namespace in silent mode:

msiexec /i omci.msi ADDLOCAL=Core,Hapi / q

To install OMCI with standard and legacy namespaces in silent mode:

msiexec /i omci.msi ADDLOCAL=Core,Hapi,Legacy / q

The following options are supported for the parameter, ADDLOCAL:

– Core,Hapi

– Core,Hapi,Legacy

To specify the installation language use the command line option, TRANSFORMS=<language ID> .mst, where <language ID> is 1031 (German), 1033 (English), 1034 (Spanish), 1041 (Japanese), 1036 (French), or 2052 (Simplified Chinese). If the installation language is not specified, the


22

installer selects the default operating system language, or to English if OMCI does not support the operating system language. For example, the following command line installs the French version in silent mode:


msiexec /i omcix86.msi TRANSFORMS=1036.mst /qn


msiexec /i omcix64.msi TRANSFORMS=1036.mst /qn

Performing a Custom Installation in Silent ModeTo specify a custom installation directory, modify the command line as follows:


msiexec /i omcix86.msi INSTALLDIR=<destination> /qn


msiexec /i omcix64.msi INSTALLDIR=<destination> /qn

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:


msiexec /i omcix86.msi INSTALLDIR=c:\destination


msiexec /i omcix64.msi INSTALLDIR=c:\destination

Upgrading OMCI in Silent ModeTo upgrade from the previous version to a later version of OMCI , execute the following command:

For 32-bit Windows installations:




Installing, Upgrading, and Uninstalling OpenManage Client Instrumentation

A reboot might be required for the upgrade. To suppress it, modify the command line as follows:


msiexec /i omcix86.msi REBOOT=REALLYSUPPRESS /qn


msiexec /i omcix64.msi REBOOT=REALLYSUPPRESS /qn

Uninstalling OMCI in Silent ModeYou can uninstall OMCI in silent mode either using or without using the .msi file.

To uninstall OMCI using the .msi file, run the following command:


msiexec /x omcix86.msi /qn


msiexec /x omcix64.msi /qn

To uninstall OMCI without the .msi file, run the following command:


msiexec /X{4FFF8105-AE32-434C-91FC-02828C183616} /qn

NOTE: Only users with administrator privileges can install or uninstall OMCI 8.x.


msiexec /X{47F8D37E-D1F2-44E2-8920-40FAB519A624} /qn



3Troubleshooting

Unable to Remotely Connect to WMIIf Common Information Model (CIM) information for a remote client computer system is not available to the management application or if remote BIOS update that uses Distributed Component Object Model (DCOM) fails, the following error messages may be displayed:

• Access Denied

• Win32:RPC server is unavailable

If these error messages are displayed, perform the following:

1 To verify that the client system is connected to the network, at the command prompt on the server, type:

ping <Host Name or IP Address> and press <Enter>.

2 If both the server and the client system are in a domain, perform the following steps:

a Verify that the domain administrator account has administrator privileges for both systems.

b If you are using IT Assistant on the server system, run the IT Assistant ConfigServices utility (configservices.exe available in the /bin directory of the IT Assistant installation directory). Configure IT Assistant to run under the domain administrator account, and verify that DCOM and CIM are enabled. See the IT Assistant User’s Guide for information.

c If you are using IT Assistant, use the domain administrator account to configure the IT Assistant subnet discovery for the client system. If the system has already been discovered, remove the system from the list of discovered systems, configure subnet discovery for it, and then rediscover it. See the IT Assistant User’s Guide for information.

Troubleshooting 25

3 If both the server and the client system are in a workgroup (not in a domain), perform the following steps:

a If the client system is running the Microsoft Windows XP Professional or Windows XP Professional x64 Edition operating system and the server is running Windows 2000, verify that Service Pack 2 or later is installed on the server.

b If the client system is running a version of Windows XP and is not part of a domain, edit the registry to allow remote connection with administrative privileges.

CAUTION: Back up your system data files before making changes to the registry. Incorrectly editing the registry may render your operating system unusable.

4 To make the registry change on the client system, click StartRun, then type regedit, and click OK. In the Registry Editor window, navigate to:

My Computer\HKEY_LOCAL_MACHINE\SYSTEM\

CurrentControlSet\Control\Lsa

5 Set the forceguest value to 0 (by default it is 1). Unless you modify this value, the user remotely connecting to the system has guest privileges only, even if the supplied credentials should provide administrative privileges.

a Create an account on the client system with the same user name and password as an administrator account on the system running your WMI management application.

b If you are using IT Assistant, run the IT Assistant ConfigServices utility (configservices.exe found in the /bin directory under the IT Assistant installation directory). Configure IT Assistant to run under a local administrator account, which is also now an administrator on the remote client. Also, verify that DCOM and CIM are enabled. See the IT Assistant User’s Guide for information.

c If you are using IT Assistant, use the administrator account to configure subnet discovery for the client system. Enter the user name as <client machine name>\<account name>. If the system has already been discovered, remove the system from the list of discovered systems, configure subnet discovery for it, and then rediscover it. See the IT Assistant User’s Guide for information.

26 Troubleshooting

6 Perform the following steps to modify user privilege levels for connecting remotely to a system’s WMI:

a Click StartRun, type compmgmt.msc, and then click OK.

b Navigate to WMI Control under Services and Applications.

c Right-click WMI Control and click Properties.

d Click the Security tab and select DellOMCI under the Root tree.

e Click Security.

f Select the specific group or user that you want to control access and use the Allow or Deny check box to configure the permissions.

7 Perform the following steps to connect to a system’s WMI (root\dellomci) from a remote system using WMI CIM Studio:

a Install WMI tools along with CIM Studio on the local system and install Dell OMCI on the remote system.

b Configure the system’s firewall accordingly for WMI Remote Connectivity. For example, open the TCP ports 135 and 445 in Windows Firewall.

c Set the Local Security setting to Classic - local users authenticate as themselves for Network access: Sharing and security model for local accounts in the Local Security Policy.

d In case of Windows Vista, disable UAC on the system.

e Connect to the system’s WMI (root\dellomci) from a remote system using WMI CIM Studio (for example, \\10.94.174.167\root\dellomci)

f Enter the Administrator credentials of the target remote system if prompted.

NOTE: See the applicable Microsoft documentation at http://msdn.microsoft.com for more information.

Troubleshooting 27

Installation FailureIf you are unable to complete OMCI installation, 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 supported Microsoft Windows operating system.

28 Troubleshooting