Intune Enterprise App Catalog - Win32 Apps pre-created for you!

[@divyasuman6275]

if an application has multiple exe or files to install then in that case i will create a ps1 file that will execute all exe or msi but how many .intunewin file needs to be created and can we select .intunewin file while creating win32 app??

[@IntuneVitaDoctrina]

If you have multiple exe/mi for the same software, then you can create just one .intunewin file and call the from one PS1 file. If you want to separate the files you can do multiple .intunewin files but each Win32 app can only have ONE .intunewin file, you can with dependency link Win32 apps so they install in correct order.

[@Mikey-qe1hy]

Are you able to show if the supercedence works and if the app is self service how it would update the app for the existing users that have it installed.

[@IntuneVitaDoctrina]

That is a really good question, you don't see Supersedence when creating the app, but you see it after when you go edit and it works like normal Win32 App, same goes for update the app for existing users which would depend on the software, if it accept to update to newer without uninstalling first etc which it should, unless it was installed 32-bit and you push 64-bit maybe, that varies depending on software, have to test case by case, I would estimate most would work, nothing different than from a normal Win32 app except you are limited to only the run command part, no script and do checks.

[@olegproscurchin8200]

Great one. I think the new detection method option is to make sure the app still upgrade after the first upgrade (second and up), as technically after first upgrade your version will be equal or greater, so I think that last option is to update dynamically detection method version with the latest which is same as the EXE 😉

[@IntuneVitaDoctrina]

thanks, and that would make sense why it is located in the Detection rule/method part of the App wizard! interesting feature.

[@Mrdnyaneshwarmane]

Please create app packing video on SAP GUI

[@ThomasBoling-m9g]

Have you confirmed what happens if you only use 1 license to create the packages? Does the end user not see the app?

[@IntuneVitaDoctrina]

:) that is very clever thinking of you, but yeah Microsoft went around this problem by creating another type, instead of Win32 app, it is called "Windows catalog app (Win32)" so yeah user must have license for it to accept that type.

[@elanradkin578]

Great video, do you think other package managers like Chocolaty can be as effective for app deployment as Winget and Enterprise?

[@IntuneVitaDoctrina]

also a good question, I would say "yes" for that, if you got experience and skills in Chocolaty, for use that instead, if you are new to both, I would recommend Winget for the simple reason it is already in the OS system and more or less ready to use out of the box.

[@danzirulez]

Now we have yet another way to package apps and they really don't have much felxibility. Same with winget. You get a basic package without much modification. So far I still feel that the most flexible is PSADT with intunewin into a win32 app. And there's a well known easy to use wrapper, and one could do ANY customization, and user experience, etc.

[@IntuneVitaDoctrina]

Intune Enterprise App Catalog does not have a lot of flexibility, that is basically for companies that doesn't have staff skilled in creating intunewin file. Winget is still very powerful, you can use that together with PS App Deployment Toolkit, or in your own .PS1 script make it do whatever you want, copy a config file, write a registry key, stop a service.

[@danzirulez]

@@IntuneVitaDoctrina yes, exactly what we ended up with. Nevertheless, winget fills a gap that's been there for a long time :)

[@IntuneVitaDoctrina]

That a nice combo! Winget with PS App Deployment Toolkit together :)

[@Samwhiteland2011]

You already taught me how to do Winget properly 😂 Why would I need this? it seems be lacking in some pretty key enterprise areas like Abobe and Autodesk. At current I dont see this offering much value for the cost of the licence. It might be something I check back on the apps list periodically to see if it might justify the cost

[@IntuneVitaDoctrina]

heheheh YOU don't need this :) , if you can do Winget and possible MSI installations this is not for you :) this is for companies that doesn't have invested in their staff to package. IT is new so hopefully it gets more apps to the list, but yeah it is for companies that doesn't have inhouse packagers

[@ferryknol9582]

Nice video, but what method do you prefer to use? This new Enterpise App Catalog solution or the WinGet script method you describe in kzbin.info/www/bejne/aGPKnHmJdq6MkKs I would assume the WinGet script method.

[@IntuneVitaDoctrina]

Thanks, I prefer Winget and package msi/exe myself :) but it is good to know/learn all aspects of Intune (the force (Star Wars reference LOL)) Maybe someone will come to you one day and ask "Hey I don't know howto package in Intune, how can I still deploy software" then you could mention this and Store Apps of course