'Unexpected Error, Contact Citrix Support Error ID: XDDS:DFB94D9B' – Unable to Update Machine Catalogs -Citrix Cloud

In Citrix Cloud, after updating an image, users are unable to update the machines. Users get a popup noting ‘Unexpected Error, Contact Citrix Support’. The error details note Error ID: XDDS:DFB94D9B.

  • Azure Hosting Connection
  • Test Connection test failed
  • No App Registration in Azure related to Citrix App

Related:

  • No Related Posts

Supported Databases for Virtual Apps and Desktops (XenApp & XenDesktop) AND Provisioning (Provisioning Services)

Citrix is committed to ensuring that our products function with the latest Microsoft SQL databases. Citrix supplies reasonable efforts to ensure compatibility with upcoming database releases. New versions of supported databases released after our products have been released, must work. However, Citrix recommends creating a test environment to ensure there are no unforeseen issues related to changes made to the new version or update of the third-party product. Individuals wishing to use the new release with current Citrix products must perform their own testing before using the platform. Citrix does not support any BETA versions of third-party products.

Note:

  • This document will be updated periodically as new information becomes available.
  • The Cumulative Updates for SQL versions are not called out explicitly. They are an extension of the product and supported.

What has changed from the last release of the matrix

  • Updated support for Virtual Apps and Desktops 7 1912 LTSR
Supported Databases Virtual Apps and Desktops (XenApp/XenDesktop) 7.15 LTSR / 1909 / 1912 LTSR XenApp/XenDesktop 7.6 LTSR Provisioning Services 7.15 LTSR / 1909 / 1912 LTSR Provisioning Services 7.6 LTSR XenApp 6.5 HRP07
SQL 2017
x64 Yes Yes Yes (1) Yes (1) Yes
Express Yes Yes Yes (1) Yes (1) Yes
SQL 2016 SP1, SP2
x64 Yes Yes Yes (1) Yes (1) Yes
Express Yes Yes Yes (1) Yes (1) Yes
SQL 2014 SP1, SP2, SP3
x86 Yes Yes Yes (1) Yes (1) Yes
x64 Yes Yes Yes (1) Yes (1) Yes
Express Yes Yes Yes Yes Yes
SQL 2012 SP1, SP2, SP3, SP4
x86 Yes Yes Yes (1) Yes (1) Yes
x64 Yes Yes Yes (1) Yes (1) Yes
Express Yes Yes Yes Yes Yes
SQL 2012
x86 Yes Yes Yes (1) Yes (1) Yes
x64 Yes Yes Yes (1) Yes (1) Yes
Express Yes (2) Yes (2) Yes Yes Yes
SQL 2008 R2 SP2, SP3
x86 Yes Yes Yes Yes Yes
x64 Yes Yes Yes Yes Yes
Express Yes Yes Yes Yes Yes

  1. PVS 7.7 onwards Always ON is supported. PVS 7.11 introduced Multi-subnet Failover
  2. Known issue using SQL 2012 and above with XenDesktop, Refer to article ‘CTX132438 – Unable to Create New XenDesktop Site Using SQL 2012 Server’

Note:

  • The x86 and x64 versions of SQL (version 2012 and later) have been validated with Always On, Clustered, Standalone and Mirrored modes.
  • The Express edition has been validated only as Standalone.

Related:

  • No Related Posts

Installation of Citrix Receiver LTSR may fail with the MUI message: 'Multilingual User Interface Language pack has stopped working'.

For all the LTSR Citrix Receiver stops and MUI pops up a message: “Multilingual User Interface Language pack has stopped working” and do not continue the installation.


Inspecting the CTXReceiverInstallLogs-yyymmdd-hhmmss, the installation ends suddenly during TrolleyExpress-yyymmdd-hhmmss.log

Below is a snip from the same machine that fails with .NET 3.5 enabled on the left and succeeds with .NET 3.5 disabled on the right. The stage ‘Collect environment info succeeded’ is not reached in the example on the left.


