Trends – Innovation – ITSM – IT Architecture – Requirement Analysis – Business views – Service Governance – Storage – Virtualization etc… What do I do, why do I do it, and why does everyone else do what they do? Time to reflect and this is my little pot where I share my view and others great contributions to this IT-world!

Receiver for Windows 3.4 released

About Receiver for Windows 3.4

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.4 (CitrixReceiver.exe) provides the following new features and enhancements.

Single authentication to the Access Gateway:

Use of a single session for both VPN and clientless access so that a Receiver user logs on once for both types of access and consumes only one license. This feature requires StoreFront.

Automatic start-up of a VPN tunnel when a user logs on. This feature requires that you disable the Single Sign-On with Windows setting on the Access Gateway.

Support for Access Gateway SmartAccess controls.

Improved logon and logoff operations:

Users are prompted to log on to Receiver only when a logon is required. Actions that require a log on include starting an app from Receiver or the Start menu, using the Refresh Apps command, viewing or searching for apps, or adding an account. A user is logged on only to the account associated with the requested resource.

Users remain logged on until choosing to log off or exit Receiver, roam from the internal network to an external network, or delete passwords.

A VPN tunnel is established when a remote user performs an action that results in a logon. Internal users are logged on to StoreFront.

Support for Windows 8. You can use Receiver for Windows 3.4 on Intel-based Windows 8 devices. (Receiver for Windows 8/RT is available on the Windows App Store for ARM-based Windows 8 devices.)

Support for Windows Server 2012 R2, 64-bit edition.

Support for Project Thor Technical Preview (XenApp Connector). Receiver for Windows 3.4 can be used with Project Thor Technical Preview to deliver apps with Microsoft System Center 2012 Configuration Manager.

Usability improvements, including:

App and desktop Start menu shortcuts are no longer copied to other devices, enabling users to control the location of shortcuts on each of their devices.

The Request button is removed. Users can now simply click to add an app and, if a request for permission to add the app is required, a dialog box appears.

Support for session pre-launch. The session pre-launch feature reduces launch times for applications delivered through Web Interface sites.

Support for ShareFile StorageZones. Receiver for Windows supports both ShareFile-managed cloud storage and on-premises StorageZones.

Upgraded FIPS support. Receiver for Windows 3.4 supports certificates with a minimum public key of 2,048-bit RSA and a SHA256 signature hash algorithm.

Receiver for Windows Enterprise

The Receiver for Windows Enterprise 3.4 package (CitrixReceiverEnterprise.exe) provides the following enhancements:

Support for smart card single sign-on for Windows 7 devices. When used with Web Interface, Receiver for Windows Enterprise 3.4 enables smart card pass-through authentication from Windows 7 devices.

Support for Fast Connect. Fast Connect provides the necessary technology for partners to rapidly authenticate users to Citrix sessions or desktops.

For information about Receiver for Windows Enterprise, including compatible systems, refer to the Receiver for Windows 3.2 documentation in Citrix eDocs.

Known issues

This section contains:

Installation and upgrade issues

General issues

Known issues – Desktop connections

Third-party issues

Caution: Editing the Registry 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.

Installation and upgrade issues

