Downloads:

1,257

Downloads of v 2018.05.06:

597

Last Update:

5/6/2018

Package Maintainer(s):

Software Author(s):

  • Bill Curran

Tags:

bcurran3 unofficial choco persistent packages schtasks scheduled task

(unofficial) Choco Persistent Packages (Task)

2018.05.06 | Updated: 5/6/2018

Downloads:

1,257

Downloads of v 2018.05.06:

597

Maintainer(s):

Software Author(s):

  • Bill Curran

(unofficial) Choco Persistent Packages (Task) 2018.05.06

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install (unofficial) Choco Persistent Packages (Task), run the following command from the command line or from PowerShell:

>

To upgrade (unofficial) Choco Persistent Packages (Task), run the following command from the command line or from PowerShell:

>

To uninstall (unofficial) Choco Persistent Packages (Task), 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 choco-persistent-packages -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 choco-persistent-packages -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 choco-persistent-packages installed
  win_chocolatey:
    name: choco-persistent-packages
    state: present
    version: 2018.05.06
    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 'choco-persistent-packages' do
  action    :install
  version  '2018.05.06'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: choco-persistent-packages,
    Version: 2018.05.06,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller choco-persistent-packages
{
   Name     = 'choco-persistent-packages'
   Ensure   = 'Present'
   Version  = '2018.05.06'
   Source   = 'STEP 3 URL'
}

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


