When installing the Data Protector Agent to a Windows 2008 R2 Server the following errormessage appeared:
[Critical] Cannot connect to the SCM (Service Control Manager) on client <clientname>
 Access is denied.
What we need to do now is to add a User with admin rights to the INET Service. Open a command prompt and enter these commands:
C:\Program Files\OmniBack\bin>omniinetpasswd.exe -list
This will show you if there are any users configured already
Now add a user to the INET Service. This user should have administrative permissions and – of course – this user should already be created in your AD.
C:\Program Files\OmniBack\bin>omniinetpasswd.exe -add <domain>\dataprotector
Please enter password:**********
Please retype password:**********
User '<domain>\dataprotector' was successfully added.
Last step is to add this useraccount to be used by the installation service:
omniinetpasswd.exe -inst_srv_user <domain>\dataprotector
User '<domain>\dataprotector' is configured to be used by Installation Server.
For further information RTFM HP Data Protector 6.11 CLI Reference on page 345.
The following order is recommended to patch HP Data Protector:
- Cell Server
- Media Agent
- Disk Agent
- Cell Console
- Others patches(integrations)
You may want to rename the packets after downloading because the don’t include the names.
The ESX-Server does not “know” that the attached SAS-Storage is a shared storage (like HP MSA 2xxx) so it will not allow us to create a RDM disk file within a VM. To do this we need the CLI.
Assuming the volume is already mapped to the ESX-host and can be seen by the ESX-Host we need to do the following:
- Connect to the host using a SSH session
- Display the paths using “esxcfg-mpath -m” and look for the volume – if we know the LUN we can do a grep (e.g. “esxcfg-mpath -m |grep -i l10” – this would only display the volume with the LUN-ID 10)
- Copy the naa-ID (naa.12345lotofnumbers7890)
- To create a RDM enter: “vmkfstools -z /vmfs/devices/disks/<your naa-id here> /vmfs/volumes/<your vmfs-volume here>/<your vm-name here>/<diskname here>.vmdk”
- Please note that the parameter “-z” creates a physical RDM – if you want to use a virtual RDM use the parameter “-r”
- Go to your VM and add a Disk
- Select “Existing disk” and browse to the diskfile you created in step 4
- Finish and do a rescan of disks in your VM
This error occured when I tried to install vCenter Converter on a vCenter Server 4.1 (Build 259021)
To resolve this error check the vpxd.log located in
and search for “failed to add LDAP entry”.
Copy the CN Name you find there.
In my case this was
Now open up ADSI-Edit an connect to the localhost (Port 389) chose “Connection Point” and enter
Expand “OU=Health” and rightclick “OU=ComponentSpecs” – select “New”-> “Object”. Select “container” and OK.
Enter the CN-Name you copied before.
Should look like this afterwards:
Now run the installation again.