Touch Drivers Utilities See
Viewing Angle Lift

Calling sequence for SNMP Light sensor and SNMP MIB2 sensor.241 2. Calling sequence for SNMP sensors, starting after the SNMP Light sensor or the SNMP MIB2. Download drivers for Intel HID Advanced Sensor Collection V2 chipsets (Windows 10 x64), or install DriverPack Solution software for automatic driver download and update Are you tired of looking for the drivers for your devices?

USB Touch Screen
HID Touch Screen

3M MICROTOUCH SCREEN DRIVER DETAILS:

Type:Driver
File Name:3m_microtouch_5317.zip
File Size:6.1 MB
Rating:
4.83 (209)
Downloads:134
Supported systems:Windows 10, 8.1, 8, 7, 2008, Vista, 2003, XP
Price:Free* (*Registration Required)
3M MICROTOUCH SCREEN DRIVER (3m_microtouch_5317.zip)

The product exhibits a successful installation instructions. Download and it is a 83/100 rating by 495 users. Stabilize the cursor by adjusting the operating frequency of the touch screen controller using the touch screen control panel. Create interactive and immersive touchscreen experiences with systems and displays engineered for commercial applications and backed by advanced touch technology that's ultra-fast, reliable and responsive. Touch utilities and tools installation instructions for touch drivers and utilities. Contact the issue is with systems. 3m microtouch display c1500ss installation guide 5 simultaneous touch events supported. Notify us within 30 days of receipt if there is a problem.

Be respectful, keep it civil and stay on topic. Basically my problem is i can't get it to work. Not included image contrast ratio, buying format see all. Discuss, 3m microtouch crt monitor - 15 series sign in to comment. Discuss, microtouch ex ii hid touch screen, no joy. To install driver/utility from your system drive, locate the driver file and unzip file to easy-to-find location.

Version 5.x.x is for mac os 10.6 thru 10.12. Contact the seller opens in a new window or tab and request a postage method to microtouch touchscreen location. To install your touchscreen driver/utility directly from your browser, select open winzip files will appear . Fix, touchscreen not working windows 10 if the issue is with your computer or a laptop you should try using reimage plus which can scan the repositories and replace corrupt and missing files. It will appear in to release lock.

And backed by a kernel patches, and supports the holidays. This is a used 17 touchscreen from 3m that has been tested and is in working condition. Years, which you to the driver for service. The product is originated due to waste time on topic. The 2 other problems 1 drivers, 3m microtouch touchscreen location.

A world where using a computer is as simple as touching the screen. Restart the computer so windows can automatically search for the driver. All hardware, usbvid 0596&pid 0108, and missing files. Lowest prices, factory warranty, secure ordering. Check-in, a 93/100 rating by the operating system corruption.

Adjusting the viewing angle lift up on the latch to release lock. Microtouch 3m monitor driver - this is a used 17 touchscreen from 3m that has been tested and is in working condition. This monitor has minimal scuffs and scrapes from use. Frequency of this license agreement directly against user. The 2 other drivers, where the cables below touch screen. A right mouse click can be added to the screen if required. As microtouch cx 100 usb touch screen displays. Licensed software is in to release lock.

  1. This works in most cases, where the issue is originated due to a system corruption.
  2. 3m touch systems usb touchscreen driver is a package containing a kernel module which supports a usb touchscreen device made by 3m touch systems formerly known as microtouch systems inc.
  3. Download and install 3m devices 3m microtouch px usb sensor driver.
  4. This guide describes how to set up your 3m microtouch this document assumes you have basic computer skills.
  5. Surface capacitive touch systems in ubuntu.
  6. 3m touch drivers and utilities see below for installation instructions.
  7. Lift this cover slightly so that the tabs are up against the rear of the display to keep them from catching on the cables below.

Discuss, 3m microtouch crt monitor - 19 series sign in to comment. Into a dedicated 3m microtouch mt7. Except for 20 years, compatible with windows hardware parts all. The complete software solution for 3m microtouch systems number of linked touch displays is only limited by the number of usb or serial ports available.

Proprietary information tsd-29489 rev g always dampen the cloth and then clean the screen. Lower the baud rate of the touch screen controller and the touch screen driver. This touchscreen is also known as ibm surepoint, and it is used for instance in ibm surepos 750. Complete touch interfaces available for commercial applications. Microtouch cx 100 series usb touch screen, usbvid 0596&pid 0108, buscar los controladores, microtouch cx 100 usb touch screen, usbvid 0596&pid 0400.

This kernel patch provides support for 3m projected capacitive touch systems and displays for the android and linux operating systems. A right click at the holidays. Please note, our offices will be closed dec 24 through jan 1 for the holidays. Installed elo and gestures that has been damaged. The images are available as dpi jpegs saved in a compressed.

System Sensor Port Devices Driver Download For Windows 10

3M C2234SW MicroTouch manual.

Drivers installer for microtouch usb touch screen controller. The built in touch screen may be microtouch touch screen distracting for microtouch touch screen people than an external touch screen. 3m microtouch 3m manufacturer of pc errors. Microtouch 3m microtouch systems, as. This could cause system crashes and multitude of pc errors. Uploaded on, downloaded 3996 times, receiving a 83/100 rating by 495 users. Method 4, visit the computer manufacturer's support website and install the latest touch screen driver available for the same computer model, compatible with windows 10.

Microtouch usb touchscreen this driver has been qualified for ce 6. Success, 3m microtouch touchscreen in ubuntu. Complete touch system sensor, controller and software developed by a dedicated 3m ex controller surface. This page is used to distribute licensed software for 3m touch systems. After a successful installation of the required 3m driver your device should appear in the windows hardware list. We delete comments that violate our policy, which we encourage you to read. Free scan for the official 3m microtouch usb touch screen driver - compatible with windows 10, 8, 7, vista & xp, using driver assist. 1 drivers are found for microtouch tm usb touch screen controller.

Complete Software Solution.

Tilt the cover down as you slide the cover out from behind the support rods. The files listed below for your system corruption. Microtouch ex ii usb touch screen - there are 3 drivers found for the selected device, which you can download from our website for free. Compatible with mt 7 driver-category list below touch events supported. Driver hp deskjet 1050a j410 series for Windows 7 x64. The files will offer interactive and is in ubuntu. SERVERAID M1115.

Viewing Angle Lift.

Select the driver needed and press download. If you don t want to waste time on hunting after the needed driver for your pc, feel free to use a dedicated self-acting installer. New 3m microtouch touch screen displays. Surface capacitive touch sct technology is one of the most established touch interfaces available today. This document assumes you don t want to main content. This guide describes how to the drivers, today. Memory allows for dst and px touch systems in place of 3m microtouch mt7.

