White Paper Template - Dell€¦ · Web viewUse this MS Word template for writing your ESG/SSG white papers. ... Collecting Dell Asset Information 4. ... Install the Dell Windows

Integrating Dell™ OpenManage™ and Microsoft® Systems

Management Server 2.0Enterprise Systems Group (ESG)

Dell™ OpenManage™Systems Management

Dell White PaperBy Joseph Santandrea

[email protected]

Revised July 2002

ContentsIntroduction.............................................................3Collecting Dell Asset Information............................4Automating Dell Asset Information collection.......12

Creating Dell-specific Collections..........................13Criteria for Dell Latitude Collection..................13Criteria for Dell OptiPlex Collection..................14Criteria for Dell Precision WorkStation Collection...........................................................14Criteria for Dell PowerEdge Servers Collection 15

Integrating Dell OpenManage IT Assistant............16Integrating Dell OpenManage Server Administrator17Appendix.................................................................19

Known Issue.......................................................19Description of Issue...........................................19Resolution for Issue...................................................19

Revised July 2002 Page 2 Dell Enterprise Systems Group

Section 1Introduction

Many of Dell’s server, workstation, desktop, and notebook customers have deployed Microsoft® Systems Management Server (SMS) in their management environment to assist them with asset tracking and software deployment. By following the steps outlined in this white paper, customers can fully manage their Dell systems from Microsoft SMS.


Section 2Collecting Dell Asset Information

The following four steps describe the process for collecting Dell asset data through Microsoft SMS 2.0.

1) This step is necessary to collect asset data from Dell™ OptiPlex™, Precision™, and Latitude™ systems. Supported operating systems are: Windows® 95, Windows 98, Windows NT® 4.0, Windows 2000, and Windows XP.

Install the Dell Windows Management Instrumentation (WMI) included as part of OpenManage Client Instrumentation (OMCI) 6.0 or later on the client machines (Dell Optiplex, Precision and Latitude systems) from which you would like to gather data. OMCI 6.X is factory-installed on all client machines and can be downloaded from www.dell.com. OMCI 6.X is also remotely deployable by using software distribution tools such as Microsoft SMS. Installation and configuration instructions are included in the OMCI 6.X User’s Guide.

This enables SMS to capture the following parameters in addition to the existing system parameters that would be otherwise available:

Service Tag Asset Tag System Vendor System Description BIOS revision BIOS date Memory size Processor Type Processor Speed

2) This step is necessary to collect asset data from Dell PowerEdge server systems running either Windows NT 4.0 or Windows 2000.

For systems running Windows NT 4.0, install the Windows Management Instrumentation Core version 1.5, which is downloadable from www.microsoft.com. For systems running Windows 2000, this step is unnecessary.

For either Windows NT or Windows 2000, install the latest version of Dell OpenManage Server Agent 4.0 or later (available from www.dell.com or the Dell OpenManage Application CD) or Dell OpenManage Server Administrator 1.0 or later for the PowerEdge systems from which you would like to gather data. Installation and configuration instructions are included in the respective User’s Guides. You will need to configure Server Agent to run CIM.


http://www.microsoft.com/

http://www.dell.com/

This enables SMS to capture the following parameters in addition to the existing system parameters that would be otherwise available:

Asset Tag Model Serial Number (Service Tag) SystemID

3) Edit the Managed Object Format (.mof) file called sms_def.mof to enable the collection of Dell Asset information into SMS.

Editing the sms_def.mof file informs SMS that new hardware attributes are available and directs SMS to start collecting these newly available attributes during the next SMS hardware inventory cycle.

1) Locate the sms_def.mof file on the SMS Site Server. The default location for this file is \sms\inboxes\clifiles.src\hinv.

2) Make a backup copy of the sms_def.mof file. For example, sms_def.bak.

3) Using a standard ASCII editor such as Notepad, add the following lines to the end of the sms_def.mof.

NOTE: For the attributes mentioned below, if you do not want them to appear in your SMS Hardware Inventory Reporting, change the expression SMS_Report(TRUE)to SMS_Report(FALSE).

Add the following lines to integrate the Dell WMI Provider into SMS:

NOTE: These lines are unnecessary if you do not have any client machines to manage (i.e., only have server systems).

[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;

[SMS_Report(TRUE), read: ToInstance ToSubClass]

string SystemDescription;



string ProcessorType;


sint32 MemorySize;


sint32 ProcessorSpeed;


string BIOSVersion;


datetime BIOSDate;

[SMS_Report(TRUE), read: ToInstance ToSubClass, key]

string ServiceTag;

[SMS_Report(TRUE), read: ToInstance ToSubClass, write: ToInstance ToSubClass]

string AssetTag;

};