NOTE WELL: in other machines with healthy .NET 3.5 Framework enabled, Receiver installation is successful.

Related:

  • No Related Posts

Error: “The licenses required by this edition of Citrix XenApp are not present on the license server”

Users are unable to access the applications, and the error “An error occurred while making the requested connection” is provided.

The event viewer displays the following error, which indicates a licensing issue:

Source: MetaFrame

EventID: 9014

Description: The licenses required by this edition of Citrix Presentation Server are not present on the license server LicenseServerName.

XenApp 6.5 introduces a new feature to server role called License Model, which is found in the XenApp Server Role Manager console under license configuration. You can choose from the following three types of models:

  • XenApp

  • XenDesktop concurrent system

  • XenDesktop user/device

Note: The setting to modify the License model is also possible by modifying the policies.

Related:

  • No Related Posts

CVE-2014-4700 – Vulnerability in Citrix XenDesktop could result in unauthorized access to another user’s desktop

Description of Problem

A vulnerability has been identified in Citrix XenDesktop that could result in a user gaining unauthorized interactive access to another user’s desktop.

This vulnerability affects a specific, non-default configuration of Citrix XenDesktop 7 (all versions up to and including 7.5), Citrix XenDesktop 5 (up to and including Rollup 5.6.300 for Citrix XenDesktop 5.6 FP1) and Citrix XenDesktop 4 (all versions).

This vulnerability only affects Citrix XenDesktop deployments that use pooled random desktop groups and where the broker configuration setting ShutdownDesktopsAfterUse is set to disabled. Configurations that only use assigned desktop groups, including RemotePC access scenarios and user-dedicated desktops, are not affected by this issue.

This vulnerability has been assigned the following CVE number:

    • CVE-2014-4700: Vulnerability in Citrix XenDesktop versions 7.x, 5.x and 4.x could result in unauthorized access to another user’s desktop.

Mitigating Factors

The configuration setting ShutdownDesktopsAfterUse is enabled by default in configurations that use pooled desktops groups to reset the disk image and clean the desktop. For more details, please see the following Citrix Knowledgebase article:

https://support.citrix.com/article/CTX127842

What Customers Should Do

Updates to Citrix XenDesktop have been released to address this issue. Citrix strongly recommends that affected customers apply these updates as soon as possible.

The hotfixes for Citrix XenDesktop 7.1 and 7.5 can be downloaded from the following locations:

CTX140362 – Hotfix XD710ICAWSWX86005 – For VDA Core Services 7.1/7.5 for Windows Desktop OS (32-bit) – English

CTX140363 – Hotfix XD710ICAWSWX64005 – For VDA Core Services 7.1/7.5 for Windows Desktop OS (64-bit) – English

A VDA Rollup for Citrix XenDesktop 5.6 FP1 can be downloaded from the following location:

CTX138550 – Hotfix Rollup XD560VDAWX86400 (Version 5.6.400) – For Citrix XenDesktop Virtual Desktop Agent Core Services x86 – English

CTX138551 – Hotfix Rollup XD560VDAWX64400 (Version 5.6.400) – For Citrix XenDesktop Virtual Desktop Agent Core Services x64 – English

What Citrix Is Doing

Citrix is notifying customers and channel partners about this potential security issue. This article is also available from the Citrix Knowledge Center at http://support.citrix.com/.

Obtaining Support on This Issue

If you require technical assistance with this issue, please contact Citrix Technical Support. Contact details for Citrix Technical Support are available at http://www.citrix.com/site/ss/supportContacts.asp.

Reporting Security Vulnerabilities to Citrix

Citrix welcomes input regarding the security of its products and considers any and all potential vulnerabilities seriously. For guidance on how to report security-related issues to Citrix, please see the following document: CTX081743 – Reporting Security Issues to Citrix

