Downloads of v 7.2.0:


Last Update:

16 Jul 2017

Package Maintainer(s):

Software Author(s):

  • LordMike
  • kewalaka


xencenter xenserver citrix admin

xencenter (Install)

7.2.0 | Updated: 16 Jul 2017



Downloads of v 7.2.0:



Software Author(s):

  • LordMike
  • kewalaka

xencenter (Install) 7.2.0

This Package Contains an Exempted Check

1 Test Passing and 1 Exempted Test

Validation Testing Passed

Verification Testing Exempt:

Requires dotnet4.6.2

To install xencenter (Install), run the following command from the command line or from PowerShell:


To upgrade xencenter (Install), run the following command from the command line or from PowerShell:


To uninstall xencenter (Install), 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 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

4. Choose your deployment method:

choco upgrade xencenter -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 xencenter -y --source="'STEP 3 URL'"

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

Exit $exitCode

- name: Ensure xencenter installed
    name: xencenter
    state: present
    version: 7.2.0
    source: STEP 3 URL

See docs at

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

chocolatey_package 'xencenter' do
  action    :install
  version  '7.2.0'
  source   'STEP 3 URL'

See docs at

    Name: xencenter,
    Version: 7.2.0,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller xencenter
   Name     = 'xencenter'
   Ensure   = 'Present'
   Version  = '7.2.0'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'xencenter':
  provider => 'chocolatey',
  ensure   => '7.2.0',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install xencenter version="7.2.0" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved by moderator AdmiringWorm on 24 Jul 2017.


XenCenter is a Windows-based management tool for XenServer environments which enables users to manage and monitor XenServer hosts and resource pools, and to deploy, monitor, manage and migrate virtual machines.

$ErrorActionPreference = 'Stop'

$toolsPath   = Split-Path $MyInvocation.MyCommand.Definition

$packageArgs = @{
  packageName            = 'xencenter'
  fileType               = 'exe'
  url                    = ''
  url64bit               = ''
  checksum               = 'eed2ad46c7e89d6880db83e4599864af9c46607b8efb760ff583a70332cad63f'
  checksum64             = ''
  checksumType           = 'sha256'
  checksumType64         = 'sha256'
  silentArgs             = "/i /q /Log /LogFile `"$env:TEMP\chocolatey\$($packageName)\$($packageName).Install.log`""
  validExitCodes         = @(0, 3010, 1641)
  softwareName           = 'xencenter*'
Install-ChocolateyPackage @packageArgs

$packageName = $packageArgs.packageName
$installLocation = Get-AppInstallLocation $packageName
if (!$installLocation)  { Write-Warning "Can't find $packageName install location"; return }
Write-Host "$packageName installed to '$installLocation'"

Register-Application "$installLocation\$packageName.exe"
Write-Host "$packageName registered as $packageName"
$ErrorActionPreference = 'Stop';

$packageName = 'xencenter'
$softwareName = 'Citrix XenCenter'
$installerType = 'MSI' 

$silentArgs = '/qn /norestart'
$validExitCodes = @(0, 3010, 1605, 1614, 1641)

$uninstalled = $false
$local_key     = 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*'
$machine_key   = 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*'
$machine_key6432 = 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*'

$key = Get-ItemProperty -Path @($machine_key6432,$machine_key, $local_key) -ErrorAction SilentlyContinue | ? { $_.DisplayName -like "$softwareName" }

if (($key.Count -and $key.Count -eq 1) -or $key) {
	$file = "$($key.UninstallString)"

	if ($installerType -eq 'MSI') {
		# The Product Code GUID is all that should be passed for MSI, and very 
		# FIRST, because it comes directly after /x, which is already set in the 
		# Uninstall-ChocolateyPackage msiargs (facepalm).
		$silentArgs = "$($key.PSChildName) $silentArgs"

		# Don't pass anything for file, it is ignored for msi (facepalm number 2) 
		# Alternatively if you need to pass a path to an msi, determine that and 
		# use it instead of the above in silentArgs, still very first
		$file = ''

	Uninstall-ChocolateyPackage -PackageName $packageName `
							-FileType $installerType `
							-SilentArgs "$silentArgs" `
							-ValidExitCodes $validExitCodes `
							-File "$file"
} elseif ($key.Count -eq 0) {
  Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
  Write-Warning "$key.Count matches found!"
  Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
  Write-Warning "Please alert package maintainer the following keys were matched:"
  $key | % {Write-Warning "- $_.DisplayName"}

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
xencenter (Install) 713 Wednesday, February 10, 2016 Approved

Discussion for the xencenter (Install) Package

Ground Rules:

  • This discussion is only about xencenter (Install) and the xencenter (Install) 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 xencenter (Install), 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