esx 4.x Internal AAM Error - Agent could not start.: Unknown HA error

Issue : Configuration of the HA fails on 2 hosts at 90% and sometimes 96%.
Background: Customer added 2 new hosts to the cluster and it started happening this way after that.
If he removes the recently added hosts he can successfully configure the HA on all the hosts.
Resolution:
What worked: Disable and enable HA.
What did not work: Reinstalling vmware agents
kb.vmware.com/kb/1003714
update the /etc/hosts with all the ip information of the the hosts of the cluster using
nano /etc/hosts

ESX 4.x Disable NIC teaming

Issue: Customer wanted to disable the nic teaming on his esx 4.1
Resolution: migrate all the VMs off of the host.
Disable the network service

service network stop

then disable the nic bonding

esxcli swiscsi nic remove -n vmk1 -d vmhba35

esxcli swiscsi nic remove -n vmk0 -d vmhba35

Restart the network service

service network start

check the results by

esxcli swiscsi nic list -d vmhba35

[or]

"service network stop && esxcli swiscsi nic remove -n vmk1 -d vmhba35 && esxcli swiscsi nic remove -n vmk0 -d vmhba35 && service network start && esxcli swiscsi nic list -d vmhba35" 

run the single command...

Issue Resolved.  

Stopping the copy paste initiated through GUI

Issue: Customer hast started a copy paste of a VM from one datastore to another using the datastore browser but it is taking too long and he wants to cancel it. customer does not have he vcenter server (standard license) and he cannot find the PID using the esxtop command in ESX.
Resolution: SSH to the ESX(i) host and run the following command from the vCLI
service mgmt-vmware stop && service mgmt-vmware-start
The above command should do the trick to stop the hung copy paste or prolongated copy paste issue.
If you have a vcenter server you can also try restarting the vcenter service in services.msc