Dell™ OpenManage™ Client Instrumentation Version 7.
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.
Contents 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . 7 CIM Overview . . . . . . . . . . . . . . . . . . . . . . . 7 WMI Overview . . . . . . . . . . . . . . . . . . . . . . . Data Sources Used by OMCI. OMCI Architecture . Features . . . . . . . . . . . . . . . 8 . . . . . . . . . . . . . . . . . . . . 9 . . . . . . . . . . . . . . . . . . . . . . . . . CIM 2.6 Schema Support . . . . . . . . . . . . . . Dell LegacySelect 2.0 Support 11 11 . . . . . . . . . . . . 12 . .
2 Installing And Uninstalling Dell™ OpenManage™ Client Instrumentation . . . . . . . . . . . . . . . . . . . . User Account Control in Windows Vista And Windows 7 . . . . . . . . . . . . . . . . . . . Local Installation. . . . . . 18 . . . . . . . . . . . . . . . . . . . . 19 Installing OMCI Using the DUP . . . . . . . . . . . Installing OMCI Using the .exe File . Upgrading OMCI 21 . . . . . . . . . . . . . . . . . . . . . 22 Upgrading OMCI Using the DUP . . . . . . . . . .
Retrieving Dell Information With SMS 2.0 . . . . . . . 28 . . . . . . . . . . . . . . . . . . . . . . . 31 . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 WMI Scripts 4 Alerts . Overview . . . . . . . . . . . . . . . . . . . . . . . . . ASF Alerting . . . . . . . . . . . . . . . . . . . . . . . WMI Alerting. . . . . . . . . . . . . . . . . . . . . . . 5 Component Descriptions . 6 Troubleshooting . Wakeup on LAN 33 34 34 . . . . . . . . . . . . 41 . . . . . . . . . . . . . . .
Retrieving Service Tag, Asset Tag, and BIOS Revision . . . . . . . . Changing BIOS Password . . . . . . . . . 67 . . . . . . . . . . . . . 70 . . . . . . . . 72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Newly Added BIOS Settings in OMCI 7.
1 Introduction The Dell™ OpenManage™ Client Instrumentation (OMCI) software enables remote management application programs to access client system information, monitor the client system status, or change the state of the client system; such as 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.
• 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.
OMCI uses a variety of data sources resident on the client system which includes: • Microsoft Win32 WMI providers • SMBIOS • Device drivers • Operating system registry • Operating system Application Programming Interfaces (APIs) • WMI repository OMCI Architecture The OMCI architecture is based on a layered model that is tightly integrated with the Microsoft WMI stack as shown in Figure 1-1.
For example, a management console in the WMI application layer requests the available free space on the client system hard drive. 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.
Features The following are key features of OMCI: • CIM 2.6 Schema Support • Dell LegacySelect 2.0 Support • Remote Boot Device Select • WMI Security • Event Reporting • Remote Shutdown • Remote Wake-Up Configurability • WfM Version 2.0 Compliance CIM 2.6 Schema Support CIM is a standard that describes management data that can be used by many management application programs. OMCI conforms to the CIM 2.
A network administrator can change the settings of these components either through the computer's system setup or by using a WMI management application. CAUTION: Changing LegacySelect attributes such as Integrated Drive Electronics (IDE) Controller may cause a computer system to become unusable. If this occurs, enter system setup on the client system and change the applicable setting.
processes that may be running. If the temperature increases too quickly and OMCI does not poll the system in time, it will not generate a shutdown message and the system will not shut down cleanly. OMCI also contains a start delay for the polling intervals. This determines how long after the operating system loads, OMCI starts checking for the alert status. An alert may be missed if the start delay is set too high.
Supported Operating Systems The following operating systems are supported for installing OMCI: • Microsoft Windows 7 Professional and Ultimate x86 (32-bit) and x64 (64-bit) versions • Microsoft Windows XP Professional SP2 or later x86 (32-bit) and x64 (64-bit) versions • Microsoft Windows Vista® Business and SP1 x86 (32-bit) and x64 (64-bit) versions • Microsoft Windows Vista Ultimate, SP1, and SP2 x86 (32-bit) and x64 (64-bit) versions • Microsoft Windows Vista Enterprise and SP1, and SP2 x86 (32-
Other Resources Which Might Be Of Interest • Dell Client Manager (DCM) which includes Dell-specific hardware and BIOS inventory information, helps configure and update BIOS, supports remote shutdown and remote wakeup, and provides hardware health monitoring. • For information on terms used in this document, see the Glossary on the Dell support website.
Introduction
Installing And Uninstalling Dell™ OpenManage™ Client Instrumentation 2 Dell OpenManage Client Instrumentation (OMCI) can be installed locally using the OMCI installation wizard, or remotely through a silent or administrative installation. Local Installation: OMCI 7.8 installation file is provided in two formats: as a Dell Update Package (DUP) and as a .exe file.
NOTE: Separate installation programs exist for Windows 32- and 64-bit Edition operating systems, and are available for download from the Dell Support website at support.dell.com. User Account Control in Windows Vista And Windows 7 In previous versions of Windows, user accounts were often members of the local Administrators group and had administrator privileges. Members of the local Administrators group could install, update, and run software since an administrator account had system-wide access.
During OMCI installation or uninstallation, depending upon the access level of the user, Windows Vista and Windows 7 prompts the user for administrator authorization. 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.
5 Select the setup language and click OK. You can install OMCI 7.8 in English, French, German, Japanese, Spanish, and Simplified Chinese. The InstallShield Wizard appears. 6 When the InstallShield Wizard window displays the Welcome message, click Next. The InstallShield Wizard window displays the message Setup Type. 7 Choose the installation type by clicking one of the following options: • Complete — Installs all modules and WMI support to a default directory.
Installing OMCI Using the .exe File 1 Click Download Now to download the installation file 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. It can be installed only on systems running the Windows operating systems listed in the "Supported Operating Systems" section.
8 Click Install to begin the installation. If OMCI version 6.x is installed on the system, the installation program prompts you to uninstall it and then run the installation program again. The InstallShield Wizard window displays the message Installing OMCI. A progress bar indicates the installation status. When the installation is completed, the message changes to InstallShield Wizard Completed. 9 Click Finish to end the installation. Upgrading OMCI Do the following to upgrade to OMCI 7.
Upgrading OMCI Using the .exe 1 Click Download Now to download the installation file from the Dell Support website at support.dell.com. When the File Download window appears, save the file. 2 Double-click the downloaded installation file. The Systems Management dialog box is displayed with information on the software version, supported systems, supported operating systems, and supported languages. 3 In the Systems Management dialog box, click Continue.
Uninstalling the Related Files A default OMCI uninstallation does not uninstall the driver files and the associated DLL files and they remain on the system. A command line property (UNINSTALL_DRIVER=1) has to be specified on the command line for a command line product uninstall, which will uninstall OMCI as well as the driver files. For example, the following command uninstalls the product as well as the driver files on a 32-bit supported operating system: msiexec.
setup.exe /s /L1036 /v/qn Performing a Custom Installation in Silent Mode To specify a custom installation directory, modify the command line as follows: setup.exe /s /v"/qn INSTALLDIR=" where 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" Upgrading the Client in Silent Mode To upgrade from one v
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 Administrative Installation Administrative installation allows you to install OMCI on client systems connected to a network. To create an msi file, that can be used to install OMCI on client systems on your network, perform the following steps: 1 Using the OMCI installation package, run the following command: setup.
Windows Management Instrumentation 3 WMI Overview Microsoft® Windows® Management Instrumentation (WMI) is Microsoft’s implementation of the 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.
WMI Security WMI provides for user authentication before granting access to CIM data and methods. Access privileges are enforced by Distributed Component Object Model (DCOM) security and the CIMOM. Access, whether full or limited, can be granted to users on per-namespace basis. There is no implementation of class or property-level security. By default, users that are members of the administrators group have full local and remote access to WMI.
• Processor type • Processor speed 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.
Name = "DellWMI"; ClsId = "{a29197b6-5c8d-4278-ae20-e5c14aed1280}"; }; 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; [read] sint32 ProcessorSpeed; [r
WMI Scripts 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 examples only. NOTE: To connect remotely to WMI services, you must have administrative rights for both the local and the remote systems. The following text files contain sample scripts.
Windows Management Instrumentation
4 Alerts Overview 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.
The system network interface card (NIC) and basic input/output system (BIOS) support ASF 2.0. If the BIOS allows for any ASF 2.0 configuration, then the BIOS settings are exposed through the Microsoft® Windows® Management Instrumentation (WMI) by OMCI. ASF Alerting In previous versions of OMCI, environmental alerts were sent as Desktop Management Interface (DMI) alerts. With the introduction of ASF, the environmental alerts are handled by the ASF NIC.
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 event log and to the local display.
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 • GlobalDisplaySeverityLevel: Controls the notice to the local display based on the severity level of the event OMCI recognizes the following eight WMI severity levels (represented by integers 0 through 7): • UNKNOWN
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) Description Severity Level Value FanProbe A cooling device has exceeded a minor threshold. MINOR 4 DiskSizeChanged The size of at least one hard drive has changed.
Table 4-1. Events Polled by OMCI 7.x (continued) OMCI Event (Windows Event Log Number) Description Severity Level Value DiskCapacity One of the hard drives is running out of free space. MINOR 4 MINOR 4 (105) In OMCI 7.0, only one user-defined threshold is used. The threshold is expressed as an absolute value in megabytes (MB). The default value is 50 MB. An event is generated when available free space on one of the hard drives falls below this threshold. In OMCI 7.
Table 4-1. Events Polled by OMCI 7.x (continued) OMCI Event (Windows Event Log Number) Description MemorySizeIncreased The memory size has been WARNING_DEGR 3 increased.2 ADED (103) MemorySizeDecreased (104) Severity Level Value The memory size has been WARNING_DEGR 3 ADED decreased.2 NumberOfDisksDecreased A hard drive has been removed. (102) WARNING_DEGR 3 ADED NumberOfDisksIncreased A hard drive has been added.
Alerts
Component Descriptions 5 Table 5-1 lists the Dell™ instrumentation components, their functions, their default installation locations, and other relevant information. CAUTION: 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. By default, this is C:\Program Files. Table 5-1.
Table 5-1. Instrumentation Component Information (continued) Component Default Location or File Name Functional Information SMBIOS %ProgramFiles%\Dell\OpenM Component that retrieves data from anage\ Client\dsmbios.dll 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. IAP %ProgramFiles%\Dell\OpenM Instrumentation Access Provider anage\ Client\Iap.
Table 5-1. Instrumentation Component Information (continued) Component Default Location or File Name Functional Information PC Card %ProgramFiles%\Dell\OpenM Data-provider DLL that gives anage\ Client\dpccard.dll information about the PC Cards (removable I/O cards such as a modem, local area network [LAN], synchronous RAM [SRAM], or flash memory card) present in a system. PCI %ProgramFiles%\Dell\OpenM Data-provider DLL that gives anage\ Client\dpci.
Table 5-1. Instrumentation Component Information (continued) Component Default Location or File Name Functional Information Indication Consumer %ProgramFiles%\Dell\OpenM DLL that subscribes to the CIMOM anage\ Client\IndiCons.dll for indications of interest. It is supplied by the indication provider when events are detected. The providers send indications to the CIMOM, and the CIMOM forwards them to their subscribers.
Table 5-1. Instrumentation Component Information (continued) Component Default Location or File Name Functional Information DSMBIOS %ProgramFiles%\Dell\OpenM HTML file that contains Data Routing anage\ configuration information for File Client\dsmbios_data.htm dsmbios.dll. IAP Data Routing File %ProgramFiles%\Dell\OpenM HTML file that contains anage\ configuration information for iap.exe. Client\iap_routing_data.htm Dell OMCI %ProgramFiles%\Dell\OpenM MOF file that creates the anage\ Client\Mofs\ \root
Table 5-1. Instrumentation Component Information (continued) Component Default Location or File Name Functional Information Dell %ProgramFiles%\Dell\OpenM MOF file that provides the default Instantiation anage\ values to the instances of the Cost of MOF2 Client\Mofs\DellOMCI_Inst Ownership (COO) classes defined in ant.mof DellOMCI.mof. CIM v26 LT MFL1 %ProgramFiles%\Dell\OpenM Amended MOF file from anage\ cim26lt.mof. The corresponding Client\Mofs\cim26lt.
6 Troubleshooting Wakeup on LAN If Wakeup on LAN does not function on a client computer system, perform the following checks: • 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. Updated drivers are available on the Dell support website at support.dell.com.
Remote Connection to WMI and Remote BIOS Update If Common Information Model (CIM) information for a remote client computer system is not available to the management application, or if remote BIOS update, which uses Distributed Component Object Model (DCOM), fails, Access Denied and/or Win32:RPC server is unavailable error messages may be displayed.
CAUTION: Back up your system data files before making changes to the registry. Incorrectly editing the registry may render your operating system unusable. 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 Set the forceguest value to 0 (by default it is 1).
– • Select the specific group or user that you want to control access and use the Allow or Deny check box to configure permissions. Perform the following steps to connect to a system’s WMI (root\dellomci) from a remote system using 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.
A Sample Scripts and BIOS Settings WMI Sample Scripts Clear Chassis Intrusion Status Below is a sample VBScript that will clear the chassis intrusion status of a system. This script can be run locally or remotely using the name of the system. Namespace: root\DellOMCI Class Name: Dell_SMBIOSsettings Instance 'Key' Value: 0 Property Name: ChassisIntrusionStatus Property Value: 5 '**************************************************** '*** Name: SampleChassisIntrusionClear.
'*** 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 End If '*** Initialize variables strNameSpace = "root/Dellomci" strComputerName = WScript.
'*** 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." End If '*** Sub used to display the correct usage of the '***script Sub Usage() Dim strMessage strMessage = "incorrect syntax. You should run: " & vbCRLF & _ "cscript.
'*** Purpose: To disable the desktop message box for '***all alerts on a Dell OMCI client. '***Usage: cscript.exe //nologo '***SampleDisableAlertMessages.vbs '*** '*** 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.
'*** 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 – one for each alert typ
strMessage = "incorrect syntax. You should run: " & vbCRLF & _ "cscript.exe /nologo SampleDisableAlertMessages.vbs " 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. '*** Usage: cscript.exe //nologo SampleShutdown.
'*** 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.
'*** Sub used to display the correct usage of the script Sub Usage() Dim strMessage strMessage = "incorrect syntax. You should run: " & vbCRLF & _ "cscript.exe //nologo SampleShutdown.vbs " 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.
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" strComputerName = WScript.
WScript.Echo "Method failed." End If '*** Sub used to display the correct usage of the script Sub Usage() Dim strMessage strMessage = "incorrect syntax. You should run: " & vbCRLF & _ "cscript.exe //nologo SampleRestart.vbs " 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.
'*** 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" ) Or _ (Wscript.Arguments.Count < 2) Then Call Usage() WScript.Quit End If '*** Initialize variables strNameSpace = "root/Dellomci" strComputerName = WScript.
'*** 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 '*** been flashed, it only means that the flash method was initiated '*** successfully. If objOutParam.
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. '*** Usage: cscript.exe //nologo SampleForcePXE.
(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).
'*** Sub used to display the correct usage of the script Sub Usage() Dim strMessage strMessage = "incorrect syntax. You should run: " & vbCRLF & _ "cscript.exe //nologo SampleForcePXE.vbs " 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. '*** Usage: cscript.
Dim Dim Dim Dim Dim Dim strComputerName strClassName strKeyValue objInstance strPropName 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 '*** Initialize variables strNameSpace = "root/Dellomci" strComputerName = WScript.
'*** Set the new value for the property and save the instance objInstance.Properties_.Item(strPropName).Val ue = 6 objInstance.Put_ '*** If any errors occurred, let the user know If Err.Number <> 0 Then WScript.Echo "Enabling WakeUp On Lan failed." End If End If '*** Sub used to display the correct usage of the script Sub Usage() Dim strMessage strMessage = "incorrect syntax. You should run: " & vbCRLF & _ "cscript.exe //nologo SampleWuOLEnable.vbs " WScript.
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.
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 strMessage = "Asset Tag: " strMessage = strMessage & objInstance.Properties_.
Sub Usage() Dim strMessage strMessage = "incorrect syntax. You should run: " & vbCRLF & _ "cscript.exe //nologo SampleSystemSummary.vbs " 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. '*** Usage: cscript.exe //nologo SampleBIOSPwd.
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" strComputerName = WScript.Arguments(0) strClassName = "Dell_Configuration" strKeyValue = "Configuration" strPropName = "Password" strPassEncryptPropName = "PasswordEncrypted" strPwd = WScript.
'*** If any errors occurred, let the user know If Err.Number <> 0 Then WScript.Echo "Setting the BIOS password failed." End If '*** Sub used to display the correct usage of the script Sub Usage() Dim strMessage strMessage = "Incorrect syntax. You should run: " & vbCRLF & _ "cscript.exe //nologo SampleBIOSPwd.vbs " & Chr(34) & _ " space " & Chr(34) WScript.Echo strMessage End Sub Newly Added BIOS Settings in OMCI 7.
• HotkeyToToggleWxANRadio • HTAssist • MinicardSSDEnable • NetworkActivityLED • RearSingleUSB • SRIOV Global Enable • StrongPassword • SurroundView • USB30 • WatchdogTimer • WirelessAdapter • WirelessUWB • WxANRadio NOTE: See the Dell OpenManage Client Instrumentation Reference Guide on the Dell Support website at support.dell.com/manuals for detailed information on OMCI classes, properties, and their descriptions.
Sample Scripts and BIOS Settings
Index A Dell event MOF, 46 alerts, 33 events polled, 37 local, 34 remote, 33-34 Dell instantiation MOF, 46 ASF, 33 alerting, 34 Dell OMCI MOF, 45 dellWMI.dll, 41 DEvents.dll, 43 DMTF, 33 dpccard.dll, 43 C CIM, 7 cim_iap_data.htm, 44 cim_win32_data.htm, 44 overview, 7 schema, 8 dpci.dll, 43 dsmbios.dll, 42 dsmbios_data.htm, 45 dsysInfo.dll, 43 CIMOM, 8, 27 I COM, 27 iap.exe, 42 Computer management console, 28 iap_routing_data.htm, 45 indiCons.dll, 44 indiProv.
instrumentation components, 41 S J silent installation complete, 24 custom, 25 JScript, 31 SMART, 12 SMBIOS, 9 SMS, 28 L language, specifying, 21, 23-24 LegacySelect, 11 U UAC, 18 uninstall client, 25 M updates, 14 MOF, 8 upgrade client, 25 Upgrading OMCI using the .exe, 23 O OMCI, 7, 9 architecture, 9 BIOS tokens, 72 data sources, 8 features, 11 omci.
WMI, 7-8, 28, 36, 51 alerting, 34 application layer, 9 control, 28 overview, 8 provider, 9 repository, 27 sample script examples, 51 scripts, 31 security, 28 severity levels, 36 Index 77
Index
