Feature request - Update of the Veeam Console download via the VSA/VBR login page

[petesteven]

When downloading the Windows Console for Veeam V13 via the VSA/VBR on the login page, the console downloaded is not the current version for the installed VSA/VBR, it is an older version.
This means that the console must first be updated when logging in for the first time after installation.
Feature request: provide the current versions for download via the VSA/VBR on the login page.




PS: Unfortunately, I don't have a screenshot of the updater because I clicked too quickly. But hopefully the other one will suffice.

[chris.childerhose]

Agreed here when a patch is applied the download for the console should be repackaged to provide the latest one rather than GA and then update on connection. +1

[Chalid]

Definitely a +1.

[Dynamic]

+1 from me as well.
A lot of our customers are frustrated that they can't direct download an up2date client.

[fractalenergy]

+1 also

[matteu]

+1

[fabbar]

+1

also: even if all functionalities will be moved on the web ui and console no more updated, it would be very very useful to have different console versions in the same desktop. consider we have many vbr servers and of course we cannot patch/upgrade all at the same time (many times upgrade was deferred since a support case was opened in one of these VBRs), and we need different consoles. even more so, if we would have all VSAs we would need also many desktops with different console versions, would not?

[villapla]

+1

[simo77]

+1

[Didi7]

+1

[HannesK]

Hello,
while the request is understandable and valid, the more likely solution will be that we enhance the Web UI so that the Windows console won't be needed anymore.

Best regards
Hannes

[chris.childerhose]

Agree that the Web UI will be the solution but until parity the console installer should update for download. Just my thoughts.

[petesteven]

Hello Hannes,

I understand the approach with the web UI. However, it is still far from feature-complete
I hope this changes soon; until then, it would be great if the customization feature were available. The response here shows that there are many people who are currently struggling with this.

[tibo.gabriels]

+1

[DHuppertz]

+1

[virtualcio]

+1

[F.A.N.]

+1

[sdolcourt]

Hello,
while the request is understandable and valid, the more likely solution will be that we enhance the Web UI so that the Windows console won't be needed anymore.

Best regards
Hannes

Hello, Hannes,

My two cents: HTML5 web services are "the norm" in the IT industry, yes. However, the console application continues to navigate faster that HTML. Whether vCenter, or our previous solution Actifio's AGM, waiting for web services to present a next page because of a single mouse click's action is the unsaid negative of HTML interfaces. Oops, didn't want that, click back, wait for the web server to send code and the browser to page to paint...a full size application suffers less of that problem.

We are deploying VBR at multiple sites within our company, each site has a range of user abilities, shall we say. The console's navigation speed, graphical presentation and wizard driven applets makes training site personnel much easier.

I am more perplexed why Veeam has failed (strong words) to develop a VeeamCenter, a management interface that can federate disparate sites under a single large domain, and delegate responsibility using RBAC properties - kind of like....vCenter.... Enterprise Manager does not equal a VeeamCenter; EM's biggest fault for claiming federation capabilities is the inablilty to create backup jobs.

Strongly recommend that Veeam continues the support and development of the fat console. There is value in the endeavor, despite the difficulty of managing the console with VBR.

[Dima P.]

Hello folks,

We’re currently investigating how we can address the reported behavior. Thank you for sharing your posts and insights!

[DaStivi]

There’s actually one more catch here:
If you start the VBR console without administrative permissions (UAC), it still shows the notification about the pending console update. When you proceed, the process elevates, but something goes wrong during installation — the update doesn’t install correctly in the background, and the upgrade process simply stalls.
I wasn’t able to find any workaround to make the console update succeed in this scenario. You have to log in to Windows using an admin account and run the console from that account to apply the update. After the update is completed, you can again run the console as a normal (non‑elevated) user without issues.