Creating Containers with the Auto Packager
Creating Containers with the Auto Packager
The Cloudhouse Auto Packager uses install snapshot-based packaging, combined with runtime analysis to create a Container for the applications (below), a Packaging Methodology is also provided.
- Install Capture (Required)
- Runtime Analysis (Optional)
- Edit Container Contents (Optional)
- Package Finalization (Required)
- Feature Dependent Configuration(Conditional)
The Auto Package may not be able to include files that are in use by Anti Virus software, if you are presented with a warning message click 'Retry' to include the files in the Container.
- Launch the Auto Packager, from the shortcut, and select a Package Folder to define where the Container will be created.
- Click Next, and select Start Capture to record the current state of the system.
- The Next button will be enabled when the capture has completed, click Next to proceed to the application install.
- Install the application, components and required dependencies.
- When all the installs are complete, reboot ONLY if required to do so by the application's installer.
- After the reboot has completed, the Auto Packager may be restarted using the desktop shortcut.
- Click Next.
- To perform the optional run-time analysis and detect files and registries used when the application is running follow the steps in Run-time Analysis below, otherwise click Next and proceed to Step 7.
Optional - Runtime Analysis
The following steps will enable application files and registry created, or modified, when the application is configured for the first time* to be captured in the Container:
- 'Run App' page shows a list of shortcuts installed by the application.
- Start the application through the shortcut in the Auto Packager - do not use shortcuts on the desktop or start menu.
- Perform any configuration changes* required so the app is configured for the users the first time it starts up.
- Once completed, close the programs and click Next to proceed.
- Click Complete Capture to record the final state of the system, click Next to proceed.
*If the containerized application fails during a particular work flow, or an issue is identified, during UAT it may be helpful to repeat the workflow during packaging process.
Note: Do NOT uninstall the application during Runtime Analysis, otherwise the Auto Packager will capture this change and create the Container without the application.
Optional - Edit Container
Files, registry keys and redirects can be added, removed from the Container depending upon what was captured during the install capture and run-time analysis process. To modify the contents of the Container
- Select the left hand side pane, 'Files in package' view to remove items or add re-directions for files captured in the Container by the install capture process.
- Navigate to the file or folder, and right click and select Redirect or Remove Item as required, note if you select a Folder and want to redirect all sub-folders then select Redirect Children.
- Available options in the right click menu will change to Remove Redirect, or Add Item allowing changes to be reversed.
- To include files that were detected by Runtime Analysis, select the right-hand side pane 'Files requested at runtime'.
- Navigate to the file, and right click and select 'Include in package'.
- Click Next to review the Registry Keys, repeat the above steps for the Registry Keys, click Next when done.
- Provide a name and description (optional) and unique identifier (GUID) for the application, in the Run field select the application executable that will be launched from shortcuts.
- Support Telemetry is enabled by default, a sample and description of data collected has been provided for reference. To disable it, uncheck the Help Us Improve (Enable Diagnostic Reports) checkbox.
- Select Package App to create the Container.
- To complete the capture process, click Next.
- To view the contents of the Container, click 'Open Package'.
- Click Edit this Package to modify the contents of the package or to change the name, description and initial executable in the Container.
- Optional, to store Containers at Cloudhouse.com refer to 'Upload to Cloudhouse' below.
- When you have finished, click the Window's 'X' to close the Auto Packager.
- Copy the Customer's reporting token into the Container's root directory.
- Refer to When To Edit A Container's Configuration to see if changes are required to the Container's default configuration.
- General information on editing and maintaining Containers.