Citrix App Layering

What’s new in App Layering 2008

Important:

App Layering 20.8.3 includes an important update to the included drivers. If you are using secure boot, you must upgrade to 20.8.3!

The 20.8.3 installation and upgrade packages are available for download. For new installations, download the Appliance Installation Package. For upgrades, download the Appliance Upgrade Package.

New features in this release

The App Layering 2008 release includes support for the following features and enhancements:

  • Windows 10, 2004 support: Windows 10, 2004 is now supported as the OS for layered images. Using Windows 10, 2004 requires App Layering version 2008 or later. The required changes for this version of Windows 10 are not in previous App Layering releases.

  • Citrix Hypervisor 8.2 support We now support Citrix Hypervisor version 8.2.

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 admistrators with proper permisisons can start the upgrade. (Other users can select Remind Me Later to turn off 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 won’t cause issues in spite of 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, and an agent upgrade for hypervisor and provisioning servers where you have installed the agent. Also expect to republish images to get the latest upgrades on those images.

Be sure to refer to the Upgrade article for details about upgrading from the specific version that you currently have to the lastest one!

What’s new in App Layering 2008