Session prelaunch
& session linger
Session prelaunch starts a session before the session is
requested, so the application launch time in minimised. Session Linger is used to keep the session
open for a configured amount of time once the application closes.
Support for unauthenticated
anonymous users
For delivery groups containing server OS machines. You can
allow users to access applications and desktops without presenting credentials
to storefront or receiver. Used when users access via Kiosks so that the
application may ask for the credentials, but the citrix portals do not
When configuring a delivery group, there is the option to
grant access to authenticated and unauthenticated users or both. When you grant
access to unaithenticated users you must create an unathenticated users storefront
store
Connection Leasing
Citrix recommends using a HA fault tolerant SQL database
configuration. However, that is not
enough, because there are often times when network interruptions will prevent
delivery controllers
Form accessing the database, which in turn, results in users
not being able to connect to their applications and desktops.
Connection leasing is designed to compliment the usual HA
SQL deployment, by allowing users to connect and reconnect to their most
recently used apps and desktops, even when the site database is not available.
Each controller caches users connections to the most
recently used app’s and desktops. If the database becomes unavailable, the
controllers enter into a lease connection mode and replays the cached
connections when a users attempts to reconnect to a recently used app or
desktop.
Some of you may have wondered why it wasn’t possible to group
your applications into folders in newer versions of storefront, well now you
can. This makes managing large groups of applications easier as you can
logically group applications into parent and nested folders within the delivery
group (Up to max of 5 levels nested)
This is a good option for those companies who wish to retain
much of their Xenapp 6.5 polices and have them ported into the new Xenapp 7.6
environment:
After you install the XenApp 7.6 core
components and create a Site, the migration process follows this sequence:
- Run the XenApp 7.6
installer on each XenApp 6.5 worker, which automatically upgrades it to a
new Virtual Delivery Agent for Windows Server OS for use in the new Site.
- Run PowerShell
export cmdlets on a XenApp 6.5 controller, which export application and
Citrix policy settings to XML files.
- Edit the XML files,
if desired, to refine what you want to import to the new Site. By
tailoring the files, you can import policy and application settings into
your XenApp 7.6 Site in stages: some now and others later.
- Run PowerShell
import cmdlets on the new XenApp 7.6 Controller, which import settings
from the XML files to the new XenApp Site.
- Reconfigure the new
Site as needed, and then test it.
Specify maximum simultaneuous actions, simultenues personal
storage inventory updates, and actions per minute that can occur on a host
connection
Enhanced reporting in
Studio
More details and status and error reporting when updating
pvd images. Better licensing alrets when using the licensing node
SSL/TLS
Enable secure sockets between users and VDAs by configuring
SSL/TLS on the machines where the VDA is installed and in the Delivery groups that
contain the VDAs
