Thursday, March 10, 2016

Citrix Released XenApp/XenDesktop 7.8


XenApp and XenDesktop 7.8 are available now!
 
The XenApp and XenDesktop 7.8 release comprises new Windows VDA versions and new versions of several XenApp and XenDesktop core components. You can download XenApp and XenDesktop 7.8 here.
 
With XenApp and XenDesktop 7.8 you can:
 
  • Install or upgrade a XenApp or XenDesktop Site
  • Install or upgrade VDAs in an existing Site
 
The XenApp and XenDesktop download pages for this release also include updated versions of the following software. For feature information and installation instructions, see the component's documentation.
 
  • AppDNA
  • StoreFront
  • Provisioning Services
  • Citrix Receiver for Windows
  • Citrix Receiver for Mac
  • HDX Real-time Optimization Pack
 
The product release includes the following new and enhanced features.
 
AppDisks
The new AppDisks feature separates applications and groups of applications from a master image’s OS, enabling you to manage them independently. You can now manage the applications as a distinct entity: an AppDisk.
 
AppDisks differ from other application-provisioning technologies in two ways: isolation and change management. Unlike Microsoft App-V, an AppDisk does not isolate applications; it separates them. Change management (updating master images and testing the compatibility of updates with installed applications) can be a significant expense to organizations. Using AppDNA with AppDisks provides this change management capability. AppDNA identifies potential issues with image updates and suggests remediation steps.
 
Enhanced support for Microsoft Application Virtualization (App-V)
You can now deliver Microsoft App-V applications to users without having to configure and manage Microsoft App-V management and publishing servers in Studio. Instead, you can import App-V packages directly from a network share to an Application Library held by Citrix Studio. App-V applications can be delivered through Delivery Groups to users from this library, just like other applications discovered from a master image or from Microsoft App-V servers, if you have them. The new "single admin" management method can be used instead of, or in addition to, the existing "dual admin" management method.
 
Applications node in Studio
The new Applications node in the Studio navigation pane provides a central way to manage all of your applications, regardless of Delivery Group assignment. One of its key benefits is the ability to add applications to more than one Delivery Group at one time.
 
In earlier releases, to manage applications, you selected a Delivery Group in the Studio navigation pane, and then selected the Applications tab in the middle pane. Now, you simply select Applications in the navigation pane.
 
When you add an application to more than one Delivery Group, you can specify the priority of each Delivery Group (0 is the highest); XenApp or XenDesktop will attempt to launch the application from the highest-priority Delivery Group; if that is not possible, the application in the second-highest Delivery Group will be launched, and so on.
 
The Add Application wizard offers a dropdown from which you select the source of applications: a machine created in the Machine Catalog, an App-V package, an application you have already added to the Site (perhaps in another Delivery Group), or a manually-defined application.
 
Updated Create Delivery Group wizard and Edit Delivery Group interface
In previous versions, the Create Delivery Group wizard included a page for specifying the delivery type (applications and desktops, applications only, or desktops only). In this version, the Delivery Type page is displayed only if you selected a Machine Catalog containing assigned desktop OS machines; in that case, you can specify whether the machines in that catalog will deliver desktops or applications. For all other machine types, the machines in the group can deliver applications and desktops. In some cases, you can change the delivery type later by editing the Delivery Group.
 
In previous versions, the Create Delivery Group wizard included a page for specifying a StoreFront address. In this version, the StoreFront page no longer appears in the Create Delivery Group wizard. It is assumed you will provide a StoreFront server address from the StoreFront node in Studio. You can also specify StoreFront information later by editing the Delivery Group.
 
The Applications page in the Create Delivery Group wizard now offers a new dropdown from which you select the source of applications you're adding to the Delivery Group: a machine created in the Machine Catalog you selected, an App-V package, an application you have already added to the Site (perhaps in another Delivery Group), or a manually-defined application.
 
The Desktops (or Desktop Assignment Rules) page enables you to specify which users or groups can launch a VM, use a desktop, or have a desktop assigned. If the Delivery Group contains machines from a static assigned catalog, you can also specify the maximum number of desktops per user.
 
The Summary page now includes an optional description field that is displayed in Citrix Receiver. You can change this description later by editing the Delivery Group.
 
Improved tag interface in Studio
Tags are strings that identify items such as machines, applications, Delivery Groups, and policies. After adding a tag to an item, you can tailor search queries and policy assignments to apply only to items that have a specified tag.
 
In previous versions, one dialog box was available for adding and editing tags, and tags could be assigned only to policies. This version offers a more robust and easy-to-use interface, as well as wider applicability.
 
VMware SSL thumbprint
The VMware SSL thumbprint feature addresses a frequently-reported error when creating a host connection to a VMware vSphere hypervisor. Previously, administrators had to manually create a trust relationship between the Delivery Controllers in the Site and the hypervisor's certificate before creating a connection. The VMware SSL thumbprint feature removes that manual requirement: the untrusted certificate's thumbprint is stored on the Site database so that the hypervisor can be continuously identified as trusted by XenApp and XenDesktop, even if not by the Controllers.
 
When creating a vSphere host connection in Studio, a dialog box allows you to view the certificate of the machine you are connecting to. You can then choose whether to trust it.
 
And more! See XenApp and XenDesktop 7.8: What’s new for more information.

No comments:

Post a Comment