Once that is accomplished, we can use some basic scripting to create a Printer Port, install the install the Printer Driver and add the Printer to Windows. We just need the relevant files to inject into the Driver Store. With that in mind, we can bypass the installer entirely. Often, when we focus on Printer Drivers, the app installer is just a fancy wrapper and the ultimate payload is always the same – getting the printer driver installed in Windows. Spending time nudging these legacy installers in the right direction can become tiresome. In my experience, drivers and firmware often fall behind of this utopian vision of autonomous application installations. As an app packager, you may be reading this and choking on your coffee – we have a long way to go until every vendor is on the same hymn sheet. Many app developers are slowly coming around to the idea that admins need to be able to install applications silently and autonomously. There are many ways to skin this cat and what made it more challenging was the Printer Driver was packaged in the dark ages (putting it politely). Recently, a customer asked if it was possible to install network printers, on Azure AD Joined Windows 10 devices, using Microsoft Intune. Win32 apps are very versatile and I often use them for customers to do other things besides installing applications.

My affinity to, and admiration for, Win32 apps has probably not gone unnoticed recently. In this post I will show you how to easily install Printer Drivers and Printers, from Intune, using Win32 apps and PowerShell.

Sharp printer driver unavailable