Essentially the outcome of this blog post should leave you with a method that’s easy to maintain and support for newer Visual C++ applications being released. In this blog post we’ll cover how to create a new Win32 application that contains the installation files for all the currently supported Visual C++ redistributables and how PowerShell can be used to create a functioning detection rule for the Win32 application. Hence, another approach is required to ensure the baseline applications are installed onto the device.

These days when we talk about provisioning with Windows Autopilot and manage a device using Microsoft Intune, the reference image doesn’t fit into the picture anymore. Reference images have for ages been the primary choice for many organizations to make sure new devices are installed using a set of predefined applications, also known as baseline applications. Picture this scenario, you want to provision a new cloud managed device and leverage Windows Autopilot and on top of that have all the supported Visual C++ redistributables installed on that device. It’s all possible using the Intune Management Extension, which cannot be mentioned enough, is a great extension to cloud managed devices. Those devices, either being managed as Hybrid Azure AD joined devices or Azure AD joined devices, there’s no difference in how the Win32 applications are delivered from Microsoft Intune to the device. Installing applications, specifically Win32 applications, have for some time now been possible with Microsoft Intune managed devices, also sometimes referred to as cloud managed devices.

Vcredist_x64