VirtualCenter Server Service Fails

[sgunelius]

I've already opened a support request with VMware on this, but after being on hold for an hour and a half, I thought I'd pose this one to the community. I'm running vCenter and HP Insight Manager/RDP on the same server. It appears that our upgrade of Insight Manager and the addition of RDP to support our new c7000 blade chassis "broke" vCenter. It sounds like the HP and VMware products may be competing for the same port and now the VirtualCenter Server service fails to start. As I needed to upgrade from VC 2.0 to 2.5, I performed an in-place upgrade which went well, but again the service won't start.

Is there some specific configuration that has be done to allow these products to coexist on the same server? Thank you very much.

[sgunelius]

It appears that HP's RDP may take sole ownership of port 8443 when those services start and when the vCenter service starts, it fails with this port being unavailable. It looks like HP has a documented solution for this (see below), so I'll report back my findings afterwards.

Scott

[sgunelius]

I had no luck trying to reconfigure RDP to play nicely with vCenter, but did narrow down the culprit service and set it to manual. I'll have to research further how to reconfigure "Altiris Deployment Server Data Manager" to accommodate vCenter. Does anyone else have any suggestions? Thank you.

Scott