Amazon WorkSpaces Application Manager
Administration Guide

Understanding Color Coding

You can determine the status of an item in the dashboard by looking at the color. If the item has a conflict, hover over the item to see a message.

The following table shows the meaning of each color.

Item codes

Color / attribute Item type Description
Black All items Normal.
Grey Template folders The folder does not contain any files.
Grey Italic

Files

Folders and subfolders

Registry keys and values

The item is excluded from the package.
Blue

Files

Folders and subfolders

Registry keys and values

The item was added after the package was created. This color does not apply to items that were manually added to the package.
Magenta

Files

Folders and subfolders

Registry keys and values

The item was changed after the package was created. This color does not apply to items that were manually added to the package.
Red

Files

Folders and subfolders

Registry keys and values

The item was skipped during package creation.
Red All items The item is missing from the package or the item has a conflict. For more information, see the following table on conflict codes.
Bold Folder Working folder.
Bold File Command line.

Red text in the tabs represent a conflict in your package. The following sections describe the conflicts in the tabs.

Files tab

Field Meaning

Source File

The file for the item is not in the package. Add the missing file to the package.

Fonts tab

Field Meaning

Action

The fonts are set to be registered, but the font will not be visible to the operating system because the Fonts key is set to Virtual-isolated (layer 4).

Action and File Disposition

The fonts are set to be registered, but the font will not be visible to the operating system because the font file is set to Virtual-isolated (layer 4).

File Path

The file for the item is not in the package. Add the missing file to the package.

Startup tab

Field Meaning

Name and Command Disposition

The Registry Run (or RunOnce) key asset cannot be started by the system because the key is set to Installed-permanent (layer 1) or Installed-temporary (layer 2), but its target command line is set to Virtual-integrated (layer 3) or Virtual-isolated (layer 4)so it will not be visible to the system.

Command Disposition for entries under HKCU Run or HKCU RunOnce

One of these two conditions exists:

  • The shortcut file does not exist on the system.

  • The startup shortcut cannot be started by the operating system because it is set to Installed-permanent (layer 1) or Installed-temporary (layer 2), but its target command line is set to Virtual-integrated (layer 3) or Virtual-isolated (layer 4) so it will not be visible to the operating system.

Services & Drivers tab

Field Meaning

Action

This action cannot be performed on a service whose type is not specified.

Error Control

The error control type is not specified.

Interactive

The interactive setting is not specified.

Image File

The driver is set to start on boot or system start, but its service key or image file is set to Virtual-integrated (layer 3) or Virtual-isolated (layer 4) so it will not be visible to the system at that time.

Image File and Key Disposition

The image file layer is greater than the service key layer, which can yield inconsistent behavior except if the service key is set to Virtual-integrated (layer 3) or Virtual-isolated (layer 4).

Name

The service is set to restart or reboot automatically upon failure. This will cause the service to always restart when the application is shut down, which will put it back into the Running state. To fix this issue, set the failure action of the service to Turn Failure Actions OFF.

Start

The start type is not specified.

Type

The service type is not specified.