Hi,
We have recently purchased Habitat and was hoping there was a tool to manage Windows "Winget" on workstations, as you had announced this in one of your blogs. I have maybe missed it. Please can you point me in the right direction. Thanks.
Winget intergration
Re: Winget intergration
Oh how I like to be a half step ahead of a request!
I beleive we were in a comms a few days ago about this requests, here are some updates. I am starting to test (run through the mill) new WInGet Intergrations as we speak. I am working through most of the base issues and we have a pretty good working model in build 1.0.1.44. This means that we will have support for WinGet available in our next release. For those whom have not heard, Build 1.0.1.44 will have a new Applications Manager replacing the old one with our current CFA 3.6 plugin.
Below is a current image of the Habitat Applications Manager at the Client console view. I have enabled this client to use WinGet instead of the default Chocolatey services.
You get the same Software view as Chocolatey
You get the logs from any WinGet process
To Auto Install packages to agents, you use the same approved software list, but with WinGet Package names instead of Chocolatey package names.
Example: 7zip is a standard app available in almost any package manager. When installing it from a Chocolatey repository you would use the package name 7zip.install. On WinGet that same 7zip application installs with the package name of 7zip.7zip . WHen using Habitat Application Manager, you may have both in your global list, then approve the correct package at the client level that meats the package manager used.
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 scripts, 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 usually does not.
• Community and Packages: Chocolatey has a larger and more established community with a vast repository of packages.
I beleive we were in a comms a few days ago about this requests, here are some updates. I am starting to test (run through the mill) new WInGet Intergrations as we speak. I am working through most of the base issues and we have a pretty good working model in build 1.0.1.44. This means that we will have support for WinGet available in our next release. For those whom have not heard, Build 1.0.1.44 will have a new Applications Manager replacing the old one with our current CFA 3.6 plugin.
Below is a current image of the Habitat Applications Manager at the Client console view. I have enabled this client to use WinGet instead of the default Chocolatey services.
- Enable WinGet by checking the box under the client
- Screenshot 2024-12-06 111117.png (122.68 KiB) Viewed 480 times
You get the same Software view as Chocolatey
- Screenshot 2024-12-06 111826.png (26.74 KiB) Viewed 480 times
You get the logs from any WinGet process
- Screenshot 2024-12-06 111855.png (42.82 KiB) Viewed 480 times
To Auto Install packages to agents, you use the same approved software list, but with WinGet Package names instead of Chocolatey package names.
Example: 7zip is a standard app available in almost any package manager. When installing it from a Chocolatey repository you would use the package name 7zip.install. On WinGet that same 7zip application installs with the package name of 7zip.7zip . WHen using Habitat Application Manager, you may have both in your global list, then approve the correct package at the client level that meats the package manager used.
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 scripts, 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 usually does not.
• Community and Packages: Chocolatey has a larger and more established community with a vast repository of packages.
Re: Winget intergration
Great Thanks I will look forward to the update coming out.
Yes I think I posted to the forum before emailing yourselves. Thanks integrating the feature and quick responses.
Yes I think I posted to the forum before emailing yourselves. Thanks integrating the feature and quick responses.