HP Nic Teaming error

[Gav0]

After converting 2 HP DL360 G5's with teamed nics i now get the below error when trying to launch the HP Network Configuration Utility:

"An error occured due to the invalid data in the xml file used by this application.  The XML file has been corrupted and should be reinstalled from the installation media"

This has happened on both servers I have converted so far and although the lack of nic teaming isnt a huge issue, i'm concerned that this may be an idication that the conversion processes didnt go a smoothly as it appeared and there may be more corrupt files lurking.

does anyone know if this is a known issue?

I am using Stand Alone Converter 4.3

Many thanks

[vmroyale]

Hello.

You should uninstall the HP Network utilities in the VM.  Use your vSwitch for redundancy now.

Good Luck!

[Troy_Clavell]

you cannot use the hardware teaming software in a virtual machine.  You will need to uninstall the HP Network Configuration Utility.  For that matter uninstall everything hardware related.

Also, go through device manager and uninstall and "ghosted" devices.

1. Click Start, click Run, type cmd.exe, and then press ENTER.
2. Type set devmgr_show_nonpresent_devices=1, and then press ENTER.
3. Type Start DEVMGMT.MSC, and then press ENTER.
4. Click View, and then click Show Hidden Devices.

[admin · Accepted solution]

Hello

Good morning from Canada

After converting P2V you MUST remove all the hardware agents from the Virtual Machine which includes the HP NIC Teaming, it will not work properly

on your VM and it may cause lots of weird issues

As you can see on this KB under  "Tasks to perform after conversion has completed" section http://kb.vmware.com/kb/1004588

Tasks to perform after conversion has completed

After conversion has completed:

1. Review the virtual hardware settings:
   
   
   • Adjust the number of virtual NICs. If  you need to customize the host name or IP address, leave all NICs  disconnected but present.
   • Remove any unnecessary devices such as USB controllers (if running on ESX), COM ports or floppy drives
     
     
2. Start the virtual machine in Safe Mode. For more information, see Booting a Windows Guest Operating System into Safe Mode (1004011).
3. Click Start > Control Panel > Add / Remove Programs.  Remove any unnecessary programs used to install or support device  drivers, such a RAID management tools, network teaming or management  software, wireless card management software, and video and sound  drivers. Do not restart if prompted by an uninstall program.
4. Restart the virtual machine into Normal mode.
5. Remove  any additional devices or device drivers that were used to support  hardware on the physical server. Use either the Device Manager or  Control Panel, depending on the version of Windows, to remove  unnecessary devices. It may also be necessary to view the Event Log to  clear any remaining device startup failure messages.
6. VMware recommends changing the HAL in the virtual machine to uniprocessor if  the source server is configured with multi-CPU hardware abstraction  layer (HAL), and the destination virtual machine is configured to use a  single CPU. For more information, see Modifying the Hardware Abstraction Layer (HAL) for a Windows virtual machine (1003978).
7. Install VMware Tools and restart if prompted.
8. If required, customize the virtual  machine's identity. VMware recommend using the Microsoft Sysprep utility  to accomplish this, however it can also be accomplished by manually  changing its computer host name, IP address, and any other required  unique identification. For more information, see How to Use Sysprep: An Introduction http://technet.microsoft.com/en-us/library/bb457073.aspx.
9. If the System Configuration Utility(msconfig) was used prior to conversion, select the Normal startup option to change switch back to a normal boot configuration. For more information, see Using the Windows System Configuration utility (1004010).
10. Apply any previously removed static IP address settings, as required.
11. Reconnect any disconnected virtual NICs, as required.

[Gav0]

Thanks to everyone that has answered so quickly.  Makes sense that all H/W related utilities should be removed.

I just wasnt sure if the fact it was failing was due to an incompatability issue or because the conversion screwed up - i guess its safe to assume it's compatability related?