Download, install and update the newest version of several software packages based on the powerful Evergreen module from Aaron Parker, Bronson Magnan and Trond Eric Haarvarstein and the Nevergreen module from Dan Gough https://github.com/DanGough/Nevergreen https://github.com/aaronparker/Evergreen
I'm no powershell expert, so I'm sure there is much room for improvements!
The idea is to select a client or server that periodically checks for updates and if updates are available, downloads them. This can be done every day or once a week by launching the script "Evergreen Software Updater.ps1" via scheduled task and the -noGUI parameter. You decide which software do download by launching the script once amd make your selection. The selected items are stored in a XML file. The "Evergreen Software Installer.ps1" script must be launched on your clients. If you have a golden master like in Citrix MCS/PVS environments it's sufficient to launch the script only on this machine. This can be done manually or automatic, like you prefer. Again, you decide which package gets installed by selecting the software, the selection is also stored in a XML file.
IMPORTANT: Make sure you copy ALL files and subfolders, there are some files needed for the scripts to run!
You can use the example shortcuts in the shortcut folder to lauch the scripts. Just copy the shortcuts and change the target.
If you want to update your Citrix components like PVS target device, WEM Agent or VDA you have to copy the recent Citrix files into the subfolders under the 'Citrix' folder!
- Cloud - Place the current WEM cloud agent here (like 'Citrix Workspace Environment Management Agent.exe') and place the current VDA standalone installer here (VDAServerSetup.exe)
- Current - Extract the files from the current release ISO here (the install scripts look for the right folder structure)
- LTSR - Extract the files from the current release ISO here (the install scripts look for the right folder structure)
- WEM - Place the current WEM agent here (like 'Citrix Workspace Environment Management Agent.exe')
To download and install 'MS 365 Apps' on (from) your network location you have to create a 'Configuration.xml' file with the Office 365 customization tool (https://config.office.com/). You can also use my example XML files in the subfolder of the 'MS 365 Apps-Semi Annual Channel' folder.
The updater always checks for the latest version of the Evergreen module and the script, so you don't have to do this. If there are new scripts available you have to download and replace your current scripts.
Sometimes the software version found with Evergreen differs from the installed version in the registry, that's stupid, but we can't influence that. Don't blame the Evergreen module! Let me show you an example:
MS Teams
Let's check the installed version:
(Get-ItemProperty HKLM:\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*Teams Machine*"}).DisplayVersion
The result is: 1.3.0.28779
Let's check the version with Evergreen:
(Get-MicrosoftTeams | Where-Object {$_.Architecture -eq "x64"}).Version
The result is: 1.3.00.28779
So there is one "0" more! We have to insert a "0" to the installed version to be able to compare the versions:
IF ($Teams) {$Teams = $Teams.Insert(5,'0')}
