FEATURE REQUEST: Allow multiple remote console versions on Cloud Connect

[TT_rick]

Hi all,

We have one (1) server running Veeam B&R Cloud Connect, and have recently upgraded on this server from version 12.1 to 12.2. We currently have 38 tenants, and are regularly adding more tenants.

To manage Veeam B&R for the tenants, from our Veeam B&R Cloud Connect console, we go to Cloud Connect view > Tenants, Right Click the tenant > Remote console, and select the Tenant's Veeam server. If the version of Veeam B&R on the customer’s server is the same as our Veeam B&R Cloud Connect server, then the remote console opens. If they are running a different version, then the connection fails with error message:
Tenant's backup server and this console's versions do not match. Please install the same console version or connect using Remote Desktop.

The long term solution is obviously to remote on to each of the tenants server running B&R, and update Veeam B&R. However this is a long labourious process, especially as the upgrade requires a reboot of the server to install the new VC_redist, and these are production servers. A number of these sites are also on the wrong end of slow satellite internet connections, so even downloading the 11.5GB Veeam B&R 12.2 ISO can take several hours for these sites. It will take several months to update Veeam B&R for each of the tenants currently running version 12.1


My Feature Request is that multiple versions of the Veeam B&R remote console can be installed on a single server running Veeam B&R CloudConnect, and when going through the process listed above to open the remote console and connect to the Tenant server, the version of Veeam B&R on the tenant server is detected, and the appropriate version of the Veeam B&R Remote Console is opened.


Case #07407025 — Feature Request: allow multiple versions of Remote Console on CloudConnect server

Thank you
Rick

[Gostev]

Hi, Rick. This request was previously discussed in great details already, please search the forum for the existing discussion if you're interested in details. I only want to highlight that I would not recommend taking several months to update 12.1 tenants because bad actors will start exploiting vulnerabilities fixed in 12.2 any day now (first research articles have already been published). Thanks

[rafael.bartz]

I have same problem.

https://ibb.co/QnqKx0s

Version is same!!! https://ibb.co/2Yb8kP2

I didn't find anything related to this error on the forum, only this POST, referring to this error.