<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Ynt: Agent Install in HPE Morpheus VM Essentials Software</title>
    <link>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/agent-install/m-p/7275242#M3232</link>
    <description>&lt;P&gt;One additional point.&amp;nbsp;&lt;/P&gt;
&lt;DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;I think there's an important distinction here. Requiring an Agent connection to the management plane and providing a path from one customer VM to the entire VM estate are not the same thing.&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;The documented design is an outbound HTTPS/WSS connection from the Morpheus Agent to the configured Appliance URL on TCP 443. The Agent does not open an inbound management port in the customer VM.&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;The connection is security-sensitive and HPE explicitly documents the Manager/Agent relationship as a “remote-shell-equivalent trust boundary,” which is why Manager access, Agent keys and role permissions need to be protected.&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;However, I don't see anything in the documentation supporting the statement that compromising one customer VM gives an attacker a simple jump through VM Essentials to every other VM. That would require an additional compromise of the management plane or its authorization/security controls.&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;You can also restrict the customer network so the only permitted management-plane connection is to the VM Essentials Appliance URL/VIP on TCP 443. The customer VMs do not need unrestricted access to the management network.&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;I do agree with the underlying question you're asking: whether all of the functionality currently provided by the Morpheus Agent could eventually be delivered without any IP connectivity from the guest to the Manager. I don't have confirmed roadmap information on that and if I did, I can't reveal it publicly.&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;P&gt;Sources here are the same as my previous reply.&amp;nbsp;&lt;/P&gt;
&lt;/DIV&gt;</description>
    <pubDate>Fri, 13 Nov 2026 16:06:05 GMT</pubDate>
    <dc:creator>CalvinZito</dc:creator>
    <dc:date>2026-11-13T16:06:05Z</dc:date>
    <item>
      <title>Agent Install</title>
      <link>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/agent-install/m-p/7274244#M3056</link>
      <description>&lt;P&gt;Is there an offline/air gapped installer for the VM Agent?&lt;/P&gt;&lt;P&gt;Currently in order to install the agent it either needs internet or a connection the management VM.&lt;/P&gt;&lt;P&gt;As we are going to run customer VMs we can't allow them a route to the management VM.&lt;/P&gt;&lt;P&gt;In vCenter it mounts an iso for the first install is this an option or in the pipeline?&lt;/P&gt;&lt;P&gt;Making all VMs need eithert internet or a route to the management VM is not a good idea at all.&lt;/P&gt;</description>
      <pubDate>Tue, 20 Oct 2026 16:10:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/agent-install/m-p/7274244#M3056</guid>
      <dc:creator>RBarlow92</dc:creator>
      <dc:date>2026-10-20T16:10:35Z</dc:date>
    </item>
    <item>
      <title>Ynt: Agent Install</title>
      <link>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/agent-install/m-p/7274285#M3059</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;An offline installer would help with the initial installation, but the Morpheus guest agent still needs to communicate with the Manager afterwards. HPE’s documentation specifies access to the configured Appliance URL over TCP 443, so installing it from an ISO would not remove that requirement. Internet access itself is not mandatory if the Manager is reachable.&lt;/P&gt;&lt;P&gt;If your customer VMs cannot have any access to the Manager, you can select Skip Agent Install during provisioning or disable Install Agent on the Virtual Image. You would lose the features provided by the agent, such as guest-level monitoring, log collection and task execution, although some utilization statistics are still available without it.&lt;/P&gt;&lt;P&gt;I haven’t found a documented ISO-based installer for the Morpheus guest agent or any public roadmap information confirming one is planned.&lt;/P&gt;&lt;P&gt;I understand your concern about keeping customer networks separate from the management network. For that setup, the requirement goes beyond an offline installer—the agent would also need a way to communicate without a network connection from the guest to the Manager.&lt;/P&gt;&lt;P&gt;&lt;A href="https://support.hpe.com/hpesc/public/docDisplay?docId=sd00008769en_us&amp;amp;page=GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.html" target="_blank"&gt;https://support.hpe.com/hpesc/public/docDisplay?docId=sd00008769en_us&amp;amp;page=GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://support.hpe.com/hpesc/public/docDisplay?docId=sd00008769en_us&amp;amp;page=GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.html" target="_blank"&gt;https://support.hpe.com/hpesc/public/docDisplay?docId=sd00008769en_us&amp;amp;page=GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 21 Oct 2026 10:57:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/agent-install/m-p/7274285#M3059</guid>
      <dc:creator>duru19</dc:creator>
      <dc:date>2026-10-21T10:57:59Z</dc:date>
    </item>
    <item>
      <title>Ynt: Agent Install</title>
      <link>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/agent-install/m-p/7274296#M3061</link>
      <description>&lt;P&gt;That is horrendous. VMWare talks to the agent to handle monitoring/VM tasks why can't HPE VME?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Giving routes to the manager VM from all VMs is a terrible security issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there nothing in the roadmap to make this work in the way VMWare does?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I can't be the only person who has raised this as a security issue as a simple jump from one customer vm over the VME vm then allows access to the entire VM estate.&lt;/P&gt;</description>
      <pubDate>Wed, 21 Oct 2026 11:25:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/agent-install/m-p/7274296#M3061</guid>
      <dc:creator>RBarlow92</dc:creator>
      <dc:date>2026-10-21T11:25:09Z</dc:date>
    </item>
    <item>
      <title>Ynt: Agent Install</title>
      <link>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/agent-install/m-p/7274305#M3062</link>
      <description>&lt;P&gt;I understand your point. Keeping customer networks isolated from the management plane is a reasonable requirement, and skipping the agent does not give you the equivalent functionality you are asking for.&lt;/P&gt;&lt;P&gt;One distinction I should have made clearer in my earlier reply is that the Morpheus agent and the QEMU Guest Agent are separate components. QEMU already supports guest-to-host communication through virtio-serial, without requiring an IP route from the guest to the Manager. HPE also documents its use for certain snapshot consistency operations. So this is not an inherent limitation of KVM.&lt;/P&gt;&lt;P&gt;The Morpheus agent, however, currently has a documented requirement to reach the Appliance URL over TCP 443. That explains the current behaviour, but it does not resolve your isolation concern.&lt;/P&gt;&lt;P&gt;Being able to reach that service does not, by itself, grant access to the rest of the VM estate; that would require an additional compromise or authorization failure. Nevertheless, exposing a central management service to customer workloads is a valid concern.&lt;/P&gt;&lt;P&gt;I don’t have any confirmed roadmap information for moving these functions to a host-mediated channel. This needs an answer from HPE’s product team: whether they plan to support the required monitoring and guest operations without customer VMs needing network access to the Manager.&lt;/P&gt;</description>
      <pubDate>Wed, 21 Oct 2026 12:01:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/agent-install/m-p/7274305#M3062</guid>
      <dc:creator>duru19</dc:creator>
      <dc:date>2026-10-21T12:01:58Z</dc:date>
    </item>
    <item>
      <title>Ynt: Agent Install</title>
      <link>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/agent-install/m-p/7275241#M3231</link>
      <description>&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;From my v9.1.0 Copilot Notebook: &lt;BR /&gt;I understand the concern, but I want to clarify the network requirement because the VM does not need unrestricted access to the HPE VM Essentials management network.&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;The HPE Morpheus Software Agent does not listen for inbound management connections in the guest. The Agent initiates an outbound HTTPS/WebSocket connection to the configured Appliance URL on TCP 443. That connection is then used for Agent telemetry and authorized management operations.&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;In a segmented environment, the firewall policy can therefore be limited to:&lt;/DIV&gt;
