|
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:
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.
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.
|
Thursday, March 10, 2016
Citrix Released XenApp/XenDesktop 7.8
XenApp and XenDesktop 7.7 features
Recently Citrix released XenApp and XenDesktop 7.7 with new features. Looks like Citrix is going in right direction of giving as same features as XenApp 6.5 to support customers.
XenApp and XenDesktop 7.7 have been Released to Web (RTW) and can be found at citrix.com/downloads (login required) under their respective sections. In addition to the core releases the following components are available as separate downloads:
·
Virtual Delivery Agent
7.7 installers
·
Provisioning Services
7.7
·
HDX Realtime Optimization
Pack 2.0
·
Profile Management 5.4
·
License Server 11.13.1
·
Citrix Receiver 4.4
Documentation can be found at docs.citrix.com. Please review the known issues for important information regarding in-place upgrades.
What’s New?
This product release includes the following new and enhanced features.
o Zones
Deployments that span widely-dispersed locations connected by a WAN can face challenges due to network latency and reliability. Configuring zones can help users in remote regions connect to local resources without forcing connections to traverse large segments of the WAN. Using zones allows effective Site management from a single Citrix Studio console, Citrix Director, and the Site database. This saves the costs of deploying, staffing, licensing, and maintaining additional Sites containing separate databases in remote locations.
Zones can be helpful in deployments of all sizes. You can use zones to keep applications and desktops closer to end users, which improves performance.
For more information, see the Zones article.
o Improved database flow and configuration
When you configure the databases during Site creation, you can now specify separate locations for the Site, Logging, and Monitoring databases. Later, you can specify different locations for all three databases. In previous releases, all three databases were created at the same address, and you could not specify a different address for the Site database later.
You can now add more Delivery Controllers when you create a Site, as well as later. In previous releases, you could add more Controllers only after you created the Site.
For more information, see the Databases and Controllers articles.
o Application limits
Configure application limits to help manage application use. For example, you can use application limits to manage the number of users accessing an application simultaneously. Similarly, application limits can be used to manage the number of simultaneous instances of resource-intensive applications, this can help maintain server performance and prevent deterioration in service.
For more information, see the Manage applications article.
o Multiple notifications before machine updates or scheduled restarts
You can now choose to repeat a notification message that is sent to affected machines before the following types of actions begin:
Updating machines in a Machine Catalog using a new master image
Restarting machines in a Delivery Group according to a configured schedule
If you indicate that the first message should be sent to each affected machine 15 minutes before the update or restart begins, you can also specify that the message be repeated every five minutes until the update/restart begins.
For more information, see the Manage Machine Catalogs and Manage machines in Delivery Groups articles.
o API support for managing session roaming
By default, sessions roam between client devices with the user. When the user launches a session and then moves to another device, the same session is used and applications are available on both devices. The applications follow, regardless of the device or whether current sessions exist. Similarly, printers and other resources assigned to the application follow.
You can now use the PowerShell SDK to tailor session roaming. This was an experimental feature in the previous release.
For more information, see the Sessions article.
o API support for provisioning VMs from hypervisor templates
When using the PowerShell SDK to create or update a Machine Catalog, you can now select a template from other hypervisor connections. This is in addition to the currently-available choices of VM images and snapshots.
o Support for new and additional platforms
See the System requirements article for full support information. Information about support for third-party product versions is updated periodically.
By default, SQL Server 2012 Express SP2 is installed when you install the Delivery Controller. SP1 is no longer installed.
The component installers now automatically deploy 32-bit and 64-bit Microsoft Visual C++ 2012 runtimes, as well as 2008 and 2010 runtimes. Visual C++ 2005 is no longer deployed.
You can install Studio or VDAs for Windows Desktop OS on machines running Windows 10.
You can create connections to Microsoft Azure virtualization resources.
The product ISO no longer includes versions of the Citrix Receiver for Mac and the Citrix Receiver for Linux. You (or your users) can download and install the Citrix Receivers from the Citrix website. Alternatively, you can make those Citrix Receivers available from your StoreFront server (see the Make Citrix Receiver installation files available on the server section in the StoreFront 3.0.x documentation, or the equivalent documentation for the StoreFront version you are using).
Citrix Director
The Director version provided with this release contains the following new and enhanced features:
o Proactive monitoring and alerting
You can now configure proactive alerting and notifications when thresholds are reached. This enables quicker responses even when you are not viewing the monitoring console.
For more information, see Alerts and notifications.
o SCOM integration
Deployments that use Microsoft System Center 2012 - Operations Manager to monitor deployments can now view alerts provided by the Operations Manager on the Dashboard and in other high level views in Director. For example, if connections to supported hypervisors fail, the administrator can check Director for Operations Manager alerts. After reviewing alert details in Director, the administrator can then switch to the Operations Manager console for additional troubleshooting, if needed.
For more information, see SCOM alerts.
o Windows Authentication
Director now supports Integrated Windows Authentication. For single sign-on, a user's Windows credentials are automatically used to access Director. This support allows users to log on to their machines using any credential provider and supporting hardware, and use that logged-on identity to access Director.
For more information, see Use Director with Integrated Windows Authentication.
o Desktop and Server OS usage
The Trends view now shows the usage of Desktop OS by Site and by Delivery group, and it shows the usage of Server OS by site, by Delivery group, and by Machine. This gives you a real-time view of your OS usage, enabling you to quickly assess your site’s capacity needs.
For more information, see Monitor historical trends across a Site.
o Application limits in Director
Application limits configured in Studio are shown in existing views and counts in Director. For example, the User Connection Failures on the Dashboard will indicate when a connection attempt fails because it would exceed an application limit.
For more information, see Application limits.
Have a nice day!!!!!!!!!1
XenApp 7.7 is Ready for Microsoft Azure
Last Quarter Citrix released XenApp 7.7 and it supports Microsoft Azure.
https://www.citrix.com/blogs/2016/01/20/xenapp-7-7-is-ready-for-microsoft-azure/
Have a nice day!!!!!!!!!
Why does ICA and RDP connections over NetScaler 11.0 63.16 hang or show latency?
Its a known issue..
Need to upgrade Netscaler firmware to 11.0.64
http://support.citrix.com/article/CTX205592
Have a nice day!!!!!
Need to upgrade Netscaler firmware to 11.0.64
http://support.citrix.com/article/CTX205592
Have a nice day!!!!!
Subscribe to:
Posts (Atom)