Amazon WorkSpaces Application Manager
Administration Guide

Application Packaging Issues

The following are possible application packaging issues.

How can I hide the Add/Remove Programs entry for my application?

Many applications add an entry in the Add or Remove Programs or Programs and Features list in the Windows Control Panel. This entry can be confusing because the application is virtual and cannot be uninstalled. You can remove this entry from the list.

To hide the application entry

  1. In the project in Amazon WorkSpaces Application Manager Studio, choose the Registry tab.

  2. Open the context (right-click) menu of the following registry key and choose Delete.


I cannot change the settings in my package

You opened your package in read-only mode by double-clicking the package in the dashboard. To change the settings in your the package, open the package in update mode by choosing Update on the Amazon Studio toolbar. If the application in the package is already installed on the packaging instance, a message box offers a choice to overwrite the existing files. Choose Yes to overwrite the files on the package instance with the files in the package. The overwritten files are displayed in the Progress dialog box.

Some application install new printer devices, which can be included in a package. On the Files tab of Amazon WorkSpaces Application Manager Studio, the spool folder is a subdirectory found under the SystemDir system folder. Applications that come with printer drivers may not work properly if this folder is removed from the Files tab. On the Registry tab, the following registry key contains references to the printer drivers in the spool folder:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows NT x86\Drivers

If a new printer does not appear in the application, use the following procedure.

To restart the print spooler

  1. In Amazon WorkSpaces Application Manager Studio, choose the Project tab on the top of the project pane.

  2. Under 3. Optional settings, choose Settings.

  3. In the Settings dialog box, choose Virtualization.

  4. Under Special requirements, choose Restart Print Spooler and OK.

I cannot retrieve my application list

If you receive an error from the Amazon WorkSpaces Application Manager Studio stating that your app list could not be retrieved, verify that you have created the proper IAM role as explained in Create the Application Packaging Role, and that you applied that role to the packaging instance.

My application does not run because of a licensing issue

Many applications employ some form of copy protection to prevent theft and enforce proper licensing. Amazon WorkSpaces Application Manager Studio does not remove copy protection. If you need to enable multiple users to use an application, package the application so that it uses a serial number for high volume licensing and multiple systems can activate with a single key (for example, Microsoft products use volume license keys). Otherwise, the application prompts users for a license; not all systems will be able to activate and make the application fully functional.

Test the package on other systems to ensure that there is no form of license enforcement that you are not already aware of. If the package does not work or prompts for licensing, retest the package on the packaging instance. If the application binds to hardware, it should work on the same system. For information about supported licensing models, contact the software ISV.

My application fails to start

Sometimes an application can fail to start when the command line is incorrect. You might have to specify a different executable at the command line or you might need to add parameters. Check the original application shortcut, typically found on the Start menu, and use the same command line and parameters as what appears in 4. Package build of the Amazon WorkSpaces Application Manager Studio.

Another problem may be that some applications modify the PATH environment variable of the local machine during installation or after starting for the first time. There may be some system-specific entries included in the PATH variable (for example: PATH=%PATH%;C:\ApplicationPath1;C:\ApplicationPath2). Ensure that the package does not contain system-specific entries by choosing the Environment tab, Path, and then checking for the any application-specific path environment variables in the Value field.

My application is missing dependencies

Many applications require the presence of a specific runtime library or a minimum version of the . NET Framework. Amazon WorkSpaces Application Manager Studio comes with the latest builds of the following C + + runtime libraries:

  • Visual C++ 2008 x86 and x64

  • Visual C++ 2005 x86 and x64

If your application requires other dependencies, install the dependencies before you install the application. After you capture the dependency installation, set the disposition of the dependency files and registry keys to Virtual-isolated (layer 4) before you upload your package.

To set the disposition of files and registry keys

  1. In Amazon WorkSpaces Application Manager Studio, choose the Files tab on the top of the project pane.

  2. Open the context menu (right-click) for the dependency file or folder and choose Properties.

  3. In the Properties dialog box, choose Virtual-isolated (layer 4) and OK.

  4. On the Registry tab, open the context menu (right-click) for the registry hive or key and choose Disposition.

  5. In the Registry Key Disposition dialog box, choose Virtual-isolated (layer 4) and OK.

My file associations do not work

Windows manages file extension associations to applications under the HKEY_CLASSES_ROOT hive of the Windows registry. The file type must be set in the registry and the application executable must not be hidden. Make sure that the file extensions you need exist in the Registry tab of the project. If the extension is missing, manually add the extensions.

You can also package a new version of the application where you choose All processes under Capture file and registry activity for the following processes in the Capture Application Installation dialog box, run the application, and configure the default file associations. Check that the application executable file is not hidden and the disposition is set to Virtual-integrated (layer 3).

To create a new package version

To create a new package version, you need the installation files.

  1. In Amazon WorkSpaces Application Manager Studio, choose the Dashboard tab on the top of the project pane, select your project in the list, and then choose Update in the toolbar and Close.

  2. Under 2. Application installation, choose Install.

  3. In the Capture Application Installation dialog box, do the following:

    • For the Installer path field, enter the path and file name to your installer.

    • For the Command line parameter field, enter any parameters required to install your application.

    • Under Capture file and registry activity for the following processes, choose All processes.

    • Choose Ignore changes under the Installer path specified above.

    • Choose Launch, install your application, and then choose OK and Close.

  4. On the Files tab, open the context (right-click) menu for your executable file and choose Properties.

  5. In File Properties, under Disposition, choose Virtual-integrated (layer 3) and OK.

  6. On the Project tab, do the following:

    • In 4. Package build, enter text to describe this new version in the Label field. This text appears as a version of the package.

    • In 5. Package upload, choose Upload.