AL001 - Colliding Layer Identifiers

Description: Citrix AppLayering layers are checked for the presence of duplicated layer identifiers. A collision occurs when two or more packages contain the same identifiers.

Background: Each Citrix AppLayering layer contains a set of metadata information that describes basic properties of the layer. Some of these properties are critical to the internal consistency of the system. These include, for example, a layer identifier which plays a crucial role in determining the identity of the layer determining the relationship and so on.

More Information: None available.

Manual Remediation: Duplicated layer identifiers should be changed so that they are globally unique on each system.

AL002 - Files

Description: The Citrix AppLayering layer is compared to other layers and scanned for the presence if identical file names in the same folder. A collision may occur when the same file is installed by more than one layer.

Background: Files are the main element of nearly every application. Proper working of the application depends on the availability of specific versions of these files in the appropriate locations. If different applications install different versions of the same file in the location, then it might cause a collision between them.

More Information: None available.

Manual Remediation: Self-developed software should be reauthored to access the colliding files in a different location. Conflicts caused by unneeded resources should be resolved by manually cleaning up each layer from the resources that do not belong to nor are required by the core application.

AL003 - Registry

Description: The Citrix AppLayering layer is compared to other layers and scanned for the presence of identical registry value names containing different data.

Background: The Windows registry contains three basic elements: keys, values, and data. A collision occurs if multiple applications add the same registry value with different data.

More Information: None available.

Manual Remediation: Self-developed software should be reauthored to read the registry values from a different key or different value name. Conflicts caused by unneeded resources should be resolved by manually cleaning up each layer from resources that do not belong to nor are required by the core application.