Upgrade and Redeploy the Commander VM Access Proxy

If you're upgrading to Commander Release 8.6.1, and you currently use a Commander VM Access Proxy, it's recommended that you also upgrade to Commander VM Access Proxy Version 3.4.

Although you may be able to use your existing Commander VM Access Proxy, Version 3.4 offers the following improvements:

  • A container-based installation process, which is simpler and will provide easier upgrades in the future.
  • Security enhancements.
  • Improved copy/paste functionality in Secure RDP, Secure SSH, and Secure VNC connections.
  • The ability to install the VM Access Proxy on a machine with a Linux distribution of your choice that complies with your company's best practices and security requirements.

To download the VM Access Proxy version 3.4 package, go to the Downloads page.

Version compatibility

Version 3.4 of the VM Access Proxy is recommended for use with Commander 8.4.x or higher.

Versions 3.0-3.3 of the VM Access Proxy are compatible with Commander versions 8.3.x, 8.2.x, 8.1.x, 7.5.x, 7.1.x, 7.0.x.

Note: Although versions 3.0-3.3 of the VM Access Proxy are also compatible with Commander 8.4.x and 8.5.x, for new installations, it's recommended that you use VM Access Proxy 3.4. VM Access Proxy 3.0-3.3 is deprecated and will be removed in a future release.

Redeploy an Upgraded Commander VM Access Proxy

To deploy a version 3.4 VM Access Proxy that will replace an existing version 3.3 or lower VM Access Proxy, perform the following steps:

  1. If you want to be able to access the old VM Access Proxy to copy configuration or roll back the upgrade, keep the old server running.
  2. Disable or disconnect the network card on the old VM Access Proxy server.
  3. Deploy the new version of the VM Access Proxy alongside your old version. For details, see Deploy VM Access Proxies.

    Tip: Use the same IP address and DNS/FQDN name for the version 3.3 or lower VM Access Proxy server.

  4. Apply the SSL and customized configurations that you applied to the old server to the new server.

    Note: On 3.3 and lower VM Access Proxies, the configuration folder is /var/lib/tomcat/conf; on 3.4 VM Access Proxies, the configuration folder is /var/data/conf.

  5. Restart the new VM Access Proxy server with the following command:

    sudo docker-compose restart

  6. In Commander, configure the VM Access Proxy to point to the FQDN of the new VM Access Proxy server. See Add VM Access Proxies to Commander.
  7. Make sure you can open a secure console session through the VM Access Proxy.
  8. Power off the old VM Access Proxy server until you're ready to decommission it.