Skip to content

Why

Evergreen's focus is on integration with PowerShell as a simple solution to provide application version numbers and download URLs. This has many use cases, including:

  • Integration with Azure DevOps or Packer to create evergreen machine images on-premises, in Azure, AWS, or other cloud platforms
  • Import applications into Microsoft Endpoint Manager - keep the Microsoft Deployment Toolkit, Configuration Manager or Microsoft Intune up to date with the latest versions of applications
  • Validating or auditing a desktop image to ensure the current version of an application is installed
  • Audit installed application versions in an image or a Windows desktop
  • Create a library of application installers - by regularly running Evergreen functions, you can retrieve and download the current version of an application and store it in an application directory structure for later use
  • Track application updates to stay on top of new releases
  • Submitting manifests to Winget or Chocolatey or similar - Evergreen can return an object with a version number and download URL that can be used to construct manifests for the most recent versions

There are several community and commercial solutions that manage application deployment and updates already. This module isn't intended to compete against those, and Evergreen isn't intended to be a fully featured package manager for Windows.

Evergreen can be complementary to 3rd party solutions - for example, Evergreen can be used with the Chocolatey Automatic Package Updater Module to find the latest version of an application and then create and submit a Chocolatey package, or it can be used to create a Windows Package Manager manifest (see a sample script here: New-WinGetManifest.ps1).