AppV-MSI-SCCM

UWP [Desktop App Converter]

Posted on April 4, 2016 Updated on April 7, 2016

Project Centennial – Technology that converts existing Win32/.Net Applications, Games, Web Apps into UWP without major change in the Code. It’s been informed by Microsoft that this process will be carried out by a tool called Desktop App Converter which will be made available in the Windows.

• Why to Convert:
  One app that works great on all the devices that runs Windows 10 such as Laptops, Mobiles, XBOX & so.
  You don’t have to re-write the code to make such an app rather you can convert the existing ones without major changes in the code.
• What cannot be Converted:
  System NT Services
  The apps that has Kernel Integrations [Kernel Drivers]
  Note: Not Limited. The above are the ones that were discussed in the Build 2016.
• Requirements:
  Source Binaries for the app to be converted.
  OS Core Image which will be used for Capturing.
  Silent Parameters that can be used by the Converter to run the app unattended.
• How to Convert:
  The Desktop App Converter has 2 important files[DesktopAppConverter.PS1 & DesktopAppConverter.CMD] that carries the conversion process. Have to run 1 among any of the 2 files with the parameters below,
  [Path to PS1 or .CMD] -Installer [Path to Installer of Target App] -InstallerArguements [Silent Parameters in between “”] -Destination [Path to Store output] -PackageName [Name of the Target App in between “”] -Publisher [Manufacture of the Target App in between “”] -ExpandBaseImage [Path to the Core OS Image] -Verbose
• How the conversion works:
  It followed as Checking Pre-Requisites – Checking Minimum Windows Version Met or Not, PowerShell Version & so
  Validating Input – Validate if the if the target application Installer Exists, Output Folder exists or Not – if not, Create & so
  Setup Conversion Environment – Creates a light weight virtual machine for Capturing.
  Create AppX Manifest – Core DNA of the Application. The one similar in AppV 5.X Package – Used for editing the Package.
  Generates Virtual File System – The one similar to AppV 5.x – Everything in this will be Files created by the Installer except Assets Folder which contains Icons [This is created by the Converter].
  Generates Virtual Registry System – The one similar to AppV 5.x – Registry.Dat – Contains registry changes made by the Installer.
  Output – Below is the image of the output that we get,
  
  The process is not yet completed as we still have to generate .AppX Package. We need 2 more executables that will be part of Windows SDK.
  MakeAppX.exe – Command Line: [Path of MakeAppx.exe Pack -d [Path of Directory Contains the VFS, Registry.Dat & AppXManifest.xml] -p [Path to store output]
  Signtool.exe – This is used to sign the app using certificate file. Yet to get more information about this.
  Testing – Add-AppxPackage [Path of .AppX File].
  Additional Modification – If required any modifications the those has to be modified in the AppX Manifest.xml.

If you wish to find more information on this, have a look HERE.

• Conclusion:
  Uses light weight VM to perform capturing. This is something that I’ve seen in AppVolumes by VMware.
  Most of the things are quiet similar to the job we usually do.
  People with AppV 5.X will have a better understanding of the Process as they are already familiar with AppXManifest, Registry.Dat & VFS.
  Have to wait till the release of Windows Insider Program to do more research.