WinGet Support in 3.7
Posted: Fri Dec 13, 2024 4:48 pm
New WinGet Support in 3.7
As of Build 3.7.0.1, we have updated to the Chocolatey for Automate 3.7 code base. This includes easier management and distribution of workloads and improved automated package installations, updates, and removals. In this version, we have added support for WinGet and Chocolatey to coexist inside your RMM environment, and to be configured at the client level, allowing you to control which package manager is used for each client.
Windows Package Manager Support
Chocolatey For Automate offers you two package managers that work on Windows Agents. Chocolatey from Chocolatey.org and Microsoft's WinGet service. Either can be configure as the default package manager to use for any client under managerment. The approved packages controlers can be used for both package managers. Only approve client level applications that match you package manager.
Client View - Installed WinGet Packages
WinGet is available under the client console view. By default any enabled client will use Chocolatey by default. If you want the client to use WinGet instead, select the Use WinGet check box. This will force the client to use Winget for all future updates and installs. It will scan using WinGet for all future package status reports and will display the WinGet logs instead of Chocolatey Logs.
Client View - WInGet Logs
WinGet Requirments
By the nature of WinGet and its user level requirments, we are limited inside of Automate scripting on how WinGet can be executed. WinGet wants to manage software packages at the user level and with an expected user profile on the agent. To be able to do this using Automate scription we have to check for an logged in user console then launch a command to that console. The caviot is for scans and updates to take place, a use must be logged into console. A scan is very lgiht and quick, you can increase the scan rate to catch logged out systems more offten during the day by adjusting the Chocolatey scan Group schedule.
For successful management of WinGet, we download and deploy the official WinGet package manager and the Microsoft WinGet PowerShell Modue to the allUsers profile in Powershell. If you are having issues with scans and logs, make sure the agent has these things installed.
For those that want to know, here's a basic comparison between Chocolatey and WinGet:
Chocolatey
• Developer: Community-driven, started by Rob Reynolds in 2011.
• Installation: Uses .nupkg files for packaging.
• Capabilities: Can run PowerShell scripts, allowing for more complex installation processes. Supports installing software from community repositories and custom repositories2.
• Permissions: Typically requires administrative privileges to install software.
• Community Support: Large and mature community with thousands of packages available.
• GUI: Has a graphical user interface (GUI) version in addition to the command-line tool.
WinGet
• Developer: Developed by Microsoft, introduced in 2020.
• Installation: Uses .msix files for packaging.
• Capabilities: Primarily focuses on installing software from the Microsoft Store and a winget-specific community repository. Does not support running PowerShell scripts for installation4.
• Permissions: Generally, does not require administrative privileges for installation.
• Community Support: Growing community, but not as extensive as Chocolatey's.
• GUI: Only available as a command-line tool.
Key Differences
• Flexibility: Chocolatey offers more flexibility with its ability to run PowerShell using the agent service, making it suitable for more complex installations.
• Ease of Use: WinGet is simpler to use for basic installations, especially for software available in the Microsoft Store.
• Permissions: Chocolatey often requires admin rights, while WinGet does not. WinGet must run as the user logged into console.
• Community and Packages: Chocolatey has a larger and more established community with a vast repository of packages but may impose bandwidth limits where WinGet has a smaller repo size but should not have any limits imposed.
WinGet Windows Server Support
Yes, **WinGet can run on Windows Server**, but there are some considerations to keep in mind:
1. Windows Server 2025: WinGet is officially included in Windows Server 2025 as part of the App Installer. You can use WinGet to install, update, and uninstall applications on this version.
2. Windows Server 2022 and Earlier: WinGet is not officially supported on Windows Server 2022 or earlier versions. However, it can be installed manually in experimental mode. You may need to resolve dependencies manually, such as VCLibs 14 and UI.Xaml.2.7.
3. Server Core: WinGet is not supported on Windows Server Core. It requires the Desktop Experience feature to be installed.
If you're using Windows Server 2025 or later, you should be able to use WinGet without any issues. For older versions, you might need to manually install and configure WinGet.
When Enabling WInGet, You will need to have the "Use WinGet", "Chocolatey Approved", and "Chocolatey Installed" EDFs selected for each agent you want to use WinGet. WinGet is exchanged for Chocolatey during Installs, scans, and log collection.
As of Build 3.7.0.1, we have updated to the Chocolatey for Automate 3.7 code base. This includes easier management and distribution of workloads and improved automated package installations, updates, and removals. In this version, we have added support for WinGet and Chocolatey to coexist inside your RMM environment, and to be configured at the client level, allowing you to control which package manager is used for each client.
Windows Package Manager Support
Chocolatey For Automate offers you two package managers that work on Windows Agents. Chocolatey from Chocolatey.org and Microsoft's WinGet service. Either can be configure as the default package manager to use for any client under managerment. The approved packages controlers can be used for both package managers. Only approve client level applications that match you package manager.
Client View - Installed WinGet Packages
WinGet is available under the client console view. By default any enabled client will use Chocolatey by default. If you want the client to use WinGet instead, select the Use WinGet check box. This will force the client to use Winget for all future updates and installs. It will scan using WinGet for all future package status reports and will display the WinGet logs instead of Chocolatey Logs.
- ClientView_Main_winget.png (93.3 KiB) Viewed 3218 times
Client View - WInGet Logs
- ClientView_Main_winget-logsTab.png (98.72 KiB) Viewed 3218 times
WinGet Requirments
By the nature of WinGet and its user level requirments, we are limited inside of Automate scripting on how WinGet can be executed. WinGet wants to manage software packages at the user level and with an expected user profile on the agent. To be able to do this using Automate scription we have to check for an logged in user console then launch a command to that console. The caviot is for scans and updates to take place, a use must be logged into console. A scan is very lgiht and quick, you can increase the scan rate to catch logged out systems more offten during the day by adjusting the Chocolatey scan Group schedule.
For successful management of WinGet, we download and deploy the official WinGet package manager and the Microsoft WinGet PowerShell Modue to the allUsers profile in Powershell. If you are having issues with scans and logs, make sure the agent has these things installed.
For those that want to know, here's a basic comparison between Chocolatey and WinGet:
Chocolatey
• Developer: Community-driven, started by Rob Reynolds in 2011.
• Installation: Uses .nupkg files for packaging.
• Capabilities: Can run PowerShell scripts, allowing for more complex installation processes. Supports installing software from community repositories and custom repositories2.
• Permissions: Typically requires administrative privileges to install software.
• Community Support: Large and mature community with thousands of packages available.
• GUI: Has a graphical user interface (GUI) version in addition to the command-line tool.
WinGet
• Developer: Developed by Microsoft, introduced in 2020.
• Installation: Uses .msix files for packaging.
• Capabilities: Primarily focuses on installing software from the Microsoft Store and a winget-specific community repository. Does not support running PowerShell scripts for installation4.
• Permissions: Generally, does not require administrative privileges for installation.
• Community Support: Growing community, but not as extensive as Chocolatey's.
• GUI: Only available as a command-line tool.
Key Differences
• Flexibility: Chocolatey offers more flexibility with its ability to run PowerShell using the agent service, making it suitable for more complex installations.
• Ease of Use: WinGet is simpler to use for basic installations, especially for software available in the Microsoft Store.
• Permissions: Chocolatey often requires admin rights, while WinGet does not. WinGet must run as the user logged into console.
• Community and Packages: Chocolatey has a larger and more established community with a vast repository of packages but may impose bandwidth limits where WinGet has a smaller repo size but should not have any limits imposed.
WinGet Windows Server Support
Yes, **WinGet can run on Windows Server**, but there are some considerations to keep in mind:
1. Windows Server 2025: WinGet is officially included in Windows Server 2025 as part of the App Installer. You can use WinGet to install, update, and uninstall applications on this version.
2. Windows Server 2022 and Earlier: WinGet is not officially supported on Windows Server 2022 or earlier versions. However, it can be installed manually in experimental mode. You may need to resolve dependencies manually, such as VCLibs 14 and UI.Xaml.2.7.
3. Server Core: WinGet is not supported on Windows Server Core. It requires the Desktop Experience feature to be installed.
If you're using Windows Server 2025 or later, you should be able to use WinGet without any issues. For older versions, you might need to manually install and configure WinGet.
When Enabling WInGet, You will need to have the "Use WinGet", "Chocolatey Approved", and "Chocolatey Installed" EDFs selected for each agent you want to use WinGet. WinGet is exchanged for Chocolatey during Installs, scans, and log collection.