Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Develop Intune integration #215

Closed
chritea opened this issue May 19, 2020 · 28 comments
Closed

Develop Intune integration #215

chritea opened this issue May 19, 2020 · 28 comments
Labels
Issue-Feature This is a feature request for the Windows Package Manager client.
Milestone

Comments

@chritea
Copy link

chritea commented May 19, 2020

Description of the new feature/enhancement

As an Enterprise Administrator I want to be able to select and deploy WinGet packages directly from Intune like I can with the Microsoft Store for Business. An auto update mechanism exists which helps me to stay current with 3rd party software on my devices.

@chritea chritea added the Issue-Feature This is a feature request for the Windows Package Manager client. label May 19, 2020
@JoshPhillips59
Copy link

Seconded

@pl4nty
Copy link

pl4nty commented May 20, 2020

Related to #151, Intune integration would need DO support (and Microsoft Connected Cache too?)

@denelon
Copy link
Contributor

denelon commented May 22, 2020

This looks like it might be similar to #118 and #213. I'm fine keeping this open to look at specific needs for Intune.

@denelon denelon added this to the Package Manager Backlog milestone May 23, 2020
@nach1man
Copy link

nach1man commented Oct 1, 2020

This is something that would greatly benefit our company as we attempt to manage multiple applications being pushed out via Intune. Having to automate a whole workflow of checking the package version, pulling the new version, if it's MSI then push directly via Intune, else if it's EXE then use the Win32 Content Prep Tool and then pushing via Intune is proving to be quite an endeavor. Looking at Chocolatey, they recommend the internalization of packages (totally understandable), but still, it doesn't fully integrate with Intune. I highly support a WinGet-Intune integration of even the most basic proportion.

@sjansen1
Copy link

sjansen1 commented Aug 4, 2021

Please implement this, packaging is such a time consuming task with all the different types of installers, having access to winget would be a big plus.

@Simpuhl
Copy link

Simpuhl commented Jan 25, 2022

2022, any updates on this ?

@denelon
Copy link
Contributor

denelon commented Jan 26, 2022

According to the blog post, first half of 2022. It's likely to be closer to the middle of the year.

@roconnor04
Copy link

Really hope this comes sooner rather than later.

@denelon
Copy link
Contributor

denelon commented Feb 9, 2022

Work is in progress.

Related to:

@Romanitho
Copy link

To wait for official support, we have this
https://github.com/Romanitho/Winget-Install

@larsuhartmann
Copy link

Really hoping on this - are there any updates regarding the timeframe we can expect it?

@janne-tech
Copy link

is there any update intune preview H1 ?

@denelon
Copy link
Contributor

denelon commented Jul 1, 2022

We are actively working on the Intune integration via Windows Package Manager. The Intune team will determine when they are going to have a preview. I'll see if anything has been published. If you are interested, send me an e-mail and I will forward the request to the Intune team.

@Romanitho
Copy link

Let's support PowerShell first, no ? 😋
Then, it will be naively supported 😅

@denelon
Copy link
Contributor

denelon commented Jul 28, 2022

@denelon
Copy link
Contributor

denelon commented Oct 26, 2022

Latest update: https://www.youtube.com/watch?v=11ezQMwnR_4

@RaffTechAU
Copy link

Is there any information as to when WinGet/Intune Integration will be in Preview and whether Windows 10 will be supported?

@kornflex
Copy link

To wait for official support, we have this https://github.com/Romanitho/Winget-Install

I tried :
winget installed as local system , winget.exe is in the directory.
When I try to install "kiosk browser" : nothing. check.ps1 return an error in intune reporting.

When I try by myself to install package as local system, winget do nothing : no error, command is launch and I get C: prompt

I try on windows 20h2

@kornflex
Copy link

Latest update: https://www.youtube.com/watch?v=11ezQMwnR_4

In the video, they can force install in "affection"
In my intune, I just have in "affectation" : "available for devices" only

@denelon
Copy link
Contributor

denelon commented Nov 30, 2022

Updates to Windows App Management in Intune with Winget

https://www.youtube.com/watch?v=QtftJQn9WYQ

@denelon
Copy link
Contributor

denelon commented Feb 8, 2023

We've published a NuGet package with "in process" access to talk to the WinGet COM APIs. We're still working on documentation to help explain how the Integration with Intune works so others can also leverage the same mechanism for MDM integration.

As WinGet is delivered via MSIX, the system level access requires additional effort to enable.

@byjrack
Copy link

byjrack commented Apr 12, 2023

