Today's increased demand for efficiency in IT necessitates knowledge of how to speed up workflow using powerful tools such as PowerShell and Intune.

In this article, we will: Have a look over the AZ module, Understand how authentication with Azure works, Explore Microsoft Graph and Microsoft.Graph.Authentication module and Learn how to put all of this together to get the list of Win32 applications from Intune via PowerShell.

In PowerShell scripting, ensuring scripts continue after a reboot can be challenging, especially when managing configurations or updates that require a system restart. There are two primary strategies for local and remote execution environments to address this issue.

PowerShell App Deployment Toolkit (PSADT) is the go-to solution for enterprises aiming to standardize their software deployment process.

Installing MSI packages through PowerShell is a widely known technique that simplifies the deployment of software across multiple systems, especially for system administrators and IT professionals.

Running Python scripts from PowerShell is a powerful way to integrate Python's capabilities into a Windows environment. Before diving into how to execute a Python script from PowerShell, it's important to ensure Python is installed on your Windows machine.

VBScript (Visual Basic Script) is a scripting language introduced by Microsoft in the mid-1990s. It was designed to offer a lightweight scripting capability for web development and Windows administration. In October 2023, Microsoft announced the VBScript deprecation in upcoming Windows releases, making it available only as a feature on demand.

Customizations for applications inside the Windows OS are usually done either in files or the registry, depending on the developer's choice.

We've all been there - you're trying to uninstall a piece of software, but it just doesn't seem to be as straightforward as you'd like. Perhaps the traditional uninstall process is proving to be a hassle, or maybe the software doesn't seem to want to leave your system, no matter how hard you try.

In today’s software development industry, the partnership between PowerShell and MSI packaging continues to grow stronger.

Working with registry files is quite a simple task. However, depending on the action you want to take, you can encounter various scenarios.

With the rise of configuration files in various applications, understanding the ins and outs of INI files can elevate your productivity as a developer or software enthusiast. Despite their roots in the 16-bit Microsoft Windows platforms, INI files remain a crucial part of application configurations.

Installing software drivers can often seem like a complex task, but it doesn’t have to be. While MSI technology doesn't directly support driver installation, the Operating System (OS) provides a multitude of ways to achieve this.

The Run PowerShell inline script is offered as a predefined Custom Action in Advanced Installer. This action lets you directly type a code into the Advanced Installer editor. After saving your project and building the MSI, the custom action will execute according to your configuration.

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.