How to Manually Update Veeam Backup Agent Deployment Packages on Veeam Service Provider Console Server

KB ID: 4297
Product: Veeam Service Provider Console | 6.0
Published: 2022-06-01
Last Modified: 2022-06-01
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Article Applicability

This article is intended to be used in environments where the Veeam Service Provider Console server does not have internet access or cannot reach the Veeam Installation Server (vac.butler.veeam.com).

If the machine where Veeam Service Provider Console is installed has internet access, the software will automatically download the latest Veeam Backup Agent deployment packages, thereby removing the need to perform the steps documented in this article.

Challenge

When the Veeam Service Provider Console server does not have internet access it is unable to download the latest deployment packages for Veeam Backup Agents (i.e., Veeam Agent for Microsoft Windows, Veeam Agent for Linux, Veeam Agent for Mac) from the Veeam Installation Server.

Solution

This article documents how to manually update the Veeam Backup Agent deployment packages stored on the Veeam Service Provider Console server.
Updating Veeam Backup Agents Deployment Packages

When the Veeam Service Provider Console server does not have access to the internet, the Veeam Backup agent setup files can be downloaded on a machine with internet access and then copied to the Veeam Service Provider Console server.

 

Note: The download URLs below will require that you know the build number of Veeam Service Provider Console that is installed. This can be found within the Configuration page of the Veeam Service Provider Console Web UI under Support Information.

VSPC Build Number

Updating Veeam Agent for Microsoft Windows Deployment Package

  1. Connect to the Veeam Installation Server using the following address:
    Replace <vspc_version> (including the brackets) with the Veeam Service Provider Console build version.
https://vac.butler.veeam.com/api/v1/agents/file/update?version=<vspc_version>&product_version=0.0.0.0&product=vaw
  1. The contents of a JSON file will be displayed, copy the URL address from the url parameter for the package.

    Note: If using Firefox, simply click the package link, and the download will start. Skip to Step 4.
  2. Paste the address from the url parameter into the browser's address bar and save the Veeam Agent for Microsoft Windows installer.
  3. Rename the downloaded Veeam Agent for Microsoft Windows installer file to VeeamAgentWindows.exe
  4. Copy the VeeamAgentWindows.exe file to the Veeam Service Provider Console server, or to a location that is accessible from the Veeam Service Provider Console server.
  5. Connect to the machine hosting the Veeam Service Provider Console Server component.
  6. Replace the file in the following path with the downloaded VeeamAgentWindows.exe:
    <install_path>\ApplicationServer\AgentPackage
    
    where <install_path> is the path to the directory where Veeam Service Provider Console is installed.
    Default Path: C:\Program Files\Veeam\Availability Console\ApplicationServer\AgentPackage

 

Note: If Veeam Agent for Microsoft Windows version 5.0.0.4301 is installed on the machine where the Veeam Service Provider Console Management Agent is installed, that Veeam Agent for Microsoft Windows deployment must be updated manually and cannot be updated using Veeam Service Provider Console.

Updating Veeam Agent for Mac Deployment Packages

  1. Connect to the Veeam Installation Server using the following address:
    Replace <vspc_version> (including the brackets) with the Veeam Service Provider Console build version.
 https://vac.butler.veeam.com/api/v1/agents/file/update?version=<vspc_version>&product_version=0.0.0.0&product=vam
  1. The contents of a JSON file will be displayed with two package url parameters.
    Copy each  url and paste them into a a different browser tab to download each of the packages.

    Note: If using Firefox, simply click on each package download link to start the download.
  2. Copy the Veeam Agent for Mac pkg files to the Veeam Service Provider Console server, or to a location that is accessible from the Veeam Service Provider Console server.
  3. Connect to the machine hosting the Veeam Service Provider Console Server component.
  4. Navigate to the following folder:
    <install_path>\ApplicationServer\MacPackages\VamPackages
    
    where <install_path> is the path to the directory where Veeam Service Provider Console is installed.
    Default Path: C:\Program Files\Veeam\Availability Console\ApplicationServer\MacPackages\VamPackages
  5. Within the VamPackages folder will be a folder for the existing Veeam Agent for Mac package, delete the existing agent version folder.
  6. Create a new folder with the build number contained in the name of the  Veeam Agent for Mac pkg files downloaded in Step 3.

    Example: If the pkg file is named "Veeam Agent for Mac-1.0.1.822.pkg" the folder you'd create would be named "1.0.1.822"
  7. Copy the two Veeam Agent for Mac  pkg files download in Step 3 into the newly created folder.

Updating Veeam Agent for Linux Deployment Packages

To simplify updating the Veeam Agent for Linux deployment packages, the following PowerShell script was created that will download the necessary packages and create the folder structure that Veeam Service Provider Console will expect. If you would prefer to perform the downloads manually and create the folder structure yourself, please see the "Manually Updating Veeam Agent for Linux Deployment Packages" instructions in the next section.

  1. Run the val_download.ps1 script file on a machine with internet access.

    In the folder where the script was run a directory named ValPackages will be created. The script will then download the necessary Veeam Agent for Linux deployment files and place them within subdirectories of that ValPackages folder.

    Note: This script requires at least PowerShell version 4.0.
  2. Copy the ValPackages folder to the Veeam Service Provider Console server, or to a location that is accessible from the Veeam Service Provider Console server.
  3. Connect to the machine hosting the Veeam Service Provider Console Server component.
  4. Navigate to the following folder:
    <install_path>\ApplicationServer\LinuxPackages\
    
    where <install_path> is the path to the directory where Veeam Service Provider Console is installed.
    Default Path: C:\Program Files\Veeam\Availability Console\ApplicationServer\LinuxPackages
  5. Replace the ValPackages folder with the folder created by the val_download.ps1 script.
  6. Restart the Veeam Management Portal Service.

 

Manually Updating Veeam Agent for Linux Deployment Packages

  1. Connect to the Veeam Installation Server using the following address:
    Replace <vspc_version> (including the brackets) with the Veeam Service Provider Console build version.
https://vac.butler.veeam.com/api/v1/agents/file/update?version=<vspc_version>&product_version=0.0.0.0&product=val
  1. For each of the listed packages, 47 at time of writing this article, do the following:
    1. Copy URL address from the url parameter file.
    2. Go to the copied address and save the file.

    Note: Using Firefox will greatly simplify this process as the JSON file will open in an interactive window so that each URL path can be clicked to start the download.
  2. Copy all of the download files to the Veeam Service Provider Console server, or to a location that is accessible from the Veeam Service Provider Console server.
  3. Connect to the machine hosting the Veeam Service Provider Console Server component.
  4. Navigate to the folder where you have copied the downloaded files.
  5. For each downloaded package do the following:
    1. Find the package name in the ValPackageIndex.xml file.
    2. Move the package file to the folder:
      <path>\ApplicationServer\LinuxPackages\ValPackages\<version>\<architecture>
      
      where:
      • <path> is the path to the directory where Veeam Service Provider Console is installed.
      • <version> is the value specified in the Packages version parameter for the package.
      • <architecture> is the value specified in the Packages arch parameter for the package.

        Create new folders, if necessary.
    Mind the following:
    • Packages with names containing ‘i586’ must reside in folders for both x86 and x64 architectures.
    • Packages with names containing ‘nosnap’ are not included in the XML file. These packages must reside in folders for both x86 and x64 architectures. The necessary version is specified in the type parameter.
    • If a version folder includes only one architecture folder, you must create a folder with the same content for the other architecture type.
  6. Restart the Veeam Management Portal Service.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.