&lt;UL&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;&lt;STRONG&gt;Source:&lt;/STRONG&gt; Customer workload network&lt;/LI&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;&lt;STRONG&gt;Destination:&lt;/STRONG&gt; The specific VM Essentials Appliance URL or load-balancer VIP&lt;/LI&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;&lt;STRONG&gt;Port:&lt;/STRONG&gt; TCP 443&lt;/LI&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;&lt;STRONG&gt;Direction:&lt;/STRONG&gt; Outbound from the workload network&lt;/LI&gt;
&lt;/UL&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;That does not require a general route from customer VMs to the complete management network or to the other VMs being managed. The destination can be restricted to a single published endpoint on TCP 443.&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;VM Essentials also supports configuring an alternate Appliance URL for each Cloud. That allows workloads in a particular Cloud or network segment to use a separately published endpoint rather than the primary management address.&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;An offline installer would help get the Agent package onto the VM without Internet access, but it would not remove the Agent’s ongoing communication requirement. Once running, the Agent still needs to reach the configured Appliance URL on TCP 443. Internet access is not required if the VM can reach that internal endpoint.&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;The QEMU Guest Agent is a separate component. It provides certain host-to-guest functions without a normal IP connection, but it is not a replacement for all HPE Morpheus Software Agent capabilities. Without the Morpheus Agent, some statistics may still be available through the hypervisor, but guest-level monitoring, log aggregation, the Agent command bus, and some automation capabilities will be unavailable or reduced.&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;P&gt;If the requirement is that customer VMs cannot initiate even a tightly restricted TCP 443 connection to a dedicated VM Essentials endpoint, then the current documented option is to operate those VMs without the Morpheus Agent. I do not have confirmed roadmap information for moving all Morpheus Agent functions to a host-mediated channel.&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Sources:&amp;nbsp;&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;A href="https://docs.morpheusdata.com/en/9.1/getting_started/requirements/requirements.html#network-connectivity" target="_blank" rel="noopener"&gt;&lt;SPAN&gt;Getting Started &amp;gt; Requirements &amp;gt; Network Connectivity&lt;/SPAN&gt;&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;
&lt;DIV&gt;&lt;A href="https://docs.morpheusdata.com/en/9.1/getting_started/functionality/agent/overview.html" target="_blank" rel="noopener"&gt;Getting Started &amp;gt; Core Functionality &amp;gt; Morpheus Agent &amp;gt; Overview&lt;/A&gt;&lt;/DIV&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;DIV&gt;&lt;A href="https://docs.morpheusdata.com/en/9.1/getting_started/functionality/agent/agentInstallation.html" target="_blank" rel="noopener"&gt;Getting Started &amp;gt; Core Functionality &amp;gt; Morpheus Agent &amp;gt; Agent Installation&lt;/A&gt;&lt;/DIV&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;DIV&gt;&lt;A href="https://docs.morpheusdata.com/en/9.1/getting_started/functionality/agent/features.html" target="_blank" rel="noopener"&gt;Getting Started &amp;gt; Core Functionality &amp;gt; Morpheus Agent &amp;gt; HPE Morpheus Software Agent Key Features&lt;/A&gt;&lt;/DIV&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;DIV&gt;&lt;A href="https://docs.morpheusdata.com/en/9.1/administration/settings/settings.html#appliance-settings" target="_blank" rel="noopener"&gt;Administration &amp;gt; Settings &amp;gt; Appliance URL&lt;/A&gt;&lt;/DIV&gt;
&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Fri, 13 Nov 2026 16:00:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/agent-install/m-p/7275241#M3231</guid>
      <dc:creator>CalvinZito</dc:creator>
      <dc:date>2026-11-13T16:00:49Z</dc:date>
    </item>
    <item>
      <title>Ynt: Agent Install</title>
      <link>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/agent-install/m-p/7275242#M3232</link>
      <description>&lt;P&gt;One additional point.&amp;nbsp;&lt;/P&gt;
