Software deployment tools for MSPs and IT teams

Software deployment tools for MSPs and IT teams

MSP Tools & Reviews

Technology

IT Operations

BEST PRACTICES

BUYING GUIDE

ENDPOINT MANAGEMENT

+12

Conrad Lunderstedt

October 6, 2026

232 views

Share

Includes the six jobs every software deployment solution handles, Group Policy software installation step by step, printer GPOs after the Point and Print change, Intune Win32 and Store apps, RMM script push across client tenants, PDQ, Configuration Manager, winget and a rollout order in rings.

A new hire starts Monday and needs eleven applications working by nine. The technician who installs them by hand will do the same job again on Tuesday, and the one who packaged them once will be on the next ticket. This guide sorts the software deployment tools that MSPs and in-house IT teams use to push apps to a whole fleet: what each route does, which one fits which kind of fleet, and where a push breaks.

TL;DR

A deployment tool does four jobs: pick the devices, deliver the package, install it silently in the right context, and confirm it landed. Skip the last one and you have a script, not a deployment.

Windows has four main routes: Group Policy software installation (MSI only), Intune Win32 and Store apps, a script push from an RMM, and dedicated tools such as PDQ Deploy or Configuration Manager. Package managers like winget and Chocolatey sit underneath all of them.

Pick by fleet, not by feature list. Domain-joined and on-prem points one way, Entra-joined and cloud-first another, and an MSP running twenty tenants a third.

The failures repeat: wrong install context, a detection rule that doesn't match, an installer that wants a click, and a reboot nobody planned for.

Roll out in rings. One device, then a pilot group, then everyone with a deadline, with the uninstall assignment ready before you need it.

What software deployment tools do

A software deployment tool takes an installer, decides which devices should have it, runs it without anyone clicking Next, and then checks that the application is present. That last step separates deployment from scripting. A script that runs msiexec on 400 machines tells you it ran. A deployment tool tells you which 388 machines have the app, which 9 failed with a return code, and which 3 haven't checked in.

What separates one software deployment solution from another is how it handles six jobs:

Targeting. Groups, OUs, tags or dynamic queries, so a new laptop picks up its apps without a ticket.

Packaging. A silent install command, an uninstall command and any transforms or config files, stored once and reused.

Install context. System for machine-wide apps, user for per-profile ones, chosen per package.

Detection. A rule that proves the app is present, separate from the installer's exit code.

Retries and reboots. A plan for exit code 1618 (another install is running), 3010 (restart required) and devices that are offline.

Lifecycle. Upgrades, supersedence and a tested uninstall for the day a version breaks something.

MSPs need a seventh: the same package and the same report across every client tenant, from one console.

Commercial products bundle those jobs in different shapes. ManageEngine Endpoint Central ships predefined package templates, takes silent switches for EXE packages, and targets a domain, OU, computer or custom group on Windows, Mac and Linux. NinjaOne's software deployment module deploys, patches, uninstalls and tracks applications from the same console as its RMM. PDQ, Intune and Configuration Manager each get their own section below.

The category overlaps with two neighbours. Patch management keeps what's installed current, and the same tools often do both, which is why Intune, Configuration Manager and PDQ appear in both conversations. The broader field of IT automation software covers workflows around the install, such as onboarding runbooks, and this post stays on the install itself.

OS deployment comes first and usually lives in a different tool. Disk imaging or Windows Autopilot gets Windows itself ready on the device, and the software deployment tool installs and maintains the apps from then on.

The devices set the constraints. A Windows fleet has four realistic routes, and each one makes a different assumption about how the device is joined, where it sits on the network, and who is logged in.

Four routes into one Windows device: Group Policy pushes MSIs from a share, Intune wraps any installer with detection rules, an RMM runs scripts as SYSTEM across tenants, and PDQ Deploy or Configuration Manager push packages from a console, each with different targets, formats and proof of install

Four routes to a Windows fleet

Group Policy software installation

