Folks,

While patching ESX 3.0.1 servers, discovered that the patches didn't take on one server. I tried to migrate a guest Solaris 10 server to another ESX 3.0.1 server that was patched so I could redo the patches. The migration hung and after 15 minutes, I tried service mgmt-vmware restart followed by service vmware-vpxa restart. Both commands ran without a hitch but the vitrual server showed up as orphaned.
I removed the orphaned server from inventory and then navigated through the storage information to the virtual server's folded and selected the .vmx file and readded the server to inventory on the ESX host that needs patching.

It is now in inventory but showing as powered off.

I logged onto the server remotely and restarted vmware-tools - a couple of times, I've also pinged the server hosting VirtualCenter 2.0.1.

Still showing as powered off. Also showing VMware Tools as not running.

Since this is a production server hosting an Oracle database, I'm leery about clicking the power on button.

Does anyone know if this will just update VirtualCenter or will I get a reboot? Or will it be safer to migrate to another ESX host?

Any other ideas as to how to get VirtualCenter to recognize that the server is up?

Thanks.

Mike