#pragma namespace ("\\\\.\\Root\\cimv2")

//************************************

//*** Registers Framework Provider ***

//************************************

instance of __Win32Provider as $Q

{

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 MemorySize;

[read] sint32 ProcessorSpeed;

[read] string BiosVersion;

[read] string ProcessorType;

[read] string ServiceTag;

[read] string SystemDescription;

[read] string SystemVendor;

};


Add the following lines to integrate the Dell OpenManage Server Agent 4.X or Server Administrator 1.X Provider (for server systems) into SMS:

NOTE: These lines are unnecessary if you do not have any server machines to manage (i.e., only have client systems).

#pragma namespace("\\\\.\\Root\\CIMV2")

instance of __Win32Provider as $DataProv

{

Name = "MS_VIEW_INSTANCE_PROVIDER";

ClsId = "{AA70DDF4-E11C-11D1-ABB0-00C04FD9159E}";

ImpersonationLevel = 1;

PerUserInitialization = "True";

};

instance of __InstanceProviderRegistration

{

Provider = $DataProv;

SupportsPut = True;

SupportsGet = True;

SupportsDelete = True;

SupportsEnumeration = True;

QuerySupportLevels = {"WQL:UnarySelect"};

};

[union, ViewSources{"Select * from DELL_Chassis"}, ViewSpaces{"\\\\.\\root\\CIMV2\\Dell"}, Dynamic : ToInstance, provider("MS_VIEW_INSTANCE_PROVIDER")]

class DELL_Chassis : CIM_ManagedSystemElement

{

[PropertySources("AmpStatus") ] string AmpStatus;

[PropertySources("AssetTag") ] string AssetTag;


[PropertySources("Caption") ] string Caption;

[PropertySources("CreationClassName"), key ] string CreationClassName;

[PropertySources("Description") ] string Description;

[PropertySources("FanStatus") ] string FanStatus;

[PropertySources("InstallDate") ] datetime InstallDate;

[PropertySources("LogFormat") ] uint16 LogFormat;

[PropertySources("MemStatus") ] string MemStatus;

[PropertySources("Model")] string Model;

[PropertySources("Name") ] string Name;

[PropertySources("ProcStatus") ] string ProcStatus;

[PropertySources("PsStatus") ] string PsStatus;

[PropertySources("SerialNumber") ] string SerialNumber;

[PropertySources("Status") ] string Status;

[PropertySources("SystemClass") ] uint16 SystemClass;

[PropertySources("SystemID") ] uint16 SystemID;

[PropertySources("Tag"), key ] string Tag;

[PropertySources("TempStatus") ] string TempStatus;

[PropertySources("VoltStatus") ] string VoltStatus;

};

#pragma namespace("\\\\.\\root\\cimv2\\sms")

[SMS_Report(TRUE),

SMS_Group_Name("Dell Server Summary"),

SMS_Class_ID("Dell|ServerSummary|1.0")]


class DELL_Chassis : SMS_Class_Template

{

[SMS_Report(FALSE)]

string AmpStatus;

[SMS_Report(TRUE)]

string AssetTag;

[SMS_Report(FALSE),key]

string CreationClassName;

[SMS_Report(FALSE)]

string FanStatus;

[SMS_Report(FALSE)]

uint16 LogFormat;

[SMS_Report(FALSE)]

string MemStatus;

[SMS_Report(TRUE)]

string Model;

[SMS_Report(FALSE)]

string ProcStatus;

[SMS_Report(FALSE)]

string PsStatus;

[SMS_Report(TRUE)]

string SerialNumber;

[SMS_Report(FALSE)]

uint16 SystemClass;

[SMS_Report(TRUE)]

uint16 SystemID;


[SMS_Report(FALSE),key]

string Tag;

[SMS_Report(FALSE)]

string TempStatus;

[SMS_Report(FALSE)]

string VoltStatus;

};

4) Save the sms_def.mof file.

5) Manually compile the sms_def.mof file to verify that the file compiles cleanly.

Open a command box and enter the following command to compile the MOF file:

mofcomp –N:root\cimv2 \sms\inboxes\clifiles.src\hinv\sms_def.mof

If the compilation is successful, you will see a message that will include the line:

MOF file has been successfully parsed

If the compilation fails, you will see a message stating that an error has occurred and details about the error. If there are any errors, then you probably did not correctly edit the sms_def.mof file. Edit the MOF file again, fix any errors, and compile it again. Repeat the process until the MOF file compiles successfully.


Section 3Automating Dell Asset Information collection

The following three steps describe the process for automating Dell asset information collection through Microsoft SMS 2.0.

1) Make sure Dell WMI has been installed on systems belonging to the SMS site.

The OpenManage client instrumentation must be installed on Dell portables, workstations and desktops. The OpenManage server agent must be installed and configured to run CIM on Dell servers.

