PowerShell commandlets don't work after new U4a install

[mclordhelmet]

After installing 9.5 U4a as a new install from the ISO media, Powershell commandlets will error as described in KB2325 (https://www.veeam.com/kb2325) until the console is opened and connected to for the first time. Our Veeam deployments are scripted and as such a manual console opening and connecting is not desired. We determined that the change being made just after the console is opened/connected is that the file Veeam.Backup.DBCreator.dll located in "<INSTALL_DIR>\Veeam\Backup and Replication\Console" is replaced by the Veeam.Backup.DBCreator.dll located in "<INSTALL_DIR>\Veeam\Backup and Replication\Backup". A simple scripted copy of this file from the BACKUP to CONSOLE directory will allow the Powershell commandlets to work properly without any need to open/connect the console manually. Just wanted to pass this info along for anyone out there who is attempting a fully automated deployment of their B&R server.

[wishr]

Hi Matthew,

Thanks for sharing the workaround with the Veeamazing community! It's appreciated!

Regards,
Fedor

[mclordhelmet]

UPDATE!!!! I discovered that our script was not actually installing the U4a "update" portion of the U4a media. When using the command-line silent install with the U4a media, it only installs U4. U4a has to be done separately. This is why we were getting the out of date error in PowerShell. The workaround I posted is valid, but should NOT be necessary if you ensure the update (U4a) is installed just after U4 before any Veeam specific PowerShell commandlets are attempted.

[wishr]

Hi Matthew,

Once again, thanks for sharing this valuable information!