Search This Blog

Friday, March 12, 2021

MSIX Modern Packaging – Part 5

clip_image002

 

Introduction

In the last “MSIX Modern Packaging – Part 4” we did some ninja tricks to be able to use context menu to right click a file and open with Notepad++ captured into MSIX. As you probably also experienced, context menus are something that are not going very well in MSIX. YET. Let’s see if the team behind, can do some magic to fix that in the future.

In this chapter it is time to see how we can centrally deploy this application.

Requirements

  • Microsoft Endpoint Manager (Configuration Manager or Intune)

Importing MSIX to MEMCM

Startup Configuration manager console

clip_image004

 

Click on Software Library

clip_image006

 

Find Application Management and right click Applications

clip_image008

 

Create Application

clip_image009

 

Choose Manually to specify the application information and click next

clip_image011

 

Fill in information and click Next

clip_image013

 

Fill in information and click Next

clip_image015

 

Click Add

clip_image017

 

Choose MSIX in the dropdown and browse for your MSIX file

clip_image019

 

Click Next

clip_image021

 

Information will be taken from the package. Click next

clip_image023

 

If not chosen already,  limit operation system requirement to Windows 10. Click Next

clip_image025

 

We have no dependencies. Click Next

clip_image027

 

Click Next

clip_image029

 

Press Close

clip_image031

 

Press Next

clip_image033

 

Click Next

clip_image035

 

Press close

clip_image037

 

Right click and deploy

clip_image039

 

In collection choose “All Users” and click next

clip_image041

 

Add content to your distribution point and click next

clip_image043

 

Install and make it available. Click Next (You could also make it required to push the software, but you should never do that to all devices or all users before thorough testing.)

clip_image045

 

Click Next

clip_image047

 

Click Next

clip_image049

 

Click Next

clip_image051

 

Click Next

clip_image053

 

Well that was an awful lot of steps just to create an application Click Close

clip_image055

 

On our client we now see the software available

clip_image057

 

Install it

clip_image059

clip_image061

Importing MSIX to Microsoft Intune

Start by going to https://endpoint.microsoft.com/

Choose Apps

clip_image063

 

Click Windows

clip_image065

 

Click Add

clip_image067

 

Choose Line-of-business app and click select

clip_image069

 

Select app package file

clip_image071

 

Browse for you package and click ok

clip_image073

 

Add information as you go along. It is always a good idea to include logo to let your users be able to find the product faster when going into the company portal. Click Next

clip_image075

 

Next

clip_image077

 

We will make the app available for all users in the company portal

clip_image079

 

Click Create

clip_image081

 

By going through this app import you can quickly see the how the team have simplified and improved the experience.

Going to the company portal I now see my app coming from Intune.

(The reason you see also the Notepad ++ from Configuration Manager is because I have a Co-managed environment where I flipped the switch for applications. I can then have the best of both worlds.)

clip_image083

Summary

Going through the 2 examples of how to centrally deploy MSIX packages, it is clear to all that Microsoft have upgraded the experience when adding MSIX applications to Intune. Configuration manager had 24 steps where Intune had 8 and a much leaner version of creating packages for deployment.

Stay tuned for part 6

No comments:

Post a Comment