package { 'choco-persistent-packages':
  provider => 'chocolatey',
  ensure   => '2018.05.06',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install choco-persistent-packages version="2018.05.06" 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 approved by moderator gep13 on 5/7/2018.

Description

#choco-persistent-packages (re)installs any missing crucial Chocolatey packages that you designate as persistant packages. Uninstall a persistent package and it will be installed again ready for use the next day.

###This package creates a Windows Scheduled Task to run "cinst $env:ChocolateyInstall\config\persistentpackages.config -y" every day at a time that you specify. And because sometimes package installations go wrong... it will also create a Windows Scheduled Task to run "taskkill /im choco.exe /f /t" to stop the Chocolatey (choco.exe) process and all child processes at a time you specify.

###WHO IS THIS FOR?
choco-persistent-packages is designed for Chocolatey Pro and Chocolatey Business licensed users who's computers are not necessarily under Active Directory Directory Services Group Policy control or other system mananagement utilities that can enforce software installation and desired state.

###WHY DO I NEED THIS?
If you have users/employees/a friend/a little brother/etc. that uninstalls programs/Chocolatey packages that you don't want uninstalled, choco-persistent-packages will (re)install those programs/Chocolatey packages that you deem necessary to keep installed. Basically you create a list of important packages and choco-persistent-packages will reinstall them every day if they are missing.

###WHY DO I NEED TO BE A CHOCOLATEY PRO OR BUSINESS USER?

You don't. But choco-persistent-packages will only work if the Chocolatey package data is missing. If a program is uninstalled outside of Chocolatey via Programs and Features this will not have any effect as Chocolatey and choco-persistent-packages will not know the program has been uninstalled. Chocolatey Pro and Business editions include a feature called Package Synchronizer - Automatic Sync which removes the Chocolatey package data when a program is uninstalled via Programs and Features. After this synchronization occurs (every execution of choco.exe), choco-persistent-packages will see the program/package missing and reinstall it at the designated time.

###INSTALL INSTRUCTIONS:
You can install choco-persistent-packages with TIME and ABORTTIME parameters to make it run daily at your preferred time. If you enter no parameters at all, choco-persistent-packages will default to run at midnight every day and abort the process at 1 AM. When entering the TIME and ABORTTIME parameters, use "Military Time." Not entering the correct format will fail the install. Please see the examples below.

###INSTALL EXAMPLES:

  • choco install choco-persistent-packages --params "'/TIME:04:00'" - (re)installs persistent packages at 4 AM and aborts at 1 AM 21 hours later.
  • choco install choco-persistent-packages --params "'/TIME:06:30 /ABORTTIME:08:30'" - (re)installs persistent packages at 6:30 AM and aborts at 8:30 AM.

####A NOTE ON DEFAULTS:

  • If you don't specify any parameters, choco-persistent-packages defaults to running daily at midnight and aborting at 1 AM. (My preference!)
  • Not specifying a TIME will always default to midnight. Not specifying an ABORTTIME will always default to 1 AM. If you're setting a TIME, be sure to also set the ABORTTIME.

###POST INSTALL INSTRUCTIONS:

  • Edit \ProgramData\Chocolatey\config\persistentpackages.config and read the comments section.

If you have a previous release of choco-persistent-packages installed, upgrading to a new version will NOT modify your current scheduled task or list of persistent packages. You will need to uninstall and re-install to take advantage of the new ABORTTIME feature.

PACKAGE NOTES


tools\chocolateyinstall.ps1
$packageName = 'choco-persistent-packages'
$toolsDir    = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$pp          = Get-PackageParameters
$TaskCommand = 'cinst $env:ChocolateyInstall\config\persistentpackages.config -y'
$CheckConfig = "$env:ChocolateyInstall\config\persistentpackages.config"

$GotTask = (&schtasks /query /tn choco-persistent-packages) 2> $null
if ($GotTask -ne $null){
   Write-Host Existing choco-persistent-packages scheduled task found. Keeping existing scheduled task and persistentpackages.config file. If you want to change the task runtime or abort time, uninstall and reinstall the package. Uninstalling the package will not delete your persistentpackages.config file. -foreground magenta -background blue
   exit
  }

if (Test-Path $CheckConfig){
    Remove-Item "$toolsDir\persistentpackages.config"
    } else {
      Move-Item "$toolsDir\persistentpackages.config" "$env:ChocolateyInstall\config" -Force -ErrorAction 'SilentlyContinue'
	  $WhoAmI=whoami
      $Acl = Get-Acl "$env:ChocolateyInstall\config\persistentpackages.config"
      $Ar = New-Object  system.security.accesscontrol.filesystemaccessrule($WhoAmI,"FullControl","Allow")
      $Acl.SetAccessRule($Ar)
      Set-Acl "$env:ChocolateyInstall\config\persistentpackages.config" $Acl
    }
	
Write-Host "" 
Write-Host "choco-persistent-packages Summary:" -foreground magenta	

if ($pp["Time"] -eq $null -or $pp["Time"] -eq ''){
     $RunTime = "00:00"
     Write-Host " * TIME NOT specified, defaulting to MIDNIGHT." -foreground magenta
    } else {
      $RunTime = $pp["Time"]
	  Write-Host " * TIME specified as $RunTime." -foreground magenta
	 }

if ($pp["ABORTTIME"] -eq $null -or $pp["ABORTTIME"] -eq ''){
      Write-Host " * ABORTTIME NOT specified, defaulting to 1 AM." -foreground magenta
	  $AbortTime = "01:00"
    } else {
	  $AbortTime = $pp["ABORTTIME"]
	  Write-Host " * ABORTTIME specified as $AbortTime." -foreground magenta
    } 	 

SchTasks /Create /SC DAILY /RU SYSTEM /RL HIGHEST /TN "choco-persistent-packages" /TR $TaskCommand /ST $RunTime /F
SchTasks /query /tn "choco-persistent-packages"
SchTasks /CREATE /SC DAILY /RU SYSTEM /RL HIGHEST /TN choco-persistent-packages-abort /TR "taskkill /im choco.exe /f /t" /ST $AbortTime /F
SchTasks /query /tn choco-persistent-packages-abort
Write-Host " * To configure, edit $env:ChocolateyInstall\config\persistentpackages.config and read the comments section." -foreground magenta
Start-Sleep -s 10

tools\chocolateyuninstall.ps1
#persistentpackages.config file purposely not deleted as not to lose configuration on a re-installation
$packageName = 'choco-persistent-packages'

SchTasks /Delete /TN “choco-persistent-packages” /F
SchTasks /Delete /TN choco-persistent-packages-abort /F

tools\persistentpackages.config
<?xml version="1.0" encoding="utf-8"?>
<packages>
</packages>

<!--
EDIT THIS FILE ABOVE TO DESIGNATE YOUR PERSISTENT PACKAGES

Edit between the package tags above and insert your list of persistent packages in any of the following formats:

<package id="packagename" />
<package id="packagename" version="1.23" />
<package id="packagename" version="1.23" source="someLocation" />

These Chocolatey packages will be (re)installed on the schedule you specificied during installation of choco-persistent-packages.

If any package is already installed, Chocolatey will attempt and just throw the error packagename vx.x already installed and waste a few seconds of your computer's time. If it's not there, it will be installed.

Official Chocolatey packages.config information can be referenced here: 
https://chocolatey.github.io/usage.html#the-packagesconfig-file

If you want to auto-generate a package list of all your existing packages you can do so with my choco-package-list-backup package. Then just copy the packages.config to \ProgramData\Chocolatey\config and rename packages.config to persistentpackages.config. I recommend doing this and then editing out all non-essential packages.

EDIT THIS FILE ABOVE TO DESIGNATE YOUR PERSISTENT PACKAGES
-->

</xml>

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
(unofficial) Choco Persistent Packages (Task) 2018.04.23 172 Thursday, April 26, 2018 Approved
(unofficial) choco persistent packages (Task) 2017.08.20.01 215 Friday, January 5, 2018 Approved
(unofficial) choco persistent packages (Task) 2017.08.20 273 Sunday, August 20, 2017 Approved
Discussion for the (unofficial) Choco Persistent Packages (Task) Package

Ground Rules:

  • This discussion is only about (unofficial) Choco Persistent Packages (Task) and the (unofficial) Choco Persistent Packages (Task) 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 (unofficial) Choco Persistent Packages (Task), 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