The oldest route still works. A Group Policy Object under Computer Configuration, Software Settings, Software installation points at an MSI on a network share, and the package installs when the computer starts. Assigned to a user, it installs at logon or on first launch. Published to a user, it appears in Add or Remove Programs for them to install.

Setting it up takes four steps in the Group Policy Management Console:

Copy the MSI to a shared folder and give the computer accounts read access to the share and the folder, because a computer-assigned package installs before anyone signs in.

Create a GPO and link it to the OU that holds the target computers.

Under Computer Configuration, Policies, Software Settings, right-click Software installation, choose New, then Package, and type the UNC path, such as \\fs01\packages\app.msi . Microsoft's KB says to type the UNC path rather than browse to it, so every client resolves the same network location.

Choose Assigned. If the app needs a transform (.mst) for a licence key or a server address, choose Advanced instead and add it on the Modifications tab before you click OK, because the package goes live the moment you do, and fixing a transform afterwards means an uninstall or an upgrade package.

Plan for the first install to need a second restart. Microsoft's Logon policy reference explains that client computers apply Group Policy in the background by default, so extensions such as Software Installation take two logons to apply changes. The "Always wait for the network at computer startup and logon" policy, under Computer Configuration, Administrative Templates, System, Logon, makes processing synchronous and removes the wait, at the cost of slower startups.

Upgrades and removal live in the same node. A newer MSI replaces the old one from its Upgrades tab, either by uninstalling the old package first or by upgrading over it, and Redeploy application reinstalls a package everywhere it already landed. Remove offers two exits: uninstall immediately from users and computers, or leave existing copies alone and block new installs. Ticking "Uninstall this application when it falls out of the scope of management" removes the app from computers that move to an OU the GPO doesn't cover.

The limits are in Microsoft's own KB 816102, updated February 2026. The package has to be an MSI, the path has to be a UNC share the computer account can read, and installation happens at startup or logon, so a laptop that never restarts on the office network never gets it. There is no reporting beyond the event log and no way to say "install by Friday". It suits a small domain with a few MSI-packaged line-of-business apps and nothing else.

Group Policy printer deployment

Printers are the other job that domain-joined fleets still hand to Group Policy. Group Policy Preferences create shared, TCP/IP or local printer connections under User Configuration, Preferences, Control Panel Settings, Printers, with item-level targeting by security group or IP range, and the Print Management console's Deploy with Group Policy option pushes a connection per user or per computer. Our Group Policy guide walks through both, step by step.

The driver is where printer GPOs stall. Since the August 10, 2021 updates, Windows requires administrator rights to install a driver through Point and Print by default, per Microsoft's KB5005652 , so a standard user on a PC without the driver gets a credential prompt instead of a printer. Ship the driver first as a package through the same tool that deploys your apps, and let the GPO only connect the queue.

Intune Win32 and store apps

Intune has two app types worth knowing for a fleet. The Win32 app type wraps any installer, MSI or EXE, into an .intunewin file with the Win32 Content Prep Tool. You supply the install command, the uninstall command, an install context of System or User, requirement rules, and detection rules that tell Intune how to confirm the app is present. Microsoft's Win32 documentation, updated April 2026, caps a package at 30 GB and has the Intune management extension check for new assignments every hour.

Two settings carry most of the weight. Return codes decide what happens next: 0 is success, 3010 is a soft reboot, 1641 is a hard reboot, and 1618 tells Intune to retry three times, five minutes apart. Detection rules decide whether the install counts: an MSI product code, a file or registry check, or a PowerShell script that returns 0 and writes to STDOUT. Intune re-evaluates required apps roughly every 24 hours, so an app that installs but fails its own detection rule gets installed again tomorrow.

The second type, Microsoft Store app (new), pulls from the same catalog winget uses. Intune keeps those apps updated on its own, which removes a whole class of packaging work for common tools. The trade is control: the publisher hosts the content, paid apps aren't supported, and the device needs to reach the Store. Our Intune review covers where Intune stops being enough for a mixed fleet.

