Upgrade Commander VM Access Proxy

If you currently use a 3.0 to 3.4 VM Access Proxy, it's recommended that you upgrade it to version 3.7, which offers important Apache Tomcat and Log4j security updates.

In cases where it's vital to minimize downtime, Snow Software recommends that you deploy a new VM Access Proxy alongside your current production proxy, rather than upgrading it by replacing it. Commander fully supports the use of multiple VM Access Proxies running different versions. Therefore, you can confirm the new VM Access Proxy functions as expected before you decommission the original proxy and risk unexpected downtime.

Version 3.7 also offers the following improvements over versions 3.0 to 3.4:

  • A container-based installation process, which is simpler and will provide easier upgrades in the future.
  • Improved copy and paste functionality in Secure RDP, Secure SSH, and Secure VNC connections.
  • Security enhancements.

To download the latest version of the VM Access Proxy, go to the Downloads page.

Version compatibility

The following table lists the recommended version of the VM Access Proxy to use with your installation of Commander.

VM Access Proxy version

Commander version

3.7

8.4.x to 9.0.0.

3.4

8.4.x to 8.9.x

It's highly recommended that you upgrade to version 3.7 because it includes Apache Tomcat and Log4j critical security updates.

3.0 to 3.3

7.1.x, 7.5.x, 8.1.x, 8.2.x, 8.3.x

  • It's highly recommended that you upgrade to version 3.7 because it includes Apache Tomcat and Log4j critical security updates.
  • VM Access Proxy versions 3.0 to 3.3 are deprecated and will be removed in a future release.

Update VM Access Proxy 3.4 and above

  1. In the directory where the docker-compose.yml file is located, shut down and remove the VM Access Proxy containers with the docker-compose command:

    docker-compose down

  2. Back up the docker-compose.yml file.
  3. Log in to Snow Commander Support Downloads, download the SnowAccessProxy-<version>.zip file, and extract.
  4. Replace the docker-compose.yml file using the newer one extracted from the SnowAccessProxy-<version>.zip file.
  5. Update and start the containers with the docker-compose command:

    docker-compose up -d

Redeploy an upgraded VM Access Proxy

To upgrade the VM Access Proxy from version 3.3 or lower, perform the following steps:

  1. If you want to access the old VM Access Proxy to copy the 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.

    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.

    For VM Access Proxy 3.3 and lower, the configuration folder is /var/lib/tomcat/conf; for VM Access Proxy 3.4, 3.6 and 3.7, 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.