1. Ensure the Service Portal on the Commander application server is published through the firewall on TCP port 443.
2. When a user requests a secure VM connection through the Service Portal:
   • Commander sends the user’s browser a token identifying the request and the VM Access Proxy URL configured in Commander.
3. The user’s browser creates a session to the VM Access Proxy, published through the firewall on TCP ports 443 and 8443.
   
4. The VM Access Proxy then contacts Commander on TCP port 443 with the token and requests session details. Commander responds with the VM’s address and the protocol to use.
5. Based on the protocol, the following occurs:
   • RDP: The VM Access Proxy establishes the session to the cloud account and creates an in-browser RDP session over TCP port 8443 between the VM Access Proxy and the browser.
   • SSH: The VM Access Proxy establishes the session to the guest operating system and creates an in-browser SSH session over TCP port 8443 between the VM Access Proxy and the browser.
   • VNC: The VM Access Proxy establishes the session to the cloud account and creates an in-browser VNC session over TCP port 8443 between the VM Access Proxy and the browser.
   • VMware console: The VM Access Proxy proxies the session between the cloud account (vCenter server) and the browser over TCP port 443.
   • SCVMM console: The VM Access Proxy proxies the session between the cloud account (Hyper-V server) and the browser over TCP port 8443.
6. Confirm the required network routes:
   • For all connection scenarios, routes must exist between Commander and the VM Access Proxy.
   • For vCenter and SCVMM, routes must exist between Commander, the VM Access Proxy, and the host (Hyper-V or ESXi).
   • For RDP, SSH, and VNC, routes must exist between Commander, the VM Access Proxy, and the target VM.
7. Configure DNS properly if users access VMs both inside and outside the cloud network:
   • Internal DNS responses should return private addresses for internal requests.
   • External DNS responses should return public addresses for external requests.

Outcome

Following these steps ensures secure, browser-based connectivity for VMs through Commander VM Access Proxy, supporting multiple protocols with appropriate firewall and DNS configurations.