What the Intune agent does after you click Assign: hourly check-in, a 30 GB package cap with Delivery Optimization, return codes 0, 3010 and 1641 with three retries five minutes apart on 1618, a 24-hour detection re-check, and a 1,440-minute default restart grace period

RMM script push

An RMM agent runs as SYSTEM on every managed device, which makes it a deployment tool the moment you hand it a script. The usual pattern is a PowerShell script that downloads or copies the installer, runs msiexec /package app.msi /quiet /norestart or winget install --id Publisher.App --silent --scope machine , checks the exit code, and writes a line the RMM collects. Read our guide to what RMM does if the agent model is new to you.

The strength is reach. The agent doesn't care whether the device is domain-joined, Entra-joined or a workgroup laptop in someone's kitchen, and an MSP can run the same script across every client from one console. The gap is everything a purpose-built tool does for you: detection, dependencies, supersedence and retry logic are yours to write. OpenFrame handles the same job through scripts run across a client's devices with the output collected in one place.

Flamingo, which publishes this guide, builds OpenFrame , open, AI-native infrastructure for IT and security that covers large areas of RMM, patching and remote access, with AI agents working inline: Fae resolves support requests and Mingo runs IT operations. It costs $1 per device a month, including 10M AI tokens, or $0.80 on annual billing with 25M, with a 14-day free trial.

Dedicated deployment tools and package managers

PDQ Deploy is the on-prem specialist. It pushes installers, Windows updates and PowerShell to domain-joined or VPN-connected Windows computers, ships a library of more than 200 prebuilt silent packages, and can trigger a deployment on a schedule or when a machine's heartbeat returns. As of October 2026, PDQ lists the licence at $1,950 a year per administrator, which includes PDQ Inventory. The condition is the network: the console has to reach the target, so remote laptops need a VPN or an agent. PDQ's agent-based product, PDQ Connect, covers that case from $12 per device a year, with automated deployments on the $18 Plus tier and a 100-device minimum (pricing page read November 4, 2026). Our PDQ Deploy review works out where Connect costs less than Deploy.

Configuration Manager is the enterprise route. An application carries one or more deployment types, each with its own install command, detection method and requirements, and content is staged on distribution points before a required or available deployment goes to a collection. It is heavy to run and pairs with Intune through co-management, which is why it shows up in organisations that already have it and rarely in ones that don't.

Underneath all of these sit the package managers. winget ships with Windows 10 1809 and later, Windows 11 and Windows Server 2025 as part of App Installer, and its install , upgrade , export , import and configure commands handle EXE, MSI, MSIX, Inno, Nullsoft and portable installers. Chocolatey wraps native installers into packages the same way and predates it. The catch is the source: Chocolatey's own documentation says the community repository is not intended for organisational use, so companies host an internal repository, and a Store policy can block winget's public source on managed devices.

This r/sysadmin thread is the question every 50-user shop asks at some point: one tool for deployment, patching and licensing, and which of the routes above it should be.

Windows software deployment: what every route shares

Whichever route delivers the package, Windows software deployment meets the same four details on the device.

SYSTEM has no mapped drives. Intune and Configuration Manager run system-context installs as SYSTEM, and an RMM agent runs everything that way, so the installer has to come from a download, the tool's own content cache, or a share the computer account can read.

winget needs a first sign-in. Microsoft's WinGet documentation says the tool isn't available until a user has signed in to Windows once, because the Microsoft Store registers it in the background, so a freshly imaged machine can fail a winget script until someone signs in.

Dependencies come first. A line-of-business app that needs a runtime such as the Visual C++ Redistributable should get it as its own package, set as a dependency where the tool supports one, as our VCRUNTIME140.dll guide shows.

App Control decides what runs. On a fleet that enforces App Control for Business, an app the policy doesn't trust is blocked, unless the policy trusts a managed installer such as the Intune Management Extension. Our WDAC guide covers both routes.