Installation of Receiver for Windows 3.3 (CitrixReceiver.exe) by a user fails if CitrixReceiver.exe was previously installed by an administrator. This issue is caused by a third-party component. [#300624]

Receiver for Windows does not properly install on a Windows 8 computer if .NET 3.5 is not installed. When you install Receiver for Windows on such computers, the Receiver installer prompts you to download and install .NET 3.5. After completing the .NET installation, the Receiver installation starts but does not complete. To complete the installation, use Programs and Features to uninstall Receiver and then reinstall it. [#352779]

During installation of CitrixReceiver.exe on a Windows 8 machine that does not have .NET 3.5 installed or enabled, if you cancel the prompt to install .NET 3.5 and then attempt to uninstall Receiver, the uninstallation fails. To complete the uninstallation, install or enable .NET 3.5 on the machine and then uninstall Receiver. To enable .NET 3.5 on a Windows 8 machine, go to Control Panel > Programs and Features > Turn Windows Features On or Off and select .Net Framework 3.5. [#354996]

A silent install of CitrixReceiver.exe on a Windows 8 machine waits indefinitely (although Receiver installs successfully). To work around this issue, do not use the -waitparameter on the PowerShell command line. [#354627]

After a silent install of Receiver Enterprise 3.4, the Online Plug-in Settings do not appear on the About > Advanced page until after you restart Receiver. [#346815]

In an environment with AppController 2.0 deployed, Receiver does not indicate that a user is logged on: The Receiver menu includes the Log On command and the user name does not appear in the Receiver window. The user can, however, use the Receiver window to launch apps and perform other tasks. To avoid this issue, upgrade to AppController 2.5 before users upgrade to Receiver for Windows 3.4. [#353789]

For deployments with Merchandising Server, you must upgrade to Receiver Updater for Windows 3.4 to enable Receiver for Windows 3.4 to be uninstalled. In addition to upgrading Receiver Updater, inform users that when responding to the prompt after restarting Receiver they should click Postpone. Receiver is not uninstalled if Restart is clicked. [#346341]

If a user uninstalls a plug-in using the Control Panel and restarts the computer, the plug-in continues to display in the list that appears when you right-click the Receiver icon, click About and then expand Advanced. This occurs only when Receiver is installed from Citrix.com or your own download site. [#320277]

If you use Web Interface with Internet Explorer 8 and Windows 7 to upgrade to this version of Citrix Receiver, the upgrade finishes, but the Upgrade in Progress message remains on the screen and the log on screen does not appear. Workaround: Restart the browser [#247858]

Before installing Receiver for Windows on a Windows XP Embedded thin client device, increase the RAM disk limit of the device to 100 MB. [#266384]

When the offline plug-in is not installed and a streamed application is configured to fallback to ICA and the XenApp server is down, an incorrect error message appears informing you that the correct plug-in is not installed. [#273813]

General issues

A SaaS app with an icon that is larger than 48×48 cannot be subscribed in Receiver. [#353794]

On a computer running Windows 8, two icons appear on the desktop when a user logged on as a non-administrator installs CitrixReceiverEnterprise.exe by right-clicking the .exe and choosing Run as administrator. In this case, only the icon for the Online plug-in provides access to Receiver commands. [#350660]

After using the Receiver Reset command on a Windows 2008 R2 machine, Receiver cannot be launched from the Start menu and the Open command no longer appears in the Receiver menu. To work around this issue, restart Receiver after resetting it. (To reset Receiver, right-click the Receiver icon, choose About, expand Advanced, and then click Reset Receiver.) [#355092]

When configured with multiple stores, Receiver might confuse the gateways required to connect to a store causing incorrect apps being available to users. Work around: Configure only one store. [#263165]

If you use the Receiver with XenApp 5.0 Feature Pack 2 for Windows Server 2003 (32- or 64-bit editions), the Receiver plays audio even when you configure the Turn off speakers policy setting to disable the audio. [#242703]

When you launch applications using the Web Interface, Connection Center does not enumerate the sessions. [#261177]

After you launch a published application that is filtered by XenApp for Access Gateway, other published applications do not launch. [#263003]

In some environments, content redirection may not work until the published application is launched for the first time. [#252515]

When versions of Receiver are localized in Traditional Chinese, Korean, or Russian and integrated with Access Gateway Standard Edition, the Receiver log on screen displays in English because of an Access Gateway Standard Edition language limitation. [#263442]

If Certificate Revocation List (CRL) checking is disabled in Internet Options on the user device, this overrides the CertificateRevocationCheck registry setting for Receiver for Windows. This means users may be able to access Web sites that do not have valid certificates. As a workaround, ensure that the Check server revocation option located atSettings > Control Panel > Internet Options > Advanced is enabled. [#32682]

Receiver does not support the VPN keyword in Access Gateway ClientChoices mode. [#274828]

If the VPN keyword is removed from an application after a user subscribes to it, Receiver continues to attempt an Access Gateway connection for the application. Workaround: Unsubscribe and then re-subscribe to the application to synchronize the VPN keyword removal on Receiver. [#298387]

If synchronization progress overlays do not appear in Windows Explorer for files and folders, restart your computer. [#319284]

For ShareFile contact list of over 1000 contacts, the dialog boxes for sending or sharing files or folders are unresponsive after you click the To button and until the contact list loads. [#323737]

The Receiver icon is displayed instead of an application icon in the task bar when an application is launched from Receiver using XenApp 5.0 and earlier versions. [#310366]

Desktop connections

Loss of video is experienced if files are being played with a published version of Windows Media Player through a virtual desktop session, and the Desktop Viewer window is changed from full-screen to window mode. As a workaround, minimize and restore the Media Player window, and then pause and resume the application (or stop and restart it). [#246230]

You cannot log off normally from Windows XP 32-bit virtual desktops if you start (but do not log on to) the Receiver in the desktop session. If the Receiver logon dialog box is not completed, you cannot log off from the desktop. To work around the issue, complete the logon dialog box or close it. This issue is not observed on other virtual desktop operating systems. [#246516]

If virtual desktops are installed with the Virtual Desktop Agent supplied with XenDesktop 5.0, Receiver for Windows 3.0 displays an error if the user starts a published application from the desktop. The workaround is to use the Virtual Desktop Agent supplied with XenDesktop 5.5. [#263079]

The Citrix Desktop Lock does not redirect Adobe Flash content to domain-joined user devices. The content can be viewed but is rendered on the server, not locally. As a workaround, Adobe Flash redirection can be configured for server-side content fetching to pass the content from the server to the user device. This issue does not occur on non-domain-joined devices or when the content is viewed with the Desktop Viewer. [#263092]

The Desktop Viewer Devices menu may not close when the user clicks the Devices icon. It also may remain open after its corresponding dialog box closes. If this occurs, click the Devices icon again. [#262202]

Windows Media Player, when displayed in the non-primary monitor of a two-monitor Windows user device, may not work as expected. Due to an issue with the DirectX video mixing renderer filter VMR-9, the screen is black and there is no sound, although the player’s progress bar advances. To correct this issue, edit the registry on the user device from which the XenDesktop connection is launched. In the HKEY_CURRENT_USER\Software\Citrix subkey, create the HdxMediaStream key. Name the key DisableVMRSupport. Set the type as REG_DWORD. Give the key the value 3. [#262852]

Third-party issues

When using Internet Explorer to open a Microsoft Office document in Edit mode from SharePoint, Microsoft Office might display the message, “Access denied.” Workaround: Go to the SharePoint site and check out the document, edit it, and check the file back in to SharePoint. [#258725]