NOTE: In order for changes to the sms_def.mof file to take effect, WMI services must be restarted.

2) Make sure SMS Hardware Inventory is enabled on the site server.

Under the Client Agents in Site Settings, enable the Hardware Inventory Client Agent.

3) Make sure SMS Hardware Inventory has collected the Dell summary properties.

The collection of Dell specific properties may take time to populate in the SMS Administrator Console.


Section 4Creating Dell-specific Collections

Microsoft SMS provides “collections” to facilitate group actions. Collections are accessed via the SMS Administrator Console. By right-clicking on the Collections icon, users can create new collections. For detailed instructions, please refer to the Microsoft Systems Management Server Administrator’s Guide. Dell-specific collections can be created using the following criteria described below.

Criteria for Dell Latitude Collection

Criterion Type: Simple ValueOperator: “is like”Simple Value (String): %Latitude%

Attribute Class: Dell SummaryAttribute: SystemDescription

Attribute Class: Computer SystemAttribute: Model

Under the query statement properties section, change the logical operator to “OR.” The final screen should appear as:

Dell Summary.SystemDescription is like "%Latitude%"ORComputer System.Model is like "%Latitude%"


Criteria for Dell OptiPlex Collection

Criterion Type: Simple ValueOperator: “is like”Simple Value (String): %OptiPlex%

Attribute Class: Dell SummaryAttribute: System Description

Attribute Class:Computer SystemAttribute: Model


Dell Summary.SystemDescription is like "%OptiPlex%"ORComputer System.Model is like "%OptiPlex%"

Criteria for Dell Precision WorkStation Collection

Criterion Type: Simple ValueOperator: “is like”Simple Value (String): %Precision%




Dell Summary.SystemDescription is like "%Precision%"ORComputer System.Model is like "%Precision%"


Criteria for Dell PowerEdge Servers Collection

Criterion Type: Simple ValueOperator: “is like”Simple Value (String): %PowerEdge%


Attribute Class: Dell Server SummaryAttribute: Model



Computer System.Model is like "%PowerEdge%"OR

Dell Server Summary.Model is like "%PowerEdge%"ORDell Summary.SystemDescription is like "%PowerEdge%"


Section 5Integrating Dell OpenManage IT Assistant

The Dell OpenManage IT Assistant must first be installed on the management station running Microsoft SMS 2.0. IT Assistant can be downloaded from http://support.dell.com/ or can be installed from the Dell OpenManage Systems Management CD. Once installed, IT Assistant can be linked to Microsoft SMS by adding a snap-in to a customized Microsoft Management Console (MMC).

For detailed instructions on how to add a snap-in to an MMC, refer to “Microsoft Systems Management Server Administrator’s Guide.”

When adding the snap-in, select “Link to Web Address” and then browse to

..\IT Assistant\UserInterfaceComponents\default.htm

This will enable the launch of IT Assistant from within the MMC.


http://support.dell.com/

Section 6Integrating Dell OpenManage Server Administrator

The Dell OpenManage Server Administrator must first be installed on Dell Servers that are clients to the management station running Microsoft SMS 2.0.Server Administrator can be installed from the Dell OpenManage Systems Management CD Version 3.0 (and later). To integrate Server Administrator, use the context menu integration feature of SMS2.0 to extend the functionality of the System Node located in the Collections of the SMS Administrator Console. The extension of the node can be accomplished by defining several registry entries.

Under “My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\NodeTypes\{4D26C0D4-A8A8-11D1-9BD9-00C04FBBD480}\Extensions\SMS_Tools” create a new Key “Dell OpenManage Server Administrator”.

NOTE: If “SMS_Tools” Key does not exist, then create this first, and under “SMS Tools” Key create the “Dell OpenManage Server Administrator” Key.

In the Dell OpenManage Server Administrator Key, create five new String Value’s and name them: Name, Description, CriteriaMessage, CommandLine, CriteriaQuery. Fill the String Value’s with the following respective data:

1) "Name" = Dell OpenManage Server Administrator2) "Description" = Dell OpenManage Server Administrator3) "CriteriaMessage" = Dell OpenManage Server Administrator is not installed on "##SUB:Name##".4) "CommandLine" = "c:\\program files\\internet explorer\\iexplore.exe" -new https:\\##SUB:Name##:1311

NOTE: Customize the path to point to the proper location of iexplore.exe in order to launch the Microsoft Internet Explorer web browser. In this example, it is located in the C:\Program Files\Internet Explorer location. One can also add the path of the iexplore.exe to the system path and use just the iexplore.exe rather than the full path in the CommandLine String Value.

5) "CriteriaQuery" = SELECT * FROM SMS_G_System_SoftwareProduct,


