Environment Windows Server 2008 R2 Citrix XenApp 6.5 RU5

Issue Slow logon speeds into XenApp Published desktop/applications, hangs for a period of time on ‘Applying Folder Redirection Settings’

Resolution On the XenApp Servers, apply the following registry key HKLM\Software\Microsoft\Windows\CurrentVersion\Explorer FolderRedirectionWait (REG_DWORD) = 0

Further details – http://support.citrix.com/article/CTX133595/

Environment

HP T510 running ThinPro 4.4

Citrix XenApp 6.5 on Windows Server 2008 R2

Issue

Users were using HP Thin Clients and the device itself would display the following error in front of their Citrix XenApp published desktop:

“The X Request 2.0 caused  error: “6 : BadCursor (invalid Cursor parameter)”

Cause

Users would scroll through documents using the mouse wheel.

Resolution

1. Run ‘fsunlock’

2. browse to: /usr/lib/ICAClient/config/usertemplate/All_Regions.in

3. Locate [Virtual Channels\ZeroLatency]

4. Modify ZLMouseMode=* to ZLMouseMode=0

5. Save the file

6. Run ‘fslock’

Environment

Exchange 2010

Citrix NetScaler 10.x

Issue

Users creating a new email and clicking on To: to browse the Global Address List would receive an Exchange timeout error message.

Resolution

Create a new TCP Profile

GUI:

• System
• Profiles
• Add
• Name: RPC_Profile
• MSS: 1460
• Keep-Alive Probes – Enable
• Connection idle time before sending probe (secs) – 30
• Keep-alive probe interval (secs) – 20
• Everything else defaults

Bind this profile to the RPC Load Balanced VIP

• Traffic Management
• Load Balancing
• Virtual Servers
• <Exchange RPC LB VIP Name>
• Profiles > Add
• TCP Profile – Select RPC_Profile
• Ok
• Done

CLI:

add ns tcpProfile RPC_Profile_RPC -mss 1460 -KA ENABLED -KAconnIdleTime 30 -KAprobeInterval 20

add lb vserver <Exchange RPC LB VIP Name> TCP <IP_Address> * -persistenceType SOURCEIP -timeout 150 -cltTimeout 180 -tcpProfileName RPC_Profile

Environment:

• Windows Server 2008 R2 SP1
• Citrix XenApp 6.5 RU5

Issue:

Attempting to add a network printer the following error is displayed

• “Connect to Printer. Windows cannot connect to the printer. No printers were found”
• Operation failed with error 0x00000006

Resolution:

Microsoft’s resolution for this issue is to install KB2778831, however there are instance of this hotfix being applied and the issue still occurring.

Manual Fix:

1. Open Registry Editor
2. Browse to HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Providers
3. Back up then delete the Client Side Rendering Print Providers key
4. Restart the Printer Spooler service
5. Printers should now add successfully

Environment

• Windows Server 2008 R2
• Citrix XenApp 6.5

Resolution 

• 1.Log onto the RDS server and launch Remote Desktop Services Manager or connect via another server.
• 2.Get the Session ID of the hung session from the Session tab

1.  Session: Disconnected 
2. User: <Blank> 
3. ID: <number> 
4. State: Disconnected 
5. ClientName: <Blank> 
6. LogOnTime: Unknown 

• 3.Click on Processes tab
• 4.Click on ID column to sort the processes by ID
• 5.Find the hung ID number
• 6.There is normally 3 processes visible
  1.LogonUI.exe
  2.Winlogon.exe
  3.Csrss.exe
• 7.Right-click on winlogon.exe and End Process, once you end this process the other 2 will disappear.
• 8.DO NOT end process on csrss.exe, this will crash and reboot the RDS server
• 9.Now the user has cleared from the RDS server and from AppCenter.

Environment

• Windows Server 2008 R2
• Citrix XenApp 6.5 RU5

Issue

During users logon to XenApp published applications and published desktops there can be a lengthy delay on “Please wait for the User Profile Services”, it can hang on this for up to 30 secs.

Solution

In the Group Policy Management browse to:

• Computer Configuration
  • Administrative Templates
    • System
      • User Profiles

Modify the policy setting “Set maximum wait time for the network if a user has a roaming user profile or remote home directory” to “Enabled” and set the value Wait for network for maximum (seconds) to 0.

