If you’ve worked with MSI Windows Installer, you most likely know that the Windows Installer database includes various interrelated tables as a standard format for component management.

In the previous article discussing "Repackaging vs. Wrapping", we touched upon the concept of working with wrappers in the world of software packaging and deployment.

Object Linking and Embedding (OLE) is a proprietary technology developed by Microsoft that enables developers to embed and link to other objects.

In this article, we'll explore how to deploy an MSIX using Group Policies, covering Direct MSIX Deployment with Scheduled Tasks and the MSI Wrapper method.

There are multiple ways to deploy PowerShell scripts in SCCM. Some of the most popular options are the Application model, the Legacy Packages model, and most recently, the Scripts option.

One of the main challenges IT Pros face with application packages is the unattended installation. Unattended installations ensure that the same configuration is applied to all your active systems in the infrastructure, and no human error during installation can change that configuration.

There are multiple ways to provide an extra layer of security for your applications in order to distribute them safely and build trust with your users. One of the most reliable methods is using Signed Certificates.A Signed Certificate is a Public Key Cryptography certificate that verifies the identity of the certificate holder listed in the certificate and generates Digital Signatures.

With Advanced Installer’s PowerShell automation, you can automatically create the Updates Configuration File –the one placed on your server and used by the Updater to determine if there are any updates available.

On September 21st, 2021, the Morphisec team published an article explaining how a PowerShell script can be used to deploy malware via an MSI installation package.

During the installation process of WebApps, there are cases where users are asked to select an SSL certificate. This is because this certificate is used by the IIS elements.

We got a question in the Advanced Installer forum about the possibility of passing arguments to a service when the parameters are received from a configuration file, such as an .INI file.

Sometimes we need to have a single distribution package as an MSIX, which includes MSIX supported features along with MSI features that are no longer available (such as old drivers).

Over the years, we've received many questions regarding how Custom Actions work with PowerShell scripts in MSI.

On a recent post, we explored how MSIX deployments are done via SCCM, covering the scenario when a per-user installation is needed.

In our IT Pro world, the best practice we have in place regarding app deployment is that all applications are installable per machine. No matter if it’s an MSI, EXE, or other custom types of installers.