Skip to main content

Citrix Receiver for Windows 3.3

Citrix have released a new version of Citrix Receiver 3.3. Citrix Receiver is not released in an Enterprise edition anymore version 3.2 was the last Receiver that came in an Enterprise edition.

About Receiver for Windows 3.3

Citrix Receiver for Windows provides users with self-service access to resources published on XenApp or XenDesktop servers. Receiver combines ease of deployment and use, and offers quick, secure access to hosted applications, desktops, and data. Receiver also provides on-demand access to Windows, Web, and Software as a Service (SaaS) applications. You can use it for Web access or configure it for use with Citrix CloudGateway.

What’s New

Citrix Receiver for Windows 3.3 provides the following new features and enhancements.

  • Simplified use for first-time and returning users:
    • Users have just one package choice when installing Receiver for Windows 3.3 from the Citrix.com or your own download site.
    • Users can set up a Receiver account by entering an email address or a server URL. Receiver determines the Access Gateway, StoreFront server, or AppController virtual appliance associated with the email address and then prompts the user to log on and proceed with the installation.
    • The simplified interface no longer includes a Preferences panel.
  • ShareFile integration. When used with Citrix ShareFile Enterprise, Receiver enables users to share and send documents from the Receiver window. Documents are stored in the cloud and synced with Receiver across all devices. The ShareFile Outlook plug-in is installed with Receiver for Windows, enabling users to attach large files to emails from Outlook.
  • Template to create a site-specific download site. For administrators who need more control, Citrix provides a template that you can use to create a download site for Receiver.
  • Automatic updates. For Receivers installed from Citrix.com or your download site, a new update service built in to Receiver automatically handles updates, in most cases silently. Receiver Updater for Windows is needed only if you prefer to use Merchandising Server to distribute Receiver and its updates.
  • Access to SaaS apps from outside the firewall without a VPN. Receiver for Windows 3.3 does not require a VPN connection to access SaaS apps remotely. (Enterprise Web apps published and accessed through CloudGateway still require a VPN connection.)

System Requirements and Compatibility for Receiver for Windows

Operating system

  • Windows 7 Enterprise SP1, 32-bit and 64-bit editions (including Embedded Edition)
  • Windows 7 Enterprise, 32-bit and 64-bit editions
  • Windows XP Professional SP3, 32-bit edition and SP2, 64-bit edition
  • Windows XP Embedded
  • Windows 7 Thin PC
  • Windows Server 2008 R2 Enterprise SP1
  • Windows Server 2008 Enterprise, 32-bit and 64-bit editions (not supported by XenDesktop connections)
  • Windows Server 2008 R2 Enterprise, Foundation, Standard, and Datacenter, 32-bit edition (not supported by XenDesktop connections)
  • Windows Server 2003, 32-bit and 64-bit editions (not supported by XenDesktop connections)
    Important: For XenDesktop connections, be aware that the Citrix Desktop Lock is only supported on Windows XP Professional, Windows XP Embedded, Windows 7, and Windows Embedded Standard 7. If your deployment includes Windows 7 or Windows Embedded Standard 7, see the additional requirements in this topic.

For operating system requirements for ShareFile integration, see “Availability of Receiver for Windows 3.3 features” later in this topic.

Hardware

  • VGA or SVGA video adapter with color monitor
  • Windows-compatible sound card for sound support (optional)
  • For network connections to the server farm, a network interface card (NIC) and the appropriate network transport software

Server

  • XenApp (any of the following products):
    • Citrix XenApp 6.5 for Windows Server 2008 R2
    • Citrix XenApp 6 for Windows Server 2008 R2
    • Citrix XenApp 5 for Windows Server 2008
    • Citrix XenApp 5 for Windows Server 2003
    • Citrix XenApp 4, Feature Pack 1 or 2, for UNIX operating systems
  • XenDesktop (any of the following products):
    • XenDesktop 5.6
    • XenDesktop 5.5
    • XenDesktop 5
    • XenDesktop 4
  • To manage connections to apps and desktops, Citrix Receiver supports CloudGateway or Web Interface.
    CloudGateway:

    • CloudGateway Express, with StoreFront 1.2, 1.1 or 1.0For direct access to StoreFront stores.
    • CloudGateway Express, with StoreFront 1.2, 1.1 or 1.0 configured with a Receiver for Web siteFor access to StoreFront stores from a web browser.
    • CloudGateway Enterprise 2.0 or 1.0, with StoreFront 1.2, 1.1 or 1.0For access to Windows, Web, and Software as a Service (SaaS) apps. ShareFile integration requires the latest versions.
    Web Interface:

    • Web Interface 5.x for Windows with XenApp Services and XenDesktop Services sites (also known as PNAgent sites)For access to apps from a web browser.
    • Web Interface 5.x for Windows with XenApp Services or XenDesktop Services sites and the PNAgent pluginFor access to apps from a web browser.
  • Merchandising Server 2.x

