---------------------------------------
Microsoft Web-Based Enterprise Management (WBEM) SDK Build 450 Interim Release Notes
March 1998
---------------------------------------
(c) Microsoft Corporation

This document provides late-breaking or other information that supplements the Microsoft WBEM SDK Build 450 interim documentation.

NOTE: This is preliminary documentation and subject to change.

------------------------
How to Use This Document
------------------------

To view the Release Notes file on-screen in Windows Notepad, maximize the Notepad window and click Word Wrap on the Edit menu. To print the Release Notes file, open it in Notepad or another word processor, and then use the Print command. 

--------
CONTENTS
--------

1.  Introduction  to Web-Based Enterprise Management (WBEM)
2.  System Requirements
3.  How to install Build 450
4.  Using the debug symbols
5.  Some changes since Beta 2
6.  Release Errata
7.  Support / Reporting bugs
8.  DMI Provider Notice
9.  WBEM SDK Feedback and Issues Reporting


1. Introduction to WBEM:

The key purpose of the WBEM initiative is to consolidate and unify the data provided by existing management technologies. WBEM focuses on solving real enterprise issues by allowing problem areas to be tracked from end to end - from the user/application level through the systems and network layers to remote service/server instances. 

For more information, please see:

    http://wbem.freerange.com/

It is not recommended that you download the beta that is available on the Freerange.com Web site, since the Build 450 pre-release version of WBEM is newer than beta 2.

WBEM is included as an operating system (OS) component on both Microsoft Windows 98 and Windows NT 5.0. This pre-release of the WBEM SDK contains both the OS-specific components and the SDK components for the following platforms:

    Windows NT 5.0 beta 1
    Windows NT 4.0 Service Pack 3
    Windows 98
    Windows 95 OSR2

The OS components include the repository and the providers to allow interaction with existing management technologies and information sources.  The SDK components include tools and sample code for creating applications to use WBEM.


2. SYSTEM REQUIREMENTS

The WBEM SDK beta 2 release requires the following minimum configurations.

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 3 or higher
Microsoft Windows 95	                        DCOM
Microsoft Windows 95 OSR2				None (see below)
HP-UX 10.20							None

Hardware Requirements:

Different minimum computer configurations exist, depending upon the Microsoft operating system used. For WBEM SDK development purposes, it is recommended that a Win32 developer have a computer that consists of at least:

	Pentium processor
	32 MB RAM
	30 MB of available hard disk space
	Monitor/video card support for 256 colors at an 800 X 600 resolution.
	TCP/IP Netcard

Testing a Win32 application developed by using the WBEM SDK requires a machine with the following minimum specifications:

	486 computer running at least 50 Mhz.
	16 MB RAM
	20 MB of available hard disk space
	TCP/IP Netcard

For a complete instantiation of WBEM classes on a machine running Windows 95, you must be running OEM Service Pack 2 (OSR2) and DMReg must be installed. The WBEM Win32 providers need DMReg for some Windows 95 instrumentation. However, DMReg is not required if you are developing your own provider, unless you are deriving from one of the Win32 DMReg classes and want to see a completely populated instance.

For security reasons, it is recommended that the WBEM SDK be installed on a Windows NT File System (NTFS) formatted drive. Otherwise it is difficult to secure the Common Information Model Object Manager (CIMOM) directory.


3. How to install Build 450:

If you are installing Build 450 on a machine which does not have WBEM Build 220 (beta 2), skip to step f.
  
  a. Remove from your current WBEM directory any files which should not be deleted. This 	    includes extra subdirectories, as the entire WBEM directory tree will be deleted by 	    Uninstall.
  b.  Run the WBEM Beta 2 Uninstall.
  c.  Go into your Internet Explorer options and delete the Temporary Internet Files.
  d.  Reboot.
  e.  From a command prompt, go to the Downloaded Program Files subdirectory off your 	    operating system's main directory (for IE3, go to the occache directory instead). 	    Delete any OCX or DLL file dated 10/16/97, along with the HMMV.INF file.
  f.  Install the WBEM 450 SDK. NOTE: By default this version of the SDK installs into the 	    \System32\Wbem directory.
  g.  From a command prompt, go to the Wbem\Include directory and run NMAKE.


4. Using the Debug symbols:

The WBEM SDK can be installed on either a Windows NT 5.0 workstation or server.  

Installing the debug symbols
The debug symbols included with the SDK do not have a built-in installer.  They can simply be copied from the CD-ROM to the hard disk.  The debug symbols need to be in the same directory as the component counterpart.  Generally, these are found in the WBEM directory off the System32 directory. 