Related:

  • No Related Posts

How to Configure Multiple License Types within a Single XenApp and XenDesktop Site

NOTE:

  • This feature does not allow you to use a mix of licenses for different Product Editions. For example, you can’t combine XenApp Platinum and XenApp Advanced licenses in the same site. You’d still need two sites for that.
  • Choice of Product Code and Edition combination can depend on the features you want to enable for your deployment’s sessions. There are some differences between XenApp and XenDesktop enabled features for the same Product Edition.
  • Changes to the Site licensing type could invalidate your custom licensing Delivery Group due to XenApp User/Device not being an accepted combination

Reference:

https://www.citrix.com/blogs/2017/07/07/introducing-multi-type-licensing-in-xenapp-xendesktop-7-14/

https://docs.citrix.com/en-us/xenapp-and-xendesktop/7-15-ltsr/manage-deployment/licensing/multi-type-licensing.html

https://www.citrix.com/products/citrix-virtual-apps-and-desktops/feature-matrix.html%20to

Related:

  • No Related Posts

Citrix Workspace App (CWA) for Linux – ICA File Not Launching Automatically

If there is a mixed environment of Linux endpoints connecting to a particular store, i.e some endpoints have Citrix Workspace App installed and some do not have Citrix Workspace app installed then please refer to the following steps:

This will allow the users launching their desktop/app either using Receiver for HTML5 or Workspace app/Receiver for Linux.

Note: Step a) Administrator Configuration, is required only for storefront version lower than 1906.

a) Administrator configuration

  1. In DDC, launch Citrix Studio > Click Stores under Citrix StoreFront in the left pane > Manage Receiver for WebSites (in Right panel) > configure > Deploy Citrix Receiver – give the deployment option as “Use Receiver for HTML5 if local receiver is unavailable

    User-added image

  2. Open the file “web.config” in the path – C:inetpubwwwrootCitrixStoreWeb

    Add “Linux” to protocolHandler element as shown below:

    User-added image

    Note: this is required only for DDC version lower than 1906. For 1906 and above no modification in web.config needed

​b) User configuration

  1. When you access storefront from Firefox, on the first page select “Detect Receiver”

    User-added image

  2. For those users that have Receiver installed Select “Already Installed” and go ahead with the next steps.

    For those users who do not have Workspace App or Receiver for Linux installed and wants to go ahead with HTML5 receiver select “Use light version

    User-added image

  3. If the user has selected “Already Installed”: Follow “Always open ICA files” as mentioned above. From now on whenever we click on a desktop/app enumeration, it launches automatically with wfica, thus enabling a smooth seamless user-experience with launch of virtual applications and desktops.

Related:

  • No Related Posts

How to Manually Install and Configure Citrix Receiver for Pass-Through Authentication

Single Sign-on authentication can be configured on both new and upgraded setup.

Configuring Single Sign-on on a new Citrix Receiver for Windows setup
Configuring Single Sign-on on an upgraded Citrix Receiver for Windows setup
Single Sign-on Troubleshooting and Diagnostics
More How Do I

To configure Single Sign-on on a new setup:

  1. Enable Domain pass-through and optionally User name and password authentication on StoreFront or the Web Interface.

  2. Configure XML trust services on the Delivery Controller.

  3. Modify Internet Explorer settings and Install Citrix Receiver for Windows with Single Sign-on.

1. Enable User name and password and Domain pass-through on StoreFront or the Web Interface

Depending on the XenApp/XenDesktop deployment, Single Sign-on authentication can be configured on StoreFront or the Web Interface using the Management Console.

  • StoreFront server: Launch StoreFront Studio, go to Store > Manage Authentication methods > enable Domain pass-through.

Note: Single Sign-on is not supported if Citrix Receiver for Windows is connected to XenApp/XenDesktop using NetScaler Gateway.

