Multiple notification

I need a solution

We are setting up the rules for windows desktop patch deployment. It usually will be run quarterly. Therefore, we need to apply multiple patch in one-go. The policy is set that the re-start notification will be pop-up and allow user the delay re-start upto 4 hours.

The pop-up can allow users to specify how long will the next pop-up. However, we found that when applying multiple patch which require multiple re-start, the pop-up notification will be pop-up again and again. For example, if 3 patches need to have re-start after application, the notification windows will be poped when the 1st patch applied. If the user choose remind me 2 hours later, user will expect that the notification windows will be popup again 2 hours later. However, the notification windows will be popup again when the 2nd patches has been applied and so on.

Does anyone can share how should I set the policy so that the notification massage windows will pop-up acccording to the user time set?

0

Related:

  • No Related Posts

How to Configure GSLB Setup for Internal Users From GUI

This article contains information about how to configure a GSLB setup for internal users using the same host name.

In some scenarios, the administrator requires that all external users (coming through the Internet) must go through the Access Gateway , whereas all the internal users within the Domain can just logon into Web Interface or get an Internal IP address.

NOTE :

It is not necessary to create an explicit external view for external users as anything that passes through the DNS policy goes through the regular GSLB load balancing policy or method.

Requirements

A NetScaler appliance installed with NetScaler software release 8.0 or later configured with GSLB basic setup. You must configure the following in the basic GSLB setup:

  • One remote and/or local GSLB virtual server

  • Two GSLB services, one local and the other remote service, or both local services

  • The services are bound to the domain using the virtual server

Background

To implement this solution DNS views are used.

The policies associated with the DNS Views can be configured to provide different views or IP addresses depending on various network attributes, such as Interface, IP (LDNS), and PORT.

Related:

  • No Related Posts

Workspace Environment Management (WEM): Active Directory search improvements in WEM 4.6

Introduction

The Active Directory (AD) system built into the WEM Administration Console and WEM Infrastructure Server has been refactored in WEM 4.6 to improve performance and stability.

Although AD searches performed by the WEM Console and WEM Infrastructure server in previous WEM versions have typically returned results quickly, many customer environments consist of multiple AD forests or AD domains. The Active Directory improvements introduced in WEM 4.6 are designed to improve performance and stability; particularly for multi-forest/domain environments.

Active Directory improvements in WEM 4.6

Global Catalog (GC) mechanism: AD searches are initiated against the AD forest’s Global Catalogue Server (GC) instead of searching against each of the forest’s Domain Controllers in turn.

Asynchronous search mechanism: AD searches are performed on all forests (GC servers or domains) at the same time, instead of searching one by one.

AD search timeout mechanism: If the AD User or Machine object lookup points to a forest or domain that is currently unavailable, a configurable timeout been introduced to prevent prolonged searching. The timeout value is set through the WEM Administration Console (Active Directory Objects => Advanced => Active Directory search timeout (msec)), as shown below:

User-added image
The default value is 1 second (1000 msec). The value set here affects AD searches for both the WEM Administration Console and the WEM Infrastructure Server. If an AD search time exceeds the value specified in this field, AD searching will stop.

Customers can set this to a preferred value based on their real environment conditions.

NOTE: Citrix recommends using a timeout value of at least 500 msec to avoid a timeout before the AD search completes.


Troubleshooting Active Directory searches in WEM

If AD searches are failing:

  • Check that the Active Directory search timeout (msec) is appropriate for the environment. This means that there is no specific value to recommend. Consideration needs to be given if the environment includes multiple AD forests or AD domains.
  • Generate WEM Administration Console and WEM Infrastructure Server debug logs that capture the failed AD search occurrences. In the logs, Active Directory-related entries are marked as AD: in the header of the body, right after the function name:

User-added image

Related:

  • No Related Posts

Server Error in ‘/ICT/administration’ Application

I need a solution

Hi,

We have followed the instructions from the documentation guide (Installation Guide for Symantec Information Centric Tagging 15.0) https://support.symantec.com/en_US/article.DOC10620.html 

ICT is being used only for classification purpose so we don’t have the AD RMS.

After following the steps,

  1. Two Servers – An Active Directory Machine and An ICT Server Machine
  2. On the ICT Server Machine we installed SQL Server 2012
  3. Created OU and Groups in Active Directory for ICT
  4. Created Databases in SQL Server 2012 and Assign Rights for the ICT Account
  5. Ran the Scripts on the Databases
  6. Configured the Application Pool for ICT
  7. Modified the web.config file in inetpub/wwwroot/ict/administration/
  8. Ran the installer for Symantec_ICT_SERVER_Administration_15-0-1-2
  9. This error is shown when accessing the administration console

Kindly advise how to resolve this error. Thanks !

0

Related:

  • No Related Posts

How to Retain Printer Settings in ICA

The following settings can be applied to an auto-created printer of the user:

  1. From the system tray, go to Properties in the Printing Preferences option of the local printer on the General tab.

    Printing Preferences
  2. Settings in the Device Settings tab.

    Device Settings

  3. The settings highlighted (refer image) in the Advanced tab.

    Advanced

Note: If you intend to auto-create your printers with the Citrix Universal Print driver, you cannot use the Print directly to the printer option because this would disable EMF printing. So when a printer is auto-created with the Citrix Universal Print driver, it automatically sets it to Spool print documents so program finishes printing faster.

To retain these settings to be applied on the next logon and to the auto-created printer settings of the user, verify the following:

  • The driver on the client must be an exact match of the driver on the server (Driver name, version, devmode size, and so on)
  • The registry entries under HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlPrintEnvironmentsWindows NT x86DriversVersion-3PrinterDriverName must also match the entries of the server. (This registry key applies for version 3 drivers.)
  • If the preceding conditions do not match, then the driver is not considered a match and the default settings are used instead.

Retain printer settings from a session to apply at future logons

The settings listed in the previous section are the only settings that can be retained from auto-created printers and the same conditions apply.

To retain the settings, make the changes from the Printers and Faxes folder on the server. Following are the two methods to retain the settings:

  1. Provide users access to the servers desktop and the Printers and Faxes folder.
  2. Publish the Printers and Faxes folder. Refer to CTX884335 – How to Publish the Printers Folder for procedure to publish the folder.