Environment:

• Citrix NetScaler SDX appliances
• Citrix Command Centre 5.x (and think it occurs in version 4.x also) on Windows Server 2008 R2

Issue:

While running a NetScaler SDX discovery in Command Centre the discovery fails with the following error message:

“Unknown device ; <sdx_ip_address> ; not supported by command center”

(The discovery of the NetScaler VPX instances discovered fine independently)

– Checked discovery logs and found the below error:

Troubleshooting Steps:

– Checked from the Command Centre server and was able to ping and SSH to SDX Management IP with same credentials used in the Command Centre NetScaler SDX profile.
– In the C:\Program Files (x86)\Citrix\Citrix Command Center\logs\discoveryLogs.txt log file, I could see it was trying to add the NetScaler SDX as “CBSDX” (CloudBridge SDX I assume).

• INVENTORYERR: Device not recognized as CBSDX. SYSID null <sdx_ip_address>
• INVENTORYERR: Exception while login to =<sdx_ip_address>
• Localized : English : nsroot failed to login

Resolution:

Within Command Centre,

• On the Administration tab,
• Under Settings,
• Click SSL Settings and then
• Select the Enable TLSv1 option
• Restart the Command Centre service.

NOTE: After restarting the Command Centre service and its running again, it can take a while before your able to log in again.

Check the service status in the C:\Program Files (x86)\Citrix\Citrix Command Center\logs\wrapper.log file

INFO | jvm 1 | 2016/05/23 14:47:00 | Starting up as Primary Server and correcting the Server information in the Database.
INFO | jvm 1 | 2016/05/23 14:47:00 |
INFO | jvm 1 | 2016/05/23 14:47:01 |
INFO | jvm 1 | 2016/05/23 14:47:01 | Starting Citrix Command Center “Primary” Server Modules, please wait
INFO | jvm 1 | 2016/05/23 14:47:15 |
INFO | jvm 1 | 2016/05/23 14:47:15 |
INFO | jvm 1 | 2016/05/23 14:47:15 |
INFO | jvm 1 | 2016/05/23 14:47:15 | Process : SyslogServerBE [ Started ]
INFO | jvm 1 | 2016/05/23 14:47:16 | Process : ProcessTest [ Started ]
INFO | jvm 1 | 2016/05/23 14:47:17 | Process : ShutdownDatabaseServer [ Started ]
INFO | jvm 1 | 2016/05/23 14:47:19 | Process : CLIRMIService [ Started ]

If you see a lot of [Failed] statues, restart the Command Centre server.

Issue:

When attempting to remediate an ESXi host with 6.0 Update 2, the following error displays in Update Manager:

“The host returns esxupdate error code:14. There is an error when resolving dependencies. Check the Update Manager log files and esxupdate log files for more details.”

In /var/log/esxupdate.log

esxupdate: ERROR: DependencyError: VIB VMware_bootbank_vsanhealth_6.0.0-3000000.3.0.2.43.4064824 requires esx-base >= 6.0.0-2.43, but the requirement cannot be satisfied within the ImageProfile.

Solution:

There is a dependency for Update 2 that needs installing first,  weirdly enough the dependency is included in Update 2.

Resolution:

• Enable ESXi Shell and SSH on ESXi host
• Download Update 2 from VMware Patches
• Copy zip file to /vmfs/volumes/datastore (file is too large to copy to /var/tmp)
• Use Putty to connect to ESXi host
• Run: esxcli software vib install -n esx-base -n vsan -n vsanhealth -d /vmfs/volumes/datastore1/update-from-esxi6.0 6.0_update02.zip

-n = Specifies VIBs from a depot, using one of the following forms: name, name:version, vendor:name, or vendor:name:version.

-d = Specifies full remote URLs of the depot index.xml or server file path pointing to an offline bundle .zip file.

• Reboot the ESXi host.
• To confirm the components installed correctly run: esxcli software vib list
• These are the dependencies and versions installed:

• Once the server is back online now use Update Manager to remediate Update 2 (and any additional patches) onto ESXi host.

Environment

VMware vCenter 6.0.0 Build 4541948 (Update 2a) – could effect other vCenter versions also.

Issue:

After a period of a week or more the vCenter Web Console slows down dramatically to the point where the website doesn’t load anymore and the browser times out.

Looking into the /var/log/vmware/vsphere-client/logs/vsphere-client-virgo.log file you it displays the following Out Of Memory error:

Run: less vsphere-client-virgo.log

“[2017-03-15T13:59:07.853+13:00] [ERROR] ing.timer.TimerFactoryBean#0 o.s.scheduling.timer.MethodInvokingTimerTaskFactoryBean Invocation of method ‘update’ on target class [class com.vmware.vise.vim.cm.healthstatus. HealthStatusUpdater] failed java.lang.OutOfMemoryError: PermGen space”

Solution:

1. (Workaround) Reboot the vCenter, according to VMware Support you should reboot it often to ensure the vCenter doesn’t run out of memory.
2. (Permanent fix) Increase the memory size for vspherewebclientsvc in the service-layout.mfx file from 256 to 512.
   1. Use WinSCP to connect to vCenter Server
   2. Browse to and edit: /etc/vmware/service-layout.mfx
   3. Find the line with the firstboot_name ngc_firstboot
   4. Under the column ‘MaxPermMB’ change the value from 256 to 512
   5. Save service-layout.mfx file
   6. SSH to vCenter Server
   7. Run: /etc/init.d/service vsphere-client restart

We are currently using an on house written app that allows users to add/remove/set as printer their network printers.

Our users like this custom tool because its so simple to navigate around but going into our new XenApp 7.15 environment on Windows Server 2016 OS this tool doesn’t work.

In this new environment we are going to implement Citrix Workspace Environment Management (WEM) and I noticed it comes with the ‘Manage Printers’ function as part of the WEM agent deployed to the XenApp Member servers, this tool is very good but its semi hidden away and takes a couple of clicks to find it where our users were used to having a desktop printer icon to get to the custom app.

I decided to see if the WEM ‘Manage Printers’ function can be made into a desktop icon, the details to turn this into an application are:

• Command Line: C:\Program Files (x86)\Norskale\Norskale Agent Host\PrnsMgmtUtil.exe
• Working Directory: C:\Program Files (x86)\Norskale\Norskale Agent Host
• Icon File: C:\Windows\System32\shell32.dll
• Icon Index: 16
• Display Name: Printer Management
• Action Type: Create Application Shortcut

Dont forget to ‘assign’ the new application in Action Assignment.

Environment:

• Windows Server 2016
• Citrix XenApp 7.15
• Citrix XenApp Self-Service Password Reset 1.1.0.15097

Issue:

Creating a new ‘User Configuration’ in the ‘Enable Self-Service Password Reset’ section

• The Service Address returns and error “Cannot access your service address!”.

• Browsing to https://fqdn/MPMService returns “Error 403 – Forbidden: Access is denied”
• Event Viewer has the following:

Resolution:

Either:

1. Disable the Internet Explorer proxy server, if possible
2. Enable ‘Bypass proxy server for local addresses’
3. Create a proxy server exception

Issue:

Scanning for new thin clients discovers the available thin clients, select ‘Include’ to bring the device into Universal Management Suite (UMS).

During the inclusion process it fails with the error “ERROR: Cannot connect to remote management server”.

Reason:

Communication between UMS server and thin client requires port 30001 to be open on the server running IGEL UMS. This is visible in the Windows Firewall log file (C:\Windows\System32\LogFiles\Firewall\pfirewall.log) if ‘Log dropped packets’ is enabled.

Solution:

• Allow the following ports on the Windows Firewall
  • 30001, 30005 (For further information refer to: http://edocs.igel.com/#10202276.htm)
• Disable Windows Firewall

IGEL have some great Profile templates available from their website which are a great starting point for ideas on what can be done within the IGEL OS.

Once the file has been downloaded, unzip it.

Within Universal Management Suite browse to:

System > Import > Import Profiles and browse to .\UMSDemonstration\Template via Import, then select the relevant IGEL OS

Once the templates have been imported it will look similar to this:

I was asked recently about creating a locked down Kiosk Browser Session in the IGEL Operating System. Below is the standard configuration I’d do when creating such a Profile. I will continue to update this post with any new information that might be relevant.

Create a Kiosk Browser Session

1. Create a new Profile, and give it a meaningful name.
2. Navigate to: Sessions > Browser > Browser Sessions
3. Select Add in the right hand window
4. Give a Session Name

Browser Session Options

Set Browser Home Page

1. Navigate to: Sessions > Browser > Browser Sessions > {Session Name} > Settings
2. Change ‘When browser starts’ to ‘Show my home page’
3. Enter ‘Home Page’ address for the browser to open with

Enable Browser Session AutoStart

Navigate to: Sessions > Browser > Browser Sessions > {Session Name}

To ensure the browser launches when the desktop has loaded you need to enable ‘AutoStart’. Along with this setting enable ‘Restart’, Restart means the browser will automatically relaunch if it is closed. Enabling ‘AutoStart Delay’ with a value (in seconds) is the time between the desktop loading and the browser automatically launching.

Set Browser to Full Screen

Navigate to: Sessions > Browser > Browser Sessions > {Session Name} > Window

To make the browser launch in full screen enable ‘Start in fullscreen mode’. While you here enable ‘Hide local filesystem’. Setting this will hide the local file system when you attempt to save files. ‘Hide configuration page of the browser’ will already be enabled.

Customizing the Menu & Toolbars

Navigate to: Sessions > Browser > Browser Sessions > {Session Name} > Menus & Toolbars

• Enable ‘Hide App Menu/Menu Bar‘
  • This removes the App Menu to the right hand side of the browser
• Enable ‘Hide Search input‘
  • This removes the search input from the browser
• Enable ‘Hide URL Input‘
  • This removes the URL input from the browser

• Enable ‘Hide Tabs Toolbar‘
  • This removes the tabs from the top of the browser and also the ability to launch new tabs

• Disable Browser Context Menu

Navigate to: Sessions > Browser > Browser Sessions > {Session Name} > Context

• Enable ‘Hide the browser’s context menu’
  • This completely removes the browser context menu (but not the Tab Context Menu) including:
    • Save Page As button
    • View Page Source / Info

After applying the latest firmware to devices, I was looking at changing to the latest Citrix Receiver included in that firmware but the existing profile I was using didn’t show the latest Receiver, v13.7.0 was missing.

I had to change Profile ‘Based On’ to the newer firmware and SAVE, important to save the firmware change (and UMS won’t prompt to be saved either) or it still won’t commit the change.

After making this change above, the profile can be edited and you now can see the latest Receiver version.

For a while I have been putting my common IGEL profiles into a GitHub repository, feel free to download them for your own use, contact me know if you want to upload any of your own to assist the @IGELCommunity !

https://github.com/carlbehrent/igelprofiles

Workspace Environment Manager has a cool little feature for end users to use called ‘Capture Screen’, it can be accessed by right clicking on the WEM Agent in the System Tray.

This utility captures the users screen and lets them either Save the image or send it straight to a pre-configured email address (Service Desk etc). Enable Screen Capture in the WEM Administration Console under:

Advanced Settings > UI Agent Personalization > Helpdesk Options

By default the Comments field is greyed out on the end point and needs to be enabled within the WEM Administration Console.

To enable the Comments field you need to put the WEM variable “##UserScreenCaptureComment##” (without quotes) anywhere in the ‘Email Template’ field as below.

After putting in the variable, apply the settings in the WEM Administration Console and then refresh the WEM Agent on the end point. Now when selecting Capture Screen the Comments field is enabled for user input.

You can use a combination of variables through the Custom Subject and Email Template as below, remembering that ##UserScreenCaptureComment## needs to be somewhere in the Email Template.

User Comment:    ##UserScreenCaptureComment##
User Name:           ##UserName##
Display Name:      ##FullUserName##
XenApp Server:   ##ComputerName##
RDS Session ID:   ##RDSSessionID##
Client Name:       ##ClientName##

Refer here for possible variables to use: https://docs.citrix.com/en-us/workspace-environment-management/current-release/reference/dynamic-tokens.html

Issue

When doing either a scripted upgrade of Citrix Receiver to v4.10.x from v4.x the installation fails.

A manual upgrade works as expected.

Upgrade Script example

.\CitrixReceiver.exe /noreboot /silent /includeSSON /ENABLE_SSON=Yes /EnableCEIP=false

TrolleyExpress.log file
C:\Users\<install user>\AppData\Local\Temp\CTXReceiverInstallLogs-20180524-160141\TrolleyExpress-20180524-160141

shows something similar to the following:

Error - CComponentManager::GetInstallStatus(598) - Installation NOT successful for 'XenApp Web Plugin', error: 1603.
Information - CComponentManager::GetInstallStatus(603) - Installation NOT successful for 'Citrix Receiver (DV)', it never fully tried to install, possibly due to issues.
Information - CComponentManager::GetInstallStatus(603) - Installation NOT successful for 'HDX Flash', it never fully tried to install, possibly due to issues.
Information - CComponentManager::GetInstallStatus(603) - Installation NOT successful for 'HDX Aero', it never fully tried to install, possibly due to issues.
Information - CComponentManager::GetInstallStatus(603) - Installation NOT successful for 'Authentication Manager', it never fully tried to install, possibly due to issues.
Information - CComponentManager::GetInstallStatus(603) - Installation NOT successful for 'Self Service Plug-in', it never fully tried to install, possibly due to issues.
Information - CComponentManager::GetInstallStatus(603) - Installation NOT successful for 'WebHelper', it never fully tried to install, possibly due to issues.
Information - CComponentManager::GetInstallStatus(645) - Created entry for RTME Plugin for reinstalling it if it was installed previously
Information - CComponentManager::GetInstallStatus(692) - Need to repaire plugin with UpgradeCode = {9FAB00CA-B032-4E4E-8D0C-E3B35802335D}
Information - CtxInstallHelpers::CInstalledClientPkg::FindInstalledClient(154) - No existing clients found with given upgrade code: {9FAB00CA-B032-4E4E-8D0C-E3B35802335D}
Information - CComponentManager::GetInstallStatus(704) - Repairs Receiver plugin with Product code = 
Information - CComponentManager::GetInstallStatus(713) - No Plugin found with UpgradeCode = {9FAB00CA-B032-4E4E-8D0C-E3B35802335D}
Information - CApp::SetExitCode(120) - Exit code is 1602 (called with 1603)
Information - CApp::Remove_Reg_Uninstall(1641) - CApp::Remove_Reg_Uninstall
Information - CApp::ExitInstance(1335) - Exit Code = 1602

“No Plugin found with UpgradeCode = {9FAB00CA-B032-4E4E-8D0C-E3B35802335D}”

Solution

• None currently, it’s a known issue with Citrix for upgrading to v4.10.x and 4.11.x, it’s meant to be resolved in v4.12.x.
• New installs and manual upgrades work as expected
• Upgrading to v4.9.x LTSR and earlier works as expected.

Issue

Attempting to install an .msp file (in my case Citrix XenApp 6.5 RollUp7) it fails to install with the following error message.

Error Message

Troubleshooting Steps

1. Run the msp with the verbose logging switch for example:

.\XA650W2K8R2X64R07.msp /L*v C:\Temp\RollUp7.log

2. Have a look in the C:\Temp\RollUp7.log file and you’re looking for the highlighted in red below “C:\Windows\Installer\d5c63.msi

Log File:

=== Verbose logging started: 30/05/2018 8:17:04 Build type: SHIP UNICODE 5.00.7601.00 Calling process: C:\windows\System32\msiexec.exe ===
MSI (c) (EC:F0) [08:17:04:901]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

MSI (c) (EC:F0) [08:17:04:901]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

MSI (c) (EC:10) [08:17:04:917]: Resetting cached policy values
MSI (c) (EC:10) [08:17:04:917]: Machine policy value 'Debug' is 0
MSI (c) (EC:10) [08:17:04:917]: ******* RunEngine:
 ******* Product: {1471A89F-8CAB-4C46-89AB-942432D1DD3D}
 ******* Action: 
 ******* CommandLine: **********
MSI (c) (EC:10) [08:17:04:917]: Machine policy value 'DisableUserInstalls' is 0
MSI (c) (EC:10) [08:17:05:057]: Cloaking enabled.
MSI (c) (EC:10) [08:17:05:057]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (EC:10) [08:17:05:151]: End dialog not enabled
MSI (c) (EC:10) [08:17:05:151]: Original package ==> C:\windows\Installer\d5c63.msi
MSI (c) (EC:10) [08:17:05:151]: Package we're running from ==> C:\windows\Installer\d5c63.msi
MSI (c) (EC:10) [08:17:05:166]: Note: 1: 2276 2: 3: 75 
DEBUG: Error 2276: Database: . Codepage 75 not supported by the system.
1: 2276 2: 3: 75 
This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.
C:\windows\Installer\d5c63.msi
MSI (c) (EC:10) [08:17:05:213]: Note: 1: 1708 
MSI (c) (EC:10) [08:17:05:213]: Product: -- Installation failed.

MSI (c) (EC:10) [08:17:05:213]: Windows Installer installed the product. Product Name: . Product Version: . Product Language: . Manufacturer: . Installation success or error status: 1620.

MSI (c) (EC:10) [08:17:05:213]: MainEngineThread is returning 1620
=== Verbose logging stopped: 30/05/2018 8:17:05 ===

3.  Browse to C:\Windows\Installer\ folder (hidden protected OS folder) and rename the .msi to .old mentioned in the log file.

4. Re-run the .msp install

5. This time it will prompt for the original msi files, in my case it was the mps.msi

6. Browse to the original msi file where it may be and now the .msp file will install normally.

Fellow Citrix CTA René Bigler highlighted an issue in the IGEL Community Slack channel that when using Storefront enabled for ‘Use Receiver for HTML5 if local Recevier is unavailable’ it would automatically default to HTML5 and fail to launch the app/desktop.

I did further testing to isolate exactly where the issue might lie. Here’s my testing and results carried out.

Environment
-Citrix XenApp 7.15 CU2
-Storefront 3.15 and 3.16
-IGEL OS 10.05.100
-Citrix Receiver 13.9.1 and 13.10.0

Test #1
-Storefront 3.15, Receiver Deployment Option: Install locally
-IGEL OS 10.05.100
-Citrix Receiver 13.9.1

Result: Logged into Storefront browser, launched XenApp desktop successfully using native Receiver

Test #2
-Storefront 3.15, Receiver Deployment Option: Install locally
-IGEL OS 10.05.100
-Citrix Receiver 13.10.1

Result: Logged into Storefront browser, launched XenApp desktop successfully using native Receiver

Test #3
-Storefront 3.15, Receiver Deployment Option: Use Receiver for HTML5 if local Recevier is unavailable.
-IGEL OS 10.05.100
-Citrix Receiver 13.9.1

Result: Logged into Storefront browser, launched XenApp desktop successfully using native Receiver

Test #4
-Storefront 3.15, Receiver Deployment Option: Use Receiver for HTML5 if local Recevier is unavailable.
-IGEL OS 10.05.100
-Citrix Receiver 13.10.1

Result: Logged into Storefront browser, launched XenApp desktop successfully using native Receiver

Test #5
-Storefront 3.16, Receiver Deployment Option: Install locally
-IGEL OS 10.05.100
-Citrix Receiver 13.9.1

Result: Logged into Storefront browser, launched XenApp desktop successfully using native Receiver

Test #6
-Storefront 3.16, Receiver Deployment Option: Install locally
-IGEL OS 10.05.100
-Citrix Receiver 13.10.1

Result: Logged into Storefront browser, launched XenApp desktop successfully using native Receiver

Test #7
-Storefront 3.16, Receiver Deployment Option: Use Receiver for HTML5 if local Recevier is unavailable
-IGEL OS 10.05.100
-Citrix Receiver 13.9.1

Result: Logged into Storefront browser, launched XenApp desktop, attempted to use HTML5 and failed

Test #8
-Storefront 3.16, Receiver Deployment Option: Use Receiver for HTML5 if local Recevier is unavailable
-IGEL OS 10.05.100
-Citrix Receiver 13.10.1

Result: Logged into Storefront browser, launched XenApp desktop, attempted to use HTML5 and failed

Issue

Issue appears to be with any Receiver for Linux version running on Storefront 3.16 (1808)

Workaround

If you are running Storefront 3.16 (1808) and the Receiver for Linux, ensure you have ‘Install Locally’ set rather than ‘Use Receiver for HTML5 if local Recevier is unavailable’ then your XenApp desktops/apps will launch.