Scenario Steps Description
Configured on StoreFront or the Web Interface with Management Console StoreFront server: Launch StoreFront Studio, go to Store > Manage Authentication methods > enable Domain pass-through. When Citrix Receiver for Windows is not configured with Single Sign-on, it automatically switches the authentication method from Domain pass-through to Username and Password, if available.
Receiver for Web IS Required Launch Stores > Receiver for Websites > Manage Authentication methods > enable Domain pass-through.

User-added image

When Citrix Receiver for Web is not configured to allow Domain pass-through, it automatically switches the authentication method to Username and Password, if available.

If you are launching published applications using web browsers for Storeweb, enable the Single Sign-on feature as described in the sectionGroup Policy Settings.

StoreFront IS NOT configured If Web Interface is configured on a XenApp server, open XenApp Services Sites > Authentication Methods > enable Pass-through.

User-added image

When Citrix Receiver for Windows is not configured with Single Sign-on, it automatically switches the authentication method from Pass-through to Explicit, if available.

2. Configure XML trust services on the Delivery Controller

On XenDesktop 7 or later or XenApp 7.5 or later, run the following PowerShell command as an administrator on the Delivery Controller:

asnp Citrix*

Set-BrokerSite -TrustRequestsSentToTheXmlServicePort $True

Refer to the Knowledge Center article: Error: “An error occurred while making the requested connection“.

Note: On XenApp 6.5, XML Service Port and Trust is enabled using the Graphical User Interface. For more information, see Configuring the Citrix XML Service Port and Trust.

3. Modify Web Browsers settings and Install Citrix Receiver for Windows with Single Sign-on

3.1 Modify the web browsers settings

3.1.1 Configuring IE, Chrome, Edge browsers and Citrix Workspace for Windows for Single Sign-on

Modify the Internet Explorer settings to add StoreFront URL or Web Interface URL to the list of Security Zones in Internet Options. There are two methods to modify Security Zones:

NOTE: At any time, use only one of the following methods.

Option 1
  1. Local Intranet: Open Internet Explorer > Internet Options > Security > Local Intranet, Click Sites. The Local intranet window appears.
  2. Click Advanced.
  3. Add the URL of the StoreFront or Web Interface FQDN with appropriate http or https protocol.
Option 2
  1. Trusted Sites: Open Internet Explorer > Tools > Internet Options > Security >Trusted Sites > Sites
  2. Add StoreFront or Web Interface FQDN with appropriate http or https protocol.
  3. In the Internet Options > Security tab, select Trusted Sites.
  4. Click Custom level. The Security Settings – Trusted Sites Zone window appears.
  5. From the User Authentication options, select Automatic logon with current user name and password.

User-added image
Note: Automatic logon with current user name and password can be configured using Group Policy. For more details, see Managing Browser Settings with Group Policy Tools.

3.1.2 Configuring Firefox for Single Sign-on

  • Open Firefox
  • Type about:config in the address bar
  • A security warning page will appear. To continue, click “I accept the risk!”

  • List of configurations will be available. In the search bar type “network.automatic-ntlm-auth.trusted-uris” and add the store URL to that configuration

3.2 Install Citrix Receiver for Windows

  1. Download Citrix Receiver for Windows (CitrixReceiver.exe) from Citrix Downloads.
  2. Log onto the client device with administrator privilege.
  3. You can install Citrix Receiver for Windows in two ways:
    Using the Graphical User Interface Using the Command Line Interface
    1. Double-click CitrixReceiver.exe.
    2. In the Citrix Receiver Installation wizard, select Enable Single Sign-on.User-added image
    3. Click Next.
    4. After the installation is complete, log off from the client device and log on again.
    1. Open a command prompt as an administrator and change to the directory to where CitrixReceiver.exe is located.
    2. Run the following command to install Citrix Receiver for Windows with the Single Sign-on feature enabled:

      CitrixReceiver.exe /includeSSON /silent
  4. After the installation is complete, log off from the client machine and log on again.
  5. Launch the Task Manager to verify that the ssonsvr.exe process is running.