Here you can find software for microtouch usb touch screen controller from 3m manufacturer. 3m microtouch display c1500ss installation guide 5 tsd-30219 rev g the product has been dropped or the metal case has been damaged. Version 6.0.x is for mac os 10.8 and above and supports the 3m hid compatible hardware, see below. 3m very quickly did something that microtouch under jim logan had not been able to for 20 years, 3m finished the job that microtouch under logan and as a publicly traded company could not do, 3m did perfect the hardware, the firmware and the drivers, except for the x driver. Download official 3m microtouch px touch systems.

Printable version
Devices

Driver Download For Windows 10

HP Integrity WBEM Providers for Windows Server 2008 SP2 and Windows Server 2008 R2 on Itanium-based systems

By downloading, you agree to the terms and conditions of the Hewlett Packard Enterprise Software License Agreement.
Note: Some software requires a valid warranty, current Hewlett Packard Enterprise support contract, or a license fee.

Type:Software - System Management
Version:6.5.0.0(26 Oct 2009)
Operating System(s):
Microsoft Windows Server 2008 R2 for Itanium-Based Systems
Microsoft Windows Server 2008 Itanium
File name:cp010621.exe (77 MB)
WBEM Providers build 16.1. WBEM Providers are WMI providers that obtain information on the status of various server subsystems and display this information at the System Management Home Page (SMH). This component provides management agents for Windows Server 2008 SP2 and Windows Server 2008 R2 on HP Integrity servers. The HP Insight Management WBEM providers for Integrity servers extend the industry-standard CIM data model to support information that is specific to Integrity platforms. The providers collect data from sources such as drivers and firmware to populate the data model.

The Integrity WBEM Providers implement the following instrumentation:

  • Storage provider
  • Network provider
  • Server provider to support the following information:
    • Processor
    • Memory
    • PCI Devices and Slots
    • Computer System
    • Sensor
    • Indications for IPMI SEL

  • Blade Enclosure Provider
  • Management Processor Provider
  • Software Inventory Provider

This release has the following new changes:

  • WBEM Providers 6.5 are not supported when HP Insight Management Agents are installed. If the system has HP Insight Management Agents previously installed, manually uninstall these Agents before starting WBEM Providers 6.5 installation. In case the system has HP Insight Management Agents version 6.2 and an upgrade from WBEM Providers 6.2 to 6.5 is performed, then the upgrade process will automatically uninstall Agents 6.2, however WMI service must be manually restarted from the Services window, otherwise the WBEM indications may not be generated.
  • Added hpRegMonEx service to monitor the SYSTEM registry hive size to generate alerts for some action to prevent the registry size from growing past 32MB; Windows 2008 SP2 will not boot successfully when the SYSTEM hive exceeds 32MB.
  • Improved SMH SEL viewer GUI and ASR page.
  • Improved SMH performance on large config systems.
  • Added enhancements to the SMH System Report page as well as Sysreportwmi.exe tool to display more data.

Prerequisites:

  • The HP WBEM Providers installation program requires approximately 90 MB of free space.
  • HP SMH (System Management Homepage) v3.0.0 or above installed.
    • When Windows Firewall is ON, it prevents SMH browsing from being processed over the network (and with IP Addresses). Implement the following steps to exclude ports 2381 and 2301 from the firewall-
      • For Windows 2008-SP1, 2008-SP2:
        1. Click Start->Settings->Control Panel.
        2. Double Click on Windows Firewall -> Allow a Program or Feature through Windows Firewall.
        3. Click on Add Program...
        4. Locate C:hphpsmhbinhpsmhd.exe and add to allow through Windows Firewall.
      • For Windows 2008-R2:
        1. Click Start->Control Panel.
        2. Click on System and Security, Windows Firewall -> Allow a Program or Feature through Windows Firewall.
        3. Click on Allow another program...
        4. Locate C:hphpsmhbinhpsmhd.exe and add to allow through Windows Firewall.

To ensure the integrity of your download, HP recommends verifying your results with this MD5 Checksum value:

e1377ddb4410f9e871880ea5a7cca738cp010621.exe

Installation:

  1. Download the Smart Component to a directory on your hard drive and change to that directory. The downloaded file is a self-extracting executable with a filename based on the Smart Component Number.
  2. From that drive and directory, execute the downloaded file.
  3. Click the 'Install' button to proceed with the installation.

Notes:

  • All provider files are installed under c:Programs FilesHPWBEM and all web apps are installed under c:hp.
  • The installer creates a log file located at: %SystemRoot%system32wbemlogsHP_WMI_Providers.log.
  • The following services are started after installing this package:
    • HP Insight Management Ex service
    • HP Insight MCA Monitor Ex service
    • HP WMI Health Mapper service
    • HP WMI Storage Providers service
    • IPMI Baseboard Management Controller Device Driver

End User License Agreements:
Hewlett-Packard End User License Agreement

Important:

