Citrix have released Virtual Driver Channel tool for XenApp and XenDesktop environments.

Description

This tool provides the ability to pass the end client information to a XenApp application in XenApp / XenDesktop environments. The tool creates a virtual channel between a XenDesktop VDA and a XenApp server session. The virtual channel driver on the VDA monitors the status of client connections and sends notifications when a client connects or disconnects to the VDA. XenApp applications can use provided APIs to collect end client information or status.

Prerequisites

Install an ICA client before installing VDCLNTINFO.msi on the XenDesktop client. The current release of the vdclntinfo setup does not have dependency checking, and requires the ICA client to be installed first.

Installing Virtual Driver Channel

Install an ICA client before installing VDCLNTINFO.msi. Install VDCLNTINFO.msi. Kill wfcrun32.exe if it is running.

How to Test Virtual Driver Channel

To Verify that it is working: Copy ctxclntinfo.exe to a XenApp Server. Connect to a XenDesktop that has VDCLNTINO.msi installed. Launch a XenApp CMD session or a published desktop from the XenDesktop VDA. Run ctxclntinfo.exe. It should output the client name and IP address. Run ctxclntinfo.exe /loop. It will wait on client connect/disconnect notifications. You can now disconnect from the VDA and reconnect to the VDA from a different client. The demo application outputs the new client information.

How To Use Virtual Driver Channel

See README.pdf for APIs associated with the tool.

Source

Download Virtual Driver Channel here

The long waited Citrix Branch Repeater 6.0 is out for download. Here is whats new in this release.

Release 6.0 is a major software release for the Citrix Branch Repeater. This release contains a number of new features along with bug fixes.

Release 6.0 is the first production release of the Branch Repeater 6.x software, which introduces traffic shaping, enhanced reporting, improved Windows Filesystem and Outlook/Exchange acceleration, and many other features.

Release Highlights

This major release of Repeater and Branch includes a significant number of new features, including:

• Smart Acceleration
  Now traffic can be prioritized based on a variety of different parameters including service class, protocol, QoS parameters, IP address or range, port, etc.  Applications are automatically detected and QoS features can be applied to all traffic including unaccelerated protocols like UDP.

• Extensive Reporting on WAN Bandwidth Utilization
  Repeater administrators will have a vastly improved view into WAN operations and bandwidth utilization with several new dashboards and graphs.
• ICA Prioritization based on Desktop Group or Published Apps
  XenDesktop and XenApp administrators can prioritize traffic on a WAN link based on an individual’s desktop group or a specific XenApp published application.
• Over 500 Pre-Defined Service Classes
  Repeater and Branch Repeater 6.0 includes and automatically detects over 500 pre-defined applications on the WAN.  Priorities can be assigned to the pre-defined service classes so unintended traffic like games can be given very low priority or blocked.
• And Many More Features
  Support for new features in the next releases of XenDesktop and XenApp, new printing acceleration enhancements, SMB2 and encrypted MAPI acceleration, acceleration for Outlook and Exchange 2010 and support for the Citrix License Server.

New Features in Release 6.0

• Traffic shaping which expedites WAN traffic according to user-selectable policies. Both accelerated and non-accelerated traffic are shaped to give full control over the link. Traffic shaping replaces the “Repeater QoS” feature.
• Traffic classification and reporting give greater visibility into WAN traffic. • Multi-stream ICA support provides a better user experience for XenApp and XenDesktop by combining acceleration with enhanced traffic shaping.
• Vista/Windows 7/Windows Server 2008 Filesystem acceleration. New SMB2 accel- eration features increase remote filesystem performance.
• Windows filesystem acceleration. Signed SMB can now be accelerated.
• Enhanced MAPI Acceleration. Encrypted connections between Outlook and Exchange Server can now be accelerated.
• Support for multiple links. In previous releases, Branch Repeater had a single-link model. Release 6.0 supports up to ten independent links, each with its own link speed, so traffic can be shaped precisely on every link.
• Remote license server support. Release 6.0 allows a remote network license server to supply the Branch Repeater licenses, simplifying deployment.
• Dashboard page provides a quick view of current system status.
• “Features” page. The product’s enable/disable toggles have been combined on a single page.
• Simplified menu structure. The number of top-level menu categories has been reduced. Entries within a category are now alphabetized. Similar functions have been combined into a single page, such as “Advanced Deployments,” which con- tains the functionality of the old high-availability, WCCP, group-mode, and proxy-mode pages.

