About Local App Access for Xenapp 65 for Windows Server 2008 r2

Embed Size (px)

Citation preview

  • 8/12/2019 About Local App Access for Xenapp 65 for Windows Server 2008 r2

    1/2

    About Local App Access for XenApp 6.5 for Windows Server 2008 R2

    Known Issues

    This section contains:

    Installation Issues General Issues

    Installation Issues

    After upgrading a user device from a previous version of Citrix Receiver to the Seamless AppTechnology Client, an error might result when the user later attempts to launch applications

    from within a hosted desktop session. Afterward, the user cannot launch applications from

    the hosted desktop. This issue occurs when the Seamless App Technology client is installed

    using the auto-installer rather than the command line. To work around this issue, perform

    one of the following actions:

    After upgrading to the Seamless App Technology Client, on the user device, open theWindows Registry and add the subkey HKEY_CURRENT_USER\Software\Citrix\ICAClient\Engine\Lockdown Profiles\All Regions\Lockdown\Virtual

    Channels\Control\ClientHostedAppsShortcuts. For Value, enter an asterisk (*).

    Log on to the user device as an administrator, remove all instances of Citrix Receiver,and restart the device. Afterward, perform a fresh install of the Seamless App

    Technology Client from the command line, using the parameter

    ALLOW_CLIENTHOSTEDAPPSSHORTCUTS=1. For more information, refer to the

    section "Enabling Local App Access for Subscribers" in theIntegrating Local User

    Applications in XenApp 6.5guide. [#271089]

    General Issues

    When the icon for a locally installed application on the subscriber's computer is changed, theoriginal icon appears when the application is launched from a hosted desktop. [#159588]

    When a subscriber launches two hosted desktop sessions on the same user device, shortcutsto local applications in the Start and Programs menu disappear when the subscriber ends one

    of the hosted desktop sessions. This occurs because Local App Access supports only one

    hosted desktop session per user on the XenApp server. [#255935]

    When URL redirection is enabled, URLs that are not added to either the whitelist or blacklistmight not render on the XenApp server when launched from a hosted desktop session. If the

    user uses the Run command from within the hosted desktop to launch these URLs through

    Internet Explorer, the URLs are displayed in separate instances of Internet Explorer that is

    locally installed on the user device. [#261451]

    If the taskbar on the user device is in a different location from the taskbar on the hosteddesktop, the user device's taskbar might appear on top of the hosted desktop session when

    the user's mouse hovers nearby. However, if the user device's taskbar and hosted desktop's

    taskbar are in the same location (for example, both are near the bottom of the screen), the

    user device's taskbar remains hidden when the user's mouse hovers nearby. This issue occurs

    on user devices running Windows 7 only. [#274153]

  • 8/12/2019 About Local App Access for Xenapp 65 for Windows Server 2008 r2

    2/2

    Pinning shortcuts to locally-installed applications to the hosted desktop's taskbar or Startmenu might result in failed or incorrect application launches, or incorrect icon grouping. This

    occurs because Local App Access does not support pinning shortcuts to locally-installed

    applications to the hosted desktop's taskbar or Start menu. [#278595]

    If the Japanese character is included in the hosted desktop name, shortcut icons are notfully cached, resulting in incomplete shortcut enumeration when users log on to the sessionwith a user device running the Japanese version of Windows XP. Additionally, when the

    hosted desktop session is terminated, the Local Programs and Local Desktop folders remain

    on the XenApp server until the user who initiated the session has logged off. This issue does

    not affect administrators accessing hosted desktops whose names include this character. To

    resolve this issue for users, remove this character from the name of the hosted desktop.

    [#301408]