Downloads:

4,291

Downloads of v 7.5.00104:

341

Last Update:

4/5/2018

Package Maintainer(s):

Software Author(s):

  • Spiceworks Inc.

Tags:

network-monitoring helpdesk small-business network-management network-mapping medium-business purchasing

Spiceworks

7.5.00104 | Updated: 4/5/2018

Downloads:

4,291

Downloads of v 7.5.00104:

341

Software Author(s):

  • Spiceworks Inc.

Spiceworks 7.5.00104

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install Spiceworks, run the following command from the command line or from PowerShell:

>

To upgrade Spiceworks, run the following command from the command line or from PowerShell:

>

To uninstall Spiceworks, 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 spiceworks -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 spiceworks -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 spiceworks installed
  win_chocolatey:
    name: spiceworks
    state: present
    version: 7.5.00104
    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 'spiceworks' do
  action    :install
  version  '7.5.00104'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: spiceworks,
    Version: 7.5.00104,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller spiceworks
{
   Name     = 'spiceworks'
   Ensure   = 'Present'
   Version  = '7.5.00104'
   Source   = 'STEP 3 URL'
}

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


package { 'spiceworks':
  provider => 'chocolatey',
  ensure   => '7.5.00104',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install spiceworks version="7.5.00104" 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 by moderator flcdrg on 9/6/2019.

Description

Join over 2.2 million IT professionals and download Spiceworks.
Spiceworks is the complete network monitoring and management, help desk, PC inventory, and software reporting solution to manage Everything IT in small and medium businesses.
The following (but not limited to) features allow IT pros to:
* Discover virtual server information
* View and kill processes remotely
* Get more out of your help desk
* Purchase CDW equipment directly from your application
* Discover installed applications on your workstations
* Find out what Cloud services are being used
* Implement a help desk ticketing system
* Track purchases in-app, request quotes from vendors


tools\chocolateyInstall.ps1
$packageArgs = @{
  packageName   = 'spiceworks'
  unzipLocation = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
  fileType      = 'exe'
  url           = 'https://download.spiceworks.com/Spiceworks/current/Spiceworks.exe'
  silentArgs    = '/S'
  validExitCodes= @(0,3010)
  softwareName  = 'spiceworks*'
  checksum      = '7E2A38689EF2B99BA3BDD70D2BC8F50D1FE7199B'
  checksumType  = 'sha1'
}

Install-ChocolateyPackage @packageArgs
tools\chocolateyuninstall.ps1
$packageName = 'spiceworks'
$installerType = 'EXE'
$silentArgs = '/VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-'
$validExitCodes = @(0) #please insert other valid exit codes here, exit codes for ms http://msdn.microsoft.com/en-us/library/aa368542(VS.85).aspx
 
  $processor = Get-WmiObject Win32_Processor
  $is64bit = $processor.AddressWidth -eq 64
  if ($is64bit) {
    $unpath = "${Env:ProgramFiles(x86)}\Spiceworks\uninst.exe"
  } else {
    $unpath = "$Env:ProgramFiles\Spiceworks\uninst.exe"
  }
  Uninstall-ChocolateyPackage "$packageName" "$installerType" "$silentArgs" "$unpath" -validExitCodes $validExitCodes

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
Spiceworks 7.5.00101 319 Thursday, December 14, 2017 Approved
Spiceworks 7.2.00528 657 Friday, November 14, 2014 Approved
Spiceworks 7.2.00526 301 Wednesday, November 12, 2014 Approved
Spiceworks 7.2.00521 295 Friday, November 7, 2014 Approved
Spiceworks 7.2.00226 380 Monday, September 15, 2014 Approved
Spiceworks 7.2.00221 298 Monday, August 18, 2014 Approved
Spiceworks 7.2.00218 377 Friday, July 4, 2014 Approved
Spiceworks 7.2.00207 321 Tuesday, July 1, 2014 Approved
Spiceworks 7.2.00202 329 Wednesday, June 11, 2014 Approved

This package has no dependencies.

Discussion for the Spiceworks Package

Ground Rules:

  • This discussion is only about Spiceworks and the Spiceworks 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 Spiceworks, 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