Downloads:

1,328

Downloads of v 3.4.0:

41

Last Update:

12/12/2018

Package Maintainer(s):

Software Author(s):

  • Particular Software

Tags:

servicecontrol nservicebus particular admin

ServiceControl (Install)

This is not the latest version of ServiceControl (Install) available.

3.4.0 | Updated: 12/12/2018

Downloads:

1,328

Downloads of v 3.4.0:

41

Maintainer(s):

Software Author(s):

  • Particular Software

ServiceControl (Install) 3.4.0

This is not the latest version of ServiceControl (Install) available.

This Package Contains an Exempted Check

1 Test Passing and 1 Exempted Test


Validation Testing Passed


Verification Testing Exempt:

Required due to dependency.

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

>

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

>

To uninstall ServiceControl (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 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 servicecontrol -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 servicecontrol -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 servicecontrol installed
  win_chocolatey:
    name: servicecontrol
    state: present
    version: 3.4.0
    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 'servicecontrol' do
  action    :install
  version  '3.4.0'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: servicecontrol,
    Version: 3.4.0,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller servicecontrol
{
   Name     = 'servicecontrol'
   Ensure   = 'Present'
   Version  = '3.4.0'
   Source   = 'STEP 3 URL'
}

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


package { 'servicecontrol':
  provider => 'chocolatey',
  ensure   => '3.4.0',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install servicecontrol version="3.4.0" 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.

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

This package was approved as a trusted package on 12/12/2018.

Description

ServiceControl is a suite of back-end tools that collect useful information about a running NServiceBus system.

ServiceControl on installation utilizes a trial that expires after 14 days. In order to install a non-trial license please follow the steps outlined in the documentation here https://docs.particular.net/servicecontrol/license.

NOTE: It's best practice to install the license VIA your organizations choice of configuration management tool (puppet, chef, ansible, etc.)


tools\chocolateyinstall.ps1
# https://docs.particular.net/servicecontrol/installation-silent

$ErrorActionPreference = 'Stop'

$url64bit   = 'https://github.com/Particular/ServiceControl/releases/download/3.4.0/Particular.ServiceControl-3.4.0.exe'
$checksum64 = '337d30f690da11d2e4930b1b2fecd33e4a6219255039d5df0e024919ad8b5c85'

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

Install-ChocolateyPackage @packageArgs
tools\chocolateyuninstall.ps1

$ErrorActionPreference = 'Stop'

$packageArgs = @{
  packageName    = $env:ChocolateyPackageName
  softwareName   = 'ServiceControl'
  # 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)"}
}

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
ServiceControl (Install) 4.4.0 14 Wednesday, October 23, 2019 Approved
ServiceControl (Install) 4.3.4 14 Friday, October 18, 2019 Approved
ServiceControl (Install) 4.3.3 40 Friday, September 20, 2019 Approved
ServiceControl (Install) 4.3.2 16 Saturday, September 14, 2019 Approved
ServiceControl (Install) 4.3.1 15 Saturday, September 7, 2019 Approved
ServiceControl (Install) 4.3.0 21 Wednesday, August 28, 2019 Approved
ServiceControl (Install) 4.2.0 18 Tuesday, August 27, 2019 Approved
ServiceControl (Install) 4.1.0 22 Saturday, August 17, 2019 Approved
ServiceControl (Install) 4.0.1 21 Thursday, August 1, 2019 Approved
Discussion for the ServiceControl (Install) Package

Ground Rules:

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