Looking forward to having a more first party experience for adding winget entries to the Company Portal similar to the MSStore integration added.

Also would like to see Intune expose a winget REST source that mirrored Company Portal so users can use the cli to pull in things they want. May have some limits based on scoping etc, but have them work better together with fewer registries.

@denelon
Copy link
Contributor

denelon commented Jun 8, 2023

We've provided the full capabilities for Intune to leverage WinGet. We will continue adding new capabilities via the COM APIs as we develop new functionality in Windows Package Manager.

@denelon denelon closed this as completed Jun 8, 2023
@byjrack
Copy link

byjrack commented Jun 12, 2023

@denelon are you aware of a public Issue tracker on the Intune side where we can keep an eye on their progress? Not a winget thing, but I know our biggest issue has been elevating the user context for apps that need it. Moving to machine via SYSTEM context can be done with PATH work, but normal Logs etc I find break in the client.

@denelon
Copy link
Contributor

denelon commented Jun 12, 2023

@byjrack, I'm not aware of a public issue tracker for them. I'll forward your request and see what we can do here.

@denelon denelon modified the milestones: Backlog-Client, v1.6 Client Jun 13, 2023
@SorenLundt
Copy link

SorenLundt commented Oct 30, 2023

Would this allow us to install any WIn32App from winget-pkgs repo ?

So far I have been using this to integrate with InTune:
https://github.com/SorenLundt/WinGet-Wrapper

@byjrack
Copy link

byjrack commented Oct 30, 2023

Yup I think we all use some sort of variant of that today, but it's definitely not a first party option.

Expectation is that it acts more like the experience with Store apps.

I am also trying to figure out if there is a method to use it via the existing COM interface implementation as well. Will still need some scripting, but maybe simplify some of the integration in scripts.

nidietr-MSFT added a commit to nidietr-MSFT/winget-cli that referenced this issue Dec 6, 2024
44d81dc8 Using early-return in UrlBuilder::GetQuery()
9e9b27e3 Fixing "Use of string after lifetime ends"
21bf6b98 Adding functional proxy tests
46388eaa Adding a ProxyServer implementation
7a0bfbec Exposing Path and Query via UrlBuilder
b2014df3 Adding unit tests for proxy validation
cdd840b0 Adding proxy input string support
216210ab Adding required permissions to enable uploading of CodeQL results (microsoft#214)
fb953d6e Bump github/codeql-action from 2 to 3 (microsoft#215)
52af7124 Enabling CodeQL scanning (microsoft#211)
e555d764 Bump clang-format from 18.1.5 to 19.1.1 (microsoft#210)
ab8f0e72 Setup: improving build tools installation (microsoft#207)

git-subtree-dir: src/SfsClient/sfs-client
git-subtree-split: 44d81dc8e7614c0be8777db22431e5065aa7a6b8
nidietr-MSFT added a commit to nidietr-MSFT/winget-cli that referenced this issue Dec 6, 2024
c639a506 Adding support for a custom proxy input (microsoft#218)
258d189b Improve logging when the content type is wrong (microsoft#221)
216210ab Adding required permissions to enable uploading of CodeQL results (microsoft#214)
fb953d6e Bump github/codeql-action from 2 to 3 (microsoft#215)
52af7124 Enabling CodeQL scanning (microsoft#211)
e555d764 Bump clang-format from 18.1.5 to 19.1.1 (microsoft#210)
ab8f0e72 Setup: improving build tools installation (microsoft#207)

git-subtree-dir: src/SfsClient/sfs-client
git-subtree-split: c639a506e712dbd29ca7ca0c78d5216658e78748
nidietr-MSFT added a commit to nidietr-MSFT/winget-cli that referenced this issue Dec 10, 2024
0e27525d Bumping version to 1.1.0 (microsoft#222)
c639a506 Adding support for a custom proxy input (microsoft#218)
258d189b Improve logging when the content type is wrong (microsoft#221)
216210ab Adding required permissions to enable uploading of CodeQL results (microsoft#214)
fb953d6e Bump github/codeql-action from 2 to 3 (microsoft#215)
52af7124 Enabling CodeQL scanning (microsoft#211)
e555d764 Bump clang-format from 18.1.5 to 19.1.1 (microsoft#210)
ab8f0e72 Setup: improving build tools installation (microsoft#207)

git-subtree-dir: src/SfsClient/sfs-client
git-subtree-split: 0e27525d597c730e71646fd0b15bdc8c8503f24d
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature This is a feature request for the Windows Package Manager client.
Projects
None yet
Development

No branches or pull requests