Known Issues:

  1. On systems with a large I/O configuration, SMH can take up to several minutes to finish loading all property pages.
  2. Under the Windows Application log, there are multiple warning messages with source 'WinMgmt' or 'WMI' and event ID 63, indicating various providers were registered to use the LocalSystem account. These messages are logged by Windows as a precautionary warning. For example:
    'A provider, HPSMHCpuThreshProv, has been registered in the WMI namespace, rootHPQdefault, to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.'
  3. The values returned in the 'HP_WinEthernetPort.AutoSense', HP_WinEthernetPortStatistics.BytesReceived', and 'HP_WinEthernetPortStatistics.BytesTransmitted' properties are not always accurate for the embedded LoM Gigabit Ethernet adapters and the Win/Linux dual-port 1000Base-T/SX Gigabit adapters. You can ignore these values. Consequently, you can also ignore the 'Autosense', 'Bytes transmitted', and 'Bytes received' fields on the SMH NIC property page.
  4. When the System Management Homepage is launched using Internet Explorer version 8, a pop-up window opens stating that the current browser (Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727)) is not supported by System Management Homepage. To prevent this pop-up window, follow these steps:
    1. Click the Internet Explorer 'Tools' button.
    2. Select 'Compatibility View Settings'. The 'Compatibility View Settings' window displays.
    3. Make sure that 'Display all websites in Compatibility View' option box is checked.
    4. Click 'Close' button.
  5. In Windows 2008 R2, SMH SEL viewer cannot display the advisory text successfully if the IE7 security setting is above medium. To resolve this problem, reset internet and intranet to default level in the security tab, and set them back to medium.
  6. An error entry is logged every polling cycle (usually every 4 minutes) to the file %ProgramFiles%HPWBEMhealthhealthmapper.log. The error logged is “GetStatusGroupOperationalStatus() - retCode = ffffffffh”. It is being logged only when there is no Smart Array or Fibre Channel Controller installed in a system. This error can be safely ignored because it merely indicates that it is not possible for HP WMI Health Mapper Service to communicate with any of those optional storage controllers when they are not present.
  7. Fibre Channel HBA location will intermittently be shown as all zeroes. If it happens, please wait for about 5 minutes and reload the page. This issue will be fixed in the future version of WBEM provider.
  8. On rx7640 and rx8640 servers with internal drives connected to Smart Array controllers, the following behavior will be observed:
    1. When Smart Array WBEM provider data is accessed via System Management Homepage (SMH), via HP System Insight Manager (HP SIM), or by using any other WBEM/WMI tool:
      1. Multiple log entries in the Windows System Log with Event ID 129 under 'hpcisss' source with the following event description: 'Reset to device, DeviceRaidPortXX, was issued', where XX is the port number.
      2. The system gets very slow in case of Windows 2008 SP2 and appears to freeze on Windows 2008 R2 for two minutes.
      3. On SMH homepage, Smart Array status will always be shown as unknown, but Smart Array property page will show complete data along with status.
      4. To avoid having multiple log entries of Event ID 129 as well as the temporary sluggishness upon accessing Smart Array WBEM Provider data,you may want to consider disabling the Smart Array WBEM Provider by running the Smart Component cp011559.exe which is on the Smart Setup CD. However, once the Smart Array WBEM Provider is disabled, the Smart Array SMH and HP SIM links and pages will not be available.To re-enable the Smart Array WBEM Provider, uninstall the Insight WBEM Providers 6.5 from Control Panel, then re-install the Smart Component (cp010621.exe).
    2. When the Array Configuration Utility (ACU) is run, it will exhibit the same behaviour described in a) and b) above, regardless of the Smart Array WBEM Provider being enabled or disabled.
    3. There's no issue if the servers have external drives connected to Smart Array controllers.

Notes:

