What’s new in App Layering 4.11
Release date: May 30, 2018
This release includes the following features and improvements.
Full support for Windows 10 Store apps: Windows Store apps no longer have to be removed from an OS layer, starting with Windows 10 version 1703. If you are creating a brand new OS layer, you can use store apps by installing version 1709. If you have an existing Windows 10 layer that is version 1703 or earlier, you can add the Store apps by updating the layer to Windows 10 version 1703, or 1709 or later. If you have an existing Windows 10 version 1709 OS layer, you must wait for the release of Windows 10 version 1809 to restore the Store apps.
Enhanced Azure support: Our MS Azure connector now supports both desktops and session hosts. Using an MS Azure connector configuration, you can now publish layered images for Windows 10 to MCS running in Azure.
Support for Japanese language version of your OS: Now you can create Images for use with the Japanese language version of your operating system.
Office 365 User layer for Session Host: The Office 365 User layer gives users improved login times and faster handling of large files in Outlook. To use this feature, you publish a new type of layered image that, when deployed, manages a specialized User layer for persisting Office 365 Outlook data. Each user receives an Office 365 User layer to persist their Outlook settings and data. When a user logs into any pooled session host, their Office 365 User layer data is immediately available. When the user logs off, their Outlook settings and data are persisted and available when the user logs in.
Improved connector configuration management: With this release you can manage App Layering connectors much more easily.. Connector configurations let you automate the publishing of layered images for use in your target environments, either on-premises or cloud.
Performance guidance: For increased performance of layer packaging and creation we recommend that you keep copies of boot disks and packaging disks and reuse them when adding more layers. You can set this cache in most connector configurations, and receive reports on its effectiveness in the new connector management UI.
Citrix App Layering How Do I page: Find answers to the most commonly asked questions about deploying App Layering on our new How Do I page. Browse issues by topic category, or search the content.
Labs features in this release
Labs features are previews of potential functionality for future releases. While a feature is in Labs, you should not use it in production.. There is no guarantee that Labs feature will remain in the product, nor that the feature will work as originally designed if and when they are released. The Labs features available in this release include the following:
Full User Layer: User layers let you persist user profile settings, data, and user-installed applications in non-persistent VDI environments. This feature is supported in Windows 7 64-bit and Windows 10 64-bit environments.
App layers can be assigned as Elastic layers to layered 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.
There is no guarantee that an App layer will work on a different OS layer. If there are issues with the layer on a different OS, then disable this feature and only use the OS that you used to create the App layer.
To use a Labs feature, you need to enable the feature first. Then check this option in the Edit Properties menu for the layer that you want to assign elastically.
For information about platforms supported by Citrix App Layering, see System requirements.
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.
If you have chosen to stay on a version of the App Layering product released before version 19.1, see the Upgrade article for the upgrade path and the download link for the version that you need to upgrade to first.