The vCommander VM Access Proxy allows you to secure your virtualized infrastructure behind a firewall while still permitting your users console, RDP, VNC and SSH access to their VMs. When you configure the vCommander VM Access Proxy, your users may access their VMs within a browser, without the need for a network connection to the managed system. The VM Access Proxy enables:

  • Secure RDP and secure VNC access for Windows VMs on all supported managed system types
  • Secure SSH and secure VNC access for Linux VMs on all supported managed system types
  • Secure console access for VMs on both vCenter 5.x and SCVMM (Secure console access is not available for vCenter 4.x managed systems.)

The vCommander VM Access Proxy is deployed as an appliance using vCenter or SCVMM 2012 R2.

vCenter


Follow the procedure below to deploy the appliance using vCenter.

  1. Download the vCommander VM Access Proxy package from the Embotics website.
  2. Extract the archive.
  3. In vCenter, deploy the OVF template: Go to FileDeploy OVF Template and complete the wizard.
  4. Start the deployed VM.

SCVMM 2012 R2


Follow the procedure below to deploy the appliance using SCVMM 2012 R2.

  1. Download the vCommander VM Access Proxy package from the Embotics website.
  2. Extract the archive.
  3. Manually copy the vCommander_VMAccess_Proxy_disk_1.vhd file into the VHDs directory of the Library Server.
  4. In the SCVMM console, go to the Library view.
  5. Refresh the Library Server and make sure that the Console Proxy drive appears in the list.​
  6. On the Home tab of the Virtual Machine Manager, click Import Template.
  7. On the Select Package page of the wizard, in the Package pathy field, browse to the Console Proxy.xmlfile you extracted from the archive.
  8. On the Configure References page, under Library Resources, click the pencil icon.
  9. Select vCommander_VMAccess_Proxy_disk_1.vhd in the list and click OK.
  10. Confirm you want to overwrite the template.
  11. Click Import to complete the wizard.
  12. Once the template has been imported, in the VMM console, select the Console Proxy template and clickCreate Virtual Machine. Complete the Create Virtual Machine wizard.
  13. Once deployed, start the Console Proxy virtual machine.
  14. You must now obtain the IP address for the new virtual machine, which will be required during configuration in vCommander. To do so, login to the Proxy Console using the credentials:username – vcommander
    password – gRHrB211
  15. Issue the command ifconfig to retrieve the IP address.