Downloads of v 1.30.0:


Last Update:

03 Jun 2021

Package Maintainer(s):

Software Author(s):

  • Particular Software


servicepulse nservicebus particular admin

ServicePulse (Install)

  • 1
  • 2
  • 3

1.30.0 | Updated: 03 Jun 2021



Downloads of v 1.30.0:



Software Author(s):

  • Particular Software

  • 1
  • 2
  • 3
ServicePulse (Install) 1.30.0

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files


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


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


To uninstall ServicePulse (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 servicepulse -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 servicepulse -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 servicepulse installed
    name: servicepulse
    state: present
    version: 1.30.0
    source: STEP 3 URL

See docs at

chocolatey_package 'servicepulse' do
  action    :install
  version  '1.30.0'
  source   'STEP 3 URL'

See docs at

    Name: servicepulse,
    Version: 1.30.0,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller servicepulse
   Name     = 'servicepulse'
   Ensure   = 'Present'
   Version  = '1.30.0'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'servicepulse':
  provider => 'chocolatey',
  ensure   => '1.30.0',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install servicepulse version="1.30.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 as a trusted package on 03 Jun 2021.


ServicePulse is a web application aimed mainly at administrators. It gives a clear, near real-time, high-level overview of how a system is functioning.

$ErrorActionPreference = 'Stop'

$url64bit   = ''
$checksum64 = 'a86a45986b18f9beea4a74699e5068cb1f98c0020d6c1155dbe213eefb72cb0a'

$packageArgs = @{
  packageName    = $env:ChocolateyPackageName
  fileType       = 'EXE'
  url64bit       = $url64bit
  checksum64     = $checksum64
  checksumType64 = 'sha256'
  silentArgs     = "/quiet /norestart /LV* `"$($env:TEMP)\$($packageName).$($env:chocolateyPackageVersion).log`""
  validExitCodes = @(0)

Install-ChocolateyPackage @packageArgs

$ErrorActionPreference = 'Stop'

$packageArgs = @{
  packageName    = $env:ChocolateyPackageName
  softwareName   = 'ServicePulse'
  # Installer fails when fileType is not EXE and uninstall fails when fileType is not MSI.  It's confusing but it's the only way it works.
  # It's most likely because the below conditional in this file that deals with looking for certain keys in the registry if the file is an MSI
  fileType       = 'MSI'
  # MSI
  silentArgs     = "/quiet /norestart /LV* `"$($env:TEMP)\$($packageName).$($env:chocolateyPackageVersion).log`""
  validExitCodes = @(0)

$uninstalled = $false
# Get-UninstallRegistryKey is new to 0.9.10, if supporting 0.9.9.x and below,
# take a dependency on "chocolatey-core.extension" in your nuspec file.
# This is only a fuzzy search if $softwareName includes '*'. Otherwise it is 
# exact. In the case of versions in key names, we recommend removing the version
# and using '*'.
[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName']

if ($key.Count -eq 1) {
  $key | % { 
    $packageArgs['file'] = "$($_.UninstallString)"
    if ($packageArgs['fileType'] -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).
      $packageArgs['silentArgs'] = "$($_.PSChildName) $($packageArgs['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
      $packageArgs['file'] = ''

    Uninstall-ChocolateyPackage @packageArgs
} 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
ServicePulse (Install) 1.29.0 36 Friday, May 7, 2021 Approved
ServicePulse (Install) 1.28.0 98 Friday, November 20, 2020 Approved
ServicePulse (Install) 1.27.1 53 Friday, October 30, 2020 Approved
ServicePulse (Install) 1.27.0 45 Wednesday, October 21, 2020 Approved
ServicePulse (Install) 1.26.0 58 Tuesday, September 29, 2020 Approved
ServicePulse (Install) 1.25.4 93 Wednesday, July 8, 2020 Approved
ServicePulse (Install) 1.25.3 92 Tuesday, June 2, 2020 Approved
ServicePulse (Install) 1.25.2 58 Thursday, May 28, 2020 Approved
ServicePulse (Install) 1.25.1 99 Tuesday, May 5, 2020 Approved

This package has no dependencies.

Discussion for the ServicePulse (Install) Package

Ground Rules:

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