Guest OS Agent install like VMware Tools?

[mixdrop]

Hello.

I'm using HVM Essentials v8.0.6.

Is there a way to install the guest OS agent separately (other than downloading it from the GUI or HVM-Manager) like VMware Tools?

Thank you in advance.

[ncelebic]

Installing the agent is simple and you can find the script for installation in the record of the compute resource in Actions -> Download Agent Script.  That script inserts the API key of the computer resource into the agent configuration on the target.  Each compute resource has it's own key, unlike VMWare Tools.  You can script it outside of Morpheus/HVM Manager but it is more to manage.

[mixdrop]

Thank you for your reply.

The reason I asked this question is that whether I download a script or push-install from the GUI, the virtual machine needs to have the HVM-Manager segment IP, which means the virtual machine needs to have an extra network.

Having an HVM-Manager segment just for agent installation is inefficient, and it also makes NIC adapter management difficult.

So I was wondering if it would be possible to install the agent separately as a file (like VMware tools).

Thank you.

[mixdrop]

I looked at it again and now I understand.
The api key links the manager to the guest OS.

I haven't tried it, but would adding a virtual machine network to HVM-Manager enable push installation?

[ncelebic]

If the HVM Manager creates the VM, the agent will be installed via cloud-init or unattend script, unless disabled.  That's the primary installation method.

Adding the agent later, if needed, will require the RPC User/Pass to be setup in the compute record in HVM Manager and for that resource to be reachable.  You don't have to have it on the same network, just able to reach the resource.

[Arnout_Verbeken]

If your VM's are on a separate compute network and the VME Manager is on another network, and there is no route between both networks,  you can define a proxy in "Network - Proxies" and add that proxy in your VLAN config ("Network - Networks - Edit the Compute VLAN and add the proxy").

If you want to install the VME Agent, there needs to be communication between the VM's network and the VME Manager's Network, either routed or via proxy.

[Arnout_Verbeken · Accepted solution]

And here is an interesting table with some communication flows.
https://support.hpe.com/hpesc/public/docDisplay?docId=sd00006453en_us&page=GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.html#ariaid-title6

While this info is linked to Morpheus Enterprise, it is also applicable for Morpheus VM Essentials.

So if Cloud(base) init is not enabled, you need port 5985/5986 open to install the agents in the VM (also be aware of Windows Firewall blocking) and you need port 443 open for the communication between agent and appliance afterwards.
If you have Cloud(base) init, I think port 443 is enough since the agent install will be "pulled in" the VM (initiator) instead of "pushed in" in the VM (target).