Issues installing the VBR console on a client with Veeam Agent for Microsoft Windows already installed

[iDeNt_5]

Hi all,

I open a thread here, because I think my issue is something that it could be discussed between a support case (that I already opened - Case #08249837) and a technical thread on the R&D forum, due to the fact I assume there is a SW compatibility mismatch that it could be reported in the Veeam doc.

I post the case opening text below:
I'm wondering why during the setup of the VBR console on a client with Veeam Agent for Microsoft Windows v13 already installed I receive an error message saying the Veeam Backup Transport is already installed.

According to the Veeam documentation (https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13), the only requirement in this scenario is that the client involed has not to be part of the Veeam Backup Infrastructure Servers, that is not in our case.

So what is the solution? Have I to manually uninstall the Transport Service and then let the Veeam Console reinstalling it automatically?

Thanks.

P.S. The client is a W10 x64 22H2

[vnikiforov]

Hello, Matteo,

Veeam Agent doesn't install Veeam Backup Transport. A standalone agent is a single service plus the tray. Veeam Backup & Replication deploys the transport on client. When a computer is added to a protection group, the rescan job installs Veeam Installer Service, which then installs Veeam Transport Service, and the job upgrades it whenever the backup server updartes.

The console setup installs and requires the same transport component.The last bullet in Before You Begin covers this case. That page says: "for example", as one of the examples, protections groups also included.

Do not remove the transport manually. Setup would then replace the build that agent management deployed with its own, which creates the version mismatch.
Please use a dedicated computer for the console.

Also a note: Windows 10 22H2 isn't on the current v13 console supported OS list, which includes only Windows 10 LTSC 2021 and Windows 11 23H2 to 25H2.

[iDeNt_5]

Hi Vladimir,

OK, understood, except for the part "That page says: "for example", as one of the examples, protections groups also included.".

The example you referred is linked to the statement "We do not recommend installing the Veeam Backup & Replication console on the machine that is used in the role of a different backup infrastructure component", that is a different thing between a client that belong to a PG (that is not a Veeam Infrastructure component), so I would still recommend adding this case to the documentation, just for the sake of clarity.

Thanks for the explanation.

[vnikiforov]

Hello, Matteo,

Yep, agree that needs to be changed I made a request for documentation team.