Downloads:

52

Downloads of v 10.0.2.1094:

8

Last Update:

21 Jul 2020

Package Maintainer(s):

Software Author(s):

  • Veeam Software AG

Tags:

veeam-one-monitor-server veeam-one veeam one monitor server admin

Veeam ONE Monitor Server

10.0.2.1094 | Updated: 21 Jul 2020

Downloads:

52

Downloads of v 10.0.2.1094:

8

Maintainer(s):

Software Author(s):

  • Veeam Software AG

Veeam ONE Monitor Server 10.0.2.1094

This Package Contains an Exempted Check

1 Test Passing and 1 Exempted Test


Validation Testing Passed


Verification Testing Exempt:

This package requires IIS and SQL Server (express) to be installed and a reboot for .NET Framework installation.

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

>

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

>

To uninstall Veeam ONE Monitor Server, 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-monitor-server -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-monitor-server -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-monitor-server installed
  win_chocolatey:
    name: veeam-one-monitor-server
    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-monitor-server' 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-monitor-server,
    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-monitor-server
{
   Name     = 'veeam-one-monitor-server'
   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-monitor-server':
  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-monitor-server 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 Server

Veeam ONE Server is responsible for collecting data from virtual servers, vCloud Director servers and Veeam Backup & Replication servers, and storing this data into the database. As part of Veeam ONE Server, the following components should be installed: Veeam ONE Monitor Server and Veeam ONE Reporter Server.

Manual steps

You'll need an SQL Server (express) installed. It's not required to have this installed on this server. You'll need to specify parameters to connect to the SQL Server.

This package requires you to install the IIS Windows feature and WAS Configuration API feature. You can install these by executing choco install IIS-WebServer WAS-ConfigurationAPI --source windowsfeatures

After installing this package, the Veeam ONE Reporter Server package must be installed. Package parameters are not passed to depended packages, therefore it's not added as a dependency. You must install this package manually on the same machine for Veeam ONE to work.

Package Parameters

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

This package accepts a lot of parameters. Some of them are required the installation. For the full list of parameters, please have a look at the documentation

<!-- PARAMETERS.md -->
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 = 'Monitor\VeeamONE.Monitor.Server.x64.msi'

$service = get-service w3svc -ErrorAction SilentlyContinue
if(!$service) {
  Write-Warning "IIS is not installed on this machine! `nPlease install IIS on this machine as described on the package page"
  throw
}

$pp = Get-PackageParameters

$silentArgs = ""

$validOptionsTypes = '0','1','2'
$validOptionsBool = '0','1'

if ($pp.perfCache) {
  $silentArgs += " VM_MN_CACHE=`"$($pp.perfCache)`""
  if(!(Test-Path -Path $pp.perfCache )){
    New-Item -Path $pp.perfCache -ItemType Directory
  }
}

if ($pp.installationType) {
  if (-not $validOptionsTypes.Contains($pp.installationType)) {
    Write-Warning "$($pp.installationType) is an invalid value for the installationType parameter."
    throw
  }
  $silentArgs += " VO_INSTALLATION_TYPE=$($pp.installationType)"
}

if ($pp.vcSelectedType) {
  if (-not $validOptionsTypes.Contains($pp.vcSelectedType)) {
    Write-Warning "$($pp.vcSelectedType) is an invalid value for the vcSelectedType parameter."
    throw
  }
  $silentArgs += " VM_VC_SELECTED_TYPE=`"$($pp.vcSelectedType)`""

  if ($pp.vcSelectedType -eq '1') {
    if ($pp.hvType) {
      if (-not $validOptionsTypes.Contains($pp.hvType)) {
        Write-Warning "$($pp.hvType) is an invalid value for the hvType parameter."
        throw
      }
      $silentArgs += " VM_HV_TYPE=$($pp.hvType)"

    }
  }

  if($pp.vcSelectedType -eq '0' -or $pp.vcSelectedType -eq '1') {
    if(-not $pp.vcHost -or -not $pp.vcPort -or -not $pp.vcHostUser -or -not $pp.vcHostPass) {
      Write-Warning "vcHost, vcPort, vcHostUser and vcHostPass are required when vcSelectedType is 0 or 1"
      throw
    }
    $silentArgs += " VM_VC_HOST=`"$($pp.vcHost)`" VM_VC_PORT=$($pp.vcPort) VM_VC_HOST_USER=`"$($pp.vcHostUser)`" VM_VC_HOST_PWD=`"$($pp.vcHostPass)`""

    if ($pp.backupAddLater) {
      if (-not $validOptionsBool.Contains($pp.backupAddLater)) {
        Write-Warning "$($pp.backupAddLater) is an invalid value for the backupAddLater parameter."
        throw
      }
      $silentArgs += " VM_BACKUP_ADD_LATER=$($pp.backupAddLater)"
    }

    if(-not $pp.backupAddLater -and (-not $pp.backupAddType -or -not $pp.backupAddHost -or -not $pp.backupAddUser -or -not $pp.backupAddPass)) {
      Write-Warning "backupAddType, backupAddHost, backupAddUser and backupAddPass are required when vcSelectedType is 0 or 1 and backupAddLater is not 1"
      throw
    }

    if (-not $validOptionsBool.Contains($pp.backupAddType)) {
      Write-Warning "$($pp.backupAddType) is an invalid value for the backupAddType parameter."
      throw
    }
    $silentArgs += " VM_BACKUP_ADD_TYPE=$($pp.backupAddType) VM_BACKUP_ADD_NAME=`"$($pp.backupAddHost)`" VM_BACKUP_ADD_USER=`"$($pp.backupAddUser)`" VM_BACKUP_ADD_PWD=`"$($pp.backupAddPass)`""
  }
}

if ($pp.sqlServer) {
  $silentArgs += " VM_MN_SQL_SERVER=$($pp.sqlServer)"
}

if ($pp.sqlDatabase) {
  $silentArgs += " VM_MN_SQL_DATABASE=$($pp.sqlDatabase)"
}

if ($pp.sqlAuthentication) {
  if(-not $pp.sqlPassword -or -not $pp.sqlUsername) {
    throw 'sqlUsername and sqlPassword are required when using sqlAuthentication...'
  }
  $silentArgs += " VM_MN_SQL_AUTHENTICATION=$($pp.sqlAuthentication) VM_MN_SQL_USER=`"$($pp.sqlUsername)`" VM_MN_SQL_PASSWORD=`"$($pp.sqlPassword)`""
}

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 += " VM_MN_SERVICEACCOUNT=`"$($fulluser)`" VM_MN_SERVICEPASSWORD=`"$($pp.password)`""
}

if ($pp.licenseFile) {
  if(!(Test-Path -Path $pp.licenseFile )){
    throw "Invalid license file provided"
  }
  $silentArgs += " EDITLICFILEPATH=$($pp.licenseFile)"
}

$packageArgs = @{
  packageName    = $env:ChocolateyPackageName
  isoFile        = $installPath
  softwareName   = 'Veeam ONE Monitor Server*'
  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 Monitor Server 10.0.0.750 44 Monday, March 23, 2020 Approved
Discussion for the Veeam ONE Monitor Server Package

Ground Rules:

  • This discussion is only about Veeam ONE Monitor Server and the Veeam ONE Monitor Server 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 Monitor Server, 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