------------------------------------- Microsoft WBEM Readme File June l998 ------------------------------------- (c) Microsoft Corporation, 1998 This document provides late-breaking or other information that supplements the Microsoft WBEM SDK documentation. ------------------------ How to Use This Document ------------------------ To view the Readme file on-screen in Windows Notepad, maximize the Notepad window and click Word Wrap on the Edit menu. To print the Readme file, open it in Notepad or another word processor, and then use the Print command on the File menu. -------- CONTENTS -------- 1. INTRODUCTION 2. SYSTEM REQUIREMENTS 2.1 Operating System Requirements 2.2 Hardware Requirements 3. UPGRADE INFORMATION 4. INSTALLATION 5. DUAL BOOT COMPUTERS 6. NETWORK CARD REQUIRED 7. ODBC ADDITIONAL KNOWN ISSUES 1. INTRODUCTION This document provides the following information for the version 1.1 release of the Web-Based Enterprise Management (WBEM): System requirements Installation instructions A description of known issues with the release 2. SYSTEM REQUIREMENTS WBEM version 1.1 requires the following minimum configurations. 2.1 Operating System Requirements The following operating systems are supported in this release of the WBEM SDK. Operating system Required -------------------------------- ------------------------ Microsoft Windows NT version 4.0 Service Pack 4 2.2 Hardware Requirements Minimum computer configurations exist and are based on the Microsoft operating system used. For WBEM development purposes, it is recommended that a Win32 developer have a computer that consists of at least: Pentium computer 32 MB RAM 30 MB of available hard disk space Monitor/video card support for 256 colors at an 800 X 600 resolution Network card 3. UPGRADE INFORMATION If you have previously installed the Beta versions of the WBEM, you must remove it before installing this release. >>>To remove the Beta WBEM: 1. Make sure that the HyperMedia Object Manager (HMOM)--now known as the CIM Object Manager (CIMOM)--and any HMOM clients are stopped before uninstalling the SDK. To stop CIMOM, from the command prompt, type, "cimom /KILL". 2. On Windows NT 4.0, remove the Beta version using the Add/Remove Programs option from Control Panel. 3. After removing the Beta version of the WBEM SDK, install v1.1 release using the instructions in section 4, Installation. 4. INSTALLATION To install the WBEM, run the Wbemcore.exe file and follow the prompts. If you need to reinstall WBEM, you must first remove the current installation. See the instructions in section 3, Upgrade Information. Then run the Wbemsdk.exe application. Installation requires Microsoft Internet Explorer version 4.01 or higher. This product can be downloaded at no cost from the Microsoft Web site at http://www.microsoft.com/ie. 5. DUAL BOOT COMPUTERS The use of WBEM SDK on dual boot computers has not been tested. 6. NETWORK CARD REQUIRED This version of WBEM requires a network card to install. 7. ODBC ADDITIONAL KNOWN ISSUES ---------------------------- Classes with Array Type Properties: ----------------------------------- Beware of large Cartesian product matrices! (See documentation on ODBC handling of array types.) A simple query can produce thousands of instances. For example, the query "Select * from Win32_Printer" run against an HP LaserJet 5SI with array properties of 2 Capabilities, 2 CapabilitiesDescriptions, 54 PaperSizesSupported, and 54 PrinterPaperNames will produce a matrix of 11664 instances. Specifying only the necessary properties instead of "*" is preferred unless the array properties are the ones of interest. Array Properties in Access: --------------------------- For classes with properties of type String Array, queries of the form "Select *" produce one array element per instance, as do queries of the form "Select Property[, Property]..." if the properties are specified exactly (in case-sensitive form). If the itemized property list contains names in mismatched case (for example, "mystring" instead of "MyString") then the whole array is returned for each instance of the Cartesian product number of instances returned. For example: "select * from MyTable" or "select k, MyString from MyTable" produces: k MyString 1 StringOne 1 StringTwo "select k, myString from MyTable" produces: k myString 1 [StringOne][StringTwo] 1 [StringOne][StringTwo] For classes with properties of type Array Boolean, explicitly specifying an array property with mismatched case (for example, "mybool" instead of "MyBool") will return False (0) for each element of the array. For classes with properties of type Array Real or Array Integer, explicitly specifying an array property with mismatched case (for example, "myint" instead of "MyInt") will produce an "ODBC -- Call Failed" error. ("WBEM ODBC Driver]ISAM error (#1020)") Array Properties in Visual Basic: --------------------------------- When making a query in an ODBCDirect workspace using the OpenRecordset method of a Connection object, arrays of type String are returned as field type dbMemo. However, no size or value is returned; that is, the properties FieldSize and Value are not present. Although an instance is returned for each element in the array, the values themselves are inaccessible with this method. For classes with properties of type Array Boolean, explicitly specifying an array property with mismatched case (for example, "mybool" instead of "MyBool") will return False (0) for each element of the array. For classes with properties of type Array Real or Array Integer, explicitly specifying an array property with mismatched case (for example, "myint" instead of "MyInt") will return no instances.