Archive for June, 2011

Citrix Branch Repeater 6.0

Written by Thomas Poppelgaard. Posted in Branch Repeater, VMware, Windows Server 2008R2, XenApp, XenDesktop, XenServer

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

Types of Licensing Available for NetScaler and Access Gateway Enterprise Edition Appliances

Written by Thomas Poppelgaard. Posted in Access Gateway, Netscaler

Summary

This article contains information about various types of licenses available for NetScaler and Access Gateway Enterprise Edition appliances.

Types of Licenses

Citrix provides the following types of licenses for NetScaler and Access Gateway Enterprise Edition appliances:

  • Retail NetScaler (physical box) License: This is a license for the physical appliance. This license helps you to enable all necessary features of the appliance and 5 Secure Socket layer (SSL) Virtual Private Network (VPN) connections. By default, this license is allocated to Hostname “ANY” in the MyCitrix Web site. You cannot change this allocation.
  • Other NetScaler licenses: These licenses include Internal, Partner USE, DEMO, EVALUATION, or VPX. You need to allocate these licenses to to Host ID of the appliance.
    Refer to the following Knowledge Center articles for more information:
  • Access Gateway Platform License: You must upload this license to increase the Independent Computing Architecture (ICA) connections up to 10000.
  • Access Gateway Universal Licenses: This license increases Full SSL VPN connections.

You need to allocate some of these licenses to the NetScaler Licensing Hostname, which is configured in the /nsconfig/rc.conf file. This hostname is not necessarily the same Hostname that was created by running the set ns hostname, unless you have configured otherwise. By default, the hostname in the /nsconfig/rc.conf file is “ns”, as shown in the following command output:

root@ns# grep hostname /nsconfig/rc.conf
hostname=”ns”

If there is an issue with the hostname allocated for the Access Gateway Platform license, then you can verify the content of the /var/log/license.log file, which should be similar to the following sample content of a /var/log/license.log file:

34 (CITRIX) Wrong hostid on SERVER line for license file:
9:50:34 (CITRIX)       /nsconfig/license/license_20110316121246.lic
9:50:34 (CITRIX) SERVER line says HOSTNAME=My-Netscaler, hostid is HOSTNAME=ns
9:50:34 (CITRIX) Invalid hostid on SERVER line

In the preceding sample, the license is incorrectly assigned to the My-Netscaler hostname considering that to be the Licensing Hostname because the hostname was set as My-Netscaler by running the set ns hostname command. However, the rc.conf file has the hostname set as “ns”.

Unable to Download ARDBP32.bin when Using XenServer or Hyper-V with HP Flex-10/Flex Fabric Module

Written by Thomas Poppelgaard. Posted in HP, Provisioning

Symptoms

You are unable to download ARDBP32.bin when using XenServer or Hyper-V with HP Flex-10/Flex Fabric module.

Affected Hardware

HP G7 Blade enclosures using the NC553i with a Flex-10 module

Cause

During the PXE boot process, the target device attempts to download ARDBP32.BIN from the TFTP service that resides on the Provisioning Services server.

Targets that send their TFTP request from a XenServer or Hyper-V Virtual Machine that then passes through the Flex-10 have their UDP checksum invalidated which causes the packet to be dropped when it reaches the Provisioning Services server.

Status

Citrix is aware of the issue and is working with HP and Emulex to resolve this issue.

Workarounds

If the Flex-10 module is replaced with a pass-through module, then the Bin file can download correctly.

This document applies to: Provisioning Services 5.6

RES Workspace Manager 2011 Best Practices

Written by Thomas Poppelgaard. Posted in Best Practise, Whitepapers

The last couple of months a group people has shared their knowledge to create best practices with RES Workspace Manager 2011. These whitepapers are now published, apart from the fact that they can help in a POC to do a setup and a check.

The whitepapers also give an insight in common problems for an industry or an desktop/application delivery technique. So they can give you proper solution selling questions next to the one you got from the sales training.

You can download this papers here: http://www.ressoftware.com/support/best-practices-white-papers

Wyse Configuration Manager

Written by Thomas Poppelgaard. Posted in Wyse

Wyse Configuration Manager – Features

With Wyse Configuration Manager (WCM) you can manage WES7 thin clients (WES2009 will follow shortly) using a centrally located XML file. Things that can be managed using the XML file include:

  • RDP, View and ICA connections
  • Display settings (wallpaper, screenresolution, etc.)
  • Keyboard and mouse settings
  • Wired and wireless settings
  • Power settings
  • Browser, Aero and firewall settings
  • Much more…

In a lot of organizations WCM will eliminate the need to stream entire 4GB image files accross the network to customize the WES clients based on their needs. With WCM it is just a matter of creating a DHCP option tag (so the agent on the client knows where to find the XML file) and the XML file (using a reference client or the standalone WCM console application) and you are good to go.

And the best part of it, WCM comes totally free with every Wyse WES7 client.

The WCM console and agent can be downloaded from Wyse.com -> Support -> Software Downloads

Recent Comments

Server 2016 Support

|

Wonderful website. A lot of useful info here. I am sending it to a few friends ans also sharing in delicious. And obviously, thanks for your sweat!

Server 2016 Support

Thomas Poppelgaard

|

Thanks Jose, I have corrected the map plus updated the map so 29 datacenters are now alive.

Jose Brenes

|

Your map of Australia is wrong. You have put the state of Victoria inside the West Australian state.

Tobias K

|

Note that on XenServer 7.1, installing VDA 7.13 also works to enable vGPUs running XenDesktop 7.11 even using the newer “NvFBCEnable.exe -enable -noreset” command. Tested with an M60 using various profiles.

Alex

|

So how come version 3.11 doesn’t work for application switching?