Browser

  • Internet Explorer Version 6.0 through 9.0Connections to StoreFront or Web Interface support the 32-bit mode of Internet Explorer.
  • Mozilla Firefox Version 1.x through 5.x
  • Google Chrome Version 10.0 and later

Connectivity

Citrix Receiver for Windows supports HTTPS and ICA-over-SSL connections through any one of the following configurations.

  • For LAN connections:
    •  StoreFront using StoreFront services or Receiver for Web sitesSingle sign on to Web and SaaS apps published through AppController requires StoreFront 1.2 or 1.1.
    • Web Interface 5.x for Windows, using XenApp Services and XenDesktop Services sites

    Windows non-domain joined, kiosk, managed devices (with or without Desktop Lock) and domain-joined (with Desktop Lock), managed devices (repurposed PCs) are supported for LAN only connections.

  • For secure remote or local connections:
    • Citrix Access Gateway Enterprise Edition 10
    • Citrix Access Gateway Enterprise Edition 9.x
    • Citrix Access Gateway VPX
    • Citrix Access Gateway 5.0
    • Citrix Secure Gateway 3.x (for use with Web Interface only)

    Windows domain-joined, managed devices (local and remote, with or without VPN) and non-domain joined devices (with or without VPN) are supported.

    For information about connections that do not require a VPN, refer to http://support.citrix.com/article/CTX131908.

    For information about the Access Gateway versions supported by StoreFront, refer to the Access Gateway and StoreFront documentation in eDocs.

Certificates

For information about security certificates, refer to topics under Secure Connections and Secure Communications.

Authentication

Receiver for Windows 3.3, when used with StoreFront 1.2, 1.1 or 1.0, supports the following authentication methods:

  • Domain
  • Domain pass-throughReceiver for Web sites do not support domain pass-through authentication.
  • Security token*
  • Two-factor (domain plus security token)*
Receiver for Windows 3.3, when used with Web Interface 5.X, supports the following authentication methods:

  • Domain
  • Security token
  • Two-factor (domain plus security token)*
  • SMS*
  • Client certificate (requires Access Gateway Enterprise Edition; can be used alone or with other authentication methods)

* Available only in deployments that include Access Gateway.

For information about authentication, refer to the Access Gateway documentation and the “Manage” topics in the StoreFront documentation in eDocs. For information about other authentication methods supported by Web Interface, refer to “Configuring Authentication for the Web Interface” in the Web Interface documentation in eDocs.

Upgrades

Upgrades are supported only for Citrix online plug-in 11.2, 12.0, and 12.1, and Receiver for Windows 3.x releases.

Availability of Receiver for Windows 3.3 features

Some of the features and functionality of Receiver are available only when connecting to newer XenApp and XenDesktop versions and might require the latest hotfixes for XenApp, XenDesktop, and Secure Gateway.

ShareFile integration with Receiver for Windows

  • ShareFile integration with Receiver for Windows is available for the following operating systems:
    • Windows 7, 32-bit and 64-bit editions
    • Windows XP Professional, 32-bit and 64-bit editions
    • Windows Vista, 32-bit and 64-bit editions
    • Windows Server 2008 R2, 64-bit edition
  • ShareFile integration with Receiver is available for the following deployment scenarios:
    • CloudGateway Enterprise with StoreFrontProvides seamless integration of ShareFile functionality in Receiver.
    • CloudGateway Enterprise without StoreFrontRequires Receiver users to manually add a ShareFile account in the Receiver interface to access the Receiver Docs view.