SMS_G_System_DELL_SERVERSUMMARY_1_0 WHERE ResourceID = ##SUB:ResourceId## AND SMS_G_System_SoftwareProduct.ProductName="Server Administrator"

One can also create a .reg file and import it to the registry. The below shows the contents of the registry file (.reg) that is used to add Server Administrator in the context menu of system’s in collections of the SMS Administrator Console. This assumes that the SMS_Tools key does not exist.Add the following lines to a file and give it with a .reg extension.

REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\NodeTypes\{4D26C0D4-A8A8-11D1-9BD9-00C04FBBD480}\Extensions\SMS_Tools]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\NodeTypes\{4D26C0D4-A8A8-11D1-9BD9-00C04FBBD480}\Extensions\SMS_Tools\Dell OpenManage Server Administrator]"Name"="Dell OpenManage Server Administrator""Description"="Dell OpenManage Server Administrator""CriteriaMessage"="Dell OpenManage Server Administrator is not installed on \"##SUB:Name##\".""CommandLine"="\"c:\\\\program files\\\\internet explorer\\\\iexplore.exe\" -new https:\\\\##SUB:Name##:1311""CriteriaQuery"="SELECT * FROM SMS_G_System_SoftwareProduct, SMS_G_System_DELL_SERVERSUMMARY_1_0 WHERE ResourceID = ##SUB:ResourceId## AND SMS_G_System_SoftwareProduct.ProductName=\"Server Administrator\""

Double-clicking on the saved .reg file will automatically import the entries.

The Dell OpenManage Server Administrator launch functionality has now been added to the context menu for each of the systems listed in the Collections of the SMS Administrator Console. This can be verified by right-clicking on any system in the collections and seeing the new entry in the context menu called “SMS Tools”. This will extend to “Dell OpenManage Server Administrator” which can be used to launch Server Administrator to a particular system. The CommandLine String Value contains the command line to be executed. While the CriteriaQuery String Value contains a valid Windows Management Instrumentation (WMI) query language (WQL) structure. This determines whether the command line is executed or a message is displayed to the user. If the query is not met by one or more rows then it will display the data in the CriteriaMessage String Value and skip executing the command line.

This query helps to launch Server Administrator only on systems that have Server Administrator installed and prevents the launch for any non-Dell systems, Dell non-Server systems and Dell Servers that do not have Server Administrator installed.



Section 7AppendixKnown Issue

The SMS Hardware Inventory agent is unable to collect Dell Server summary properties on server systems running Windows 2000 (with no Service Pack) or any version of Windows NT 4.0 with versions of the Dell OpenManage Server Agent up to and including Server Agent version 4.5.x.

Description of Issue

There is a known Windows problem (Microsoft ID Q266178) that if a WMI client (such as SMS) requests data from a single-threaded apartment provider (such as the Server Agent WMI provider) by using an asynchronous call, the provider does not work and the client may hang. This applies to the case of the SMS Hardware Inventory agent calling the Server Agent WMI provider. The problem is fixed in Windows 2000 SP1, but there is no fix for Windows NT 4.0.

A way to work around the problem on Windows NT 4.0 is to change the threading model of a provider from “Apartment” (single-threaded) to “Both” (multi-threaded). The current action plan at Dell is to change the threading model of the Server Agent WMI provide DLL from “Apartment” to “Both” sometime in the future.

Resolution for Issue

a) Upgrade your operating system to Windows 2000 SP1 or greater.

b) A future version of Server Agent will have a change that resolves the problem and will let you collect Dell Server summary properties on server systems running Windows NT 4.0.


THIS WHITE PAPER IS FOR INFORMATIONAL PURPOSES ONLY, AND MAY CONTAIN TYPOGRAPHICAL ERRORS AND TECHNICAL INACCURACIES. THE CONTENT IS PROVIDED AS IS, WITHOUT EXPRESS OR IMPLIED WARRANTIES OF ANY KIND.

Dell, Dell OpenManage, Latitude, OptiPlex, Precision and PowerEdge are trademarks of Dell Computer Corporation. Microsoft, Windows and Windows NT are registered trademarks of Microsoft Corporation in the United States and/or other countries. Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and names or their products. Dell disclaims proprietary interest in the marks and names of others.

©Copyright 2002 Dell Computer Corporation. All rights reserved. Reproduction in any manner whatsoever without the express written permission of Dell Computer Corporation is strictly forbidden. For more information, contact Dell. Dell cannot be responsible for errors in typography or photography.

Information in this document is subject to change without notice.


Documents

White Paper Template - Dell€¦ · Web viewUse this MS Word template for writing your ESG/SSG white papers. ... Collecting Dell Asset Information 4. ... Install the Dell Windows