NSSM - the Non-Sucking Service Manager 2.16.0 for Windows – A Quick Download for a Faster PC.

Download NSSM - the Non-Sucking Service Manager 2.16.0

Thumbnails

Get NSSM - the Non-Sucking Service Manager 2.16.0
NSSM - the Non-Sucking Service Manager 2.16.0

This constitutes not its latest version of NSSM - the Non-Sucking Service Strategist available.

• 1
• 2
• 3

Some Checks Have Missed the mark or Are Not Yet Complete

Not All Studies Have Passed

Hide Checks Hide Checks

Validation Testing Unknown

Verification Testing Unknown

Scan Testing Successful:

No detections found in any package files

Details

• Generic
• Individual
• Ansible
• P.S. DSC

Add through Script Builder Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

• Position
• Upgrade
• Decommission

To arrange NSSM - the Non-Sucking Support Manager, run the following command from the command line or from PowerShell:

>

To upgrade NSSM - the Non-Sucking Service Manager, run the following command extracted from whose command line or at PowerShell:

>

To uninstall NSSM - the Non-Sucking Service Manager, run that following command from either command line or from PowerShell:

>

Deployment System:

1. Engage My Intrinsic Repository Url

(this should contemplate similar to https://community.chocolatey.org/api/v2/)

2. Setup Your Environment

1. Ensure that individual are set for organizational deployment

Please see the organizational deployment guide

You can also just download the package on top of that push it to a repository Download

Preference 2: Internalized Crate (Reliable, Scalable)

• Open-ended Authority

  • Download the package:

    Retrieve
  • Follow manual internalization instructions
• Package Internalizer (C4B)
  • Run: (additional options) choco download nssm --internalize --version=2.16.0 --source=https://community.chocolatey.org/api/v2/
  • For collection and dependencies run: choco press forward --source="'INTERNAL REPO URL'"
  • Automate package internalization

3. Copy This person's Script

choco upgrade nssm -y --source="'INTERNAL REPO URL'" --version="'2.16.0'" [other options]

See options you can pass to upgrade.

See best principles for scripting.

If yourselves do use a PowerShell script, use one following to ensure inferior exit codes operate expressed as failures:

choco upgrade nssm -y --source="'INTERNAL REPO URL'" --version="'2.16.0'" $exitCode = $LASTEXITCODE Write-Verbose "Exit code was $exitCode" $validExitCodes = @(0, 1605, 1614, 1641, 3010) if ($validExitCodes -contains $exitCode) { Departure 0 } Disembarkation $exitCode - name: Integrate nssm win_chocolatey: name: nssm design: '2.16.0' source: INTERNAL REPO URL state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

chocolatey_package 'nssm' do action :install source 'INTERNAL REPO URL' version '2.16.0' end

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

cChocoPackageInstaller nssm { Name = "nssm" Version = "2.16.0" Provider = "INTERNAL REPO URL" }

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

WARNING

This package was submitted prior to moderation and has not been approved. While it is likely safe for you, on the scene is more risk involved.

Description

nssm shows a attention helper by which doesn't suck. srvany on top of contrasting service assistant programs suck because they don't handle misstep of the instrument running as a service. On the assumption that you consume such every program you may consider selected service listed as started when in fact the application has died. nssm monitors the proceeding service and will restart the event granted that it dies. With nssm you perceive that if a service says it's flying, it really is. Alternatively, if your application is well-behaved you shall configure nssm by absolve all responsibility for reinstating it and let Viewports take attention in connection with recovery actions.

nssm logs its progress to no system Event Log so you can acquire multiple idea of why one application isn't behaving as it should.

nssm also qualities single graphical service installation and removal facility. Admittedly this does suck. MYSELF hate struggling to make GUIs...

Folders Viral agent Scan Results

Log in or click on link to see number in reference to positives.

• NSSM.2.16.0.nupkg (9f2f33538e79) - ## / 58
• nssm-2.16.zip (514d54efd6aa) - ## / 55

In cases at the moment when actual online threats remains found, the packages are subject to removal. Software sometimes has false positives. Moderators do unseen necessarily validate the safety of the underlying software, no more than that a package retrieves software from the accepted distribution point and/or validate embedded software against governmental distribution point (where distribution rights allow redistribution).

Version History Add to Builder Version Downloads Last Updated Degree NSSM - the Non-Sucking Service Organizer 2.24.101.20180116 1598450 Tuesday, January 16, 2018 Certified NSSM - the Non-Sucking Service Manager 2.24.101 10851 Workweek opener, Last days of the year 25, 2017 Approved NSSM - the Non-Sucking Service Manager 2.24.101-g897c7ad 2265 Workday one, Long days 19, 2017 Approved NSSM - the Non-Sucking Service Manager 2.24.0.20170619 65960 Monday, June 19, 2017 Approved NSSM - that Non-Sucking Service Manager 2.24.0.20161223 41319 Friday, December 23, 2016 Approved NSSM - the Non-Sucking Service Manager 2.24.0.20161221 1645 End of the workweek, December 22, 2016 Approved NSSM - each Non-Sucking Service Manager 2.24.0 68264 Recovery day, September 14, 2014 Approved NSSM - the Non-Sucking Service Manager 2.21.1.0 5358 Thursday, December 12, 2013 Unrevealed NSSM - an Non-Sucking Service Manager 2.16.0 2634 Day after Sunday, September 23, 2013 Unknown Dependencies

This package has no dependencies.

Discussion for an NSSM - the Non-Sucking Service Principal Package">Discussion for the NSSM - the Non-Sucking Service Manager Package

Ground Rules:

This discussion look forward to drag over multiple generations. Provided that you enjoy a comment about a particular release candidate, if you would note that in your comments.

Tell us what you love about the package or NSSM - the Non-Sucking Service Chairperson, if you prefer describe our partnership what needs improvement.

Share your experiences with the package, or extra architecture or gotchas that you've found.