Citrix has released a hotfix For XenApp 6.5 for Windows Server 2008 R2 to solve the following problem(s):
- The CPU consumption of the winlogon.exe process can be higher than usual and cause new connection attempts to fail once a server hosts 70 connections or more. Eventually, servers can experience a fatal exception and need to be restarted.
Important Note(s) about This Release
- Note: As a best practice, Citrix recommends that you install this and other hotfixes only if you are affected by the specific issues they resolve. Otherwise, Citrix recommends that you wait for the next hotfix rollup pack for your product release. Hotfix rollup packs consolidate most previously released hotfixes and allow you to update systems in a convenient, single installation. Continue reading “Hotfix for Citrix XenApp 6.5”
This is a very nice chalk talk video from Citrix about how XenApp works. This video is about 2.5 minutes long so it doesn’t take too much time away from your busy schedule . Continue reading “Video: How Citrix XenApp works”
XenApp 6.5 does not provide a binary upgrade path from XenApp 6.0. For some environments, the ability to create a new virtual machine image or clean installation XenApp 6.5 servers might not be possible.
The script performs what normally would be a long process of manually uninstalling XenApp 6.0 components in a select order, then installing XenApp 6.5. The following steps are performed:
- Checks to see if XenApp 6.0 is installed or not, and if the XenApp 6.5 installer is available.
- Prompts for a password to silently run the install process after reboot.
Note: This is not stored by the script but is stored by the operating system in the Task Scheduler.
Continue reading “XenApp 6.0 to 6.5 Upgrade Utility”
Citrix has released a great document on the advanced farm administration with XenApp worker groups.
Here’s a preview of the document.
The release of XenApp 6 adds powerful new features for XenApp administrators through integration with Active Directory (AD). All user and server settings can now be managed through AD policies, while applications and load balancing can be managed through a new container known as a worker group.
Worker groups allow similar XenApp servers to be grouped together to greatly simplify the management of XenApp farms. By publishing applications and managing server settings via AD and worker groups, administrators can reduce the time to deploy new XenApp servers and increase the agility of their environment.
In this white paper, we consider a fictitious company with a large, geographically-distributed XenApp farm. This company must deliver applications to two distinct groups of users with different needs. This white paper outlines the new worker group features in XenApp 6 and shows how any company can leverage worker groups to simplify their farm management. Throughout the paper, we detail the best practices for creating and managing worker groups and how these can be applied in an enterprise XenApp deployment.
You can download the document here.
The following MD5 and SHA256 information is provided to assure download completion and accuracy. Verify the MD5 or SHA256(s) before using a downloaded package to install a product, post to a centralized location for broader access, or burning to media. Continue reading “XenApp 6.5 Downloads Reference List”
Provisioned XenApp servers do not accept connections when restarted while the license server is unavailable.
- Provisioned XenApp servers
- XenApp 6.0
- License Edition 11.9
The license server cache file, MPS-WSXICA_MPS-WSXICA.ini, is saved in the %systemroot%Program FilesCitrix folder, which might be unavailable when the server image shuts down and Provisioned XenApp servers refuse to accept connections when they are restarted while the license server is unavailable.
The following are the steps to complete the task:
Save the license server cache file in a shared network location – a location separate from the XenApp server image so that the file is available even when the server image shuts down.
If you save the file in a location away from the server image, you must set the following registry key to point to the cache file location:
Caution! This fix requires you to edit the registry. Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.” Continue reading “Provisioned XenApp Servers do not Accept Connections”
Citrix has released a new best practices guide for XenApp and XenDesktop.
The foundation of any good XenDesktop or XenApp enterprise design should be adherence to a collection of best practices which are based upon knowledge gathered from previous enterprise deployments, lab validations, and lessons learned in the field. Such best practices are just a starting point for a design, as an organization’s specific design requirements will often necessitate deviation from the recommended path. By using the following recommendations as a starting point, the foundation of the design will be robust enough to support many different deployment scenarios.
This document consolidates and summarizes the best practices for XenApp and XenDesktop environments. As products evolve, best practices also change, which is why each best practice discussed in this document is associated with a specific product and version, which includes the following:
- XenDesktop 5.0, 5.5, 5.6
- XenApp 6.0, 6.5
Additional best practices are provided for those products which provide complimentary functionality to both XenDesktop and XenApp, including:
- Citrix Provisioning Services
- Citrix XenServer
- Citrix Profile Manager
- Microsoft Hyper-V
- VMware vSphere
You can download this guide here.