Following are the two methods to resolve the issue if the driver mismatched:

  • Use the Citrix Universal Print driver which works for most printers. This carries the capabilities of the local printer into the session. Use the native driver if the Citrix Universal Print driver does not work for any printer.

    OR

    There are three ways to retain the settings which are controlled using a Citrix policy. Click Help within the policy to see which of the three settings would work best for your environment.

    Print Retention Properties

    Related:

    • No Related Posts

    Citrix Receiver for Windows 4.x – Issues Fixed in This Release

    Citrix Receiver for Windows 4.x

    Product: Citrix Receiver for Windows

    Current Product Version: Receiver for Windows 4.x

    The following issues were fixed in Receiver for Windows 4.x:

    Citrix Receiver for Windows 4.11

    Citrix Receiver for Windows 4.10

    Citrix Receiver for Windows 4.9

    Citrix Receiver for Windows 4.7

    Citrix Receiver for Windows 4.6

    Citrix Receiver for Windows 4.5



    Receiver for Windows 4.4 CU1 (4.4.1000)

    Receiver for Windows 4.3

    Receiver for Windows 4.2.100

    Receiver for Windows 4.2

    Receiver for Windows 4.1.200

    Receiver for Windows 4.1.100

    Receiver for Windows 4.1.2

    Receiver for Windows 4.1

    Receiver for Windows 4.0.1

    Receiver for Windows 4.0

    Receiver for Windows 4.2.100

    Compared to: Citrix Receiver for Windows 4.2

    Receiver for Windows 4.2.100 contains all fixes that were included in Receiver for Windows 4.0, 4.0.1, 4.1, 4.1.2, 4.1.100, 4.1.200, and 4.2 plus the following, new fixes:

    Keyboard System Exceptions
    Local App Access User Experience
    Session/Connection User Interface

    Keyboard

    1. When users receive a prompt to change the password by pressing the Ctrl + Alt + End key combination in a published Receiver session, the key combination might not work.

      [From RcvrForWin4.2_14.2.100][#LC0862]

    Local App Access

    1. When using the Local App Access feature “KEYWORDS:prefer=”pattern“” with any application in XenApp 7.5 and StoreFront 2.5, the Receiver might experience issues. In addition, there can be issues during auto creation of shortcuts for preferred applications by using the “prefer template directory”.

      [From RcvrForWin4.2_14.2.100][#LC2153]

    Session/Connection

    1. When switching users by using the FastConnect Scripting API, the credential prompt does not close.

      [From RcvrForWin4.2_14.2.100][#LC2299]

    2. If users start a desktop session in full-screen mode and the Desktop Viewer is disabled, scroll bars might appear when plugging in a second monitor.

      To enable the fix, set the following registry key:

      • On Windows 32-bit systems:

        HKEY_LOCAL_MACHINESOFTWARECitrixICA Client

        Name: ProcessWM_SETTINGCHANGE

        Type: DWORD

        Value: 1 (default value is zero) (this fix is only for users who disable CDViewer Bar and run Desktop in full-screen mode)
      • On Windows 64-bit systems:

        HKEY_LOCAL_MACHINESOFTWAREWow6432NodeCitrixICA Client

        Name: ProcessWM_SETTINGCHANGE

        Type: DWORD

        Value: 1 (default value is zero) (this fix is only for users who disable CDViewer Bar and run Desktop in full-screen mode)

      The following registry keys are optional. By default, this value is 0 and is needed only when the default configuration does not solve the issue.

      • On Windows 32-bit systems:

        HKEY_LOCAL_MACHINESOFTWARECitrixICA Client

        Name: MonitorLayoutUpdateDelay

        Type: DWORD

        Value: 0 to 4 (default value is zero)
      • On Windows 64-bit systems:

        HKEY_LOCAL_MACHINESOFTWAREWow6432NodeCitrixICA Client

        Name: MonitorLayoutUpdateDelay

        Type: DWORD

        Value: 0 to 4 (default value is zero)

      [From RcvrForWin4.2_14.2.100][#LA5746]

    3. This enhancement supports “Automatic Client Reconnection” for Receiver for Windows with XenApp 6.5 and server operating systems running VDA version 7.x when users connect to NetScaler Gateway and CloudBridge or HDX Insight are in the deployment.

      Note: Session Reliability and Auto Client Reconnection do not work if Multi-stream and Multi-port policies are enabled on the server and any or all of the following are true:

      • Session reliability is disabled on NetScaler Gateway
      • A failover occurs on the NetScaler appliance
      • CloudBridge is used with NetScaler Gateway

      [From RcvrForWin4.2_14.2.100][#LC1779]

    4. When running Receiver with multiple USB devices plugged into the user device, when restarting the device or connecting a new USB device, the following message appears:

      “USB Hub Power Exceeded”

      [From RcvrForWin4.2_14.2.100][#LC1904]

    5. If pooled desktop groups have multiple desktops configured per user, only the first desktop can start when using Receiver for Windows. If the user clicks on the icons of other desktops, the desktop might show a “connecting” dialog box and then fail to connect. The first desktop session appears in the foreground.

      [From RcvrForWin4.2_14.2.100][#LC0780]

    6. When importing the Client Selective Trust registry key file as described in Knowledge Center article CTX133565 and configuring both the trusted and intranet zones, if the Desktop Viewer is enabled in the Web Interface or in StoreFront, the registry key might not work. If the Web Interface or StoreFront URL is configured as a trusted zone in the browser, a file security prompt incorrectly appears when accessing the Client Drive Mapping (CDM) directory.

      [From RcvrForWin4.2_14.2.100][#LC0904]

    7. After logging off from a desktop session, if the user attempts to log off from the Windows XP Embedded Thin Client, the error message “End program concentr.exe” appears.

      [From RcvrForWin4.2_14.2.100][#LC2556]

    8. The time zone is not correct when users log on with Receiver for Windows. For this hotfix to work, the following must occur:

      • The same Microsoft time zone update hotfix must be installed on the user device and the server. For example, if Microsoft hotfix KB2998527 is installed on the user device, install this hotfix on the server.
      • If the server operating system is Windows Server 2008 R2 Service Pack 1, Microsoft hotfix KB2870165 must be installed on the server.
      • Fix #LC1061 must be installed on the XenApp server.

      [From RcvrForWin4.2_14.2.100][#LC1392]

    9. This fix enables FastConnect Scripting API support without integrating with the Self-Service Plug-in. This can be enabled by using the group policy under ADM > Citrix Components > Citrix Receiver > FastConnect API Support > Manage FastConnectAPI support and then by clearing the option “Integrate Self Service plugin with FastConnect.” You can also change the registry key “FastConnectUsingSSP” to “False” under HKEY_LOCAL_MACHINESOFTWAREPoliciesCitrixDazzle.

      [From RcvrForWin4.2_14.2.100][#LC2580]

    10. When “SelfServiceMode” is set to “False”, Start Menu shortcuts are created for background sessions, such as the Pre-launch application.

      [From RcvrForWin4.2_14.2.100][#LC1760]

    11. This fix addresses the following issues:

      • When starting a seamless published application, the application might open behind the Windows taskbar.
      • When moving the Windows taskbar to another location, the seamless session fails to resize and the taskbar might overlap with the seamless application.

      To enable this fix, you must also install the server-side Fix #LC1342.

      [From RcvrForWin4.2_14.2.100][#LC1645]

    12. An error message might appear when starting a session in Receiver for Windows 4.2 on Windows XP Embedded thin client.

      [From RcvrForWin4.2_14.2.100][#LC1929]

    13. This fix enables FastConnect Scripting API support while installing by setting “FastConnectAPISupportEnabled=True.” You can also enable this setting through the Group Policy object “Enable FastConnect API Functionality” under “Manage FastConnectAPI support.”

      [From RcvrForWin4.2_14.2.100][#LC2131]

    14. The Receiver for Windows 4.2 might stop sending network packets because of a program deadlock. As a result, the following can occur:

      • The session might not be established.
      • The Citrix HDX Engine might become unresponsive if the desktop screen resolution changes.

      [From RcvrForWin4.2_14.2.100][#LC2105]

    15. This enhancement provides support for TLS versions 1.1 and 1.2 in Receiver for Windows 4.2 Cumulative Update 1.

      [From RcvrForWin4.2_14.2.100][#LC1931]

    16. The ICA Session Round Trip time of the EdgeSight Agent might be high in random sessions across the farm.

      [From RcvrForWin4.2_14.2.100][#LC1725]

    17. With this enhancement, the “icaclient.adm” file is modified improve handling of Fast connect changes.

      [From RcvrForWin4.2_14.2.100][#LC2575]

    18. After resizing the Receiver session to “Scale to Fit” mode, the mouse and keyboard quit working in the session.

      [From RcvrForWin4.2_14.2.100][#LC2219]

    19. This enhancement improves the Citrix Diagnostic Facility (CDF) trace logs for the Fast Connect feature to not report failure when there is no failure.

      [From RcvrForWin4.2_14.2.100][#LC2573]

    20. After installing the Receiver by using the command line, a new store is automatically added in the Self-Service Plug-in when stopping and restarting the Receiver.

      The issue occurs when the “Dazzle” key under HKEY_CURRENT_USERSoftwareCitrix has a subkey called as “Properties” and the “RegDeleteKey” cannot delete the registry key that contains the subkeys and this creates duplicate store keys.

      [From RcvrForWin4.2_14.2.100][#LC2154]

    21. Application shortcuts are left behind in the desktop shortcut folder or on the Start menu when users log off by using Fast Connect Scripting APIs.

      [From RcvrForWin4.2_14.2.100][#LC2590]

    22. Multiple logon prompts might appear for unauthenticated requests when logging off by using the FastConnect Scripting API.

      [From RcvrForWin4.2_14.2.100][#LC2300]

    23. When Receiver related registry entries are created before installing the Receiver, Standard users can install Receiver for Windows without any errors, however, applications might fail to start.

      [From RcvrForWin4.2_14.2.100][#LC0410]

    24. In the FastConnect Scripting API, switching users to explicit authentication might not work.

      [From RcvrForWin4.2_14.2.100][#LC2127]

    25. This feature enhancement includes the “Per App shortcut management” option. By using Application properties, you can create shortcuts on the user’s desktop and on the Start menu for specific published applications.

      Note: The Start menu folder of the Application properties is honored only if users connect to the farm or delivery group by using the Web Interface instead of StoreFront.

      [From RcvrForWin4.2_14.2.100][#LC1930]

    26. When users log off from the Receiver by using Fast Connect, the subscription list of applications continue to appear in the side pane.

      [From RcvrForWin4.2_14.2.100][#LC2574]

    27. If Receiver for Windows is not configured with an account, applications cannot disconnect by using the disconnect SelfService command.

      [From RcvrForWin4.2_14.2.100][#LC2128]

    System Exceptions

    1. The Receiver might experience an access violation and close unexpectedly. When this occurs, users cannot start sessions by clicking application icons in the Web Interface.

      [From RcvrForWin4.2_14.2.100][#LC0650]

    2. When starting a published application with a local printer attached to the user device, Receiver for Windows might close unexpectedly with the following error message:

      “Citrix HDX Engine has stopped working”

      [From RcvrForWin4.2_14.2.100][#LC1170]

    User Experience

    1. With this fix, the Group Policy Object settings are given higher precedence than the primary store when reading the configuration for a session.

      [From RcvrForWin4.2_14.2.100][#LC2698]

    User Interface

    1. After installing the Receiver by using the command line, the store name and the description is set as existing. If the Receiver is restarted, the store name and the description might change automatically to another value. However, the URL remains the same and the connection works correctly.

      The issue occurs because when processing the Receiver sites, the store name is not retrieved from the registry; instead a new store name is generated according to the store URL.

      [From RcvrForWin4.2_14.2.100][#LC1231]

    2. This enhancement suppresses the prompt to remove applications from the application list and shortcuts if the application is no longer published or is disabled.

      [From RcvrForWin4.2_14.2.100][#LC2157]

    3. The “Learn More” link in Desktop Viewer goes to a different set of help files than when users click “Help” from the Receiver icon menu in the navigation area.

      [From RcvrForWin4.2_14.2.100][#LC2066]

    Receiver for Windows 4.2

    Compared to: Citrix Receiver for Windows 4.1.200

    Receiver for Windows 4.2 contains all fixes that were included in Receiver for Windows 4.0, 4.0.1, 4.1, 4.1.2, 4.1.100, and 4.1.200, plus the following, new fixes:

    Content Redirection Session/Connection
    HDX MediaStream Shadowing
    HDX MediaStream Windows Media Redirection Smart Cards
    HDX Plug and Play System Exceptions
    Installing, Uninstalling, Upgrading User Experience
    Logon/Authentication User Interface
    Printing Miscellaneous
    Server/Farm Administration

    Content Redirection

    1. When accessing the URLs within a published application, the server-to-client content redirection might not work and can open a browser on the server and fails to open on the client.

      [#LC0150]

    2. Occasionally, accessing a web site that contains a “HEAD” request in the URL header instead of a “GET” request might fail if the web server fails to accept the HEAD request. As a result, server-to-client content redirection does not work.

      To enable the fix, create the following registry key:

      HKEY_CURRENT_USER_SoftwareCitrixICA ClientEngine

      Name: SpecificSites

      Type: REG_MULTI_SZ

      Value: web site names (one web site per line)

      Note: A GET request rather than HEAD request is sent to any web site specified in the value. The web site name is case sensitive and wildcard ‘*’ is supported. For example, if “*.mycompany.com” is specified in this registry value, users can access both www.mycompany.com and support.mycompany.com which are the “specific” web sites.

      [#LC0326]

    3. This fix is an enhancement to Fix #LA0803. On servers with XenApp 6 Hotfix Rollup Pack 2 and XenApp 6.5 Hotfix Rollup Pack 3 installed, when accessing custom URLs within a published application, server-to-client content redirection does not work and a web browser opens on the server instead of the user device.

      [#LC0428]

    HDX MediaStream

    1. On a user device with two monitors, when playing a video in Windows Media Player within a Receiver session on the first monitor, an additional black window opens on the second monitor.

      [#LC0552]

    2. When playing a video in Windows Media Player within a Receiver session, a second black window opens with the title “Citrix HDX Movie Window.” Closing this secondary window does not have an effect on the video that is playing.

      [#LC0818]

    HDX MediaStream Windows Media Redirection

    1. Static noise can be present when playing audio through Windows Media Player.

      [#LA2911]

    HDX Plug and Play

    1. While in a session, the Receiver for Windows might become unresponsive when removing a USB device from the endpoint.

      [#LA4827]

    2. On occasion, a USB device is not released after logging off from a session, and the device is subsequently not available for use in the local session.

      [#LC0091]

    Installing, Uninstalling, Upgrading

    1. After installing the Receiver using the /includeSSON command line switch, the SSONSVR.exe process fail to run.

      [#LC0138]

    2. Attempts by a Windows SYSTEM administrator to uninstall the Receiver using the CitrixReceiver.exe /uninstall can cause the UAC prompt to appear.

      [#LC0977]

    Logon/Authentication

    1. Enabling Smart Authentication in the client ADM template automatically causes Local User Name and Password to be set to “Enabled” in the local policy even if the policy was not previously configured.

      [#LC0713]

    2. Domain pass-through authentication can fail intermittently for Citrix Receiver for Windows 3.4 with Cumulative Update 3.

      [#LC0865]

    Printing

    1. When configuring Local Printer Settings in Internet Explorer 8 to print multiple pages per sheet, the setting might not be honored; instead one page per sheet is printed. The issue occurs in scenarios where you connect from a XenApp 6.5 published desktop to an instance of Internet Explorer 8 published on a XenApp 6 server.

      [#LA3379]

    2. When clicking “Preview on client” when using the XPS Universal Printer driver, the following error message appears in Internet Explorer:

      “Internet Explorer cannot display the web page.”

      [#LA5896]

    3. Automatic creation of printers is limited to 100 per session.

      [#LC0031]

    4. This enhancement adds CDF tracing support to the LPT mapping client side component.

      [#LC0823]

    Server/Farm Administration

    1. This fix addresses a memory issue in an underlying component.

      [#LA5664]

    2. When Receiver for Windows connects to NetScaler Gateway and then passes the connection to StoreFront, only the service URL and not the beacons are included in the response from StoreFront. When this occurs, users receive an HTTP 403 error and auto-discovery might not work.

      [#LC0481]

    3. If the user disables the “USB Root Hub” setting and enables it again from the Device Manager on the user device when the device is connected to a VDA, the USB device redirection does not work.

      [#LC0541]

    Session/Connection

    1. Logons and logoffs to and from a Windows 7 client device with Receiver for Windows Enterprise Edition installed can be delayed. The issue occurs when logon/logoff scripts are applied by a GPO. Each script can cause a significant delay.

      [#LA3811]

    2. After resuming an endpoint from Sleep or Hibernate mode while connected to a XenApp or a XenDesktop session using Receiver for Windows, copy/paste operations between that endpoint and Citrix session can fail.

      [#LA3973]

    3. With Multi-Stream enabled, Receiver with Desktop Lock might fail to recover from a VDA screen saver and fail to reconnect after a VDA is locked.

      [#LA4097]

    4. When attempting to open a Microsoft Word or Microsoft Excel 2003 file from a client drive mapped into the session with read-only access, the file might fail to open.

      [#LA4198]

    5. With the “Hide Icon” policy enabled, the “About Citrix Receiver” window might appear automatically after logging on to the client device.

      [#LA4513]

    6. Attempts to launch a session using a custom virtual driver can fail.

      To enable the fix, you must create the following registry key:

      • On 32 bit Windows

        HKEY_LOCAL_MACHINESOFTWARECitrixICA Client

        Name: VdLoadUnLoadTimeOut

        Type: REG_DWORD

        Data: Any value in seconds
      • On 64 bit Windows

        HKEY_LOCAL_MACHINESOFTWAREWow6432nodeCitrixICA Client

        Name: VdLoadUnLoadTimeOut

        Type: REG_DWORD

        Data: Any value in seconds

      [#LA4540]

    7. On VOIP calls made from a PVS streamed VDA using HollyCRM with the Huawei OpenEye plugin, neither side might hear the other after two hours or more.

      [#LA4809]

    8. When pressing the Windows key or clicking the Start button to open the client-side Start menu with a seamless session window running in the foreground, clicking the taskbar icon of a local window causes the focus to remain on the seamless session window instead of shifting to the local window.

      [#LA5089]

    9. With SSL Relay enabled, Session Reliability fails to work for applications configured to utilize encryption.

      [#LA5476]

    10. After changing the password in a XenApp published desktop session, pass-through authentication to published applications from within the published desktop session fails and users receive a prompt for their user name and password.

      [#LA5587]

    11. The Receiver fails to connect to StoreFront through the Netscaler Gateway from Windows Server 2012 R2.

      [#LC0084]

    12. In Receiver for Windows 4.1, a second desktop session is created when users attempt to reconnect to a disconnected session by clicking the desktop icon in the Self-Service Plug-in window.

      [#LC0182]

    13. Cleanup.exe can exit unexpectedly while resetting the Receiver.

      [#LC0249]

    14. During session pre-launch in non-English XenApp environments, the Citrix Receiver progress bar might become visible and unresponsive with the following error message:

      “Connection Established, Negotiating Capabilities”

      [#LC0306]

    15. Typing in published instances of Microsoft Outlook can cause the session to disconnect at random.

      [#LC0323]

    16. When attempting to transfer a file by using a twain device with any third-party application, the application might exit unexpectedly.

      [#LC0369]

    17. When users connect to a Windows 7 VDA by using Receiver for Windows, if the user redirects the SpeechMike by using Desktop Viewer, the redirection might fail when the microphone button is released.

      [#LC0510]

    18. Even with file type association configured, users are prompted to choose an application to open a given file with.

      [#LC0515]

    19. Attempts to connect through a proxy server via a PAC file fail.

      [#LC0529]

    20. Citrix Receiver for Windows 13.4 Cumulative Update 3 might exit unexpectedly for published SAP applications with the following error message:

      “Citrix HDX Engine has stopped working”

      [#LC0712]

    21. The redirected COM port device does not work in a Receiver session.

      [#LC0851]

    22. If Fix #LC0031 is applied, when users disconnect or log off, the Receiver session becomes unresponsive for more than two minutes when there are other active sessions.

      [#LC0983]

    Shadowing

    1. Attempts by administrators to shadow a session can result in a black shadowing session to be initiated that might fail to redraw automatically. The issue occurs if the shadower and shadowee windows are of the same size.

      [#LA2913]

    Smart Cards

    1. The Citrix Receiver for Windows might fail to find a valid smart card certificate and the following error message might appear in the Authentication Manager debug log:

      “ERROR_WINHTTP_CLIENT_AUTH_CERT_NEEDED: Unknown error code ‘12044’”

      [#LC0783]

    System Exceptions

    1. When a client device resumes from the hibernation state, Receiver for Windows can become unresponsive.

      [#LA5023]

    2. An issue with the CDViewer process can cause a black screen to appear and trigger a .Net unhandled exception.

      [#LC1038]

    User Experience

    1. In some configurations, user sessions can experience a mouse flicker.

      [#LA309]

    2. With “Local Text Echo” enabled, the input caret in published instances of Internet Explorer might flicker or be invisible over high latency connections.

      [#LA4762]

    3. Under certain circumstances, applications launch into the background.

      [#LC0050]

    4. If users open multiple Excel workbooks and Excelhook is enabled in the registry, when closing the last workbook the Excel taskbar icon disappears, even though the Excel window is open.

      [#LC0062]

    5. Any user other than the user that installed the receiver is prompted to “Add Account” when launching Receiver for the first time.

      [#LC0253]

    6. After resuming from “Turn off the display,” the session is redrawn as a small screen in the top left corner of the monitor.

      [#LC0319]

    7. Attempts to move a published application window behind the local Windows taskbar can fail.

      [#LC0561]

    8. Application windows might redraw incorrectly in multiple monitor configurations.

      [#LC0600]

    User Interface

    1. When the Receiver Store window is closed during the application launch, the progress bar can remain visible after the application launch completes.

      [#LC0464]

    2. While launching an application or a desktop, the launch dialog remains empty for several seconds without any activity description.

      [#LC0624]

    3. This fix removes a typographical error from the default admin template.

      [#LC0848]

    Miscellaneous

    1. This feature enhancement to the Citrix Receiver installer logging allows you to:

      • Save logs to a permanent location
      • Preserve the installation history after each install
      • Collect user environment information before actual installation starts
      • Provide more debugging information in the install logs

      [#LA4615]

    2. CtxCredApi.dll and CtxCredApi(64).dll are now included in the Citrix Receiver for Windows Enterprise MSI package. The API now supports 64-bit. Use CtxCredApi64.dll for 64-bit applications.

      [#LA4630]

    3. CPU utilization of all wfica processes on a server can increase by around 10 percent when a single user uses audio in the user session.

      [#LA5918]

    4. The receiver might not be able to properly read a certificate’s organization name if the name contains special characters – specifically characters outside the first 128 of the ASCII character set.

      [#LC0801]

    5. When using the “wfica32.exe /setup” command, the wfica.ocx ActiveX add-on in fails to register Internet Explorer.

      [#LC0927]

    Receiver for Windows 4.1.200

    Compared to: Citrix Receiver for Windows 4.1.100

    Receiver for Windows 4.1.200 contains all fixes that were included in Receiver for Windows 4.0, 4.0.1, 4.1, and 4.1.2, 4.1.100, plus the following, new fixes:

    HDX MediaStream Flash Redirection Session/Connection
    Printing System Exceptions
    Server/Farm Administration User Experience

    HDX MediaStream Flash Redirection

    1. Browsing certain Web sites with HDX MediaStream Flash Redirection enabled can cause Internet Explorer to become unresponsive.

      To enable this fix, you must also install VDA/HDX Mediastream for Flash Fix #LA4151 and set the following registry key on the VDA/XenApp server:

      HKEY_LOCAL_MACHINESOFTWAREWow6432NodeCitrixHdxMediaStreamForFlashServerPseudoServer

      Name: SupportedUrlHeads

      Type: REG_MULTI_SZ

      Data: <each value on a separate line, null separated:>

      http://

      https://

      file://

      [From RcvrForWin4.1_14.1.200][#LA5255]

    2. Disabling Flash intelligent fallback in a session can cause Internet Explorer to become unresponsive.

      [From RcvrForWin4.1_14.1.200][#LA5404]

    Printing

    1. The Citrix Printer Driver (UPD) does not print barcode fonts. The font appears as blank spaces or random characters when printing documents with the Citrix Printer Driver (cpviewer.exe) or a barcode printer.

      [From RcvrForWin4.1_14.1.200][#LC0141]

    Server/Farm Administration

    1. If the “File redirection bandwidth limit” and “Overall session bandwidth limit” policies are set, the session might exit unexpectedly.

      In order to address the issue, you must install both a server and a receiver update that contains Fix #LA5925, and then set the following registry key on the server:

      • Create the following registry key:

        HKEY_LOCAL_MACHINESYSTEMCurrentControlSetservicespicadmParameters

        Name: DisableHighThroughput

        Type: DWORD

        Value: 1
      • Change the following registry key::

        HKEY_LOCAL_MACHINESYSTEMCurrentControlSetservicespicadmParameters

        Name: MaxNetCommands

        Type: DWORD

        Value: Set to a smaller value

      [From RcvrForWin4.1_14.1.200][#LA5925]

    Session/Connection

    1. If the network connection to a VDA is disconnected and then reconnected, clicking with the mouse fails.

      [From RcvrForWin4.1_14.1.200][#LA5743]

    2. COM port redirection can fail with the following error message:

      “Error in OpenPort: Comport ‘COM4′”

      [From RcvrForWin4.1_14.1.200][#LC0434]

    3. When an endpoint connected to a VDA resumes from the sleep state, the mouse and the keyboard no longer work in the VDA session.

      [From RcvrForWin4.1_14.1.200][#LC0085]

    4. The windows session running in the foreground might unexpectedly lose the foreground focus.

      [From RcvrForWin4.1_14.1.200][#LA5489]

    System Exceptions

    1. Playing a video in a media player in a pass-through session can cause the session to exit unexpectedly.

      [From RcvrForWin4.1_14.1.200][#LC0553]

    User Experience

    1. Full-screen seamless applications do not move smoothly, can be jittery and show the desktop background on the borders when moved around.

      [From RcvrForWin4.1_14.1.200][#LC0696]

    2. On wireless networks, the session window can temporarily turn a solid gray.

      [From RcvrForWin4.1_14.1.200][#LC0530]

    3. In user session governed by a policy that sets the session sound quality to High sound quality; lowest performance (Advanced Configuration > Properties > Client devices > Resources > Audio > Sound quality > High sound quality; lowest performance), no sound is audible.

      [From RcvrForWin4.1_14.1.200][#LC0329]

    4. When looping a multimedia file in an RDS desktop session, the audio and video streams stop after the file is looping for an hour or longer.

      [From RcvrForWin4.1_14.1.200][#LC0641]

    5. Session pre-launch works only the first time Receiver for Windows is launched, not once it has been configured.

      [From RcvrForWin4.1_14.1.200][#LC0701]

    Receiver for Windows 4.1.100

    Compared to: Citrix Receiver for Windows 4.1

    Receiver for Windows 4.1.100 contains all fixes that were included in Receiver for Windows 4.0, 4.0.1, 4.1, and 4.1.2, plus the following, new fixes:

    HDX 3D Pro Server/Farm Administration
    HDX MediaStream Session/Connection
    HDX Plug and Play System Exceptions
    HDX RealTime User Experience
    Installing, Uninstalling, Upgrading User Interface
    Printing Miscellaneous

    HDX 3D Pro

    1. After a few hours of usage, the wfica32.exe process can consume 100% of the CPU when using HDX 3D Pro with the H264 codec and text tracking disabled.

      [From RcvrForWin4.1_14.1.100][#LA5554]

    HDX MediaStream

    1. Attempts to view streaming videos by using a published web browser, such as Internet Explorer, might not work due to a failure in HDX MediaStream Flash Redirection.

      To enable the fix, set the following registry keys:

      • On 32-bit Windows:

        HKEY_LOCAL_MACHINESOFTWARECitrixHdxMediaStreamForFlashClientPseudoContainer

        Name: FallbackIfFlashNotExist

        Type: REG_DWORD

        Data: 0
      • On 64-bit Windows:

        HKEY_LOCAL_MACHINESOFTWAREWow6432NodeCitrixHdxMediaStreamForFlashClientPseudoContainer

        Name: FallbackIfFlashNotExist

        Type: REG_DWORD

        Data: 0

      [From RcvrForWin4.1_14.1.100][#LA5278]

    2. With HDX Mediastream for Flash Version 1.0 (First Generation Flash Redirection) enabled, Microsoft Internet Explorer might exit unexpectedly while Adobe Flash Player 11.8 or later is installed.

      [From RcvrForWin4.1_14.1.100][#LA5421]

    HDX Plug and Play

    1. after installing Receiver for Windows 4.0 on Windows XP SP3, USB ports on the docking station can no longer be redirected.

      [From RcvrForWin4.1_14.1.100][#LA4582]

    HDX RealTime

    1. HDX RealTime Webcam Video Compression redirection might fail to support Quarter Video Graphics Array (QVGA) display resolution (320×240) and can cause the wfica32.exe process to exit unexpectedly.

      [From RcvrForWin4.1_14.1.100][#LA5232]

    Installing, Uninstalling, Upgrading

    1. When upgrading to a newer version of Receiver for Windows without being connected to the Internet, the previous version is not completely uninstalled and the installation of the newer version fails.

      [From RcvrForWin4.1_14.1.100][#LA4896]

    Printing

    1. This fix addresses an issue where duplex printing fails when the Universal Printer driver is configured and has to be done manually instead.

      [From RcvrForWin4.1_14.1.100][#261552]

    2. Attempts to print an HTML document using Internet Explorer 9 can result in garbled output in the Citrix Print Viewer (cpviewer.exe) and the printout for certain type of fonts.

      [From RcvrForWin4.1_14.1.100][#LA3962]

    Server/Farm Administration

    1. If the StoreFront is configured with an unauthenticated store, Account Discovery might fail when using Receiver for Windows.

      [From RcvrForWin4.1_14.1.100][#LC0004]

    2. This feature enhancement supports auto creation of shortcuts for preferred applications by using a prefer template directory. For these applications, in addition to the existing prefer rules, the Self Service Plug-in searches for the shortcuts in the prefer template directory. If it matches the prefer rules, it copies shortcut to the user’s start menu.

      By default, this directory is one of the following:

      • %systemdrive%:Program FilesCitrixshortcuts
      • %systemdrive%:Program Files (x86)Citrixshortcuts for per user device installation and
      • %systemdrive%:Users<user name>AppDataLocalCitrixSelfServiceshortcuts for per user installation.

      The default prefer template directory location can be specified in the registry.

      HKEY_LOCAL_MACHINESoftwareCitrixDazzle or HKEY_CURRENT_USERSoftwareCitrixDazzle

      Name: PreferTemplateDirectory

      Type: REG_SZ

      Data: any path (for example, “%systemroot%:Shortcuts”)

      If the application is subsequently unsubscribed or removed from the store, the shortcut that was copied from the preferred directory is deleted.

      [From RcvrForWin4.1_14.1.100][#LC0005]

    Session/Connection

    1. When using Citrix Receiver within a virtual desktop session, attempts to launch XenApp published applications fail and the following error message appears:

      “This version of Citrix Receiver does not support selected encryption. Please contact your administrator. [Error 1029: Invalid DLL load].”

      [From RcvrForWin4.1_14.1.100][#LA4743]

    2. With Receiver for Windows 13.4 Cumulative Update 2, when seamless application has focus, the input language on the language bar changes when pressing Alt + Tab to switch active windows.

      [From RcvrForWin4.1_14.1.100][#LA4963]

    3. With the “Group similar taskbar buttons” option selected on Taskbar and Start Menu Properties on a Windows XP system, launching applications might be slow.

      [From RcvrForWin4.1_14.1.100][#LA4191]

    4. After upgrading from Version 12.2 of the Citrix online plug-in to Version 3.x of Citrix Receiver for Windows, proxy connections to external Web sites might fail to launch with NTLM proxy authentication enabled.

      [From RcvrForWin4.1_14.1.100][#LA3781]

    5. If the user device does not have a connected webcam, attempts to start a published instance of Microsoft Lync 2010 might result in the application connecting and disconnecting several times before establishing a final connection and starting the application. This can occur if you install an application that installs a webcam when no other webcams are installed, such as the Motorola Bluetooth package.

      [From RcvrForWin4.1_14.1.100][#LA4867]

    6. When starting a published application or a desktop, Kerberos authentication might not work when using pass-through authentication on an IPv4 network. This release fixes the issue for IPv4 networks only.

      [From RcvrForWin4.1_14.1.100][#LA5026]

    7. This fix addresses audio/video issues related to the Microsoft Lync 2013 VDI Plug-in for Windows. It improves the user experience for Lync users. For more information, see Knowledge Center article CTX138408.

      [From RcvrForWin4.1_14.1.100][#LA5314]

    8. If the CANcaseXL USB network adapter is redirected into a virtual desktop, it appears to malfunction in Windows Device Manager. This USB device does not support the Citrix USB redirection driver. The VDA requires installation of Fix #LA5022 in order to work properly.

      [From RcvrForWin4.1_14.1.100][#LA5022]

    9. This fix reworks Fix #LA1257, which fails to fully address the following issue:

      With the Desktop Viewer disabled, a full-screen client session does not adjust the screen resolution of the Virtual Desktop Agent in response to a change in screen resolution on the endpoint.

      [From RcvrForWin4.1_14.1.100][#LA4000]

    10. When connectivity to a XenDesktop session is lost for an amount of time that exceeds the Session Reliability timeout, DesktopViewer remains onscreen indefinitely. The session itself disappears, as expected, from the Connection Center after the Session Reliability timeout.

      [From RcvrForWin4.1_14.1.100][#LA4856]

    System Exceptions

    1. The wfica32.exe process can exit unexpectedly and the following error message appears:

      “Citrix HDX Engine has encountered a problem and needs to close.”

      [From RcvrForWin4.1_14.1.100][#LA3964]

    2. The wfica32.exe process can exit unexpectedly and the following error message appears:

      “Citrix HDX Engine has encountered a problem and needs to close.”

      [From RcvrForWin4.1_14.1.100][#LA4695]

    3. The wfica32.exe process might exit unexpectedly when starting a pass-through session from the XenApp 6.5 desktop to a XenApp 4.5 published application.

      [From RcvrForWin4.1_14.1.100][#LA5193]

    4. If the Multi-Stream policy is enabled, applications can become unresponsive when accessing the COM port.

      [From RcvrForWin4.1_14.1.100][#LA5543]

    5. In double-hop scenarios, launching Microsoft Outlook or Communicator can cause Receiver for Windows to exit unexpectedly.

      [From RcvrForWin4.1_14.1.100][#LA4813]

    User Experience

    1. When connecting or reconnecting to a session hosted on XenApp for Unix, no screen updates occur for 90 seconds.

      [From RcvrForWin4.1_14.1.100][#LA5244]

    User Interface

    1. A change introduced in Version 12.1 of the online plug-in introduced a delay in the appearance of the connection progress bar for seamless connections. However, for sessions connecting to slower servers, this behavior is not always desirable. This enhancement introduces support for the following registry key that allows you to configure the duration of the delay:

      On 32-bit Windows:

      HKEY_LOCAL_MACHINESOFTWARECitrixICA Client

      Name: NotificationDelay

      Type: REG_DWORD

      Data: <Delay, in milliseconds>

      On 64-bit Windows:

      HKEY_LOCAL_MACHINESOFTWAREWow6432nodeCitrixICA Client

      Name: NotificationDelay

      Type: REG_DWORD

      Data: <Delay, in milliseconds>

      [From RcvrForWin4.1_14.1.100][#LA0678]

    2. After changing the desktop color scheme from the default color blue to other colors, such as Olive Green or Silver (Desktop > Properties > Appearance tab > Color scheme), the text and the background color of Self-service Plug-in become identical, making it impossible to read menu items.

      [From RcvrForWin4.1_14.1.100][#LA5121]

    Miscellaneous

    1. When using email-based discovery, if the SRV record created on the DNS side includes a port other than 443, the Receiver ignores the port specified in the SRV record and continues to connect to the Access/NetScaler Gateway URL using port 443.

      [From RcvrForWin4.1_14.1.100][#LA4491]

    Receiver for Windows 4.1.2

    Compared to: Citrix Receiver for Windows 4.1

    Receiver for Windows 4.1.2 contains all fixes that were included in Receiver for Windows 4.0, 4.0.1, and 4.1, plus the following, new fixes:

    Microsoft Lync 2013 VDI Plug-in Installing, Uninstalling, Upgrading

    Microsoft Lync 2013 VDI Plug-in

    1. Video does not appear after you move the Lync conversation window to a second monitor.

      [#LA5314, #399447]

    2. When you move a Whiteboard presentation window to another user, the other user’s video does not display in your conversation window.

      [#LA5314, #399465]

    3. Receiver can exit unexpectedly in multi-party video calls or when a video conference ends.

      [#LA5314, #426035]

    4. On some client devices, video is intermittently unavailable in video calls in full-screen VDA mode.

      [#LA5314, #418675]

    5. Video distortion can occur if you move a video conference window.

      [#LA5314, #419898]

    Installing, Uninstalling, Upgrading

    1. When upgrading to a newer version of Receiver for Windows without being connected to the Internet, the previous version is not completely uninstalled and the installation of the newer version fails.

      [#LA4896]

    Receiver for Windows 4.1

    Compared to: Citrix Receiver for Windows 4.0.1

    Receiver for Windows 4.1 contains all fixes that were included in Receiver for Windows 4.0 and 4.0.1, plus the following, new fixes:

    HDX MediaStream Flash Redirection Printing
    HDX MediaStream Windows Media Redirection Session/Connection
    HDX Plug and Play System Exceptions
    Installing, Uninstalling, Upgrading User Experience
    Keyboard User Interface
    Local App Access Miscellaneous
    Logon/Authentication

    HDX MediaStream Flash Redirection

    1. When playing several multimedia files in rapid succession on http://www.youtube.com/ with HDX MediaStream Flash Redirection enabled, the PseudoContainer2.exe process might exit unexpectedly.

      [#LA3846]

    HDX MediaStream Windows Media Redirection

    1. In Version 3.4 of Receiver for Windows with HDX MediaStream Windows Media Redirection enabled, a delay of up to ten seconds can be observed before a multimedia file starts to stream.

      [#LA4141]

    HDX Plug and Play

    1. Clicking Devices within the Desktop Viewer to select a USB device to be remoted using HDX Plug-n-Play USB Device Redirection can cause the Desktop Viewer to become unresponsive.

      [#LA3348]

    Installing, Uninstalling, Upgrading

    1. Attempts by non-administrative users to upgrade the Receiver for Windows might result in the partial installation of the receiver if the receiver was installed by an administrator.

      With this fix, a non-administrative user attempting to upgrade a receiver installed by an administrator receives an error message and the installation process is terminated.

      [#LA3425]

    Keyboard

    1. When using version 3.3. of the Receiver for Windows, pressing the Alt key can cause the key to remain in a down state. As a result, pressing the “E” key subsequently can invoke Windows Explorer.

      [#LA3288]

    2. When clicking the Desktop Viewer toolbar with the Windows key pressed in full-screen mode, the key might remain in a down state. As a result, pressing the “E” key subsequently invokes Windows Explorer.

      [#LA3349]

    3. This fix addresses an issue that can cause the state of the Caps Lock, Num Lock, and/or Scroll Lock keys to be out of sync in an ICA session. This fix introduces a new parameter that allows you to force the synchronization of the keyboard LED state between the client and the server. To enable this option, add the entry “KeyboardForceLEDUpdate = On” to the [WFClient] section of the appsrv.ini file in the local user profile location or of the default.ica file in the corresponding Web Interface site.

      [#LA3682]

    4. This fix addresses an LED synchronization issue that can cause the state of the Caps Lock, Num Lock, and/or Scroll Lock keys to be out of sync between the client and server.

      [#LA4293]

    Local App Access

    1. With Local App Access enabled, clicking the Desktop Viewer causes the client local taskbar to appear needlessly.

      [#LA3049]

    Logon/Authentication

    1. Pass-through authentication might fail to work after installing XenDesktop 7 VDA on Windows Server 2008 R2. The issue occurs because the ssonsvr.exe process fails to start.

      [#LA4685]

    Printing

    1. When sending multiple Adobe Acrobat print jobs to a session printer, random pages or entire print jobs can be lost.

      [#LA3643]

    2. Session printer enumeration can take an excessive amount of time.

    3. [#LA3951]

    Session/Connection

    1. When a client device is in the sleep or hibernation state for an extended period of time with an active XenDesktop session running, upon resuming, the session might fail to reconnect as expected and become stuck in a reconnection phase requiring the session window to be manually closed.

      This fix addresses the issue so that upon resuming the client device, the session window closes as expected when reconnection fails.

      [#LA2748]

    2. When launching a published application in seamless mode, the progress bar window remains in the background.

      To enable the fix, set the following registry keys on the client-side:

      • For Windows 32-bit systems:

        HKEY_LOCAL_MACHINESOFTWARECitrixICA Client

        Name: ForegroundProgressBar

        Type: DWORD

        Data: 1
      • For Windows 64-bit systems:

        HKEY_LOCAL_MACHINESOFTWAREWow6432NodeCitrixICA Client

        Name: ForegroundProgressBar

        Type: DWORD

        Data: 1

      [#LA3491]

    3. Receiver with Desktop Lock presents a gray screen each time there is a hardware failure or if the VM is forcefully shut down from the hypervisor.

      [#LA3499]

    4. With Taskbar Grouping enabled on the client device, TaskbarGrpXpVista.dll – within wfica32.exe – unnecessarily queries the client device for information about published applications running in the session. For example, when running a published instance of cmd.exe, TaskbarGrpXpVista.dll queries C:windowssystem32cmd.exe for information about the executable. In scenarios where the published application is running from the remote share, this can cause undesirable bandwidth consumption.

      [#LA3661]

    5. With a GPO setting in place to prevent taskbar grouping, clicking taskbar icons on Windows XP and Vista client devices fails to switch focus to the associated windows.

      [#LA3889]

    6. The Receiver can become unresponsive when you click the Devices button of the Desktop Viewer toolbar while the “Citrix Receiver â?? Device Access” dialog box is displayed. This dialog box appears if the device access preference is configured to “Ask me each time” instead of the default “Do nothing.”

      [#LA3899]

    7. The Desktop Viewer (CDViewer.exe) and wfica32.exe processes might exit unexpectedly while reconnecting to a virtual desktop session.

      [#LA3944]

    8. With this fix, the IsReconnectInProgress() API is integrated to Citrix Fast Connect 2.0. The feature determines whether the reconnect process is in progress or not while the Auto Client Reconnect feature is enabled.

      [#LA4080]

    9. This fix allows pass-through applications to be reconnected and enables Workspace Control for pass-through applications.

      To enable the fix, you must set the following registry keys:

      To enable Workspace Control in pass-through mode:

      HKEY_LOCAL_MACHINESOFTWARECitrixPNAgent

      Name: ForceEnableWSC

      Type: DWORD

      Data = 1

      To enable pass-through applications to be reconnected:

      HKEY_LOCAL_MACHINESoftwareCitrixICA Client

      Name: BypassPassThruMode

      Type: DWORD

      Data = 1

      Note: This fix works only under the following conditions:

      • The two or more connection hops cannot occur within the same XenApp Services site or farm. In other words, the endpoint Receiver can connect to a XenDesktop VDA published on XenApp Services Site A, and then the pass-through client on that VDA can connect to a published application or desktop on a different XenApp Services site, Site B.
      • The second connection hop must be to a XenApp terminal session; it cannot be to a XenDesktop VDA.

      [#LA4206]

    10. When using remote assistance software in a desktop that is published to be an odd (non-even) percentage of the client screen (for example, 95%), the remote assistance session might appear to be distorted.

      [#LA4313]

    11. This compatibility enhancement extends support for HDX Plug and Play USB device redirection to additional USB devices.

      [#LA4335]

    12. A deadlock in wfcrun32.exe can prevent new sessions from launching successfully.

      [#LA4344]

    13. Attempts to connect to XenApp servers using the Citrix Quick Launch tool or static ICA files that specify “HTTPBrowserAddress=ServerName_Or_IP:Port” (for example: “HTTPBrowserAddress=192.168.1.10:8080”) can fail.

      [#LA4585]

    System Exceptions

    1. The wfica32.exe process can exit unexpectedly and the following error message appears:

      “Citrix HDX Engine has encountered a problem and needs to close.”

      [#LA3412]

    2. The wfica32.exe process might experience an access violation and exit unexpectedly.

      [#LA3639]

    3. The wfica32.exe process might exit unexpectedly.

      [#LA4208]

    User Experience

    1. This fix eliminates the unnecessary appearance of logon prompts when Receiver 4.0 is used with StoreFront.

      [#LA4652]

    User Interface

    1. Application launches fail if there is a mismatch between the application name and the display name of the published application.

      [#LA3891]

    Miscellaneous

    1. This release includes the latest version of the SSLSDK – Version 12.1.13.

      [#LA3804]

    2. This fix improves the functionality of the TerminateUser function of Receiver for Windows in some deployments.

    3. [#LA3881]

    Receiver for Windows 4.0.1

    Compared to: Citrix Receiver for Windows 4.0

    Receiver for Windows 4.0.1 contains all fixes that were included in Receiver for Windows 4.0, plus the following, new fixes:

    1. This fix eliminates the unnecessary appearance of logon prompts when Receiver 4.0 is used with StoreFront.

      [#LA4652]

    Receiver for Windows 4.0

    Compared to: Citrix Receiver for Windows 3.4

    Receiver for Windows 4.0 contains the following fixes compared to Citrix Receiver for Windows 3.4:

    HDX MediaStream Flash Redirection Session/Connection
    HDX Plug and Play System Exceptions
    Installing, Uninstalling, Upgrading User Experience
    Keyboard User Interface
    Printing Miscellaneous
    Seamless Windows

    HDX MediaStream Flash Redirection

    1. Moving a video window offscreen in whole or in part while a video file is rendering can leave a dark area on the screen. The dark area remains even after moving the video window back.

      [#LA0599]

    2. Important: Before applying this fix on a client device, see Knowledge Center article CTX126817 for important information about how the Dynamic Blacklist feature might affect client-side Flash redirection.

      In scenarios where the Enable server-side content fetching policy is enabled on the server and the Flash server-side content fetching URL list setting is configured for the Flash Redirection policy on the client, attempts to play Flash content fail if the URL to the content contains multibyte/unicode characters such as those common in Asian languages

      To enable this fix in its entirety, you must install both a client hotfix that contains Fix #LA1621 and:

      • For XenApp: an HDX Flash hotfix that contains Fix #LA1621
      • For XenDesktop: a Virtual Desktop Agent hotfix that contains Fix #LA1621

      Note: This fix also requires the corresponding language code pages to be installed on both the client and the server. The code pages are installed by default by the Windows operating system. For example, the Japanese distribution of Windows 7 installs the Japanese code pages by default. However, if you are using a URL with Japanese characters on an English distribution of Windows 7, the Japanese code pages must be installed explicitly. This applies to both the client and the server because the URLs are transferred from the client to the server when server-side content fetching is enabled.

      [#LA1621]

    3. Certain user interactions with Flash content, such as clicking buttons, can cause Pseudocontainer2.exe to exit unexpectedly.

      [#LA1948]

    4. Client-side content redirection can fail for certain types of Flash content and revert to server-side rendering, including cases where:

      1. Flash content tries to download another Flash file that does not exist or cannot be located
      2. Flash content created by Adobe Captive fails some logic checks of the client-side content redirection feature
      3. Flash content causes the client-side content redirection feature to remote unsupported interfaces to the server
      4. The client attempts to fetch Flash content even if its URL is configured in the ServerContentFetching URL blacklist

      To enable this fix, you must install both an HDX Flash and a Receiver for Windows hotfix that contains Fix #LA2198. To enable this fix for issue #1 above, you must also set the following registry key on the client:

      • On 32-bit Windows:

        HKEY_LOCAL_MACHINESOFTWARECitrixHdxMediaStreamForFlashClientPseudoContainer

        Name: FallbackIfFlashNotExist

        Type: REG_DWORD

        Data: 0
      • On 64-bit Windows:

        HKEY_LOCAL_MACHINESOFTWAREWow6432NodeCitrixHdxMediaStreamForFlashClientPseudoContainer

        Name: FallbackIfFlashNotExist

        Type: REG_DWORD

        Data: 0

      [#LA2198]

    5. When switching the focus from the Flash window (- a child window of a Web browser running seamless window) to a local window and switching the focus back to the address bar of the seamless browser window, attempts to type in the browserâ??s address bar can fail.

      [#LA2685]

    6. Important: Before applying this fix on a client device, see Knowledge Center article CTX126817 for important information about how the Dynamic Blacklist feature might affect client-side Flash redirection.

      The HDX MediaStream Flash Redirection feature might fail to work on Dailymotion videos (http://www.dailymotion.com) with an error. The issue occurs when the client and server are located in different geographical locations.

      To enable this fix, you must create the following registry key:

      HKEY_LOCAL_MACHINESOFTWARECitrixHdxMediaStreamForFlashClient

      Name: DisableRegionFiltering

      Type: REG_DWORD

      Data: 1

      [#LA3134]

    HDX Plug and Play

    1. This feature enhancement modifies the default USB Redirection behavior as follows:

      • When the Desktop Viewer is enabled, users can manually redirect USB devices.
      • When the Desktop Viewer is not enabled, USB devices are automatically redirected.

      [#LA0108]

    2. After failed attempts to map certain USB devices into a virtual desktop session, the devices disappear from the Device Manager until you restart the endpoint.

      [#LA0954]

    3. Clicking Devices within the Desktop Viewer to select a USB device to be remoted using HDX Plug-n-Play USB Device Redirection can cause the Desktop Viewer to become unresponsive.

      [#LA3348]

    Installing, Uninstalling, Upgrading

    1. After upgrading to Receiver 3.x, users cannot launch published applications and the following error message appears:

      “This version of Citrix Receiver does not support selected encryption. Please contact your administrator. Error 1046: The Virtual Driver is not loaded.”

      [#LA3120]

    Keyboard

    1. Minimizing a virtual desktop session by clicking Home on the Desktop Viewer can intermittently cause the Tab key to stop working on the endpoint until the session is disconnected.

      [#LA2925]

    2. As of Version 3.0 of the Receiver for Windows, the KeyboardTimer setting value set at HKEY_LOCAL_MACHINESOFTWARECitrixICA ClientEngineLockdownProfilesAll RegionsLockdownVirtual ChannelsKeyboard no longer works. This fix reinstates the functionality.

      [#LA2949]

    3. This fix addresses an issue that can cause the state of the Caps Lock, Num Lock, and/or Scroll Lock keys to be out of sync between the client and the server in pass-through sessions running in the foreground.

      [#LA3288]

    4. This fix addresses an issue that can cause the state of the Caps Lock, Num Lock, and/or Scroll Lock keys to be out of sync between the client and the server in pass-through sessions running in the background.

      [#LA3310]

    Printing

    1. Clicking Local Printer Settings on the Client Settings tab a a UPD printer’s Properties sheet and then closing the settings dialog box can cause the Properties sheet to become unresponsive.

      [#259485]

    Seamless Windows

    1. When using the Connection Center or the Web Interface to log off from a seamless session with unsaved data, a black window appears with the following message:

      “Programs still need to close” – with the two options – “Force Logoff” or “Cancel.” The “Cancel” option does not work.

      After installing this fix, the Cancel option works as designed. After utilizing the Cancel button, Citrix recommends that you save your data and then log out of the session to prevent further performance delays.

      [#LA0318]

    Session/Connection

    1. After disconnecting and reconnecting to a virtual desktop session, attempts to record audio from within the session can fail. To enable this fix in its entirety, you must install both a server and a client hotfix that contains Fix #LA0821.

      [#LA0821]

    2. The time required for file transfers in a client session can be slower than in an RDP session.

      To enable this fix in its entirety, you must install both a server and a client hotfix that contains Fix #LA1263.

      [#LA1263]

    3. Under certain conditions, changing the resolution of a virtual desktop session before the session disconnects unexpectedly, such as due to a network outage, can cause the session resolution to be different than expected after you reconnect.

      [#LA1377]

    4. Serial port barcode scanners cannot process labels the label’s data size exceeds 512 bytes. To enable this fix, you must set the following registry key:

      HKEY_LOCAL_MACHINESOFTWARECitrixICA Client

      Name: CommBufferSize

      Type: REG_DWORD

      Data: Range of 512 (minimum) and 2048 (maximum value)

      [#LA1695]

    5. Disabling the Network List Service and/or the Network Location Awareness service as described in Knowledge Center article CTX131577 causes Version 12.3 of the online plug-in to lose connectivity.

      [#LA2024]

    6. Attempts to launch a seamless application published to a UNC path over a low bandwidth connection can take more than two minutes to complete.

      [#LA2170]

    7. Invoking the input method of a seamless session by clicking Ctrl + Shift can change the client-side local input method as well. To prevent this issue, you must set the following registry key:

      HKEY_LOCAL_MACHINESOFTWARECitrixICA Client

      Name: Showlocallanguagebar

      Type: REG_DWORD

      Data: 1 < to show the local language bar>; 0 <to hide the local language bar>

      [#LA2180]

    8. When Auto Client Redirection is enabled, after choosing Hibernate, reconnection attempts might fail when the client is automatically closed.

      With this fix, the system can be suspended or sent into Hibernation mode with the USB device redirection, and can be auto-reconnected after the system returns from Standby mode.

      [#LA3061]

    9. Published applications might fail to launch if ICA compression is set to “OFF” for Citrix Receiver for Windows 3.x at HKEY_LOCAL_MACHINESOFTWARECitrixICA ClientEngineConfigurationAdvancedModulesTCP/IP Compress=Off.

      [#LA3072]

    10. In a multi-monitor environment, the Desktop Viewer toolbar might no longer be visible while switching the display to a secondary monitor in full-screen mode.

      [#LA3083]

    11. In dual-monitor configurations connected to a Virtual Desktop Agent and where the primary monitor is a laptop, turning the laptop display off and back on causes the session to subsequently display only on the primary monitor.

      [#LA3202]

    12. When using Version 3.3 of the Cumulative Update 1 or Version 3.4 of the Receiver for Windows on a Windows XP workstation running Internet Explorer 8, the initial application might fail to launch from the Web Interface.

      [#LA3234]

    13. Both console and XenDesktop sessions can become unresponsive (Stuck on “Welcome” screen) when attempting to reconnect to a disconnected virtual desktop session using the Receiver for Linux. The issue occurs when the WDDM driver is enabled on the Virtual Desktop Agent and another virtual desktop session is running within the session.

      [#LA3241]

    14. Version 3.4 of the Receiver for Windows might fail to start if the client’s “Regional and Language Options” for Windows 7 is set to “Kazakh (Kazakhstan).”

      [#LA3517]

    System Exceptions

    1. The wfica32.exe process can exit unexpectedly in environments where EdgeSight for Load testing is deployed.

      [#LA0289]

    2. The wfcrun.exe process can exit unexpectedly in environments where HP LoadRunner is deployed.

      [#LA0859]

    3. With the audio policy set to high definition sound, the wfica32.exe process can exit unexpectedly when playing random sample sound files in the Sound control panel of a published desktop.

      [#LA1000]

    4. Version 12.3 of the online plug-in might exit unexpectedly while disconnecting a session from a Web Interface site with a Microsoft Excel 2007 spreadsheet open.

      [#LA2274]

    5. With Local App Access enabled, connection attempts to a Virtual Desktop Agent can fail if a legal notice is configured for the Virtual Desktop Agent.

      [#LA2351]

    6. The Pnamain.exe process can exit unexpectedly when reconnecting to a session.

      [#LA2704]

    7. Sessions running on single-monitor, aero-enabled Windows client devices can disconnect unexpectedly. The issue can occur when a preview, as part of the Dynamic Window Preview feature, is sent to the client; at that time, a twi3.dll thread can terminate the Winlogon.exe process, which in turn causes the session to disconnect.

      To resolve this issue in its entirety, you must install both a XenApp and a Receiver hotfix that contains Fix #LA2858.

      [#LA2858]

    8. The wfica32.exe process might exit unexpectedly. The issue occurs due to an invalid memory dereference.

      [#LA2860]

    9. While printing in certain double-hop scenarios, the following error message appears and the Wfica32.exe process exits unexpectedly: “Citrix HDX Engine was stopped working.” The issue is caused by port names that exceed 260 characters in length.

      To address this issue, you must install both a server and a Receiver hotfix that contains Fix #LA3009 (XA650R01W2K8R2X64056; RcvrForWin3.3_13.3.104, or their replacement hotfixes).

      [#LA3009]

    10. Citrix Receiver can spawn multiple instances of the selfserviceplugin.exe process, causing the system to run out of memory.

      [#LA3460]

    11. The Desktop Viewer might exit unexpectedly during logoff.

      [#LA3567]

    12. PNMain.exe can exit unexpectedly when using the online plug-in as the pass-through client.

      [#LA0785]

    User Experience

    1. When using USB redirection, a USB SpaceMouse device might disappear from a virtual desktop session after a few hours of use.

      [#LA2256]

    2. This feature enhancement for Version 3.4 of the Receiver for Windows allows you to suppress the following authentication message for VPN logins that appears when the user switches between network connections.

      To suppress the message, create the following registry key:

      • On 32-bit Windows:

        HKEY_CURRENT_USERSoftwareCitrixReceiver

        Name: AutoSecureConnection

        Type: REG_DWORD

        Value: 0 (disables the VPN prompt)
      • On 64-bit Windows:

        HKEY_CURRENT_USERSoftwareWow6432NodeCitrixReceiver

        Name: AutoSecureConnection

        Type: REG_DWORD

        Value: 0 (disables the VPN prompt)

      [#LA3772]

    User Interface

    1. This fix modifies the Korean translation of the “Home Desktop” icon title on the Desktop Viewer toolbar to be more specific.

      [#232198]

    2. When clicking Cancel in the authentication dialog box that appears when running a desktop group shortcut on an endpoint, the following, inaccurate and misleading error message appears:

      “The application or desktop could not be launched. Check your network connection.

      [#259081]

    3. In a maximized session window, the Desktop Viewer toolbar can fail to paint properly if you click Connect in the USBMultiInsertDialogue dialog box after the Session Connection screen disappears.

      [#260390]

    4. The Client Drive Mapping Help topic of icaclient.adm incorrectly states that policies will not override user selections. Policies do override user selections.

      [#LA0398]

    5. With certain custom applications, Speed Screen Latency Reduction’s local text echo edit box displays a black bar while typing.

      [#LA0544]

    6. The welcome and/or completion messages after first successful delivery from Merchandising Server fail to appear.

      [#LA2277]

    7. The icon for Tivoli Access Manager for Enterprise Single Sign-On (TAM ESSO) in the notification area of the Windows taskbar can disappear unexpectedly when launching a published application.

      [#LA3190]

    8. The local taskbar is inaccessible if set to autohide and then moved from its default location to the top, left, or right side of the screen.

      [#LA3400]

    Miscellaneous

    1. When playing UDP audio streams, the handle count of the wfica32.exe process can increase significantly.

      [#LA3094]

    2. This fix removes a limitation to just one Program Neighborhood Web Interface 5.4 site in Receiver for Web 3.3.

      [#LA3142]

    Related:

    • No Related Posts

    Client for Open Enterprise Server 2 SP4 (IR8)

    Abstract:

    This is interim release (IR8) of Client for Open Enterprise Server 2 SP4 (formerly “Novell Client 2 SP4 for Windows”). It includes fixes for problems found after Client for Open Enterprise Server 2 SP4 was released. It also includes support for Microsoft Windows Server 2016. This is a full client package, not just a subset of files.

    Current Readme file is here.

    History of fixes is in TID 7016351.

    Document ID: 5370990
    Security Alert: No
    Distribution Type: Public
    Entitlement Required: No
    Files:

    • Client_for_Open_Enterprise_Server_2_SP4_IR8.exe (40.78 MB)

    Products:

    • Client 2 SP4 for Windows 8
    • Client 2 SP4 for Windows
    • Client 2 SP4 for Windows 8.1
    • Client 2 SP4 for Windows 7
    • Client 2 SP4 for Windows Server 2012 R2
    • Client 2 SP4 for Windows Server 2012
    • Client 2 SP4 for Windows Server 2008 R2
    • Client 2 SP4 for Windows 10

    Superceded Patches:

    Related:

    • No Related Posts

    7021483: Reflection Products and Microsoft Windows XP

    Designed for Windows XP – Optimized Status

    The following list of Reflection products and components have been tested with Windows XP and have earned the Microsoft “Designed for Windows XP – Optimized” status.

    Note: Although Microsoft’s XP certification program has been discontinued, Attachmate continues to test our products with Windows XP. For a list of newer Reflection products tested with XP, see the next section, Other Products Tested Under Microsoft Windows XP.

    Refer to your product documentation to determine which products and components are included on your Reflection product CD.

    Reflection 14.0 Products

    Reflection for Multi-Host Enterprise Standard Edition 14.0

    Reflection for Multi-Host Enterprise Professional Edition 14.0

    Reflection Suite for X 14.0

    Reflection for UNIX and OpenVMS 14.0

    Reflection for HP with NS/VT 14.0

    Reflection for IBM 14.0

    Reflection X 14.0

    Reflection NFS Client 14.0

    Reflection 14.0 Product Features

    Reflection for ReGIS Graphics 14.0

    Reflection for UNIX and OpenVMS 14.0

    Reflection FTP Client 14.0

    Reflection LPD 14.0

    Reflection 13.x Products

    Reflection for Multi-Host Enterprise Standard Edition 13.x

    Reflection for Multi-Host Enterprise Professional Edition 13.x

    Reflection Suite for X 13.x

    Reflection for UNIX and OpenVMS 13.x

    Reflection for HP with NS/VT 13.x

    Reflection for IBM 13.x

    Reflection X 13.x

    Reflection NFS Client 13.x

    Reflection 13.x Product Features

    Reflection for ReGIS Graphics 13.x

    Reflection for UNIX and OpenVMS 13.x

    Reflection FTP Client 13.x

    Reflection LPD 13.x

    Other Products Tested Under Microsoft Windows XP

    The following product were tested under Windows XP, but were not submitted for Microsoft “Designed for Windows XP – Optimized” status because Microsoft’s XP certification program has been discontinued.

    Reflection 2014 Products

    Reflection 2014

    Reflection for IBM 2014

    Reflection for UNIX and OpenVMS 2014

    Reflection 2011 Products

    Reflection for IBM 2011 R1

    Reflection for UNIX and OpenVMS 2011 R1

    Reflection Standard Suite 2011 R1

    Reflection 14.1 Products

    Reflection for Multi-Host Enterprise Standard Edition 14.1

    Reflection for Multi-Host Enterprise Professional Edition 14.1

    Reflection Suite for X 14.1

    Reflection for UNIX and OpenVMS 14.1

    Reflection for HP with NS/VT 14.1

    Reflection for IBM 14.1

    Reflection X 14.1

    Reflection for Secure IT Products

    Reflection for Secure IT Windows Client 7.0 or higher

    Reflection for Secure IT Windows Server 7.0 or higher

    For more information about supported platforms, see Technical Note 1944.

    Reflection for the Web Products

    Reflection for the Web 2014, 2011, or 2008 client components will run on Windows XP as long as Reflection for the Web is running on a system that meets minimum system requirements for the operating system, the Java runtime environment, and the web browser.

    For a list of system requirements, see the Reflection for the Web Technical Specifications: http://www.attachmate.com/Products/Terminal+Emulation/refweb/rweb/rweb.htm.

    For additional information about Reflection for the Web and Java Virtual Machines, see Technical Note 1674.

    Note: Windows XP is not a server operating system. We do not recommend running Reflection for the Web server components in a production environment on a workstation operating system such as XP.

    Products and Components with Known Issues

    The following products and components have known issues with the Microsoft Windows XP operating system.

    Reflection NFS Client

    Reflection NFS Client version 12.0 or higher has earned the Microsoft designed for Windows XP, Optimized status. Reflection NFS version 10.0 or higher can be installed on Windows XP.

    Reflection NFS Client versions 9.0 or earlier are incompatible with Windows XP. Attachmate strongly recommends that you do not attempt to install Reflection NFS Client versions 9.0 or earlier to Windows XP.

    Important: If you have Reflection NFS installed and are planning to upgrade existing workstations to Windows XP, you must first uninstall Reflection NFS Client (all versions). Not uninstalling NFS prior to upgrading may leave your workstation in an unstable state. Beginning in Reflection 14.1, NFS Client is no longer available. For details, see Technical Note 2495.

    Reflection TimeSync

    Windows XP’s built-in Windows Time Service uses the same TCP/IP port as the Reflection TimeSync component. Due to this conflict, use of Reflection TimeSync on Windows XP is not recommended. Attachmate Technical Support recommends using Windows Time Service instead of Reflection TimeSync on Windows XP. See the sections below for information about Reflection TimeSync in specific environments, and uninstalling Reflection TimeSync.

    Note: Beginning in version 14.1, TimeSync is no longer available. If you have TimeSync installed on your system, it will be removed when you upgrade to 14.1.

    Computers Upgraded to Windows XP

    If you install Reflection TimeSync to a Windows 2000 computer and then upgrade that computer to Windows XP, Reflection TimeSync will no longer function due to the port conflict.

    Reflection 10.x or Higher

    In version 10.x, Reflection TimeSync is not available for installation to Windows XP.

    Notice

    This technical note is provided for informational purposes only. ATTACHMATE CORPORATION makes no representation or warranty that the functions contained in our software products will meet your requirements or that the operation of our software products will be interruption or error free. ATTACHMATE CORPORATION EXPRESSLY DISCLAIMS ALL WARRANTIES REGARDING OUR SOFTWARE INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

    Related:

    • No Related Posts