Best Practice Packaging Project

Matt Rodgers

Application Packaging ConsultantContractor working with Software2Windows Installer/MSI packager since 2003App-V since 2013Application Jukebox packager since 2014

About Me

• Decision has been made to virtualize applications

• Refresh of assets/computers in the estate and/or operating systems. Opportunity to virtualize applications

• Why Application Jukebox?

Packaging Project Factors

DiscoveryPackagingQuality Assurance (QA)User Acceptance Testing (UAT)RemediationSign Off

Packaging Lifecycle

• Identify and compile list of applications to package. • Speak to project/business sponsors and heads of departments

• Obtain Source Media• Acquire licenses / serial keys• Determine user requirements of how the application should be configured and customised. Include a test plan if possible.• Document step-by-step process

• ideally with screenshots on how to take the source media and then how to install and configure it

Discovery

Packaging Process

• Package on a clean machine• Obtain source media, licenses and serial keys• Have the discovery document to hand• Perform a test installation or dry run of the source media• Capture the installation• Customise the package with scripts if necessary.

Packaging Process

• Follow best practices and remove unnecessary files and registry keys: http://support.software2.co.uk/entries/23504368-S2

-files-and-registry-keys-package-cleaning• Produce packaging documentation based on a template

all packagers can use• Test the package on a clean machine logged on as a user• Use a test plan if one has been provided, otherwise

perform basic functionality testing.

• Check the Application Jukebox Player Logs• C:\ProgramData\Endeavors Technologies\

StreamingCore\Log\StreamingCore.log• Event Viewer• Process Monitor (Procmon)

• https://technet.microsoft.com/en-us/library/bb896645.aspx

• Process Explorer • https://technet.microsoft.com/en-us/sysinternals/bb

896653• Windows Installer (MSI) verbose logging

Troubleshooting Issues

• Checklist of standards/processes that Application Jukebox packages must adhere to

• QA Process should be performed by a peer with the same technical experience as the packager

• If package conforms to QA standards: PASS• Send to User Acceptance Testing (UAT)

• If package does not conform to QA standards: FAIL• Return package back to packager for remediation

together with QA Checklist

Quality Assurance (QA)

• Invite key business user to test the package on a clean machine in a controlled environment

• Make sure the person performing the UAT is logged on with ‘user’ rights

• Ask user to complete a UAT checklist• Sign and complete the UAT checklist, highlight issues

found during testing• If UAT of package is successful: Obtain business signoff• If package has failed UAT: Return to packager for

remediation together with UAT Checklist

User Acceptance Testing (UAT)