Compatibility

Note: The Repeater Plug-in is not included with release 6.0 Plug-ins from prior releases will interoperate with Appliances running release 6.0

Note: Branch Repeater with Windows Server is not included in release 6.0 Branch Repeater with Windows Server Appliances from prior releases will interoperate with Appliances running release 6.0

Supported Products

Bellowed figure shows supported products and platforms for Citrix Branch Repeater

Supported Branch Repeater VPX Configurations

Release 6.0 is supported on Branch Repeater VPX running on both XenServer (5.5 and 5.6, but not 5.6 FP1) and VMware vSphere ESX/ESXi 4.1 hypervisors.

Note: The User’s Guide incorrectly states that VMware vSphere ESX 4.0 is supported. The correct list is “ESX 4.1 and ESXi 4.1.”

Note: The User’s Guide incorrectly states that the “Enable Bridging” feature is on the “System Status” page, when it is on the “Features” page.

RAM and vCPU requirements have increased with this release. See Figure 2 and Figure 3.

Licensing

Release 6.0 supports both remote license servers and locally installed licenses. If you are upgrading an existing system with a local license, it will continue to work.

Branch Repeater VPX supports two license types: remote and local licenses

• Production licenses use remote licenses hosted on a Citrix license server. Production licenses include retail, CSP, and annual licenses
• Non-production licenses (such as VPX Express and Eval licenses) are installed locally on the Branch Repeater VPX virtual appliance
• Annual and CSP licenses need to be installed on your license server

Sources (require MyCitrix ID)

Download Release notes for Citrix Branch Repeater 6.0 here

Download Quick Installation Guide for Citrix Branch Repeater 6.0 here

Download User Guide for Citrix Branch Repeater 6.0 here

Download Branch Repeater VPX for Citrix XenServer and VMware vSphere Software Release 6.0 here

Download Citrix Branch Repeater Appliance Software Release 6.0 here

Summary

This document provides an overview of the Windows services installed with the XenDesktop software. Refer to version release notes for the latest updates to these services, known issues, and such. Licensing services, which are not listed here, might also appear if the license components are installed on the same server as the XenDesktop controller.

Controller Services

VDA Services

The Citrix and AppSense relationship demonstrates over ten years of joint respect, understanding & recognition and engagement with each other as leaders in our respective fields.   Together Citrix and AppSense have developed and delivered solutions into some of the world’s largest and most demanding computing environments which can be read about in our numerous joint Case Studies and Video Testimonials, for example:
Citrix.com – Managing Finance Users with AppSense User Virtualization
Citrix.com – Managing Healthcare’s Roaming User with AppSense

One of the main drivers behind a joint AppSense and Citrix solution, is to enable and adopt a Desktop Transformation project, such as a Citrix XenDesktop environment, faster, with less risk & disruption, at lower cost and with maximum user acceptance.  Best practice and the first step in transforming your existing desktop to a low-cost, dynamic Citrix XenDesktop is to virtualize the user first, separate them along with all of their information from the existing platform, swap out and move to Windows 7 on Citrix XenDesktop, then re-apply the user and all of their relevent settings and data to the new environment.

This best practice to ‘Simplifying Desktop Transformation’ can be seen in the Citrix and AppSense White Paper within the Citrix Desktop Transformation Model:  AppSense User Virtualization – Extending the value of Citrix and forming a strategic component of the Citrix Desktop Transformation Model (DTM), which can be downloaded from Citrix.com here.

