Thanks to visit codestin.com
Credit goes to www.scribd.com

0% found this document useful (0 votes)
56 views2 pages

Application Packaging Daily Routine

The document outlines the daily routine of an Application Packaging Engineer, detailing tasks from morning kickoff and task review to end-of-day updates. It includes steps for analyzing packaging requests, pre-packaging tasks, package creation, internal testing, deployment integration, and documentation. Common tools used in the process are also listed, emphasizing the importance of organization and thorough testing in application packaging.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
56 views2 pages

Application Packaging Daily Routine

The document outlines the daily routine of an Application Packaging Engineer, detailing tasks from morning kickoff and task review to end-of-day updates. It includes steps for analyzing packaging requests, pre-packaging tasks, package creation, internal testing, deployment integration, and documentation. Common tools used in the process are also listed, emphasizing the importance of organization and thorough testing in application packaging.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Daily Routine - Application Packaging

Engineer
1. Morning Kickoff & Task Review
 - Check new tickets in Service Desk or ITSM tool.
 - Review emails from team leads, app owners, or infrastructure team.
 - Prioritize urgent requests or failed deployment issues.

2. Analyze New Packaging Requests


 - Download source files (MSI/EXE/ZIP).
 - Check vendor installation guide/documentation.
 - Determine installation type: MSI/EXE/Script.
 - Identify dependencies or prerequisites.

3. Pre-Packaging Tasks
 - Perform manual install on clean VM.
 - Document all changes (files, registry, shortcuts).
 - Use snapshot tools (Regshot/AdminStudio) if needed.

4. Package Creation
 - Create MST using ORCA or InstEd if MSI.
 - Use scripting (batch/PowerShell) for wrapping EXEs.
 - Ensure silent switches and customizations are applied.
 - Include cleanup or pre-check logic if necessary.

5. Internal Testing (UAT/QA)


 - Test install/uninstall silently in test VM.
 - Validate file placements, shortcuts, registry, etc.
 - Fix and retest if issues found.

6. Intune/SCCM Deployment Integration


 - Create application entry in Intune or SCCM.
 - Add proper detection methods (registry/file/MSI).
 - Set requirements, dependencies, or supersedence as needed.
 - Test on pilot device or test collection.
7. Documentation
 - Update packaging checklist or app-specific documentation.
 - Document install/uninstall commands, detection methods.
 - Record version info and changelogs.

8. End of Day
 - Update ticketing system with current status.
 - Log completed tasks in team tracker.
 - Send end-of-day summary if required.

Common Tools Used


 - VMware/Hyper-V - Testing VMs
 - Intune / SCCM - Deployment platforms
 - ORCA / InstEd - MST and MSI customization
 - PowerShell / Batch - Scripting tasks
 - Process Monitor / Regshot - Change tracking
 - Notepad++ / VS Code - Script editing

You might also like