Microsoft 365 Apps follow their own path: the Office Deployment Tool installs them from one XML file, and every route above can run it.

Installer formats in one minute

Every route above ends by running an installer, so the package format decides how much work the packaging step takes. MSI is the predictable one. Windows Installer owns the switches, so /quiet and /norestart behave the same on every MSI, the product code gives you a detection rule for free, and /log writes a file you can read when it fails.

EXE installers wrap whatever the vendor chose. Inno Setup, NSIS and WiX Burn each have their own silent switch, and Microsoft's own Intune docs say to ask the vendor for the arguments a package supports. winget's manifest already knows the silent flag for anything in its catalog, which is one reason the package managers save time.

MSIX is the newer format. Packages are signed, install into a container with a virtual file system and registry, and update by downloading only the changed 64 KB blocks. Microsoft's MSIX overview, updated April 2026, claims a 99.96 percent install success rate and a clean uninstall with no leftover files. The reason it hasn't replaced the others is that vendors have to ship it, and many still don't. Our guide to MSI and EXE installers covers the silent switches in depth, so this post stops here.

Installer formats and what the deployment step inherits: MSI gives the same silent switches and a product code for detection, EXE installers each have vendor-specific switches, and signed MSIX packages install into a container with 64 KB differential updates and a 99.96 percent install success rate per Microsoft

Which tool fits which fleet

The right answer follows from three questions: how are the devices joined, where do they sit on the network, and how many organisations do you manage?

Fleet Route that fits Why
On-prem Active Directory, devices in the office Group Policy for MSIs, PDQ Deploy or Configuration Manager for the rest The domain and the LAN are already there, and both tools assume them
Entra-joined, cloud-first, laptops everywhere Intune Win32 apps plus Store apps Devices only need internet, detection and reporting are built in
Hybrid-joined with Configuration Manager already running Co-management, moving app workloads to Intune over time Keeps the existing packages while the fleet moves
MSP with many small clients RMM script push with winget, a standard app list per client One console across tenants, no per-client infrastructure
Servers and lab machines winget import or configure, Ansible for Linux and Windows together Declarative lists beat click-through installs
Macs and phones MDM, not any of the above Apple and Android install through MDM commands, not msiexec

Two of those rows point to other guides. Mac fleets install through Apple MDM , and phones and tablets through the MDM platforms compared in our MDM solutions roundup.

Which deployment route fits which fleet: Group Policy with PDQ or Configuration Manager for on-prem Active Directory, Intune Win32 and Store apps for Entra-joined laptops, co-management for hybrid, RMM push with winget for MSPs, winget import or Ansible for servers, and MDM for Macs and phones

Where deployments break

The same handful of failures show up on every platform, and they're cheaper to design out than to debug at scale.

The install runs in the wrong context. A user-context install on a device where the user isn't an admin fails, and an app that writes to HKLM needs System. Intune's own guidance is that Entra registered devices should use System, and that Win32 apps assigned to users fail if the app needs rights the user doesn't have.

The detection rule doesn't match the result. The installer succeeds, the detection rule checks a version string the vendor changed, and Intune reports "not detected after installation". On a required assignment, that app installs again at the next 24-hour evaluation, and again the day after. Detect on something the installer controls: the MSI product code, or the file the app can't run without.

The installer wants a click. Intune states it does not support interactive installs, and tricks that push a dialog into the user's session are unsupported. If the vendor's EXE has no silent switch, repackage it or pick a different vendor.

The install-context trap in the wild: an r/Intune thread on getting a Win32 app to install for a user who isn't an admin, which is the first failure on the list above.

The reboot wasn't planned. A hard reboot return code restarts the device now. Map 3010 to soft reboot, set a restart grace period, and give users the 24-hour default before the machine takes the decision for them.

Bandwidth. A 2 GB package times 300 laptops in one branch office is 600 GB through one WAN link. Delivery Optimization's peer-to-peer download is on by default for Intune Win32 content, and Configuration Manager has distribution points for the same reason.

