Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/endpointmanager/wingetbridge-factory
Powershell-Scripts based on WingetBridge (Powershell-Module) for software deployment tools like Microsoft Endpoint Manager
https://github.com/endpointmanager/wingetbridge-factory
Last synced: 5 days ago
JSON representation
Powershell-Scripts based on WingetBridge (Powershell-Module) for software deployment tools like Microsoft Endpoint Manager
- Host: GitHub
- URL: https://github.com/endpointmanager/wingetbridge-factory
- Owner: endpointmanager
- License: mit
- Created: 2021-11-14T14:32:34.000Z (almost 3 years ago)
- Default Branch: master
- Last Pushed: 2021-11-27T00:41:30.000Z (almost 3 years ago)
- Last Synced: 2024-08-01T21:58:30.940Z (3 months ago)
- Language: PowerShell
- Size: 132 KB
- Stars: 3
- Watchers: 1
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
[](https://twitter.com/PaulJezek)
# wingetbridge-factory
This repository contains Powershell-Scripts based on [WingetBridge-PSModule](https://github.com/endpointmanager/wingetbridge-powershell) to automatically provide and maintain applications in various deployment tools by using the Windows Package Manager Repository.
WingetBridge Factory creates new software packages in your deployment tool, based on a list of PackageID's that you specified in this script. You can schedule the script (e.g. on a daily basis), so that new versions of software packages will be created as soon as new versions become available in the winget repository.
## Community-driven Project
While there is only one example (for MEMCM, formerly ConfigMgr) in this repository, I'm very mind-opened in supporting a community-driven collaboration to provide more examples on how to use WingetBridge for various deployment tools like Microsoft Intune or MDT.
If you are interested in contributing, please submit a pull request (PR) or contact me on [twitter](https://twitter.com/PaulJezek).
## Compatibility
The windows package manager repository contains 2900+ software packages, but in theory only **2300+ packages can be synchronized** by using WingetBridge Factory at the moment.
Each available package contains one or more installers (for various architectures, operating systems or languages) by using different installer technologies like MSI, NULLSOFT, INNO, Legacy-Setups (EXE), MSIX, APPX and APPXBUNDLE.
Unfortunately, the winget repository does not provide a reliable detection-method before installing a package on a system. It also does not provide any app-icons (to be used in a self-service-portal like Softwarecenter).
WingetBridge Factory analyze installers **on the fly** and tries to detect a reliable detection-method and extracts an icon for some installer types.
This method will not deliver always a 100% reliable detection-method and there is room for a lot of improvements. Therefore, I recommend to verify package-creation manually (at least once per new PackageIDs added into the configuration).
The available script is intended to be used with MEMCM (aka ConfigMgr) and only supports MSI, NULLSOFT, INNO and BURN installers at the moment. However, the MEMCM-script could be extended or even modified for different software deployment tools, depending on your own scripting-skills.
## Risk of damage :warning:
I highly recommend not using WingetBridge in a production environment without validating the downloaded installers before you deploy it. (e.g. by validating the certificate of a signed installer)
# WingetBridge Factory for MEMCM
The MEMCM version of the script does not respect the "MinimumOSVersion" information provided in the winget-manifest.
The function "New-CMWingetBridgePackage" is the main-function of the MEMCM asumes that a downloaded setup is compatible with the same architecture of Windows 10 and Windows 11 and set up a requirement for it.
## Planned features
* Support for INNO installers will be available within the next few weeks (added in v1.06)
* Support for BURN (WIX Bootstrapper) installers should be available within the next few weeks (added in v1.07)
* Support for Windows app packages (appx, appxbundle, msix, msixbundle) should be available within the next few weeks
* (Optional) E-Mail notification when a new software package was created
* Automatically create supersedence (MEMCM)
Follow me on twitter and github to get notified about updates.
# Initial setup
* Download the WingetBridge-Factory-Repository as ZIP-File from [here](https://github.com/endpointmanager/wingetbridge-factory/archive/refs/heads/master.zip)
* Extract the files under "C:\Applications\WingetBridgeFactory" (path can be customized)
* Make sure you don't have any security-restrictions to load the Powershell-Module. If so, please remove any NTFS Alternate Data Streams (ADS) from the zip-file before you extract it, and set the ExecutionPolicy to Unrestricted
```ps
Unblock-File .\wingetbridge-factory-master.zip
Set-ExecutionPolicy -ExecutionPolicy Unrestricted
```
* Open the correct main-script (see "Available Scripts") and follow the instructions for the initial configuration.
## Initial Configuration
In the initial setup, you specify a list of package-IDs you want to "synchronize" the latest available version into your software deployment tool.
There are multiple ways to find PackageIDs within the winget repository:
* By using the [WingetBridge-cmdlets](https://github.com/endpointmanager/wingetbridge-powershell)
* By using the [winget-cli](https://github.com/microsoft/winget-cli)
* By using your Browser [Winstall.app](https://winstall.app/)
### # CONFIGURATION STARTS HERE
This is where the configuration starts.
* $WingetPackageIdsToSync -> Specify the list of PackageIDs you want to get maintained by WingetBridge Factory
* Other variables are described inside the script.
### # CONFIGURATION ENDS HERE
This is where the configuration ends.
If you want to modify or extend the functionality of the script, I highly recommend to modify only lines below ## MAIN CODE STARTS HERE, so you can easily migrate to a newer version as soon as it will become available.
## Requirements
The scripts in this repository, depends on several open source projects:
* [WingetBridge-Powershell-Module](https://github.com/endpointmanager/wingetbridge-powershell) (Please use the latest version)
* [7-Zip v15.05 beta**](https://sourceforge.net/projects/sevenzip/files/7-Zip/15.05/) (Required to analyze NULLSOFT installers, and to extract icons)
* [WIX Toolset](https://wixtoolset.org/) (Required to analyze MSI installers)
* [lessMSI](https://lessmsi.activescott.com/) (Required to extract icons from big MSI installers)
* [innounp](http://innounp.sourceforge.net/) (Required to analyze INNO installers, and to extract Icons)
> **newer versions of 7-Zip do not extract and decode the required NSIS (nullsoft installer script). Please use v15.05!
### Additional requirements for MEMCM:
* Configuration Manager Admin-Console needs to be installed (Script depends on ConfigurationManager.psd1)
# Available Scripts
WingetBridge-Factory_MEMCM.ps1 (Mainscript for MEMCM, formerly ConfigMgr)
WingetBridge-Factory_Shared.psm1 - Module required by all other scripts (contains shared functions)
## Credits :heart:
* The developers and contributors behind [Windows Package Manager](https://docs.microsoft.com/en-us/windows/package-manager/).
* The developers and contributors behind [WIX Toolset](https://wixtoolset.org/)
* The developers behind [innounp](http://innounp.sourceforge.net)
* Igor Pavlov and the contributors of [7-Zip](https://www.7-zip.org/)
* Scott Willeke and the contributors of [lessmsi](https://lessmsi.activescott.com/)
* Everyone who is willing to use WingetBridge Factory, so software developers realize how important it is to maintain their packages through the winget-repository.
## License (applies to WingetBridge Factory only, and not it's dependencies)
See [LICENSE](LICENSE) file for licence rights and limitations (MIT)
The author of this module is not responsible for, nor does it grant any licenses to, third-party packages.