
Software deployment to every device: package it, pilot it, and know the way back
Software deployment rarely fails at the installation itself. It fails at the questions before and after: which version is actually allowed, how the management platform knows it worked, who notices first when it does not, and how you get back. This is the order we follow when a new application has to reach a hundred or a thousand devices.
Start with a catalogue: what is standard, what is available on request and what does not belong on a device. Without that list you deploy whatever happens to be asked for.
A package is only ready when it installs silently, has a detection rule and has a tested uninstall command. That last one is your way back.
Deploy in stages: a test device, a pilot group of real users, and only then everyone. Updating existing software is a separate process with its own rhythm.
First the list: which software is allowed
Most organisations do not have a software problem, they have a list problem. There are four PDF readers, three archive tools and a drawing package one person once needed, and nobody remembers who approved what. Deployment then becomes the automation of that mess.
So start with a catalogue in three groups:
- Standard: what every device gets without anyone asking. Microsoft 365 Apps, a browser, the security agent, the VPN client.
- On request: what a team or role needs. The finance package, the design software, the one tool a single client insists on. Each of these needs an owner who decides who may have it.
- Not allowed: what you deliberately do not support, with the reason next to it. That stops the same request coming back every quarter.
Record the licence model on every line as well. Deploying an application to a group without the licences for it is an audit finding you have automated yourself. How to keep track of that is covered in our piece on software licence management.
A package is more than an installer
The vendor’s installer is the starting point. A package you can send to hundreds of devices needs five things:
- A silent install. No windows, no clicks, with the options you choose (no desktop shortcut, no built-in updater if you handle updates yourself).
- A detection rule. How the platform sees that the software is present: a registry key, a file with a version number, a product code. Without good detection the platform reports a failed install that succeeded, or the other way round.
- Requirements. Which operating system, which architecture, how much free disk space, so the package never lands on a device where it cannot run.
- Dependencies. A runtime or plug-in that has to be there first.
- An uninstall command that works. More on that below.
The format depends on what the vendor ships. An MSI or MSIX is the easiest; a plain setup.exe goes into Intune as a Win32 app; many common applications are available from the Microsoft Store and through winget, so you do not have to package them yourself. On another management platform the parts have different names, but they are the same five.
Required or available: how software reaches the user
There are two ways to get software to someone, and the difference decides how many tickets you get.
- Required: the platform installs the software without asking. Right for the standard set and for anything a team cannot work without.
- Available: the software is offered in a self-service portal (Microsoft calls it the Company Portal) and users install it themselves, without admin rights. Right for the “on request” group, and it takes a large share of requests away from the service desk.
Assign to groups, never to individuals. A “Finance” or “Design” group populated from your HR system or directory means a new starter has the right software on day one and a leaver loses it. Assigning per person is quick on the first day and unmanageable after a year.
Choose deliberately between assigning to the device or to the user. On a shared desk or a meeting room PC the software belongs to the device; for someone with a laptop and a second device at home it usually belongs to the person.
Software deployment in three stages: test, pilot, everyone
A deployment that goes to everyone at once finds its faults with everyone at once. Three stages are enough:
- A test device. An ordinary device built like the rest, not the administrator’s laptop with every right. Check that the install is silent, that detection is correct and that the software starts.
- A pilot group. A handful of real users who use the software every day, from different teams and on different hardware. Give them a few working days and one place to report problems.
- Everyone. Only once the pilot has run without blocking issues. In a larger organisation, in two or three waves, so the service desk does not get everything in one morning.
Schedule installs outside working hours where you can, and tell users beforehand what they will see. A new icon that appears without explanation generates more questions than the install itself.
This is about new software. Updating what is already installed is a different process with its own rhythm and deadlines; that is in our article on patch management.
Plan the rollback before you deploy, not after
The question “how do we get it off again?” is usually asked at the moment things go wrong. Then it turns out the uninstall command was never tested, the software leaves remnants that block a reinstall, or the previous version is nowhere to be found.
- Test removal as seriously as installation. On the test device: install, uninstall, install again. If that third step fails, the package is not ready.
- Keep the previous version as a package. With a supersedence relationship in Intune the new version replaces the old one, and if something breaks you can reverse the assignment.
- Know where the data lives. Settings and files stored outside the application survive a reinstall. Data kept in the program folder does not.
Agree who decides on a rollback, too. For a business-critical application that is not the administrator alone but the owner named in the catalogue.
Self-installing: admin rights and what replaces them
As long as users have local admin rights, any catalogue is a suggestion. They install what they think they need, and with it whatever malware needs. Removing admin rights is the step that makes deployment meaningful, and also the step that meets the most resistance.
It works when something takes their place: a self-service portal with the software people actually use, a short route to request something new, and a turnaround time for those requests. For the few who genuinely need admin rights (a developer, an administrator) arrange a separate account or temporary elevation, not their everyday account.
If you deploy software that records information about how employees work, such as time tracking or monitoring, involve HR and, where you have one, the employee forum early. Whether consultation is required in your case is a question for your HR adviser or employment lawyer.
How you know the deployment worked
“Deployed” does not mean “installed”. The platform records per device whether the install succeeded, failed or is still pending, and that is where the real work is:
- Failed, with an error code. Usually a handful of causes that keep coming back: too little space, a running program holding a file, a missing dependency.
- Pending. Often devices that have not been online for weeks. Those belong in your asset management, not in the deployment.
- Not applicable. Devices that do not meet the requirements. Check that this is correct and not a group set up wrongly.
Agree a threshold at which the deployment counts as done, and what happens to the rest. An overview of which version sits where is also exactly what an auditor or an insurer asks for.
Where our work stops
What we do. We set up the catalogue with you, build and test the packages, configure group assignment and the self-service portal, run the pilot and the deployment, and report what is installed per device. We do that as part of workplace management or as a separate project.
What we do not do. We are not the software vendor. How the application itself behaves, the configuration of the finance or sector package and bugs in the program belong to the vendor of that package and its support. We make sure it lands cleanly on the device and can come off again. And whether software requires employee consultation is not something we judge; that is for your HR adviser or employment lawyer.
Questions we get about this
The five that come up most often.
What is software deployment?
Software deployment is getting an application onto many devices in a controlled way: choosing which software is allowed, packaging it so it installs silently, assigning it to groups and rolling it out in stages. It ends with a report of what is installed where, and a tested way to remove it again.
What are the stages of a software deployment?
A test device built like the rest of the estate, a pilot group of real users from different teams, and then everyone, in waves if the organisation is large. Each stage only starts when the previous one has run without blocking issues.
Is software deployment the same as patch management?
No. Deployment is about software that is not there yet: choosing, packaging, assigning. Patch management is about updating what is already installed, with a fixed rhythm and deadlines for security updates. They often use the same platform, but they are two separate agreements.
Should users keep admin rights so they can install software?
No, and as long as they have them, any software catalogue is optional. Remove the rights and replace them with a self-service portal holding the common software and a short request route. Those who genuinely need admin rights get a separate account or temporary elevation.
Do you support the application itself as well?
We make sure the software lands correctly on the device, works within the standard build and can be removed again. The functional configuration of a package and bugs in the program belong to the vendor of that software. We do help get the issue to that vendor with the right details.
Further reading
What software deployment connects to.
Shall we clean up your software catalogue together?
Send us an export of what is installed on your devices today. We turn it into a catalogue in three groups and tell you which packages are worth building first.
Practical IT knowledge in your inbox
New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.