How to package an application when installation media is available (standard packaging) - AWS End-of-Support Migration Program (EMP) for Windows Server

How to package an application when installation media is available (standard packaging)

When installation media is available, an application is packaged with the EMP Compatibility Package Builder. The package builder uses installation snapshot-based packaging along with runtime analysis to create compatibility packages for applications.

Perform the steps in the following stages to create a compatibility package using the package builder when installation media is available:

Stage 1: Install capture (Required)

  1. After you install the tools from the End-of-Support Migration Program for Windows Server product page, launch the package builder from your desktop.

  2. On the Select Package Folder page, choose Select Folder. Select a package folder to specify where the package will be created, then choose OK.

  3. Choose Next.

  4. On the Start Capture page, choose Start Capture to capture the state of the system before the application is installed.

  5. Choose Next when the capture is complete.

  6. Install the application, components, and any required dependencies.

  7. When all of the installations have completed, reboot ONLY if required by the application installer. After the reboot completes, you can restart the package builder from your desktop.

  8. Return to the package builder, and on the Install Application page, choose Next.

  9. If required, proceed to Stage 2: Runtime analysis (Optional); otherwise, choose Next to proceed to Stage 3: Edit package contents (Optional) .

Note

When it is launched from the desktop shortcut only, runtime analysis reviews file and registry operations (for example, read, modification, and creation) performed by processes. This is not a required step, but can be used to review and include changes to the registry and file system during the first run of the application. It can also be helpful to review what the application processes do when running under the EMP engine.

Stage 2: Runtime analysis (Optional)

The package builder detects all files, registry keys, and shortcuts created or modified when the application runs for the first time. Shortcuts are displayed on the Run Installed Applications screen. If no shortcuts are displayed, proceed to Stage 3: Edit package contents (Optional).

Important

Do not use any desktop or Start menu shortcuts. Start the application using only the shortcuts displayed in the package builder. If you use shortcuts other than those displayed in the package builder, configuration changes will not be captured by the package builder.

The following steps enable application files and registry entries that are created when the application is configured for the first time to be captured in the package.

  1. Start the application by using the shortcut in the package builder. Do not use shortcuts on the desktop or Start menu.

  2. Choose each shortcut to load the shortcuts.

  3. Perform any required configuration changes to ensure that the application is configured for users the first time it starts. If the packaged application fails during a particular workflow, or an issue is identified during user acceptance testing (UAT), try to repeat the workflow during the packaging process.

  4. Close the programs, and choose Next to continue.

  5. Choose Complete Capture to record the final state of the system.

  6. After the capture successfully completes, the following message displays Capture completed. Please click “next” to continue. Choose Next.

Important

Do not uninstall the application during runtime analysis or the package builder will capture this change and create the package without the application.

Stage 3: Edit package contents (Optional)

Files, registry keys, and redirects can be added to, removed from, or modified in the package depending on what was captured during the install capture and runtime analysis.

The following steps show how to modify the contents of the package.

  1. On the Captured Files page, you can use the left-hand pane Files in package to view or remove files, or to add redirections for files captured in the package by the install capture process.

  2. Navigate to the file or folder, open the context (right-click) menu, then choose Redirect or Remove Item, as required. If you choose a folder and want to redirect all subfolders, then choose Redirect Children.

    If you redirect or remove an item, the available options on the context menu changes to Remove Redirect or Add Item, which allows you to reverse your changes.

  3. To include the files detected by runtime analysis, use the right-hand pane Files requested at runtime

  4. Navigate to the file, open the context (right-click) menu, and choose Include in package.

  5. Choose Next, which displays the Captured Registry Keys page. From this page, you can view and manage registry keys in the same way as files.

  6. Choose Next when you have made the required changes for registry keys.

Stage 4: Package Finalization (Required)

  1. On the Package page, in the App Name box, enter a unique name for the application, which automatically populates the App ID box.

  2. Optionally, enter a description for the application in the Description box.

  3. From the Run drop-down list, optionally select the executable that is used to load the application.

  4. Choose Package App to create the package.

  5. Choose Next when the Press “Next” to continue message is displayed.

  6. To view the contents of the package, choose Open Package.

  7. To make changes, choose Edit this Package to modify the contents of the package or to change the name, description, and initial executable in the package.

  8. When you are finished, close the package builder by choosing the X in the top right-hand corner.