Connect HP OneView with Directory services

— original post on my personal blog —

This blog describes a step-by-step guide on how to use secure LDAP to connect the HP OneView appliance with Directory Services (Active Directory).

  • step 1. get the server certificate from the domain controller(s)
  • step 2. creating the right ldap query within HP OneView
  • step 3. adding domain groups to HP OneView

Read more

Installing WES7 with VMware view on a T5740 2gb

Recently I was asked to build a wes7 (Windows Embedded Standard 7) image with VMware view client for a HP T5740 2GB model. This request did bring some interesting problems to the table like:

  • How to get WES7 on a 2GB flash drive
  • How to import the correct drivers to the image during install
  • How to install VMware view client
  • How to enable EWF (Enhanced Write Filter) on the T5740

But first things first lets install WES7 on a 2gb flash drive.

Read more

HP Smart Zero Client, a first impression

Author: Ingmar Verheij

In the end of 2011 Hewlett-Packard introduced a range of zero clients and described them as “the affordable, reprogrammable and to-smart-to-be-called-a-zero-client, clients”. The clients come in two forms; HP Zero Clients, which are unmanaged, and the HP Smart Zero Clients. which are managed. An overview of the available products can be found on the HP website (link).


I had the opportunity to get some hands-on-experience with a HP t510 (a HP Smart Zero Client) and the HP Automatic Update Server software.

Read more

Error 242 when deploying image with HP Device Manager 4.4

When i tried to update/deploy an image from HP Device Manager 4.4 to a Compaq 6720T it constantly failed with the following error:

Fail to execute PushImage task
ErrorCode: 242, Error Detail: Failed to seek image file to end
Fail to execute common task
ErrorCode: 242, Error Detail: Failed to seek image file to end

After some troubleshooting i came to the conclusion that the HPDM agent is not up to date on the client. Make sure that your Agent and your HPDM are the same version, otherwise you can not image from HPDM. 
In HPDM there is the Agent tab, drag and drop the Update Agent template on the unit.  Once that is complete you should be able to image your system.

Determining if Battery Backed Write Cache is installed

imageI wanted to know if a certain server had a Battery Backed Write Cache module (BBWC) on it’s array controller.

I suspected it did not, but I had to be sure. Since this server was running production I couldn’t open (Visual Inspection) or reboot it.

The server didn’t have Insight Agents installed so I couldn’t query it via iLO or the Insight Agents webpage either.

imageI knew that when you do a full install of the array controller bundled software it comes with a commandline tool, hpacucli.exe.

Read more

Monitor “HP Proliant Server” health on “Citrix XenServer” with Nagios

Nagios Powered

Nagios is a powerful monitoring system that enables organizations to identify and resolve IT infrastructure problems before they affect critical business processes.

After experiencing problems with a HP Proliant DL380G6 that unexpectedly restarts, caused by a Automated Server Recovery (ASR), monitoring the status of the Citrix XenServers running on HP Proliant Servers is required in Nagios.

Nagios is a flexible solution that can be expanded with plugins. Plugins can be found at Nagios Exchange, this is where I found the check check_hpasm plugin (direct link). Unfortunately this plugin does not check the ASR status.

In this article I will describe how I’ve configured Groundwork (using Nagios) to monitor the health of HP Proliant Servers and expanded the check_hpasm plugin to check for ASR health.

Read more

BIOS setting HP BL 460c g6 for VMware

For the project where i worked on lately i documented the BIOS settings i have made with the reason why. These are the BIOS settings i use for a HP BL 460c G6 blade where vSphere ESXi 4.1 will be installed on. The bold words in the left column are the options to  be adjust. the location is written above in the same column but may vary between BIOS version.

Read more

Extremely slow Virtual Machines on HP Smart Array P410

I was deploying virtualized Citrix XenApp Servers on HP BL460c G6 servers and somehow the storage (direct attached) responded very slowly.

I had expected reduced performance (see my earlier post) since I didn’t have the  Battery Backed Write Cache module installed.
I did order them but had to start deployment before they arrived.

I did not however expect such an extreme bad performance. Deployment took ages or sometimes failed completely and when logging in to a VM it responded very sluggish.

Disk Latency

I looked in the vSphere console what the Disk Latency was. Latency under 10ms is usually considered good while a latency between 10 and 20ms is a potential performance problem.

I was shocked to notice that the Disk Latency was much higher with peaks toward 2.000 ms (2 seconds!):



Read more

HP Smart Array controller previous lockup code 0xAB

I ran into an error when I was upgrading hardware on an HP BL460c G6 Blade.

After placing 2 new (larger) hard drives the Array Configuration would hang after saving the configuration (It just kept blinking “Saving Configuration…” forever.


After a reset the Smart Array Controller (P410i) halted a very long time on Initializing and eventually failed.


I retried the whole procedure with the same result but this time the controller reported: “previous lockup code 0xAB”.

My next step would be a firmware update and this kb article from HP confirms that it was indeed a firmware issue: HP Serial Smart Array Controllers P410/411/212/712m/410i – May Hang with Lockup Error Code 0XAB Configured in Zero Memory Mode.

This kb article also tells me why I didn’t have this error on another blade: that one had the Battery Backed Write Cache module.

Scripted install VMware ESXi on HP Blade hardware

Today we got to the second stage of upgrading the customer VMware environment. The first stage was the test and Development cluster. This cluster consists 6 HP DL 380 G5 rack mounted servers and with the install script we have made it was a peace of cake! In stage 2 we upgrade (by reinstallation) a part of the production environment when we did the scripted installation all looked well installation process in running writing his image reboot and then the blade server booted the old ESX 4.0 installation instead of the new ESXi 4.1 installation. What the [beeeeep]  is going on? it should be getting in the second part of the installation script where it will set vSwitches settings e.g.. The problem was in the part of the script where the script choose the first discovered disk to install onto we had used this command:

autopart –firstdisk –overwritevmfs

But with a HP Proliant blade (BL 460c G6) this will not work unless you uses the command like this :

autopart –firstdisk=hpsa,cciss,local –overwritevmfs

the hpsa is for SA P410i BL460C G6 the cciss is for SA E200i BL460C G1 and local is for the OTA servers.

!!!!! Warning !!!!!

When using this option un-present all LUN of the responding Host before installation or else you will end up with an new installation of ESXI on your First available LUN