Other

  • Compatible plug-insFor a list of compatible plug-ins, refer to information about managing Receiver updates in the StoreFront documentation in Citrix eDocs.
  • .NET Framework Requirements
    • The .NET 2.0 Service Pack 1 and Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package are required to ensure that the Receiver icon displays correctly. The Microsoft Visual C++ 2005 Service Pack 1 package is included with .NET 2.0 Service Pack 1, .NET 3.5, and .NET 3.5 Service Pack 1; it is also available separately.
    • For XenDesktop connections: To use the Desktop Viewer, .NET 2.0 Service Pack 1 or later is required. This version is required because, if Internet access is not available, certificate revocation checks slow down connection startup times. The checks can be turned off and startup times improved with this version of the Framework but not with .NET 2.0. Use of the Citrix Desktop Lock does not require the .NET Framework to be installed.

  • HDX MediaStream Multimedia AccelerationFor applications and media formats supported by HDX MediaStream Multimedia Acceleration, refer to information about optimizing audio and video playback in the XenApp documentation in Citrix eDocs.

  • Supported Connection Methods and Network Transports:
    • TCP/IP+HTTP
    • SSL/TLS+HTTPS

  • Previous versions of the Presentation Server Client/Online Plug-in and the current icaclient.adm file. Previous versions of the Presentation Server Client and Online Plug-in are not compatible with the Receiver for Windows 3.3 icaclient.adm file.

Source

Download Citrix Receiver 3.3 for Windows (Notice the Receiver size is 42.9Mb)

How to Create a PNAgent Services Site Mobile Devices When using Web Interface on Citrix NetScaler

Summary

This article describes how to create a PNAgent Services Site for mobile devices with Web Interface on NetScaler.

Background

This article is helpful if you are providing dual authentication for the mobile users externally, and want to offer single authentication for the users internally.

When creating a Direct Mode PNAgent site, the Site Path is /Citrix/PNAgent/ by default. However, with Web Interface on NetScaler, the mobile devices can run into an issue when adding the mobile account with just the hostname such as, mobile.example.com. Currently, you have to put in the entire site path such as mobile.example.com/Citrix/PNAgent/config.xml.

Requirements

  • NetScaler software release 9.2 e or later

Procedure

To create a PNAgent Services Site for mobile devices complete the following procedure:

  • Open the Configuration Utility of the appliance.
  • Select the Web Interface node.
  • Click on the Web Interface Wizard link and follow the onscreen instructions.
  • For the Site Path, change all letters to lowercase, as shown in the following screen shot:
  • Select Direct Mode and enter the load balancing virtual IP address information.
  • Select the Enabled access through receiver client option.
  • Click Next and enter the XML Services Addresses and complete the Wizard.
  • When you add the account for Citrix Receiver, you can now use the hostname such as, mobile.example.com.
  • Enter the account credentials and click Save.

More Information

When creating a Direct Mode PNAgent site and using the default Site Path syntax /Citrix/PNAgent/, the NetScaler appliance does not respond to the letters in upper case when mobile devices are requesting the PNAgent site from the Citrix Receiver.

The following network packet trace indicates that there is an HTTP GET /citrix/pnagent/config.xml, after that the appliance responds with a 404 Not Found.
IP Information
10.0.1.73 – Client-IP (iPhone)
10.0.1.4 – NSIP
10.0.1.6 – SNIP
10.0.1.11 – Web Interface or XenApp
10.0.1.49 – Load Balancing Virtual IP address

HTTP Status 404: /citrix/pnagent/config.xml
Status report: /citrix/pnagent/config.xml
Description: The requested resource (/citrix/pnagent/config.xml) is not available

From the user perspective, after entering the account credentials, ‘Invalid Path’ appears, as shown in the following screen shot:

After creating the Direct Mode PNAgent site and changing the Site Path syntax to /citrix/pnagent/, the results are successful. You get a 200 OK result with the xml information. And, you are able to successfully add a mobile account with only typing the hostname.

Source

CPU Temperature Reported on the Citrix NetScaler MPX Appliances

