Guide to automate Veeam Agent for Windows

Here’s a guide to automate the installation of your Veeam Agents for Windows (VAW) with PowerShell and Batch scripts. Basically, I used Clint’s guide to automate the deployment of Veeam Agent for Windows. But I did some modifications for an end-user environment because the license and configuration files did not work with his PS script. The issue is you need to use those credentials would be in the Config.XML file so only an Administrator account would need to be used to install via the script. Depend on your context, end-user would use other credentials to run the script. You can follow this guide to automate Veeam Agent for Windows below…

First, backup from HPE 3PAR to local site repository (ReFS) using Direct SAN and Storage Snapshots integration (headquarters),

Then, at the end of the backup window, starting a Backup Copy job from primary site copying the freshly done backup to a NAS at the DRP site,

Branch offices are backing up on-premise to a CIFS repository with Veeam Agent for Windows,

VAW’s destination is Veeam B&R server located at the headquarters (DC1/DC2), it allows to monitor agents from Veeam Backup console and create Backup Copy Jobs. So, realizing offsite backup of branch offices to DRP site. We are able to use WAN Accelerator.

Goal: Simplify the deployment of VAW on physical sites (ROBO).

Realizing VAW template (“Config.xml”):

First, you have to realize a Veeam Agent for Windows template by utilizing the new configuration CLI / API tool that’s now available.
You can follow this step by step guide to installVeeam Agent for Windows.

Then, from an elevated command prompt CD to and run (you can follow Clint’s guide):

It exports your exact VAW configuration including all job settings. The file is located here: C$:\ProgramData\Veeam\Endpoint\!Configuration .
You can easily update or change it as necessary the file without having to export the configuration again (SMTP notifications, from:, to: etc.).

PowerShell file structure configuration:

First, you can head to the VeeamHUB @GitHub to grab a copy of the sample script that Clint is providing. Then, follow Clint’s guide to set up PowerShell file structure (license directory, Config.XML directory, VAW .exe directory etc.).

Veeam Agent for Windows deployment – Running the PowerShell script:

You have to connect to the target server on which VAW needs to be deployed, then open a PowerShell terminal.

Steps 2 and 3 don’t work (the issue is you need to use those credentials would be in the Config.XML file so only an Administrator account would need to be used to install via the script.). So, during Veeam Agent for Windows is installing, you have to select “NO” when the wizard requests to import the license.

Check « Preconfigured by system administrator » setting is implemented:

From the main interface, click on “Configure backup”:

Once setup wizard is open, click on “Backup Server” tab and enable the “Specify your personal credentials:” option. Then, enter the service account and the corresponding password.

Hope this guide will help you! Veeam Agents (Windows and Linux) are powerful. They can allow you to backup your physical workloads and workstations. Next Veeam Backup and Replication v10 release will allow to manage and monitor your Veeam Backup and Replication environment and the whole of your workstations and standalone servers from only one interface!