Laptop Application Packager wanted for 2 -3 weeks work on site in Nuneaton to support the deployment of 650 laptops

Week 1: Stabilise and Build Momentum

Days 1–2

Priority activities:

• Resolve the M Drive issue.
• Resolve the Price Tool blocker.
• Confirm the deployment approach for all applications.
• Review and prioritise the Top 60 application list.
• Package all Simple applications.
• Begin Medium application packaging.
• Confirm EPM licence coverage for the target user groups.
• Test whether EPM can reliably run installation media from a network drive.

Deliverables:

• Production sign-off achieved.
• Simple applications available through Company Portal.
• Packaging tracker agreed and baselined.
• Agreed approach for installation media storage, distribution and removal.

Days 3–5

Priority activities:

• Complete Medium application packaging.
• Validate application installation and first-run behaviour.
• Create EPM and AppLocker rules for Complex and Very Complex applications.
• Consolidate application installers and source files.
• Begin deployment to the initial lower-complexity user departments.
• Confirm whether existing AppLocker policies require application-specific updates.

Deliverables:

• Simple and Medium applications deployed.
• First rollout wave completed.
• Rollout support process operational.
• Initial EPM and AppLocker rules tested and documented.

Week 2: Accelerated Rollout

Days 6–10

Priority activities:

• Continue working through the application packaging backlog.
• Implement tested EPM and AppLocker exceptions.
• Progress department-by-department deployments.
• Process USB and application exception requests.
• Support MSN requirements and rollout planning.
• Monitor local installation media removal, disk capacity and application security risks.

Deliverables:

• Majority of the Top 60 applications addressed.
• Multiple department migrations completed.
• User support model embedded.
• Exceptions controlled and documented in line with least-privilege principles.

Days 11–14

Priority activities:

• Complete the remaining priority application work.
• Deliver final deployment waves.
• Provide hypercare support.
• Resolve outstanding onboarding issues.
• Confirm user acceptance and project readiness.
• Finalise the transition into BAU, including ownership of packaging, EPM rules, AppLocker updates and installation media housekeeping.

Deliverables:

• User rollout substantially complete.
• Application deployment model operational.
• Clear transition into BAU support.
• Outstanding risks, exceptions and residual backlog documented with owners.

Key Dependencies and Considerations

• Installation media: We need to test whether EPM will operate successfully from a network drive. If this is not viable, the media will need to be copied to a consistent local location for each installation. A controlled removal process will also be required to prevent disk-capacity issues, stale files and unmanaged files that could later be affected by live CVEs.
• Licensing: EPM requires an E5 or dedicated EPM licence. The current position is 567 E5 and 130 E3 licences, so licence coverage must be validated against the users included in each deployment wave.
• EPM rule creation: Each application will require a Certificate or File Hash rule. File Hash creation would generally require PowerShell expertise. Rules must be kept application-specific, as broader rules would increase the attack surface and would not align with least-privilege principles.
• Packaging strategy: Simple and Medium applications should continue to be packaged and deployed through the standard application management process. EPM should be used selectively for Complex and Very Complex applications where elevated permissions are required.
• AppLocker: AppLocker may require an update for each application. This may only become apparent during the first installation and first run, so testing and remediation capacity must remain within the plan.
• Delivery sequencing: Department rollout should only proceed where the required applications, licensing, EPM rules, AppLocker changes and support arrangements have been validated.

Expected Outcome

The additional TAP-funded resources would provide:

• Dedicated packaging effort focused solely on application delivery.
• Faster turnaround of Simple and Medium applications.
• An onsite engineer to support installations, troubleshooting and user engagement.
• Reduced demand on the Service Desk.
• Faster deployment through parallel packaging and rollout activity.
• A stronger likelihood of substantially completing the main rollout within the two-week window, without waiting for the full application backlog to be packaged before deployments begin.