Upgrade Commander VM Access Proxy
If you upgrade to Commander 8.9.0 and currently use the VM Access Proxy, it's recommended that you also upgrade the VM Access Proxy to version 3.4.
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 and 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 3.4 package, go to the Downloads page.
The following table lists the recommended version of the VM Access Proxy to use with your installation of Commander.
VM Access Proxy version
8.4.x, 8.5.x, 8.6.x, 8.7.x, 8.8.x, 8.9.x
3.0 to 3.3
7.1.x, 7.5.x, 8.1.x, 8.2.x, 8.3.x
Note: VM Access Proxy versions 3.0 to 3.3 are deprecated and will be removed in a future release.
To deploy version 3.4 of the VM Access Proxy that will replace an existing version 3.3 or lower, perform the following steps:
- If you want to access the old VM Access Proxy to copy the configuration or roll back the upgrade, keep the old server running.
- Disable or disconnect the network card on the old VM Access Proxy server.
- 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.
- Apply the SSL and customized configurations that you applied to the old server to the new server.
Note: On VM Access Proxy 3.3 and lower, the configuration folder is
/var/lib/tomcat/conf; on VM Access Proxy 3.4, the configuration folder is
- Restart the new VM Access Proxy server with the following command:
sudo docker-compose restart
- 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.
- Make sure you can open a secure console session through the VM Access Proxy.
- Power off the old VM Access Proxy server until you're ready to decommission it.