User-added image

Users should now be able to log on to an existing Store (or configure a new Store) using Citrix Receiver for Windows without providing credentials.

Group policy settings

Configuration described in this section is required in two cases:

• When access to StoreWeb using web browsers is required.

• Citrix Receiver for Windows version 4.3 or earlier is used.

For newer versions of Receiver (4.4 onwards) that do not require SSON via web browsers, the configuration is optional

Using Citrix Receiver for Windows Group Policy template files

• Add Citrix Receiver for Windows template files to the Local Group Policy Editor. For more information, see Configure Receiver with the Group Policy Object template . Be sure to use the ADM template of the same version as the Receiver on the Client.

Follow the below steps to configure the policy

1. Open Local Group Policy Editor. Navigate to Citrix Receiver > User authentication.

2. Open the Local user name password policy.

3. Select Enable pass-through authentication.


4. Click Apply and OK.

Note: If the existing version of Citrix Receiver for Windows does not have the Single Sign-on component installed, upgrading to the latest version with the /includeSSON switch is not supported.

After the installation is complete, log off from the client device and log on again.

Single Sign-on Diagnostics

In Citrix Receiver for Windows Version 4.5, you can use Configuration Checker to diagnose the Single Sign-on configuration.

  1. Right-click the Citrix Receiver icon in the notification area and select Advanced Preferences > Configuration Checker.

    The Configuration Checker window appears.

    User-added image

  2. Select SSONChecker and click Run.

    The test runs on all the SSON checkpoints.

After the test is complete, the results are displayed for each test.

The test describes if all the configuration requirements for Single Sign-on are met.

For more information, see Using Configuration Checker to validate Single Sign-on configuration


Verify the list of Network Providers

If users face any issues with Single Sign-on, Citrix recommends that you verify the list of network providers list on the client machin e as described below:

  1. Click Start.

  2. Enter View network connections. The Network Connection window appears.

  3. Press ALT to display the menu. Click Advanced > Advanced Settings

    Advanced Settings
    window appears.

  4. Click the Provider Order tab.

  5. Move “Citrix Single Sign On” to the top of the list to change the order of network providers.

    User-added image

Related:

  • No Related Posts

Support for Monitors Including 4K Resolution and Multi-Monitors

Information

Citrix Virtual Apps and Desktops 7 (f.k.a. XenApp and XenDesktop) supports a variety of display configurations across different endpoint devices. The purpose of this knowledge base article is to review product capabilities and support requirements with regards to display resolutions, multi-monitors, and DPI scaling configurations for the client endpoint. Deployment considerations related to performance and scalability are also included.

Display resolution standards

As of this writing the most common resolution for a desktop monitor is 1920×1080, also referred to as 1080p. The term “4K” is used to refer to a monitor that has a resolution in the order of 4000 pixels in one dimension, see 4K Resolution-Wikipedia. It is important to establish the resolution of a particular 4K monitor. In the context of this article we refer to 4K resolution as 3840 x 2160 (or 2160p) which is the most common standard based on the aspect ratio of 16:9. These ultra-high-resolution monitors are becoming more prevalent in the Enterprise with the arrival of new mobile devices (laptops and tablets) and as the traditional 1080p monitors get replaced during hardware refresh cycles.

Display resolution and multi-monitor support in the Citrix session

