Downloads:

127,250

Downloads of v 1.0.0.2:

475

Last Update:

23 Aug 2011

Package Maintainer(s):

Software Author(s):

  • Mark Russinovich

Tags:

pstools psexec file disk utilities tools chocolatey

PsTools

This is not the latest version of PsTools available.

1.0.0.2 | Updated: 23 Aug 2011

Downloads:

127,250

Downloads of v 1.0.0.2:

475

Maintainer(s):

Software Author(s):

  • Mark Russinovich

Tags:

pstools psexec file disk utilities tools chocolatey

PsTools 1.0.0.2

This is not the latest version of PsTools available.

All Checks are Unknown

2 Test of Unknown Status

Hide Checks
Hide Checks

Validation Testing Unknown

Verification Testing Unknown

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

>

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

>

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

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


Chocolatey::Ensure-Package
(
    Name: pstools,
    Version: 1.0.0.2,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller pstools
{
   Name     = 'pstools'
   Ensure   = 'Present'
   Version  = '1.0.0.2'
   Source   = 'STEP 3 URL'
}

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


package { 'pstools':
  provider => 'chocolatey',
  ensure   => '1.0.0.2',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install pstools version="1.0.0.2" 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 submitted prior to moderation and has not been approved. While it is likely safe for you, there is more risk involved.

Description

The Windows NT and Windows 2000 Resource Kits come with a number of command-line tools that help you administer your Windows NT/2K systems. Over time, I've grown a collection of similar tools, including some not included in the Resource Kits. What sets these tools apart is that they all allow you to manage remote systems as well as the local one. The first tool in the suite was PsList, a tool that lets you view detailed information about processes, and the suite is continually growing. The "Ps" prefix in PsList relates to the fact that the standard UNIX process listing command-line tool is named "ps", so I've adopted this prefix for all the tools in order to tie them together into a suite of tools named PsTools.
| Please install with chocolatey (http://nuget.org/List/Packages/chocolatey).

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
PsTools 1.2012.04.12 117114 Thursday, August 11, 2016 Approved
PsTools 1.2012.04.11 8097 Wednesday, April 11, 2012 Approved
PsTools 1.0.0.3 596 Tuesday, August 23, 2011 Unknown
PsTools 1.0.0.2 475 Tuesday, August 23, 2011 Unknown
PsTools 1.0.0.1 496 Tuesday, August 23, 2011 Unknown
PsTools 1.0 472 Tuesday, August 23, 2011 Unknown

This package has no dependencies.

Discussion for the PsTools Package

Ground Rules:

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