Hi all, I noticed this important, CTX article that you should be aware of, if you have Citrix NetScaler MPX appliance in your environment. Then its a good idea to read this article and change the values, so you dont end up with a dead unit because of the CPU dies of heating.

/Poppelgaard

Summary

This document contains information about the CPU temperature reporting on a NetScaler MPX 7500, 9500, 10500, 12500, or 15500 appliances.

Background

The NetScaler appliance reports that the temperature is high. However, the original temperature is found to be around 30 degree Celsius less than the reported temperature.

CPU Temperature Reporting on the NetScaler MPX Appliances

An Intel CPU does not report temperature directly, neither in Celsius nor in Fahrenheit. Instead, the CPUs have a Digital Thermal Sensor (DTS) that report the temperature less than the maximum operating temperature (PROCHOT). When the DTS reported value for a CPU approaches zero, the CPU is close to its maximum operating temperature. Before the temperature of the CPU reaches PROCHOT value, the protective measures are automatically enabled for the CPU to keep the processor from getting heated.

The NetScaler MPX appliance reports the CPU temperature in degree Celsius. The value is calculated by subtracting the reported value from the PROCHOT value. For example, if the CPU reports a value of 38 degree Celsius, and the PROCHOT specification for the CPU model is 100 degree Celsius, then the system reports a CPU temperature of 62 degree Celsius, which is 100 – 38.

Detailed issue description with CPU temperature measurements on NetScaler 7500 or 9500 platform are described in http://download.intel.com/design/intarch/papers/322683.pdf.

For normal operating temperatures CPU temperature sensor cannot provide reliable and precise data. When the CPU temperature is high that is 20 degree Celsius less than the maximum temperature, the CPU sensor becomes more reliable.

CPU temperature reported is a distance from the maximum allowed CPU temperature. If CPU reaches maximum allowed temperature, then the sensor reads 0 degree Celsius.

As long as the reported CPU temperature is below the allowed maximum 100 degree Celsius reported by health monitoring, CPU thermal throttling does not occur. Thermal throttling and eventual CPU thermal shutdown starts at temperatures past the reported temperature of 100 degree Celsius.

Note: The thermal monitoring and the protective features that are built into the processor are not affected. Consider the following points on this issue:

  • Thermal protection of the processor is always enabled and accurate.
  • System fans are always accurately controlled for proper system cooling.
  • The actual temperature of the CPU is lower than the reported value.

Recommendation

It is recommended to set 85 degree Celsius as an alarm threshold for CPU temperature on the NetScaler appliance to avoid invalid temperature related warnings, as shown in the following screen shot:
Note: This temperature is about 15 degree Celsius less than the maximum CPU temperature.

This document applies to:

Source

http://support.citrix.com/article/CTX133584

NetScaler – Custom LDAP Monitor Does Not Work

Problem Definition

A customer tried to configure custom LDAP monitor, but the monitor failed after it was bound to a load balancing service.

Troubleshooting Steps

The Technical Support Engineers used the nsumon-debug.pl script from the /nsconfig/monitors directory:

root@NS# cd /nsconfig/monitors
root@NS# ls -ltr
total 68
-r-xr-xr-x 1 root wheel 8784 Dec 21 06:08 nswi.pl
-r-xr-xr-x 1 root wheel 2517 Dec 21 06:08 nsumon-debug.pl
-r-xr-xr-x 1 root wheel 3184 Dec 21 06:08 nssnmp.pl
-r-xr-xr-x 1 root wheel 1453 Dec 21 06:08 nssmtp.pl
-r-xr-xr-x 1 root wheel 2509 Dec 21 06:08 nsrdp.pl
-r-xr-xr-x 1 root wheel 2392 Dec 21 06:08 nspop3.pl
-r-xr-xr-x 1 root wheel 3742 Dec 21 06:08 nsntlm-lwp.pl
-r-xr-xr-x 1 root wheel 2769 Dec 21 06:08 nsnntp.pl
-r-xr-xr-x 1 root wheel 2979 Dec 21 06:08 nsmysql.pl
-r-xr-xr-x 1 root wheel 3113 Dec 21 06:08 nsftp.pl
-r-xr-xr-x 1 root wheel 14010 Dec 21 06:08 nsall.pl
drwxr-xr-x 3 root wheel 512 Feb 1 07:18 perl_mod
-r-xr-xr-x 1 root wheel 3793 Feb 29 19:54 nsldaps.pl
-r-xr-xr-x 1 root wheel 3860 Mar 1 01:45 nsldap.pl

