Brief description of your issue
As an windows administrator I want to be able to provision windows machines using WinRM, as a part of provisioning machines I'd like to install WinGet and then use it to install all other programs needed.
There doesn't seem to be any instructions for how to install WinGet with just a remote terminal (using WinRM or alternatively OpenSSH). Nor any instructions for setting up WinGet using PowerShell.
With Chocolatey I just need to run:
Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1'))
If I can't similarly automate the setup of WinGet and then use it then theres no way to replace Chocolatey with WinGet in my provisioning scripts. Which kind of make WinGet useless for most people? Is this missing functionality or just missing documentation?
Brief description of your issue
As an windows administrator I want to be able to provision windows machines using WinRM, as a part of provisioning machines I'd like to install WinGet and then use it to install all other programs needed.
There doesn't seem to be any instructions for how to install WinGet with just a remote terminal (using WinRM or alternatively OpenSSH). Nor any instructions for setting up WinGet using PowerShell.
With Chocolatey I just need to run:
If I can't similarly automate the setup of WinGet and then use it then theres no way to replace Chocolatey with WinGet in my provisioning scripts. Which kind of make WinGet useless for most people? Is this missing functionality or just missing documentation?