In this article, you will learn the exact steps necessary to create an automated repackaging process for Microsoft Teams as an example. The best thing about this solution and script is that, with a few adjustments, this process can be used to automate any other application repackaging and configuration process.
Clean Windows 7+ virtual machine installed. There are several options available for this:
Get an MSI repackaging software that has command-line support. Most of the enterprises have this software already, but not all have command-line support that allows an automated repackaging process. In this example to automate the Microsoft Teams repackaging process, we will use Master Packager. However, we want to make packaging easy and fast for everyone. That is why we have created an auto-packaging script in PowerShell that can be adjusted for any packaging tool you may have (as long as it has command-line support) and is not only limited to use with Master Packager.
Run the script by launching VB Script placed next to the PowerShell Script. It will do all the work for you. You will get the latest available Microsoft Teams version repackaged in MSI format as a per-machine application and configured ready to use for enterprise deployment systems (SCCM/Intune/etc.).
Always download the latest Master Packager Pro MSI from https://www.masterpackager.com/pricing website and replace existing MSI in Auto Repackaging Script - Microsoft Teams folder.
Activate Master Packager by changing the e-mail address and license key inside the Repackage_Teams.vbs file. You can buy or get a trial license for testing purposes only from https://www.masterpackager.com/pricing in seconds.
In the installation directory of Master Packager (C:\Program Files (x86)\Master Packager\Auto-Repackaging script sample), there is a PowerShell script that is used to repackage applications automatically. We took this script and adjusted it for Microsoft Teams.
Ready MSI is accessible in the "C:\MRP\Repack" folder.
There are many ways to implement and use this solution. It is possible for you to manually start a Virtual Machine (VM), copy the required files to the VM and simply launch the VBScript. However, the preferred method would be to create a snapshot on the VM that has a scheduled task that will run the script when the VM boots. You can even go as far as to copy the finished package on a network share and turn the VM off when that is done and import ready MSI package directly in SCCM or Intune.
Remember that even if the solution produces a usable package, it should always be verified before deploying to production. There might be some trash files/registries left in the package. The application functionality must also be verified as we cannot guarantee that Microsoft will not change the current installation logic and break something in the process.