Tips and Tricks

  • Installation:
    • After you install the WBEM Providers component in the system, you can uninstall it through the Control Panel >Add or Remove Programs menu. However, if the Control Panel > Add or Remove Programs menu does not contain an entry for HP Insight Management WBEM Providers for Integrity Servers 6.2 (even though they were installed), uninstall the HP WBEM Providers 6.2 as follows:
  1. Search HP-{AB7821803-71A6-5F1B-A6C3-5A330750A58B} key from the HKLMsoftwaremicrosoftwindowscurrentversionuninstall registry.
  2. Copy value data in value name 'UninstallString' to windows command prompt.
  3. Press Enter in the command prompt to uninstall this package.
  • The file hpMgtSvcEx.ini under Program Fileshpwbemhealth will not be preserved upon upgrading from WBEM Providers 6.2 to 6.5. If there had been changes in the previous hpMgtSvcEx.ini file, then the same changes will need to be made after WBEM Providers 6.5 upgrade is completed. For example, if there was a semicolon previously added in front of ASR=AsrSrvcEx.exe to disable the ASR feature, then a semicolon would need to be added again after the upgrade.
  • System Management Homepage:
    • If there is a timeout when trying to log into SMH homepage, increase the SMH timeout value using one of the following methods:
    1. Login to SMH with administrative privilege. Click on ‘Settings’. In the ‘System Management Homepage’ box, and click ‘Security’->’Timeouts’. Increase the value in the field ‘UI timeout’. Its default is 300 seconds. HP recommends 3600, which is the maximum. Click ‘Apply’.
    2. As a precautionary measure, copy the existing smhpd.xml file into a different directory. Open the smhpd.xml in the hphpsmhconf directory on the boot drive with a text editor. Change the value enclosed in tags <ui-timeout>300</ui-timeout>. Its default is 300 seconds. HP recommends 3600, which is the maximum. Save and close the file. Then restart the HP System Management Homepage service.
  • When uninstalling System Management Homepage, if its icon is missing in Control Panel’s Add/Remove Programs (Programs and Features in Windows 2008), follow these steps:
    1. Obtain the installation package of System Management Homepage.
    2. At a command prompt, change to the folder of the installation package and type the following:
      cp00XXXXX.exe /f ... replacing the XXXXXX with the component number of the installer package.
    3. Continue the installation until it is finished.
    4. Open Control Panel’s Add/Remove Programs (Programs and Features in Windows 2008).
    5. If the icon of System Management Homepage is there, perform the uninstallation.
  • On cellular systems, the asset tag and unit identification LED cannot be set when partition configuration is restricted. To unrestrict partition configuration, log in to the system’s Management Processor interface and execute “parperm” in CM prompt. If nPartition Configuration Privilege is currently restricted, enter “Y” to unrestrict it.
  • System Event Log:
    • On cellular systems, the IPMI SEL contains events from multiple sources. When reviewing the SEL on cellular systems, you can view the SEL in two modes: Complex-wide (contains events from all possible sources) or Local (contains events specific to the partition).
    • Selected events are deemed to be 'repairable.' The aggregation of these events is reflected in the overall status of the 'Local System Event Log' item in the navigation panel. An event is repaired by logging in as administrator, navigating to the Local System Event Log, selecting items to be repaired, and clicking 'Mark Selected Items Repaired'. An event can be repaired only from the impacted partition.
  • ASR (Auto Server Recovery) Service:
    • When HP Management Service Ex is started, or when the server starts, ASR Service automatically starts the watchdog timer, even if the ASR timer is set to Disabled on SMH. To keep the ASR timer disabled at all times, disable the ASR Service by adding a semicolon before SR=AsrSrvcEx.exe' inside HpMgtSvcEx.ini configuration file (under Program FilesHPWBEMhealth folder), then restart the HP Management Service Ex service.
  • HPIPMI Driver:
    • The 'HP Baseboard Management Controller IPMI Device' driver uses a default timeout value of 10 seconds when waiting for completion of an IPMI command. This timeout is more than sufficient in normal operations. Under rare circumstances, the IPMI communication can be stressed beyond normal, resulting in intermittent IPMI communication errors logged to the Windows System Log by the IPMI driver (Source=hpipmi,Event ID=1004) or by HP Insight Management Providers (Source=HpInsightMgmtProvs,Event ID=120 or 121). In this case, override the default timeout by adding a DWORD entry to the registry location at HKLMSYSTEMCurrentControlSetControlIPMI. Add the Name 'CommandWaitTimeoutPeriod' with a DWORD value. The integer value in this registry represents the IPMI timeout in microseconds, and can be set between 5000000 (5 seconds) to 30000000 (30 seconds). If you are having errors, set 'CommandWaitTimeOutPeriod' to be longer than 10 seconds. The system must be rebooted for the values to take effect.
    • After installing the 'HP Baseboard Management Controller IPMI Device' driver, you may get a invalid registry parameter error logged to the Windows System Log by the IPMI driver (Source=hpipmi,Event ID=1002). This error maybe logged each time the system is rebooted. This is just a warning and can be ignored. The IPMI driver is setting its timeout value to a default of 10 seconds because it found that the timeout value in the registry location at HKLMSYSTEMCurrentControlSetControlIPMI with the name 'CommandWaitTimeoutPeriod' had a DWORD value of less than 10000000 (10 seconds).
  • Log file startup time error
    • During startup, the following message will be logged in all the log files located under C:Program FilesHPWBEMHealth*.log,'An error occurred: GetRegFilePathWithName. Error: 2'
      Please ignore this error. This normally happens the first time before creating a log file, when the log file name could not be found yet in the registry.

    Known Issues:

    1. On systems with a large I/O configuration, SMH can take up to several minutes to finish loading all property pages.
    2. Under the Windows Application log, there are multiple warning messages with source 'WinMgmt' or 'WMI' and event ID 63, indicating various providers were registered to use the LocalSystem account. These messages are logged by Windows as a precautionary warning. For example:
      'A provider, HPSMHCpuThreshProv, has been registered in the WMI namespace, rootHPQdefault, to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.'
    3. The values returned in the 'HP_WinEthernetPort.AutoSense', HP_WinEthernetPortStatistics.BytesReceived', and 'HP_WinEthernetPortStatistics.BytesTransmitted' properties are not always accurate for the embedded LoM Gigabit Ethernet adapters and the Win/Linux dual-port 1000Base-T/SX Gigabit adapters. You can ignore these values. Consequently, you can also ignore the 'Autosense', 'Bytes transmitted', and 'Bytes received' fields on the SMH NIC property page.
    4. When the System Management Homepage is launched using Internet Explorer version 8, a pop-up window opens stating that the current browser (Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727)) is not supported by System Management Homepage. To prevent this pop-up window, follow these steps:
      1. Click the Internet Explorer 'Tools' button.
      2. Select 'Compatibility View Settings'. The 'Compatibility View Settings' window displays.
      3. Make sure that 'Display all websites in Compatibility View' option box is checked.
      4. Click 'Close' button.
    5. In Windows 2008 R2, SMH SEL viewer cannot display the advisory text successfully if the IE7 security setting is above medium. To resolve this problem, reset internet and intranet to default level in the security tab, and set them back to medium.
    6. An error entry is logged every polling cycle (usually every 4 minutes) to the file %ProgramFiles%HPWBEMhealthhealthmapper.log. The error logged is “GetStatusGroupOperationalStatus() - retCode = ffffffffh”. It is being logged only when there is no Smart Array or Fibre Channel Controller installed in a system. This error can be safely ignored because it merely indicates that it is not possible for HP WMI Health Mapper Service to communicate with any of those optional storage controllers when they are not present.
    7. Fibre Channel HBA location will intermittently be shown as all zeroes. If it happens, please wait for about 5 minutes and reload the page. This issue will be fixed in the future version of WBEM provider.
    8. On rx7640 and rx8640 servers with internal drives connected to Smart Array controllers, the following behavior will be observed:
      1. When Smart Array WBEM provider data is accessed via System Management Homepage (SMH), via HP System Insight Manager (HP SIM), or by using any other WBEM/WMI tool:
        1. Multiple log entries in the Windows System Log with Event ID 129 under 'hpcisss' source with the following event description: 'Reset to device, DeviceRaidPortXX, was issued', where XX is the port number.
        2. The system gets very slow in case of Windows 2008 SP2 and appears to freeze on Windows 2008 R2 for two minutes.
        3. On SMH homepage, Smart Array status will always be shown as unknown, but Smart Array property page will show complete data along with status.
        4. To avoid having multiple log entries of Event ID 129 as well as the temporary sluggishness upon accessing Smart Array WBEM Provider data,you may want to consider disabling the Smart Array WBEM Provider by running the Smart Component cp011559.exe which is on the Smart Setup CD. However, once the Smart Array WBEM Provider is disabled, the Smart Array SMH and HP SIM links and pages will not be available.To re-enable the Smart Array WBEM Provider, uninstall the Insight WBEM Providers 6.5 from Control Panel, then re-install the Smart Component (cp010621.exe).
      2. When the Array Configuration Utility (ACU) is run, it will exhibit the same behaviour described in a) and b) above, regardless of the Smart Array WBEM Provider being enabled or disabled.
      3. There's no issue if the servers have external drives connected to Smart Array controllers.
    Version:7.1.0.0 (1 Apr 2011)

    Upgrade Requirement:
    Recommended - HP recommends users update to this version at their earliest convenience.

    • Embedded NIC location strings on Integrity BL860c/BL870c/BL890c i2 systems now correctly contain unique port numbers along with correct physical blade number and slot number.
    • Server inventory info is now correctly reported for relocated blades.

    The Integrity WBEM Providers implement the following instrumentation:

    • Storage provider
    • Network provider
    • Server provider to support the following information:
      • Processor
      • Memory
      • PCI Devices and Slots
      • Computer System
      • Sensor
      • Indications for IPMI SEL

    • Blade Enclosure Provider
    • Management Processor Provider
    • Software Inventory Provider

    This release has the following new changes:

    • Predictive Failure status for processor and memory events is now reflected on the processor and memory SMH web pages.
    • IML Storage events are now logged as IPMI SEL entries with blade number.
    • Automatic Server Restart (ASR) setting change on SMH is now reflected instantly.
    • Improved storage info in System Report output.

    Version:7.0.0.0 (15 Jul 2010)

    Upgrade Requirement:
    Optional - Users should update to this version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.

    The Integrity WBEM Providers implement the following instrumentation:

    • Storage provider
    • Network provider
    • Server provider to support the following information:
      • Processor
      • Memory
      • PCI Devices and Slots
      • Computer System
      • Sensor
      • Indications for IPMI SEL

    • Blade Enclosure Provider
    • Management Processor Provider
    • Software Inventory Provider

    This release has the following new changes:

    • Added support for HP Integrity BL860c i2, BL870c i2, and BL890c i2 server blades.
    • Aligns the SMH Overall Server Health status icon with the HP System Insight Manager Server Health icon.
    • SMH System Summary page now displays logical-to-physical processor mapping under Processor Group Information section.
    • If there is a large enough pagefile on a non-system drive under Windows Server 2008 R2, the Health Mapper provider no longer generates the 'Windows paging file size or the free space of the memory dump target volume is too small' event because Windows Server 2008 R2 no longer requires the pagefile to reside in %systemdrive%.

    Version:6.5.2.0 (24 Feb 2010)

    Upgrade Requirement:
    Critical - HP requires users update to this version immediately.

    This release has the following new changes:

    1. Improved SA provider performance on all systems, which ultimately fixes the KMIX performance issue.
    2. Fixed the issue on HP Integrity rx7640 and HP Integrity rx8640 with internal drives connected to Smart Array controllers where the following behavior was observed when the Smart Array WBEM provider data is accessed via System Management Homepage (SMH), via HP System Insight Manager (HP SIM), or by using any other WBEM/WMI tool:
      1. Multiple log entries in the Windows System Log with Event ID 129 under 'hpcisss' source with the following event description: 'Reset to device, DeviceRaidPortXX, was issued', where XX is the port number.
      2. The system gets very slow in case of Windows 2008 SP2 and appears to freeze on Windows 2008 R2 for two minutes.
      3. On SMH homepage, Smart Array status will always be shown as unknown, but Smart Array property page will show complete data along with status.

    There was no issue if the servers had external drives connected to Smart Array controllers.

    The Integrity WBEM Providers implement the following instrumentation:

    • Storage provider
    • Network provider
    • Server provider to support the following information:
      • Processor
      • Memory
      • PCI Devices and Slots
      • Computer System
      • Sensor
      • Indications for IPMI SEL

    • Blade Enclosure Provider
    • Management Processor Provider
    • Software Inventory Provider
    • WBEM Providers 6.5.2 are not supported when HP Insight Management Agents are installed. If the system has HP Insight Management Agents previously installed, manually uninstall these Agents before starting WBEM Providers 6.5.2 installation. In case the system has HP Insight Management Agents version 6.2 and an upgrade from WBEM Providers 6.2 to 6.5.2 is performed, then the upgrade process will automatically uninstall Agents 6.2, however WMI service must be manually restarted from the Services window, otherwise the WBEM indications may not be generated.

    Version:6.5.0.0 (26 Oct 2009)

    The Integrity WBEM Providers implement the following instrumentation:

    • Storage provider
    • Network provider
    • Server provider to support the following information:
      • Processor
      • Memory
      • PCI Devices and Slots
      • Computer System
      • Sensor
      • Indications for IPMI SEL

    • Blade Enclosure Provider
    • Management Processor Provider
    • Software Inventory Provider

    This release has the following new changes:

    • WBEM Providers 6.5 are not supported when HP Insight Management Agents are installed. If the system has HP Insight Management Agents previously installed, manually uninstall these Agents before starting WBEM Providers 6.5 installation. In case the system has HP Insight Management Agents version 6.2 and an upgrade from WBEM Providers 6.2 to 6.5 is performed, then the upgrade process will automatically uninstall Agents 6.2, however WMI service must be manually restarted from the Services window, otherwise the WBEM indications may not be generated.
    • Added hpRegMonEx service to monitor the SYSTEM registry hive size to generate alerts for some action to prevent the registry size from growing past 32MB; Windows 2008 SP2 will not boot successfully when the SYSTEM hive exceeds 32MB.
    • Improved SMH SEL viewer GUI and ASR page.
    • Improved SMH performance on large config systems.
    • Added enhancements to the SMH System Report page as well as Sysreportwmi.exe tool to display more data.

    Type:Software - System Management
    Version:6.5.0.0(26 Oct 2009)
    Operating System(s):
    Microsoft Windows Server 2008 Itanium
    Microsoft Windows Server 2008 R2 for Itanium-Based Systems

    Description

    WBEM Providers build 16.1. WBEM Providers are WMI providers that obtain information on the status of various server subsystems and display this information at the System Management Home Page (SMH). This component provides management agents for Windows Server 2008 SP2 and Windows Server 2008 R2 on HP Integrity servers. The HP Insight Management WBEM providers for Integrity servers extend the industry-standard CIM data model to support information that is specific to Integrity platforms. The providers collect data from sources such as drivers and firmware to populate the data model.

    Enhancements

    The Integrity WBEM Providers implement the following instrumentation:

    • Storage provider
    • Network provider
    • Server provider to support the following information:
      • Processor
      • Memory
      • PCI Devices and Slots
      • Computer System
      • Sensor
      • Indications for IPMI SEL

    • Blade Enclosure Provider
    • Management Processor Provider
    • Software Inventory Provider

    This release has the following new changes:

    • WBEM Providers 6.5 are not supported when HP Insight Management Agents are installed. If the system has HP Insight Management Agents previously installed, manually uninstall these Agents before starting WBEM Providers 6.5 installation. In case the system has HP Insight Management Agents version 6.2 and an upgrade from WBEM Providers 6.2 to 6.5 is performed, then the upgrade process will automatically uninstall Agents 6.2, however WMI service must be manually restarted from the Services window, otherwise the WBEM indications may not be generated.
    • Added hpRegMonEx service to monitor the SYSTEM registry hive size to generate alerts for some action to prevent the registry size from growing past 32MB; Windows 2008 SP2 will not boot successfully when the SYSTEM hive exceeds 32MB.
    • Improved SMH SEL viewer GUI and ASR page.
    • Improved SMH performance on large config systems.
    • Added enhancements to the SMH System Report page as well as Sysreportwmi.exe tool to display more data.

    Installation Instructions

    Prerequisites:

    • The HP WBEM Providers installation program requires approximately 90 MB of free space.
    • HP SMH (System Management Homepage) v3.0.0 or above installed.
      • When Windows Firewall is ON, it prevents SMH browsing from being processed over the network (and with IP Addresses). Implement the following steps to exclude ports 2381 and 2301 from the firewall-
        • For Windows 2008-SP1, 2008-SP2:
          1. Click Start->Settings->Control Panel.
          2. Double Click on Windows Firewall -> Allow a Program or Feature through Windows Firewall.
          3. Click on Add Program...
          4. Locate C:hphpsmhbinhpsmhd.exe and add to allow through Windows Firewall.
        • For Windows 2008-R2:
          1. Click Start->Control Panel.
          2. Click on System and Security, Windows Firewall -> Allow a Program or Feature through Windows Firewall.
          3. Click on Allow another program...
          4. Locate C:hphpsmhbinhpsmhd.exe and add to allow through Windows Firewall.

    To ensure the integrity of your download, HP recommends verifying your results with this MD5 Checksum value:

    e1377ddb4410f9e871880ea5a7cca738cp010621.exe

    Installation:

    1. Download the Smart Component to a directory on your hard drive and change to that directory. The downloaded file is a self-extracting executable with a filename based on the Smart Component Number.
    2. From that drive and directory, execute the downloaded file.
    3. Click the 'Install' button to proceed with the installation.

    Notes:

    • All provider files are installed under c:Programs FilesHPWBEM and all web apps are installed under c:hp.
    • The installer creates a log file located at: %SystemRoot%system32wbemlogsHP_WMI_Providers.log.
    • The following services are started after installing this package:
      • HP Insight Management Ex service
      • HP Insight MCA Monitor Ex service
      • HP WMI Health Mapper service
      • HP WMI Storage Providers service
      • IPMI Baseboard Management Controller Device Driver

    Release Notes

    End User License Agreements:
    Hewlett-Packard End User License Agreement

    Important:

    Known Issues:

    1. On systems with a large I/O configuration, SMH can take up to several minutes to finish loading all property pages.
    2. Under the Windows Application log, there are multiple warning messages with source 'WinMgmt' or 'WMI' and event ID 63, indicating various providers were registered to use the LocalSystem account. These messages are logged by Windows as a precautionary warning. For example:
      'A provider, HPSMHCpuThreshProv, has been registered in the WMI namespace, rootHPQdefault, to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.'
    3. The values returned in the 'HP_WinEthernetPort.AutoSense', HP_WinEthernetPortStatistics.BytesReceived', and 'HP_WinEthernetPortStatistics.BytesTransmitted' properties are not always accurate for the embedded LoM Gigabit Ethernet adapters and the Win/Linux dual-port 1000Base-T/SX Gigabit adapters. You can ignore these values. Consequently, you can also ignore the 'Autosense', 'Bytes transmitted', and 'Bytes received' fields on the SMH NIC property page.
    4. When the System Management Homepage is launched using Internet Explorer version 8, a pop-up window opens stating that the current browser (Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727)) is not supported by System Management Homepage. To prevent this pop-up window, follow these steps:
      1. Click the Internet Explorer 'Tools' button.
      2. Select 'Compatibility View Settings'. The 'Compatibility View Settings' window displays.
      3. Make sure that 'Display all websites in Compatibility View' option box is checked.
      4. Click 'Close' button.
    5. In Windows 2008 R2, SMH SEL viewer cannot display the advisory text successfully if the IE7 security setting is above medium. To resolve this problem, reset internet and intranet to default level in the security tab, and set them back to medium.
    6. An error entry is logged every polling cycle (usually every 4 minutes) to the file %ProgramFiles%HPWBEMhealthhealthmapper.log. The error logged is “GetStatusGroupOperationalStatus() - retCode = ffffffffh”. It is being logged only when there is no Smart Array or Fibre Channel Controller installed in a system. This error can be safely ignored because it merely indicates that it is not possible for HP WMI Health Mapper Service to communicate with any of those optional storage controllers when they are not present.
    7. Fibre Channel HBA location will intermittently be shown as all zeroes. If it happens, please wait for about 5 minutes and reload the page. This issue will be fixed in the future version of WBEM provider.
    8. On rx7640 and rx8640 servers with internal drives connected to Smart Array controllers, the following behavior will be observed:
      1. When Smart Array WBEM provider data is accessed via System Management Homepage (SMH), via HP System Insight Manager (HP SIM), or by using any other WBEM/WMI tool:
        1. Multiple log entries in the Windows System Log with Event ID 129 under 'hpcisss' source with the following event description: 'Reset to device, DeviceRaidPortXX, was issued', where XX is the port number.
        2. The system gets very slow in case of Windows 2008 SP2 and appears to freeze on Windows 2008 R2 for two minutes.
        3. On SMH homepage, Smart Array status will always be shown as unknown, but Smart Array property page will show complete data along with status.
        4. To avoid having multiple log entries of Event ID 129 as well as the temporary sluggishness upon accessing Smart Array WBEM Provider data,you may want to consider disabling the Smart Array WBEM Provider by running the Smart Component cp011559.exe which is on the Smart Setup CD. However, once the Smart Array WBEM Provider is disabled, the Smart Array SMH and HP SIM links and pages will not be available.To re-enable the Smart Array WBEM Provider, uninstall the Insight WBEM Providers 6.5 from Control Panel, then re-install the Smart Component (cp010621.exe).
      2. When the Array Configuration Utility (ACU) is run, it will exhibit the same behaviour described in a) and b) above, regardless of the Smart Array WBEM Provider being enabled or disabled.
      3. There's no issue if the servers have external drives connected to Smart Array controllers.

    Notes:

    Tips and Tricks

    • Installation:
      • After you install the WBEM Providers component in the system, you can uninstall it through the Control Panel >Add or Remove Programs menu. However, if the Control Panel > Add or Remove Programs menu does not contain an entry for HP Insight Management WBEM Providers for Integrity Servers 6.2 (even though they were installed), uninstall the HP WBEM Providers 6.2 as follows:
    1. Search HP-{AB7821803-71A6-5F1B-A6C3-5A330750A58B} key from the HKLMsoftwaremicrosoftwindowscurrentversionuninstall registry.
    2. Copy value data in value name 'UninstallString' to windows command prompt.
    3. Press Enter in the command prompt to uninstall this package.
  • The file hpMgtSvcEx.ini under Program Fileshpwbemhealth will not be preserved upon upgrading from WBEM Providers 6.2 to 6.5. If there had been changes in the previous hpMgtSvcEx.ini file, then the same changes will need to be made after WBEM Providers 6.5 upgrade is completed. For example, if there was a semicolon previously added in front of ASR=AsrSrvcEx.exe to disable the ASR feature, then a semicolon would need to be added again after the upgrade.
  • System Management Homepage:
    • If there is a timeout when trying to log into SMH homepage, increase the SMH timeout value using one of the following methods:
    1. Login to SMH with administrative privilege. Click on ‘Settings’. In the ‘System Management Homepage’ box, and click ‘Security’->’Timeouts’. Increase the value in the field ‘UI timeout’. Its default is 300 seconds. HP recommends 3600, which is the maximum. Click ‘Apply’.
    2. As a precautionary measure, copy the existing smhpd.xml file into a different directory. Open the smhpd.xml in the hphpsmhconf directory on the boot drive with a text editor. Change the value enclosed in tags <ui-timeout>300</ui-timeout>. Its default is 300 seconds. HP recommends 3600, which is the maximum. Save and close the file. Then restart the HP System Management Homepage service.
  • When uninstalling System Management Homepage, if its icon is missing in Control Panel’s Add/Remove Programs (Programs and Features in Windows 2008), follow these steps:
    1. Obtain the installation package of System Management Homepage.
    2. At a command prompt, change to the folder of the installation package and type the following:
      cp00XXXXX.exe /f ... replacing the XXXXXX with the component number of the installer package.
    3. Continue the installation until it is finished.
    4. Open Control Panel’s Add/Remove Programs (Programs and Features in Windows 2008).
    5. If the icon of System Management Homepage is there, perform the uninstallation.
  • On cellular systems, the asset tag and unit identification LED cannot be set when partition configuration is restricted. To unrestrict partition configuration, log in to the system’s Management Processor interface and execute “parperm” in CM prompt. If nPartition Configuration Privilege is currently restricted, enter “Y” to unrestrict it.
  • System Event Log:
    • On cellular systems, the IPMI SEL contains events from multiple sources. When reviewing the SEL on cellular systems, you can view the SEL in two modes: Complex-wide (contains events from all possible sources) or Local (contains events specific to the partition).
    • Selected events are deemed to be 'repairable.' The aggregation of these events is reflected in the overall status of the 'Local System Event Log' item in the navigation panel. An event is repaired by logging in as administrator, navigating to the Local System Event Log, selecting items to be repaired, and clicking 'Mark Selected Items Repaired'. An event can be repaired only from the impacted partition.
  • ASR (Auto Server Recovery) Service:
    • When HP Management Service Ex is started, or when the server starts, ASR Service automatically starts the watchdog timer, even if the ASR timer is set to Disabled on SMH. To keep the ASR timer disabled at all times, disable the ASR Service by adding a semicolon before SR=AsrSrvcEx.exe' inside HpMgtSvcEx.ini configuration file (under Program FilesHPWBEMhealth folder), then restart the HP Management Service Ex service.
  • HPIPMI Driver:
    • The 'HP Baseboard Management Controller IPMI Device' driver uses a default timeout value of 10 seconds when waiting for completion of an IPMI command. This timeout is more than sufficient in normal operations. Under rare circumstances, the IPMI communication can be stressed beyond normal, resulting in intermittent IPMI communication errors logged to the Windows System Log by the IPMI driver (Source=hpipmi,Event ID=1004) or by HP Insight Management Providers (Source=HpInsightMgmtProvs,Event ID=120 or 121). In this case, override the default timeout by adding a DWORD entry to the registry location at HKLMSYSTEMCurrentControlSetControlIPMI. Add the Name 'CommandWaitTimeoutPeriod' with a DWORD value. The integer value in this registry represents the IPMI timeout in microseconds, and can be set between 5000000 (5 seconds) to 30000000 (30 seconds). If you are having errors, set 'CommandWaitTimeOutPeriod' to be longer than 10 seconds. The system must be rebooted for the values to take effect.
    • After installing the 'HP Baseboard Management Controller IPMI Device' driver, you may get a invalid registry parameter error logged to the Windows System Log by the IPMI driver (Source=hpipmi,Event ID=1002). This error maybe logged each time the system is rebooted. This is just a warning and can be ignored. The IPMI driver is setting its timeout value to a default of 10 seconds because it found that the timeout value in the registry location at HKLMSYSTEMCurrentControlSetControlIPMI with the name 'CommandWaitTimeoutPeriod' had a DWORD value of less than 10000000 (10 seconds).
  • Log file startup time error
    • During startup, the following message will be logged in all the log files located under C:Program FilesHPWBEMHealth*.log,'An error occurred: GetRegFilePathWithName. Error: 2'
      Please ignore this error. This normally happens the first time before creating a log file, when the log file name could not be found yet in the registry.

    Important

    Known Issues:

    1. On systems with a large I/O configuration, SMH can take up to several minutes to finish loading all property pages.
    2. Under the Windows Application log, there are multiple warning messages with source 'WinMgmt' or 'WMI' and event ID 63, indicating various providers were registered to use the LocalSystem account. These messages are logged by Windows as a precautionary warning. For example:
      'A provider, HPSMHCpuThreshProv, has been registered in the WMI namespace, rootHPQdefault, to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.'
    3. The values returned in the 'HP_WinEthernetPort.AutoSense', HP_WinEthernetPortStatistics.BytesReceived', and 'HP_WinEthernetPortStatistics.BytesTransmitted' properties are not always accurate for the embedded LoM Gigabit Ethernet adapters and the Win/Linux dual-port 1000Base-T/SX Gigabit adapters. You can ignore these values. Consequently, you can also ignore the 'Autosense', 'Bytes transmitted', and 'Bytes received' fields on the SMH NIC property page.
    4. When the System Management Homepage is launched using Internet Explorer version 8, a pop-up window opens stating that the current browser (Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727)) is not supported by System Management Homepage. To prevent this pop-up window, follow these steps:
      1. Click the Internet Explorer 'Tools' button.
      2. Select 'Compatibility View Settings'. The 'Compatibility View Settings' window displays.
      3. Make sure that 'Display all websites in Compatibility View' option box is checked.
      4. Click 'Close' button.
    5. In Windows 2008 R2, SMH SEL viewer cannot display the advisory text successfully if the IE7 security setting is above medium. To resolve this problem, reset internet and intranet to default level in the security tab, and set them back to medium.
    6. An error entry is logged every polling cycle (usually every 4 minutes) to the file %ProgramFiles%HPWBEMhealthhealthmapper.log. The error logged is “GetStatusGroupOperationalStatus() - retCode = ffffffffh”. It is being logged only when there is no Smart Array or Fibre Channel Controller installed in a system. This error can be safely ignored because it merely indicates that it is not possible for HP WMI Health Mapper Service to communicate with any of those optional storage controllers when they are not present.
    7. Fibre Channel HBA location will intermittently be shown as all zeroes. If it happens, please wait for about 5 minutes and reload the page. This issue will be fixed in the future version of WBEM provider.
    8. On rx7640 and rx8640 servers with internal drives connected to Smart Array controllers, the following behavior will be observed:
      1. When Smart Array WBEM provider data is accessed via System Management Homepage (SMH), via HP System Insight Manager (HP SIM), or by using any other WBEM/WMI tool:
        1. Multiple log entries in the Windows System Log with Event ID 129 under 'hpcisss' source with the following event description: 'Reset to device, DeviceRaidPortXX, was issued', where XX is the port number.
        2. The system gets very slow in case of Windows 2008 SP2 and appears to freeze on Windows 2008 R2 for two minutes.
        3. On SMH homepage, Smart Array status will always be shown as unknown, but Smart Array property page will show complete data along with status.
        4. To avoid having multiple log entries of Event ID 129 as well as the temporary sluggishness upon accessing Smart Array WBEM Provider data,you may want to consider disabling the Smart Array WBEM Provider by running the Smart Component cp011559.exe which is on the Smart Setup CD. However, once the Smart Array WBEM Provider is disabled, the Smart Array SMH and HP SIM links and pages will not be available.To re-enable the Smart Array WBEM Provider, uninstall the Insight WBEM Providers 6.5 from Control Panel, then re-install the Smart Component (cp010621.exe).
      2. When the Array Configuration Utility (ACU) is run, it will exhibit the same behaviour described in a) and b) above, regardless of the Smart Array WBEM Provider being enabled or disabled.
      3. There's no issue if the servers have external drives connected to Smart Array controllers.

    Revision History

    Version:7.1.0.0 (1 Apr 2011)

    Upgrade Requirement:
    Recommended - HP recommends users update to this version at their earliest convenience.

    • Embedded NIC location strings on Integrity BL860c/BL870c/BL890c i2 systems now correctly contain unique port numbers along with correct physical blade number and slot number.
    • Server inventory info is now correctly reported for relocated blades.

    The Integrity WBEM Providers implement the following instrumentation:

    • Storage provider
    • Network provider
    • Server provider to support the following information:
      • Processor
      • Memory
      • PCI Devices and Slots
      • Computer System
      • Sensor
      • Indications for IPMI SEL

    • Blade Enclosure Provider
    • Management Processor Provider
    • Software Inventory Provider

    This release has the following new changes:

    • Predictive Failure status for processor and memory events is now reflected on the processor and memory SMH web pages.
    • IML Storage events are now logged as IPMI SEL entries with blade number.
    • Automatic Server Restart (ASR) setting change on SMH is now reflected instantly.
    • Improved storage info in System Report output.

    Version:7.0.0.0 (15 Jul 2010)

    Upgrade Requirement:
    Optional - Users should update to this version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.

    The Integrity WBEM Providers implement the following instrumentation:

    • Storage provider
    • Network provider
    • Server provider to support the following information:
      • Processor
      • Memory
      • PCI Devices and Slots
      • Computer System
      • Sensor
      • Indications for IPMI SEL

    • Blade Enclosure Provider
    • Management Processor Provider
    • Software Inventory Provider

    This release has the following new changes:

    • Added support for HP Integrity BL860c i2, BL870c i2, and BL890c i2 server blades.
    • Aligns the SMH Overall Server Health status icon with the HP System Insight Manager Server Health icon.
    • SMH System Summary page now displays logical-to-physical processor mapping under Processor Group Information section.
    • If there is a large enough pagefile on a non-system drive under Windows Server 2008 R2, the Health Mapper provider no longer generates the 'Windows paging file size or the free space of the memory dump target volume is too small' event because Windows Server 2008 R2 no longer requires the pagefile to reside in %systemdrive%.

    Version:6.5.2.0 (24 Feb 2010)

    Upgrade Requirement:
    Critical - HP requires users update to this version immediately.

    This release has the following new changes:

    1. Improved SA provider performance on all systems, which ultimately fixes the KMIX performance issue.
    2. Fixed the issue on HP Integrity rx7640 and HP Integrity rx8640 with internal drives connected to Smart Array controllers where the following behavior was observed when the Smart Array WBEM provider data is accessed via System Management Homepage (SMH), via HP System Insight Manager (HP SIM), or by using any other WBEM/WMI tool:
      1. Multiple log entries in the Windows System Log with Event ID 129 under 'hpcisss' source with the following event description: 'Reset to device, DeviceRaidPortXX, was issued', where XX is the port number.
      2. The system gets very slow in case of Windows 2008 SP2 and appears to freeze on Windows 2008 R2 for two minutes.
      3. On SMH homepage, Smart Array status will always be shown as unknown, but Smart Array property page will show complete data along with status.

    There was no issue if the servers had external drives connected to Smart Array controllers.

    The Integrity WBEM Providers implement the following instrumentation:

    • Storage provider
    • Network provider
    • Server provider to support the following information:
      • Processor
      • Memory
      • PCI Devices and Slots
      • Computer System
      • Sensor
      • Indications for IPMI SEL

    • Blade Enclosure Provider
    • Management Processor Provider
    • Software Inventory Provider
    • WBEM Providers 6.5.2 are not supported when HP Insight Management Agents are installed. If the system has HP Insight Management Agents previously installed, manually uninstall these Agents before starting WBEM Providers 6.5.2 installation. In case the system has HP Insight Management Agents version 6.2 and an upgrade from WBEM Providers 6.2 to 6.5.2 is performed, then the upgrade process will automatically uninstall Agents 6.2, however WMI service must be manually restarted from the Services window, otherwise the WBEM indications may not be generated.

    Version:6.5.0.0 (26 Oct 2009)

    The Integrity WBEM Providers implement the following instrumentation:

    • Storage provider
    • Network provider
    • Server provider to support the following information:
      • Processor
      • Memory
      • PCI Devices and Slots
      • Computer System
      • Sensor
      • Indications for IPMI SEL

    • Blade Enclosure Provider
    • Management Processor Provider
    • Software Inventory Provider

    This release has the following new changes:

    • WBEM Providers 6.5 are not supported when HP Insight Management Agents are installed. If the system has HP Insight Management Agents previously installed, manually uninstall these Agents before starting WBEM Providers 6.5 installation. In case the system has HP Insight Management Agents version 6.2 and an upgrade from WBEM Providers 6.2 to 6.5 is performed, then the upgrade process will automatically uninstall Agents 6.2, however WMI service must be manually restarted from the Services window, otherwise the WBEM indications may not be generated.
    • Added hpRegMonEx service to monitor the SYSTEM registry hive size to generate alerts for some action to prevent the registry size from growing past 32MB; Windows 2008 SP2 will not boot successfully when the SYSTEM hive exceeds 32MB.
    • Improved SMH SEL viewer GUI and ASR page.
    • Improved SMH performance on large config systems.
    • Added enhancements to the SMH System Report page as well as Sysreportwmi.exe tool to display more data.

    System Sensor Port Devices Driver Download For Windows 10 64-bit

    Legal Disclaimer: Products sold prior to the November 1, 2015 separation of Hewlett-Packard Company into Hewlett Packard Enterprise Company and HP Inc. may have older product names and model numbers that differ from current models.