MSI is a Windows Installer package format that uses Microsoft’s Windows Installer service to manage the installation (and uninstallation) of applications.

Automation is probably one of the most used words in the IT Industry these days. We can't enter a room without hearing about it in the software packaging industry. However, sometimes simplicity is key.

If we were to manually install and manage software on a large number of target devices, the process would be very expensive and complicated. To avoid that hassle, enterprises use software deployment tools to simplify these tasks.

Windows Presentation Foundation (WPF) is a powerful User Interface (UI) framework for building desktop client apps. It's a part of .NET and offers a multitude of helpful features, such as media services, controls, data binding, and security.

Often throughout the repackaging process, it's frequent to come across files featuring straightforward paths such as: C:\Program Files.

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.

Recently, I was assigned to monitor a third-party application to detect when a workstation is unlocked or a user logs in. Additionally, if the monitor goes off, the monitored app should be started.

Installing and maintaining software applications across a large number of workstations can be a cumbersome and time-consuming operation for any enterprise.

In the tech industry, there's often a dilemma about which technology to use for patches. Specifically, when an ISV (Independent Software Vendor) creates an MSI for the first time and updates come up, they must choose between MSP and MSI options.

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.

It's the beginning of a new year, and we at Advanced Installer are releasing our first product update of the year - Advanced Installer 20.3.

Custom Actions are user-defined actions that enhance the installation process by adding functionalities beyond what is offered by the standard Windows Installer actions. They are necessary when built-in options fail to meet specific installation requirements.

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.

Throughout their entire history, MSI applications have used Microsoft Windows Installer as an installation and configuration tool provided with Windows since version 2.0 for Windows XP and proceeding to version 5.0 for Windows 7, 10, and 11.

To keep up with the evolution of technology, the architecture of the processors shifted from 32 bit to 64 bit, as did the operating systems.Due to the rapid technological advancements, the logic in the registry and file system changed as well.

Do you want to transfer CustomActionData to a CustomAction in WiX? We'll show you how in this article.

Process Monitor is probably one of the most used tools by IT Pros to debug applications and check installations. We mentioned Process Monitor in our MSI Packaging Training free e-book but this time around, we want to explore it further. We will discuss its prerequisites and share how you can get started with it.

When you create an installer using the WiX Toolset, there are instances where you may want to set a custom action to run under specific conditions, such as uninstalling an application, installing an application, or running a custom script.

Manually repackaging batch applications can be time consuming, especially when you have to deploy the applications on more than one computer.