How to remove HP System Tools after using Vconverter to VM

I'm not an expert on this but I need a little direction. I am in the process of virtualizing HP Proliant servers to VMware ESX 4.1. I am using Vconverter to move a few servers over in a test environment as I'm learning to do this. One of the problem I'm having is how to remove all the HP specific drivers and software off of the VM after it's moved over. Basically when we load a physical server, we go to HP's site and download the HP Software support pack in which it loads the NIC, RAID, Power, tools for the system. How do I remvoe all that? There are uninstalled for the RAID config and manager. However, one of the problems I am running into is the "HP Network Configuration Utitlity". That is such a pain because when I look at my network places, the VMadapter shows it's adapter #6 and everything else is missing. I'm trying to figure out how to remove all that junk.
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

markzzConnect With a Mentor Commented:
All of this makes it sound so hard..
It's not.
Look at the attachment.
It's a batch renamed with a .txt extention.
This is essentially what Zane O was saying.
1. Stop all services which you believe will generate lots of disk reads and writes. (Database apps)
2. Virtualise the server with vmwares "stand alone converter 4.0.1"
3. Once complete.
4. boot the server
5. Install vmware tools.
6. Reboot
7. Run appwiz.cpl. (Add remove Programs)
8. Uninstall all applicable HP software. (generally all of it.)
9. Reboot.
10. detach the batch to your server after you have virtualised. Run the batch, Device manager will start in a mode which shows another view anabling you to see devices no longer bound to hardware.
You will need to go to view and select show hidden
11. Clean up by deleting any hardware which appears with a transperant icon.. "EXCEPT Don't touch non-plug and play and don't remove the ras adapters under networking.
The most important thing here is to cleanup the old network adapter. But if you take the time to cleanup the other hardware items the server will perform better.
12. OPen networking. (answer to your real question)Show properties of your Network adapter.. Delete the HP Teaming driver..
13. Reboot
Check it over but your essentially done..
zane_oConnect With a Mentor Commented:
Here is an excerpt from (the original site is no more)
Just in case you didn’t already know this, here is a procedure to remove the ghost nics that don’t always clean themselves up nicely:

Step 1: Open up a command prompt


Step 3: Type – “START DEVMGMT.MSC” and hit

Step 4: Once the Device Manger opens to the “View” menu and select “Show Hidden Devices”. Expand the Network Interface portion of the device tree and you should be able to remove the phantom NIC.
what tool did you use for the p2v
Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

haasjohAuthor Commented:
@ IanTh. I used the VMware Converter Tool 3.03

@Zane. I will try the command but I did go into hidden devices and did not see anything. But I will run to config. Also, this wont get rid of the the HP Network Configuration utility. It's like that util and the NIC are joined at the hip.
haasjohAuthor Commented:
Hey..... That might be it. I searched their site but guess I didn't enter the right syntax for the search. I'll give this a try in a few days and let you know.
Luciano PatrãoICT Senior Infraestructure  Engineer  Commented:

You need to disable from the Network adapter.

Check my article where you can see this and other information and tasks regarding P2V.

There is some scripts that clean all HP tools from a converted machine

Hope this can help


Here is the tool I have used in the past, it works well. It will remove all the HP Proliant Support Pack (PSP) from you new virtual server.

Hope this helps.
Luciano PatrãoICT Senior Infraestructure  Engineer  Commented:

@ianmellor this tool will remove the HP Network Configuration Utility from the Network Adapter itself, we need to disable this manually, then this will disappear.

And one of my scripts is using Guillermo HP removing tools.

Luciano PatrãoICT Senior Infraestructure  Engineer  Commented:

I mean, will NOT remove the HP Network Configuration Utility from the Network Adapter itself

haasjohAuthor Commented:
I've been authorized to make the move tomorrow (Tuesday March 15th). I will let you know how it goes.
haasjohAuthor Commented:
Ok, I am accepting "Markszz and Zane0's" solution. It appears most of the comments build or add detail to Zane0" sultion. Sorry if it gets some of you ticked.

Ok, the drawn out story

The server was an HP Proliant ML370 G2. It was old. Like dual 1 GHz processors. The system had mirrored drives, but no RAID card. So this mirror was a software mirror using dynamic disks. I figured I would break and remove the mirror first. Bad move. The system freaked out at reboot and wouldn't load. Actaully it kept blue screening. So, I booted off of an 2003 CD and went into recovery mode to take a look around. I couldn't find anything wrong, so I ran a CHKDSk /P. Still no joy.

I did a backup of the server right before I started jacking with the settings so I wasn't worried. Instead of restoring the server I used Acronis to make the backup a VM. I then used a tool to convert the VM to work on ESX. Then just copied it over. The system booted without an issue.

The first thing I had to celanup was the BOOT.INI. The old mirror crap was still showing up asking me with instance to boot off of. Once that was cleaned up, I went after the NIC software. The batch file DID NOT work on it at first. It actually killed my TCPIP WINSOCK so I ended up re-copying over the VM to start again.

Once the VM was copied, I dicovered I had to UNBIND the NIC from the HP teaming portion of the HP Network Configuration Utility and remove the NIC from there first. If you don't your asking for trouble. Once I removed the NIC from the HP utility the rest was cake. I was able to unistall the HP tools from ADD\Remove programs, then run the batch file with a few changes and I was good to go.

Thanks again
All Courses

From novice to tech pro — start learning today.