Question 3 What could be the issue.

If he enabled MFA there is an issue adding servers to VEM and it is required to be disabled to add then enabled after connection to VEM.  😁

or, the VBR version is newer/higher than the VEM server version.

Ah yes forgot about the obvious one.  Good call there. 👍🏼

The pitfall of being an expert, forgetting the obvious 🤣

Hint.. database

@MicoolPaul 

We may need your genius here :) 

Ah yes SQL cannot support Postgres and vice versa so the new one is PG and the VEM is SQL.

Hi everyone!

So the conversation point that this question focuses on is that VBEM can only manage VBR’s that utilise the same database type as itself. So if your VBEM & existing VBR fleet was SQL Server and then you went to adopt a new VBR server with Postgres, you won’t be able to manage it in VBEM.

Also, a key thing to call out here is that, whilst you have the ability to migrate your VBR server between SQL Server and Postgres, with VBEM this is a one way street! You can migrate to Postgres but you can’t migrate back afterwards! So if you start deploying VBR with Postgres you can migrate the VBR over to SQL Server if you’ve got a VBEM with SQL Server, but if your VBEM is using Postgres, all your VBRs will need Postgres, or you’ll need to deploy a new VBEM with SQL Server.