With the nsumon-debug.pl script, the engineers set the argument provided in the LDAP Monitor Base DN, Bind DN, and password along with the LDAP IP address and port number.

root@NS7039# nsumon-debug.pl nsldap.pl 10.217.130.120 389 3 “base=cn=users,dc=company,dc=com;bdn=cn=admin,cn=users,dc=company,dc=com;password=xxxxx”
nsldap.pl syntax OK
0

root@NS# nsumon-debug.pl nsldaps.pl 10.217.130.120 636 3 “base=cn=users,dc=company,dc=com;bdn=cn=admin,cn=users,dc=company,dc=com;password=xxxxx”
nsldaps.pl syntax OK
0

The engineers used the following syntax when the LDAP argument had a filter or object:

root@NS7039# nsumon-debug.pl nsldap.pl 10.217.130.120 389 3 “base=cn=users,dc=company,dc=com;bdn=cn=admin,cn=users,dc=company,dc=com;password=xxxxx; filter=objectclass=*;attribute=objectclass”
nsldap.pl syntax OK
0

root@NS# nsumon-debug.pl nsldaps.pl 10.217.130.120 636 3 “base=cn=users,dc=company,dc=com;bdn=cn=admin,cn=users,dc=company,dc=com;password=xxxxx; filter=objectclass=*;attribute=objectclass”
nsldaps.pl syntax OK
0

The listed nsumon-debug.pl scripts were successful. If there were any failures, then the exit reason for nsumon-debug.pl output appears as follows:

root@NS93ncVPX# nsumon-debug.pl nsldaps.pl 10.217.130.120 636 3 ” base=cn=users,dc=company,dc=com;bdn=cn=admin,cn=users,dc=company,dc=com;password=xxxxx”
nsldaps.pl syntax OK
1,Failed to bind to server – Connection reset by peer

root@NS93ncVPX# nsumon-debug.pl nsldap.pl 10.217.130.120 389 3 ” base=cn=users,dc=company,dc=com;bdn=cn=admin,cn=users,dc=company,dc=com;password=xxxxx”
nsldap.pl syntax OK
1,Failed to bind to server – Connection reset by peer

The other error messages or exit reasons could include invalid argument, or broken pipe.

The engineers also verified if LDAP was configured for client authentication that is they verified the LDAP policy.

The engineers also verified if LDAP required any client certificate to connect.

By default, the nsldap.pl script uses only dase, bdn, and password as argument and does not use any certificate to connect to the LDAP. The nsldap.pl script uses the parameter provided as an argument. If the LDAP is expecting a certificate, then certificate must be passed as an argument to the script. Currently, the script does not support a custom argument.

Resolution

To resolve this issue the engineers created a USER monitor instead of LDAP monitor, as shown in the following screen shots:

The engineers bound the user monitor to the load balancing Service.

Tech Preview – NetScaler for Amazon Web Services

NetScaler for AWS Tech Preview

Get the NetScaler for AWS Tech Preview, and see how your AWS environment can benefit from the same cloud networking platform used by the world’s largest web sites

The technology preview of NetScaler 10 for Amazon Web Services enables you to try world-class NetScaler application delivery capabilities within your Amazon Web Services deployments. NetScaler is the best solution to optimize, secure and control the delivery of all your enterprise and cloud services. Its rich feature set includes load balancing, full web app firewall security, fast application acceleration capabilities, and an easy-to-use policy framework for simple deployment – with absolutely no programming required.

To get started, simply:

  1. Access the NetScaler for AWS Tech Preview AMI. The AMI can be found by searching for AMI ID ami-12e94d7b
  2. Get and activate an EVAL license via the get license link below

Helpful Resources

  1. Download the NetScaler for AWS Tech Preview deployment guide
  2. For help with licensing the instance, refer to the NetScaler VPX licensing guide
  3. New to NetScaler? Documentation, knowledge base articles, additional tutorials and other information is available on the NetScaler Knowledge Center.