Version drift. The app updates itself to 12.4, the deployed package says 12.1, and reports go red. Either let the vendor updater run and detect on presence rather than version, or block the updater and own the version through supersedence.

Offline devices. PDQ needs the target on the LAN or VPN. Intune needs internet. A field laptop that's off for three weeks gets nothing until it isn't, so schedule on heartbeat and stop chasing the report.

Ticket log meme: 412 devices needed FinanceApp, 24 kept failing with 0x87D1041C not detected after install and reinstalling daily until the detection rule was changed from version equals 12.1 to file exists; 460 installs ran for 412 that were needed

A rollout order that holds

Package once, then move through rings. The first ring is one device, ideally a reimaged one, where you watch the install and the detection rule succeed by hand. The second is a pilot group of about five percent of the fleet, mixed across models and departments, with the assignment set to available so people opt in and complain early. The third is everyone, assigned as required with a deadline a week out and an availability date before it, so the content downloads and caches before the install fires.

Build the uninstall before you need it. Intune, Configuration Manager and PDQ all support an uninstall deployment, and the day an update breaks a line-of-business app is not the day to write one. For an MSI, msiexec /uninstall {product-code} /quiet is the whole command.

Read the report, not the console's green tick. Success, in progress, error, requirements not met and unknown mean different things, and "unknown" for three days usually means the device isn't checking in at all. The deployment is done when the count of devices with the app matches the count of devices that should have it, and the difference has names.

A rollout order in three rings: one device on day 0, a pilot of about 5 percent as available on days 1 to 5, everyone as required with availability on day 7 and a deadline on day 14, plus the uninstall assignment written and tested before ring 0

Deploying apps as an MSP

An MSP deploys the same twenty applications across a hundred different environments, which changes the maths. A standard app list per client, kept in a document the RMM can act on, beats twenty bespoke policies. Exceptions get written down with the reason, because the client who needs the 2019 accounting version will need it again after the next tech leaves.

Package managers earn their keep here. A winget or Chocolatey install line works on a client's Entra-joined laptops and another client's domain PCs without a repackage, and a winget upgrade --all scheduled through the RMM keeps the common tools current between patch cycles. Tie it to the patch management process rather than running a second one.

MDM-style tools are the other option for MSPs that want detection and reporting without the enterprise tooling. Our Fleet MDM review covers one open-source route, including how it handles automated patching and software deployment.

Finally, the video below walks through the Intune side end to end, from packaging a Win32 app to Store apps and assignments, which is the route this guide points Entra-joined fleets to.

The short version

Software deployment tools push an application to a fleet, install it silently in the right context, and confirm it's there. On Windows the routes are Group Policy for MSIs, Intune for cloud-joined devices, an RMM script push for reach across tenants, and PDQ Deploy or Configuration Manager for on-prem fleets, with winget and Chocolatey doing the packaging work underneath. Match the route to how the devices are joined and where they live, write the detection rule before the install command, and roll out in rings with the uninstall ready. For the wider category of tools that manage the device after the app lands, start with our guide to endpoint management software .

Conrad Lunderstedt

Solution Architect

I'm Conrad, Solution Architect at Flamingo. I've spent about 26 years in IT, roughly half of it inside MSPs and the rest in enterprise environments, so I've watched vendor decisions get made on both sides of that line. Now I spend my days talking with MSPs about the stack they already run, and helping them work through the requests and issues that come with it.

Related Content

Blog Posts

Product Releases

Podcasts

Webinars

Case Studies

Events

Onboarding Guides

Loading related content

Frequently Asked Questions

/blog/software-deployment-tools

About OpenFrame

What's included in OpenFrame? Does it integrate with my existing tools?

OpenFrame isn't built to plug into your stack. It replaces it. Instead of duct-taping a dozen tools together (RMM, MDM, SIEM, patching, remote access, each its own login and bill), we bundle it into one unified platform: RMM, MDM, monitoring, automation, remote access, patch management, security monitoring, and ticketing, plus built-in AI copilots. So "does it integrate with X?" usually means: you won't need X anymore.