Using WBEM without the debug symbols
Without the debug symbols, WBEM can be used on either a Retail (Fre) build, a Windows NT 5.0 build, or a Debug (Checked) build.

Using WBEM with the debug symbols
The WBEM debug symbols are equivalent to the Retail (Fre) debug symbols of Windows NT 5.0.
DO NOT ATTEMPT TO USE THE DEBUG SYMBOLS ON AN INSTALLATION OF A CHECKED BUILD OF NT5.


5. Some changes since beta 2: 
If you were a WBEM beta 2 user, the following information will be useful.

The provider architecture has changed significantly since Beta 2. Providers no longer need to implement the IWbemLocator interface. Instead, they can optionally implement a simpler interface, IWbemProviderInit, which is called when the provider is loaded. Provider registration is also less arcane. For details, consult the Instprov sample.

The framework architecture has changed completely; it is now simpler and much faster. Beta 2 framework code is incompatible with the new framework.

The WBEM SDK has adopted the new Common Information Model (CIM) v2 Schema from the Desktop Management Task Force (DMTF). The schema now resides in the \\Root\Cimv2 namespace, not \\Root\Default as it did previously.


6. Support / reporting Bugs:

This is a pre-release version of WBEM, and as such, is not supported.
Bugs can be reported to a Web site that will be reviewed.  Your assistance in reporting these bugs will be appreciated and will add to the overall quality of  the final release of WBEM.

Please report all bugs to
       http://wbem.freerange.com/wbemsdk/wbemrpt.htm


7. Release Errata:

   a. Hyper Media Management Protocol (HMMP) is not included in this pre-release.
   b. In many cases the documentation has not caught up to the code changes. Please bear with us in this respect. This is not a beta-quality release - it's intended as a preview.
   c. The Framework Provider and TempConsumer samples do not build. All other samples build but may have bugs due to recent changes. 
   d. Simple Network Management Protocol (SNMP) does not work with this pre-release version.
   e. There is an intermittent problem installing the SDK on a server with Microsoft Internet Information Server (IIS).  The SDK installs fine if IIS is not installed, but only sometimes when it is.


8. Desktop Management Interface (DMI) Provider Notice:

The DMI Provider component was developed by Intel Corporation.  While this pre-release version is not supported, users should report all problems directly to Intel.  Please report them via the the following URL.
    
      http://wbem.freerange.com/wbemsdk/wbemrpt.htm


9. WBEM SDK Feedback and Issues Reporting Form:

You can send feedback and report issues concerning the WBEM SDK by following the procedures in the following section. Please provide the information as completely as possible and send by e-mail to:

scotboyd@microsoft.com

   >>>To send feedback or report issues concerning the WBEM SDK via e-mail

   a. Insert the following text in the Subject line of the e-mail: 
WBEM SDK Build 450 Issues Report

   b. Provide the following contact Information:

	Primary Contact Name:  	
	Job Title:
	Voice number(s): 
	Fax number(s):
	Internet e-mail address:

	Alternative Contact Name:  	
	Job Title:
	Voice number(s): 
	FAX number(s):
	Internet e-mail address:

	Company Name:  	
	Address line1:
	Address line2:
	City:
	State:
	Zip code:
	Country:

   c. Provide a complete description of the issue you are reporting, including the sequence of steps required to reproduce it.

   d.	Provide a description of your hardware and operating system, as follows:
	
	Operating System (including Service Pack): 
	Protocol(s) in use:
	Computer brand:
	CPU (386, 486, etc):
	Multi-processor? (Y/N):
	RAM (MB):
	Network Adapters:
	Other/unusual HW:

   e.	Provide a description of the software you are using, as follows:

	Internet browser make and version: (For example, Microsoft Internet Explorer 3.02)
	Are you using DCOM? (Y/N):

   f.	Please include copies of your WBEM log files, which are stored in the directory location shown in the 'Logging Directory' value in the Windows Registry key <HKEY_LOCAL_MACHINE>/SOFTWARE/Microsoft/WBEM/CIMOM.
 
The default location is the 'LOGS' directory in the SDK installation directory.

   g.	See the WBEM SDK Release Notes or documentation for instructions on enabling logging.

   h.	If the issue is code-related, include a compile-able code example that reproduces the issue or error.

   i.	If the issue is related to the Managed Object Format (MOF) include the MOF file and the error message(s) reported by the MOF compiler.



