App Layering

What’s new in App Layering 2102

The App Layering 2102 release includes support for the following enhancement:

  • App Layering now runs on Google Cloud Platform!
  • You can:
    • Install an App Layering appliance on Google Cloud Platform.
    • Create connector configurations for Google Cloud Platform and Machine creation for Google Cloud Platform.
    • Create layers on Google Cloud Platform.
    • Move layers from a different platform to Google Cloud Platform, using the Export and Import feature.
    • Publish layered images on Google Cloud Platform, or to Machine creation running on Google Cloud.

Labs features in this release

Labs features are previews of potential functionality in future releases. While a feature is in Labs, do not use it in production. There is no guarantee that a Labs feature remains in the product. When released, the feature can work differently.

The Labs features available in this release include the following:

  • You can assign app layers as elastic layers on images that use a different OS layer: Until now, elastic layer assignments required that the app layer assigned use the same OS layer that was used to create the app layer. Now you can try assigning an app layer as an elastic layer on a layered image that uses a different OS layer.

    Important:

    Running an elastic layer on a different OS layer than the one used to create it can have issues.

To use a Labs feature, you need to enable the feature first.

Supported platforms

For information about platforms supported by Citrix App Layering, see System requirements.

Upgrade path and considerations

For the latest fixes and features, including compatibility with other software packages that you use, we encourage you to stay current with the App Layering upgrades.

Partially automated upgrades

The App Layering upgrade process is partially automated. The appliance periodically checks for upgrades and downloads the latest package, verifies it, and extracts the files. Users receive a message the next time they log in, and administrators with proper permissions can start the upgrade. (Other users can select Remind Me Later to clear the message.)

The 2005 upgrade package is large enough that older appliances cannot download it automatically. If you are running version 1911 or older, download the package manually from the downloads site. Also, we recommend running the upgrade from a management console in Secure HTTP (HTTPS). If you upgrade while in HTTP, messages do not display in the browser. If that happens, refresh the browser after 20 minutes. (Refreshing does not cause issues, despite the message that says not to refresh.) If the upgrade is still running, you get a “service unavailable error.” It is safe to ignore the message and keep refreshing the browser every few minutes until the login page appears.

If you are on a pre-19.1 version of App Layering, see the Upgrade article for the correct upgrade path.

Components that require upgrading

App Layering upgrades include:

  • The appliance upgrade.
  • An agent upgrade for hypervisor and provisioning servers where you have installed the agent.

Find the correct upgrade for the specific version that you have, using the Upgrade article.

After upgrading, get the latest version on your existing images by republishing them.

What’s new in App Layering 2102