If a user switches off a computer during a task sequence deployment the task may have the status installing in Software Center. The only way to solve this issue is to reinstall the Configuration Manager Client. You can imagine that there is a more user-friendly way.
As per SCCM 2012 build 1806 it is possible to deploy MSIX packages. In this article, I will describe all the steps that are needed to deploy a MSIX package on a Windows 10 v1809 client.
In the article Package and install a MSIX package Paint.Net 4.1.5 was packaged as a MSIX package. In Create a MSIX modification package a modification package was created to add some addins. In this article both applications will be used.
MSIX is the new packaging format to create new packages. It is aviable on Windows 10 v1809 and later. According to Microsoft packaging has never been easier. In this tutorial I will create a Paint.Net 4.1.5 package on a dedicated Hyper-V Virtual Machine. The package will be deployed with PowerShell.
In my article Package and install a MSIX package I described the steps to install a single MSIX package. In this article I will create a nodification package. Paint.Net will be modified with a package that installs some addins.
I made a script that installs all the Microsoft C++ Runtime modules. These modules can be found on the Microsoft site Latest Supported Visual C++ Downloads. On x86 only the x86 modules are installed. On x64, both x86 and x64 modules are installed.
Page 2 of 2