Deploying v10 Backup Agents though VAC

[Sross]

Hey guys,

We've pulled the trigger and upgraded CloudConnect to v10, and VAC to the latest RTM patch (3.0.0.2795). Now I am at the stage where I am trying to test deploy the v10 agents and I am apparently missing something. I tried triggering the "update agent" function but it keeps returning "already up to date" for both the communications agent and the backup agent so I presume that there is another step. I also tried using the patch function to update a single agent, but it returned a "Failed to load patch manifest data from the file" error. I've rebooted the VAC server and still everything is claiming to be "up to date"

Current version is 3.0.2.1170 for backup communication agents clients. I'll keep you all posted if there is any breakthroughs. I feel like I am supposed to add the 4.0.0.1811 agent installer somewhere in the VAC server for it to deploy or something like that.

[dalbertson]

Have you opened a case on this yet? Can you provide the case number?

[Mildur]

He‘s trying to update the agents with vac 3.0 to agent 4.0.
This is not possible at the moment.
Already told him that on reddit

He will need VAC 4.0 for his plan.

Similar question is discussed in the VCSP forums:
veeam-availability-console-f42/veeam-ag ... 64943.html

[dalbertson]

Good catch. Reading comprehension is not my friend today.