The maximum resolution and number of monitors that can be used in a Citrix session is determined based on the display adapter in use. A Citrix session may use different display adapters, each with its own set of capabilities depending on the virtual desktop agent (VDA) type and the operating system (OS). There are other factors to consider as well such as the presence of a graphics processing unit (GPU) and the HDX graphics mode in use. Supported configurations and deployment considerations are listed below:

  • Server OS VDAs (Virtual Apps / XenApp) – Supports up to 8 monitors. Display resolution is only limited by the Windows OS capabilities or the available video memory for the machine. The amount of video memory that a Citrix session can consume can be configured via Citrix policy. The default value for the Display memory Limit policy is 65536KB and this is sufficient for up to 2x4K monitors (2x32400KB).
  • Desktop OS VDAs (Virtual Desktops / XenDesktop)
    • Windows 7 – Supports up to 8 monitors. Display resolution is limited to 4094 pixels in any dimension. The VDA must have sufficient memory allocated to support the desired configuration. Refer to CTX200257 – Screen Issues Connecting to 4K Resolution Monitors for additional information.
    • Windows 10 – Supports up to 8 monitors. Display resolution is limited to 4094 pixels in any dimension on 7.15 LTSR VDAs. On 7.16 and greater VDAs, display resolution is only limited by the Windows OS capabilities or the available video memory for the machine. The amount of video memory that a Citrix session can consume can be configured via Citrix policy. The default value for the Display memory Limit policy is 65536KB and this is sufficient for up to 2x4K monitors (2x32400KB).
  • GPU-enabled Desktop OS VDAs (HDX 3D Pro) – Maximum resolution and number of monitors is strictly dependent on the GPU capabilities. For example, supported NVIDIA GPUs may support display resolutions up to 4096×2160 and up to 4 monitors depending on type or vGPU profile and license in use. Refer to CTX131385 – HDX 3D Pro GPU Support and Deployment Considerations for more information.
  • Linux VDAs – Standard VDAs support up to nine monitors, and HDX 3D Pro VDAs support up to four monitors. The Linux VDA provides the out-of-the-box multi-monitor support with a default resolution of 2560×1600 per monitor. Refer to CTX220128 – How to Configure Multi-Monitor Support on the Linux VDA for more information.

Note: While there are no controls in place to limit resolutions above 4K in Windows 10 VDAs, Citrix development testing is limited to 4K monitors currently.


High-DPI (dots per inch)

Current support for High DPI endpoints is based entirely on the Citrix Receiver or Workspace App capabilities for a given platform. Citrix Receiver for Windows 4.10 (or greater) and Citrix Workspace App for Windows are the only DPI aware clients available currently. These clients can be configured to either scale the session, ignore DPI settings and set the full native resolution, or match ( with VDA versions 1811 or newer) client resolution and DPI settings on the VDA. Refer to CTX230017 – Display DPI scaling configuration with Receiver for Windows for additional information.

Clients that are not DPI aware rely entirely on the OS to scale the application as appropriate to the endpoint DPI settings. This means that the Receiver or Workspace App can behave differently depending on the OS. Multi-monitors with different DPI scales are not supported with clients that are not DPI aware.


Performance and scalability considerations

In the context of display remoting the size of a user session can vary significantly based on display resolution and the number of monitors alone. As the session grows in size more server and client resources are required, for rendering and encoding/decoding of the graphics, and more data needs to be sent from the server to the client via the network. This has a direct impact to session performance and server scalability. Citrix highly recommends taking user requirements with respect to display configuration into account as it relates to server hardware, network links, and endpoint devices. Some deployment considerations are listed below:

  • Both display resolution and the number of monitors increase the session size. A user connecting from and endpoint with a single 4K monitor would result in the same session size as a user connecting with four 1080p monitors. Single server scalability can be reduced significantly by simply upgrading user endpoints with 4K monitors. If 4K monitor support is required additional server resources should be allocated accordingly to maintain desired user density levels.
  • Bandwidth requirements will also increase with higher resolutions and the number of monitors in use. Bandwidth constraints could limit frame rates and reduce image quality affecting session interactivity and user experience as a result.
  • The endpoint device must have adequate hardware resources available to support the desired display configuration. This could mean having enough CPU resources and in some cases a GPU that can handle the graphics workload. Performance limitations of Thin Clients may become apparent at high resolutions such as 4K, for example.

Related: