-
-
What's new in App Layering 2009
-
-
-
-
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已动态机器翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
This content has been machine translated dynamically.
This content has been machine translated dynamically.
This content has been machine translated dynamically.
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.
Este artigo foi traduzido automaticamente.
这篇文章已经过机器翻译.放弃
Translation failed!
What’s new in App Layering 2009
The App Layering 2009 release includes support for the following enhancement:
- You can now override the default repository path and layer size for user layers by configuring Citrix Studio Policies.
- The user interface for the App Layering management console has been updated with new Citrix branding images.
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!
Related information
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select Do Not Agree to exit.