&lt;DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;I think there's an important distinction here. Requiring an Agent connection to the management plane and providing a path from one customer VM to the entire VM estate are not the same thing.&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;The documented design is an outbound HTTPS/WSS connection from the Morpheus Agent to the configured Appliance URL on TCP 443. The Agent does not open an inbound management port in the customer VM.&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;The connection is security-sensitive and HPE explicitly documents the Manager/Agent relationship as a “remote-shell-equivalent trust boundary,” which is why Manager access, Agent keys and role permissions need to be protected.&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;However, I don't see anything in the documentation supporting the statement that compromising one customer VM gives an attacker a simple jump through VM Essentials to every other VM. That would require an additional compromise of the management plane or its authorization/security controls.&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;You can also restrict the customer network so the only permitted management-plane connection is to the VM Essentials Appliance URL/VIP on TCP 443. The customer VMs do not need unrestricted access to the management network.&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;I do agree with the underlying question you're asking: whether all of the functionality currently provided by the Morpheus Agent could eventually be delivered without any IP connectivity from the guest to the Manager. I don't have confirmed roadmap information on that and if I did, I can't reveal it publicly.&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;P&gt;Sources here are the same as my previous reply.&amp;nbsp;&lt;/P&gt;
&lt;/DIV&gt;</description>
      <pubDate>Fri, 13 Nov 2026 16:06:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/agent-install/m-p/7275242#M3232</guid>
      <dc:creator>CalvinZito</dc:creator>
      <dc:date>2026-11-13T16:06:05Z</dc:date>
    </item>
  </channel>
</rss>

