Your application packaging backlog is not a resource problem. It is a process problem.
Every enterprise IT team with a packaging backlog has, at some point, concluded that what they need is more packaging engineers. More hands on the same process. And for a while, that helps.
Then the Windows 11 migration programme starts. Then the Intune transition begins. Then a rationalisation project adds 200 new applications that need packaging for the consolidated estate. The backlog grows faster than headcount can address it because the constraint is not the number of people it is the nature of the process.
Manual application packaging was not designed to scale. It was designed for a world where application change was slow and predictable. That world no longer exists.
For teams that have automated none of this, it is worth being explicit about why manual packaging is so time-consuming.
For each application requiring packaging, a packaging engineer must:
For a straightforward application, this process takes between 4 and 8 hours. For a complex application with custom configuration requirements, dependencies, or legacy install behaviour, it can take 2 to 3 days.
A packaging team of three engineers, working exclusively on packaging, can deliver between 60 and 100 packages per month under good conditions. When programme demand Windows 11 migration, Intune transition, rationalisation adds 300 new packaging requirements simultaneously, the backlog does not clear. It grows.
The packaging backlog problem becomes critical at exactly the moment when migration programmes are in flight.
Windows 11 programmes require applications to be repackaged in the correct format for Intune Win32 deployment. SCCM-to-Intune transitions require the same. Application rationalisation programmes add new consolidation candidates that need packaging. All of these demands arrive simultaneously because they are triggered by the same organisational decisions.
The consequence is predictable: the migration programme timeline slips not because the OS deployment is complex, but because the application packaging pipeline cannot clear the backlog fast enough to keep the programme moving.
For a multinational defence organisation, packaging time before automation averaged 21 days per application. Post-automation: 4 days. An 81% reduction. The efficiency gain, according to the organisation, exceeded their expectations.
Automated application packaging uses a pipeline that removes the manual steps whilst retaining the governance required for enterprise deployment.
In ALICE, the packaging process works like this:
Catalogue match. ALICE matches the application to its curated catalogue, pulling installer metadata, silent install inputs, and version information automatically. No manual MSI interrogation.
Configuration in the UI. MSI property tables are extracted and surfaced in the ALICE interface. Enterprise deployment standards suppress reboot, hide UI, set ARPNOREMOVE are applied without manual MSI editing. Configuration is done in a user interface, not a command line.
Custom upload support. For applications not in the catalogue custom software, legacy tools, or bespoke internal applications ALICE accepts custom MSI or EXE upload and runs the same automated analysis pipeline.
Compilation and upload. ALICE compiles the configured package to .intunewin format and uploads to Intune as a Win32 LOB app with required configuration.
The process that previously took 4 to 8 hours per application now takes the time required to click through a configuration interface. For straightforward applications, end-to-end packaging time drops by approximately 85%.
The concern packaging teams most frequently raise about automation is loss of control: if the pipeline builds the package automatically, how do we know it is correct?
ALICE addresses this with a testing gate that cannot be bypassed.
Every package whether created manually or through the automated pipeline is deployed to a designated test group before it can progress to production. Named testers approve or reject the package with full tracking. The application cannot progress until all assigned testers have approved.
Automation handles the mechanical creation and configuration work. Human expertise handles the validation. The bottleneck moves from creation to testing and testing is the work that actually requires a packaging engineer.
The compounding value of automated packaging comes from the auto-update pipeline.
Once an application has been packaged and configured in ALICE, the per-application auto-update toggle enables automatic lifecycle management for every subsequent version. When a new version is released, ALICE detects it, repackages it using the same stored configuration, routes it through the same test group, and deploys it through the same phased rollout.
The packaging engineer configured the application once. Every future version is handled automatically, using the same governance and configuration.
For estates with hundreds of actively managed applications, this is the point at which the packaging team’s capacity and the application change demand stop being in conflict. The pipeline handles the volume. The team handles the exceptions.
Manual packaging has a fixed throughput ceiling. Automated packaging does not.
When your estate needs 300 packages to support a migration programme, a manual team of three engineers will take four to five months to deliver them. An automated pipeline with a testing gate delivers the same packages in a fraction of the time.
The packaging engineer’s role does not disappear it shifts. From mechanical creation to configuration governance, exception handling, and test approval. The work that requires human expertise.
ALICE is Camwood‘s platform for Autonomous Application Lifecycle Management. With 25 years of application packaging expertise, ALICE automates the pipeline so your team can focus on what matters.
Back to Blog Start your free 14-day trial Most business cases for IT investment fail before they reach the board…….
Back to Blog Start your free 14-day trial One estate. Three tenants. 1,847 applications. 90 days to transform it. This……
Back to Blog Start your free 14-day trial Every enterprise IT team knows they have too many applications. Almost none……
