1. A route must exist to vCenter and the ESX host.
   Commander does not act as a proxy server for console connections. A valid route between the originating system and both the vCenter and ESX host is required.
   • If no route exists, for example because the Service Portal is accessed through an Internet-facing firewall, deploy the Console Proxy appliance to provide a route.
     
     
2. A supported web browser must be used.
   Refer to VMware documentation for your version of vCenter to confirm browser compatibility.
   
   
3. The vCenter Client Integration Plug-in must be successfully installed.
   Commander cannot distribute this plug-in because VMware does not allow redistribution. If the plug-in is not installed, users will see only a black screen with a message indicating that the plug-in is missing or not properly installed.
   • A user with appropriate permissions must log in directly to vCenter and install the plug-in manually. Refer to VMware documentation for instructions.
     
     
4. Browser-specific settings must be configured.
   Depending on the browser and security policies, you may need to configure the following:
   • Enable compatibility view
   • Add Commander to Trusted Sites
   • Disable protected mode in Internet Explorer
     
     
5. Verify supported vCenter connection methods.
   For vCenter 5.5, two connection methods are supported:
   • WebMKS:
     • Supported only with HTML5 web browsers
     • No plug-in required
     • Requires vCenter 5.5 Update 2 or later
     • Secure WebSockets (wss://) must be enabled on the managed system, with port 7343 open
     • vCenter must use a valid SSL certificate
   • VMRC Plug-in:
     • Users must install the VMware Remote Console plug-in manually

Outcome

When all requirements are met, users can successfully initiate and establish VMware console connections through Commander or the Service Portal.