NeverRed's focus is to provide a simple solution to keep standard software up to date without having to package it or search and compare versions on vendor sites. https://www.deyda.net/index.php/en/neverred/
NeverRed is a simple PowerShell script to download and install the latest version for several common enterprise Windows applications. The script consists a number of simple functions to use in EUC environments like:
Exactly this is where I wanted to remedy with NeverRed.
NeverRed uses several approaches to automatically get the version number and download URL for the applications.
Various strategies and PowerShell modules are used for this purpose:
There are community and commercial products that manage application deployment and updates already. This script isn't intended to compete against those.
NeverRed's focus is on a simple solution to keep standard software up to date without having to package it or search and compare versions on vendor sites.
Documentation for NeverRed, including usage examples, is located here: Documentation.
The script uses an enumerated version notation. It can be assumed that the script undergoes changes on a regular basis. The version numbering is therefore intended to make it as easy as possible to track whether you are using the current version. See the Changelog for details of each change.
The script automatically detects if it is up to date when started on a system with internet, and if it is not, an automatic update is offered.
NeverRed supports Windows PowerShell 5.1 and PowerShell 7.0+. NeverRed should work on PowerShell Core 6.x; however, I'm not actively testing on that version of PowerShell, so support cannot be guaranteed.
The NeverRed script is published to GitHub and can be found here: NeverRed. This is the best and recommend method to get NeverRed.
The script can be started directly after download in an administrative PowerShell window.
.\NeverRed.ps1
.\NeverRed.ps1 -ESFile LastSetting.txt
Adaptation of the StartNeverRed.ps1 script to the correct path and the required configuration file. Store the customized script, for example, in BIS-F under Custom Scripts.
If you have start a previous version of the script in GUI Mode, you get a message that an update is available and whether it should be executed. With the parameter -ESFile and -GUIFile the update is performed automatically.