How is OpenFrame different from other vendors?

Most platforms give you one piece and expect you to bolt the rest on. OpenFrame unifies the whole stack in one place, with AI copilots built in. Fewer logins, fewer bills, less duct tape.

OpenFrame basics

What is OpenFrame, and who is it for?

OpenFrame is an open, AI-native infrastructure layer for IT and security. One platform covers devices, patching, remote access, help desk and security, and two AI agents work inside it: Mingo for technicians and Fae for the people they support. It runs on web, desktop, iOS and Android. MSPs, MSSPs and in-house IT teams use it to get more done with the same team.

What are software deployment tools?

Software deployment tools install applications on many devices without anyone clicking through the installer. They pick the target devices, deliver the package, run the install silently in the right context (system or user), then confirm the app is present and report per device. On Windows the main routes are Group Policy software installation, Microsoft Intune, an RMM script push, and dedicated tools such as PDQ Deploy or Configuration Manager, with package managers like winget and Chocolatey underneath.

What is the difference between software deployment and patch management?

Software deployment installs or removes an application on a fleet. Patch management keeps what is already installed current with security and feature updates. The same tools often do both, so Intune, Configuration Manager, PDQ and RMM platforms such as NinjaOne appear in both conversations, but the failure modes differ: deployment breaks on install context and detection rules, patching breaks on reboots and version drift.

Can Intune deploy EXE installers?

Yes. Intune wraps EXE and MSI installers into an .intunewin package with the Win32 Content Prep Tool. You supply the silent install command, an uninstall command, the install context, and detection rules. The installer must run silently; Microsoft states that Intune does not support interactive installations. Packages are capped at 30 GB per app.

Do I need Configuration Manager if I have Intune?

Usually not for a cloud-first fleet. Intune Win32 apps cover most application deployment needs on Entra-joined devices, and Store apps update themselves. Configuration Manager still fits organisations that already run it, need on-prem distribution points for large content, or manage servers, and the two work together through co-management while app workloads move to Intune.

How do MSPs deploy software to many clients at once?

The common MSP route is the RMM agent, which executes as SYSTEM on every managed device across tenants. A PowerShell script runs msiexec or winget install with silent switches, checks the exit code, and reports back. A standard app list per client, documented exceptions, and a scheduled winget upgrade keep the common tools consistent without per-client infrastructure.

How do I enable Win32 long paths with Group Policy?

Open the Group Policy Management Editor for a domain GPO, or gpedit.msc on a single PC, go to Computer Configuration, Administrative Templates, System, Filesystem, and enable "Enable Win32 long paths". The policy sets the LongPathsEnabled value under HKLM\SYSTEM\CurrentControlSet\Control\FileSystem to 1, and Intune can apply the same setting through the Policy CSP. It lifts the 260-character MAX_PATH limit only for applications whose manifest declares longPathAware, on Windows 10 version 1607 and later, and processes that started before the change need a restart to see it.

Will the AI do things without asking me?

Only what you allow. You set the rules: routine fixes can run on their own, everything else waits for your approval. Every action is logged.

Still deciding?

Ask Mingo answers from our docs and customer stories.

BEST PRACTICES

BUYING GUIDE

ENDPOINT MANAGEMENT

Subscribe to Flamingo Blog (RSS)

IT automation software

Disk imaging

Logon policy reference

Group Policy guide

KB5005652

Intune management extension

Intune review

what RMM does

OpenFrame

PDQ Deploy review

VCRUNTIME140.dll guide

WDAC guide

Office Deployment Tool

MSI and EXE installers

Apple MDM

MDM solutions

patch management

Fleet MDM review

endpoint management software

Additional pricing (as published)

Flamingo Raises $4.5M Seed Round · Led by Vertex Ventures, bringing total funding to $6.7M to build the open, AI-native layer for IT and security.