Downloads:

93

Downloads of v 10.0.2.1094:

40

Last Update:

21 Jul 2020

Package Maintainer(s):

Software Author(s):

  • Veeam Software AG

Tags:

veeam-one-agent veeam-one veeam one agent admin

Veeam ONE Agent

10.0.2.1094 | Updated: 21 Jul 2020

Downloads:

93

Downloads of v 10.0.2.1094:

40

Maintainer(s):

Software Author(s):

  • Veeam Software AG

Tags:

veeam-one-agent veeam-one veeam one agent admin

Veeam ONE Agent 10.0.2.1094

This Package Contains an Exempted Check

1 Test Passing and 1 Exempted Test

Hide Checks
Hide Checks

Validation Testing Passed

Verification Testing Exempt:

This package requires a reboot for .NET Framework installation.

To install Veeam ONE Agent, run the following command from the command line or from PowerShell:

>

To upgrade Veeam ONE Agent, run the following command from the command line or from PowerShell:

>

To uninstall Veeam ONE Agent, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade veeam-one-agent -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade veeam-one-agent -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode


- name: Ensure veeam-one-agent installed
  win_chocolatey:
    name: veeam-one-agent
    state: present
    version: 10.0.2.1094
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'veeam-one-agent' do
  action    :install
  version  '10.0.2.1094'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: veeam-one-agent,
    Version: 10.0.2.1094,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller veeam-one-agent
{
   Name     = 'veeam-one-agent'
   Ensure   = 'Present'
   Version  = '10.0.2.1094'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'veeam-one-agent':
  provider => 'chocolatey',
  ensure   => '10.0.2.1094',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install veeam-one-agent version="10.0.2.1094" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator mwallner on 22 Jul 2020.

Description

Exit when reboot detected

When installing / upgrading these packages, I would like to advise you to enable this feature choco feature enable -n=exitOnRebootDetected

Veeam ONE Agent

Veeam ONE Agent is a component that enables communication with Veeam Backup & Replication servers, performs collection of logs, and sends remediation commands.

Veeam ONE agent can work in the following modes:

  • Server:

    In this mode, Veeam ONE agent is responsible for analyzing log data and signature updates.

    Veeam ONE agent server is included into Veeam ONE installation package and deployed on the machine running Veeam ONE Monitor server during product installation.

  • Client

    In this mode, Veeam ONE agent is responsible for collecting logs and executing remediation actions on Veeam Backup & Replication servers.By default,

By default, Veeam ONE agent client is deployed on Veeam Backup & Replication servers when you connect these servers to Veeam ONE.

> IMPORTANT!
>
> Veeam ONE agent server must be installed on the machine that runs Veeam ONE Monitor server.

To have choco remember parameters on upgrade, be sure to set choco feature enable -n=useRememberedArgumentsForUpgrades.

Package Parameters

The package accepts the following optional parameters:

  • /server - Specifies the mode in which Veeam ONE agent will run. If you specify this parameter, the agent will be installed in Server mode. Only required for the Veeam ONE Server
  • /username - Specifies a user account under which the Veeam ONE Agent service will run. Example: /username:ONESERVER\Administrator
  • /password - This parameter must be used if you have specified the /username parameter. Specifies a password for the account that will be used to run Veeam ONE Agent. Example: /password:[email protected]
  • /create - Create the requested user on this machine, this user will be added to the local Administrators group.
  • /agentServicePort - Specifies a port that will be used by Monitor to communicate with Veeam ONE Agent. By default, port number 2805 is used. Example: /agentServicePort:2805

Example: choco install veeam-one-agent --params "/server /agentServicePort:1234"

Please Note: This is an automatically updated package. If you find it is
out of date by more than a day or two, please contact the maintainer(s) and
let them know the package is no longer updating correctly.

tools\chocolateyinstall.ps1 
$ErrorActionPreference = 'Stop';
$toolsDir     = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

$isoPackageName = 'veeam-one-iso'
$scriptPath = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
$commonPath = $(Split-Path -parent $(Split-Path -parent $scriptPath))
$filename = 'VeeamONE.10.0.2.1094.iso'
$installPath = Join-Path  (Join-Path $commonPath $isoPackageName) $filename

$fileLocation = 'Agent\VeeamONE.Agent.x64.msi'

$pp = Get-PackageParameters

$silentArgs = ""
$agentType = '0'

if($pp.server) {
  $agentType = 1
}

$silentArgs += " VO_AGENT_TYPE=`"$($agentType)`" VO_BUNDLE_INSTALLATION=`"$($agentType)`""

if ($pp.username) {
  $computername = $env:computername
  $fulluser = $pp.username
  if ($pp.username -notmatch "\\") {
    $fulluser = "$($computername)\$($pp.username)"
  }
  if(-not $pp.password) {
    throw 'Password is required when setting a username...'
  }
  if ($pp.create) {
    if ($pp.username -match "\\") {
      throw "Only local users can be created"
    }

    if (Get-WmiObject -Class Win32_UserAccount | Where-Object {$_.Name -eq $pp.username}) {
      Write-Warning "The local user already exists, not creating again"
    } else {
      net user $pp.username $pp.password /add /PASSWORDCHG:NO
      wmic UserAccount where ("Name='{0}'" -f $pp.username) set PasswordExpires=False
      net localgroup "Administrators" $pp.username /add    }
  }
  $silentArgs += " VO_AGENT_SERVICE_ACCOUNT_NAME=`"$($fulluser)`" VO_AGENT_SERVICE_ACCOUNT_PASSWORD=`"$($pp.password)`""
}

if ($pp.agentServicePort) {
  $silentArgs += " VO_AGENT_SERVICE_PORT=$($pp.agentServicePort)"
}

$packageArgs = @{
  packageName    = $env:ChocolateyPackageName
  isoFile        = $installPath
  softwareName   = 'Veeam ONE Agent*'
  file           = $fileLocation
  fileType       = 'msi'
  silentArgs     = "$($silentArgs) ACCEPT_EULA=1 ACCEPT_THIRDPARTY_LICENSES=1 /qn /norestart /l*v `"$env:TEMP\$env:ChocolateyPackageName.$env:ChocolateyPackageVersion.log`""
  validExitCodes = @(0,1638,1641,3010) #1638 was added to allow updating when an newer version is already installed.
  destination    = $toolsDir
}

Install-ChocolateyIsoInstallPackage @packageArgs

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Veeam ONE Agent 10.0.2.1094 40 Tuesday, July 21, 2020 Approved
Veeam ONE Agent 10.0.0.750 53 Monday, March 23, 2020 Approved
Discussion for the Veeam ONE Agent Package

Ground Rules:

  • This discussion is only about Veeam ONE Agent and the Veeam ONE Agent package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Veeam ONE Agent, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus