new VRO 7.2 Deployment - two notes...

[Dynamic]

Hi there,
we are currently deploying a new 7.2 VRO Environment. In this case with a the embedded SQL Database.

Just two notes or FRs:



let's get rid of the old Name VAO (Veeam Availability Orchestrator) and change it in the next version to VRO

And, if the Customer select Browse... in the same Window Database Names UI, the whole Setup Process fails (can't connect to an existing DB, for sure...) and exits the whole process, so you have to start from scratch. Is this a known issue? It's not an urgent topic, but just to inform you

Best, Markus

[Vitaliy S.]

Hi Markus,

Makes sense to switch to VRO naming convention, at least for clean installations. I will pass this and the other info to the QA team.

Thanks!