Below are a couple of highlights from the paper:

“The Citrix Desktop Transformation Model (DTM) is designed to help customers get from “wow to how” and quickly realize the many benefits of desktop virtualization. Citrix has worked closely with customers and partners – in this case AppSense User Virtualization – to develop the first industry-endorsed, repeatable method for transforming desktop computing from today’s device-centric, distributed management paradigm, to a more user-centric, virtualized model.”

When used with your Citrix Desktop Transformation Project, AppSense User Virtualization provides:

Other topics in the White Paper include:

Upon reading the White Paper and when you are ready for your next steps in Desktop Transformation, you may be interested in the joint Citrix and AppSense Proof of Concept Kit, details of which are also in the paper in the ‘Further information and next actions’ section.

There are other documents created by Citrix to help educate and cover the benefits of User Virtualization in your Citrix environment such as the Citrix Case Study on AppSense – Leading User Virtualization Solution. which provides more information on why “Citrix recommends the use of AppSense for advanced user personalization and desktop configuration requirements in enterprise environments.”

Further information can be found within the Citrix Featured Partners pages, which highlights their leading Citrix partners in their respective fields and how they add further value and form a strategic component of Desktop Virtualization and Transformation – AppSense and XenDesktop Featured Partner Page

I hope this is of help and provides insight on managing the user component of the desktop as part of your Citrix Desktop Transformation Model, please let me know if you have any questions or would like any further information.

Summary

This document describes how to map certain USB devices which might be blocked by default.

Requirements

The endpoint client device must recognize the USB device to have it mapped to the session. If the device requires a special driver, the driver must be installed on the Virtual Desktop Agent (VDA). The device can be still be mapped without the driver as long as the endpoint recognizes it, but it does not function properly.

Background

Certain USB classes are blocked by default because they are used mainly only on local workstations. Smartcard readers are an example.

Procedure

Caution! This fix requires you to edit the registry. Using Registry Editor incorrectly can cause serious problems that might 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.

Find the Class ID and Hardware ID of your device. Follow the steps below:

Open Computer Manager on your endpoint client computer, you should see something like the screen shot below for your USB device (HID compliant devices are blocked by default).

Click Properties and, on the details pane, check the Hardware ID and the Class ID.

In Desktop Studio > HDX policy > User Policies, go to the Desktop Delivery Controller (DDC) and enable Client USB devices redirection.
Go to Client USB devices redirection rules > Edit.
Set to new and for the above Hardware ID’s Allow: VID=0911 PID=1844.
Apply the rule. It should create a registry key on the VDI at HKLM\Software\*Policies\*Citrix\ICA_Client\USB and this should include the Allow: VID= PID= #device. If not, you might need to manually create that later.
On your endpoint device, check HKLM\Software\Citrix\Ica Client\GenericUSB\  and the wow6432 node respectively. If you have a 64-bit system, set in the devicerules key allow: VID=0911 PID=1844.

If you prefer to enable everything for this class, you could also remove the deny class rule. However, the preferred way is to add an allowhardware ID rule. Make sure the allow rule is on the top of the list.

The USB devices should be visible in Desktop Viewer.

If clicking on the device does not map it to the session, consider manually creating the key on the VDA.
HKLM\Software\Policies\Citrix\ICA_Client\USB\DeviceRules with the allow tags

More Information

The default values are stored on the VDA in HKLM\SOFTWARE\Citrix\PortICA\GenericUSB Type=String Name=”DeviceRules”, however, it is advised not to edit the key because when the VDA checks, it first looks at HKLM\Software\Policies\Citrix\ICA_Client\USB\DeviceRules and thereafter only checks the default location. Therefore, the preferred way is to edit the policies through Group Policy Object (GPO) templates.
You do need to edit the registry on the endpoint to allow the client to offer the USB class.

See also: http://support.citrix.com/proddocs/index.jsp?topic=/xendesktop-rho/cds-customize-usb-support-rho.html