Questions on Veeam Agent installation automation

[StevenMeier]

Hi All,

So finally have had time to create some powershell Automation for veeam agent installation and then import jobs via the xml file etc.

So created the Agent installer stuff powershell script and works fine....but next Step of importing the xml file of the preconfigured job from the exported template job I have some Questions.

note: Created a template job and exported it to the xml via the Veeam.Agent.Configurator.exe.

When looking at the xml it seemed ok. But it raised some questions.

1) if I import this job config on other or new machines wont it just create a job with same name ? (what have I missed? I looked for some documentation but I must of had a man look)
2) do I have to customise the XML for each PC or will it overwrite things like job name with the name of the local machine ?
3) how do you customise it if you have too ?

Interested in feed back or answers from folks already done this.

Cheers
steve

[Mildur]

Hi Steve

Can you elaborate on why you are not using our Veeam Backup & Replication Server (VBR) to deploy and manage the agents with backup jobs? Using VBR as a central management system seems easier to me. If you use Veeam.Agent.Configurator.exe to import XML files, you must have a valid license. The same license will allow you to manage your agents with a VBR server.
There is also the option (protection group "Computers with Pre-installed Backup Agents") to use your own deployment system, but agents will still receive the job policy from the central VBR server.

1.) Correct.

2.) Yes, there is a parameter for the job name in your XML file. The job gets created according to that parameter. I recommend to import the XML manually to one machine as a test.

3.) You need to change the job name in your XML file. All XML parameters are documented in our help center.

Job Name is documented here: https://helpcenter.veeam.com/docs/agent ... tml?ver=60

Best,
Fabian

[StevenMeier]

Thanks for the update.
We have a subscription License and the Machines with Agents Have Taken a license so I assume thats fine