Unable to create machine catalogue in AWS Error: “You do not have a host with a matching configuration and sufficient capacity”

You may see following error when you attempt to create machine catalog in AWS:

“You do not have a host with a matching configuration and sufficient capacity” “Timed out waiting for: Creating machine ‘Preparation – ABC-TEST-VDI-XY – XXxxxxxxxxxxxxxxxxxxxxx’ with pre-existing ENIs: eni-XXXXXXXXXXXXXXXXX”

The above error is seen while using Dedicated VPC and Dedicated Host on AWS

Later, you may see following error on allocating a Dedicated Host in AWS

Name: MC_CreateMachineCatalogInitialzation

An error occurred. Contact Citrix Technical Support, and provide the transaction ID above.

Exception: DesktopStudio_ErrorId : ProvisioningTaskError ErrorCategory : NotSpecified ErrorID : NoDiskContentTransferService TaskErrorInformation : Terminated InternalErrorMessage : No facility available for disk upload. Unable to create any functioning volume service VMs. Timed out waiting for: Creating machine ‘XenDesktop Temp’ with pre-existing ENIs: eni-xxxxxxxxxxxxxxxxx No facility available for disk upload. Unable to create any functioning volume service VMs. Timed out waiting for: Creating machine ‘XenDesktop Temp’ with pre-existing ENIs: eni-xxxxxxxxxxxxxxxx

Related:

  • No Related Posts

NOTICE of STATUS CHANGE ANNOUNCEMENT FOR CITRIX ADC (formerly NetScaler ADC) Traffic Domain BASED FEATURES & FUNCTIONALITIES

Citrix Systems, Inc. announces a Notice of Status Change (NSC) for Citrix ADC Traffic Domain features and functionalities. Table 1 below explains Citrix ADC life cycle management milestones as well as important information about dates and options during this period. The dates and milestones provided are in accordance with stated End of Life/End of Support policies for Citrix Systems, Inc.

Table 1. Milestones and Dates for Citrix ADC Traffic Domain features & functionalities

Milestone Definition Date/Release
Notice of Status Change The NSC date is the date on which Citrix announces the intent to initiate the lifecycle management process for Traffic Domain. Sep 1st, 2021
Feature Deprecation The dates on which these features and capabilities will be deprecated. Users will be warned to switch to the replacement features when using given build. Q3 2021 (next Citrix ADC GA release – 13.1)
Feature Removal The timeline from which these features will not be available. Q3 2023

Citrix ADC Features & Functionalities Affected

The features & functionalities affected by this announcement and their replacements are listed in Table 2 (below). The features & functionalities listed in the Feature Replacement column represent the migration path for these deprecated features/functionalities.

Table 2. Features & functionalities affected by this announcement

Feature Description Feature Replacement
Traffic Domain Admin Partition

Recommendations for Customers

Citrix recommends that all Citrix ADC customers take steps to switch from the deprecated features & functionalities to the corresponding replacements suggested in Table 2 above.

Tools to aid in migration from Traffic Domains to Admin Partitions are available at https://github.com/citrix/ADC-scripts/tree/master/td-to-ap

For More Information

Related:

  • No Related Posts

XenMobile Android Enterprise & iOS devices failed to enroll after ADC upgrade to 13.0-82.41+ or 12.1-62.23+

Please refer to the following Citrix ADC doc to enable SSO configuration for XenMobile Gateway Virtual server.

https://docs.citrix.com/en-us/citrix-adc/current-release/aaa-tm/single-sign-on-types/enable-sso-for-auth-pol.html

GUI Configuration Guide:

  • Part 1: Configure a traffic policy that enabled http SSO:

5. Navigate to Security > AAA – Application Traffic > Policies > Traffic, Select Traffic Profiles tab, and click Add.

  • Part 2: After configured traffic policy, please bind it to XenMobile Gateway Virtual Server.

Navigate to Citrix Gateway> Virtual Servers, select XenMobile Gateway and Edit.

image.png

Then Scroll DOWN to the bottom to find Policies section to add binding a traffic policy:

image.png
image.png
Select the traffic policy we just created, for example named as vpn_tf_pol, then bind it with a high Priority value like 63000

image.png

CLI Configuration Guide:

Demo configuration commands follows:

//Creating traffic policy with SSO enabled

add vpn trafficaction vpn_tf_act http -SSO ON

add vpn trafficpolicy vpn_tf_pol true vpn_tf_act

//Binding traffic policy to XenMobile Gateway Virtual server

bind vpn vserver _XM_XenMobileGateway -policy vpn_tf_pol -priority 63000

Related:

  • No Related Posts

XenMobile Android Enterprise & iOS devices failed to enroll after ADC upgrade to 13.0-82.41+ or 121.1-62.23+

Please refer to the following Citrix ADC doc to enable SSO configuration for XenMobile Gateway Virtual server.

https://docs.citrix.com/en-us/citrix-adc/current-release/aaa-tm/single-sign-on-types/enable-sso-for-auth-pol.html

GUI Configuration Guide:

  • Part 1: Configure a traffic policy that enabled http SSO:

5. Navigate to Security > AAA – Application Traffic > Policies > Traffic, Select Traffic Profiles tab, and click Add.

  • Part 2: After configured traffic policy, please bind it to XenMobile Gateway Virtual Server.

Navigate to Citrix Gateway> Virtual Servers, select XenMobile Gateway and Edit.

image.png

Then Scroll DOWN to the bottom to find Policies section to add binding a traffic policy:

image.png
image.png
Select the traffic policy we just created, for example named as vpn_tf_pol, then bind it with a high Priority value like 63000

image.png

CLI Configuration Guide:

Demo configuration commands follows:

//Creating traffic policy with SSO enabled

add vpn trafficaction vpn_tf_act http -SSO ON

add vpn trafficpolicy vpn_tf_pol true vpn_tf_act

//Binding traffic policy to XenMobile Gateway Virtual server

bind vpn vserver _XM_XenMobileGateway -policy vpn_tf_pol -priority 63000

Related:

  • No Related Posts

XenMobile Android Enterprise & iOS devices failed to enroll after ADC upgrade to 13.0-82.41+

Please refer to the following Citrix ADC doc to enable SSO configuration for XenMobile Gateway Virtual server.

https://docs.citrix.com/en-us/citrix-adc/current-release/aaa-tm/single-sign-on-types/enable-sso-for-auth-pol.html

GUI Configuration Guide:

  • Part 1: Configure a traffic policy that enabled http SSO:

5. Navigate to Security > AAA – Application Traffic > Policies > Traffic, Select Traffic Profiles tab, and click Add.

  • Part 2: After configured traffic policy, please bind it to XenMobile Gateway Virtual Server.

Navigate to Citrix Gateway> Virtual Servers, select XenMobile Gateway and Edit.

image.png

Then Scroll DOWN to the bottom to find Policies section to add binding a traffic policy:

image.png
image.png
Select the traffic policy we just created, for example named as vpn_tf_pol, then bind it with a high Priority value like 63000

image.png

CLI Configuration Guide:

Demo configuration commands follows:

//Creating traffic policy with SSO enabled

add vpn trafficaction vpn_tf_act http -SSO ON

add vpn trafficpolicy vpn_tf_pol true vpn_tf_act

//Binding traffic policy to XenMobile Gateway Virtual server

bind vpn vserver _XM_XenMobileGateway -policy vpn_tf_pol -priority 63000

Related:

  • No Related Posts

XenMobile Android Enterprise & iOS devices failed to enroll after ADC upgrade to 13.0

Please refer to the following Citrix ADC doc to enable SSO configuration for XenMobile Gateway Virtual server.

https://docs.citrix.com/en-us/citrix-adc/current-release/aaa-tm/single-sign-on-types/enable-sso-for-auth-pol.html

GUI Configuration Guide:

  • Part 1: Configure a traffic policy that enabled http SSO:

5. Navigate to Security > AAA – Application Traffic > Policies > Traffic, Select Traffic Profiles tab, and click Add.

  • Part 2: After configured traffic policy, please bind it to XenMobile Gateway Virtual Server.

Navigate to Citrix Gateway> Virtual Servers, select XenMobile Gateway and Edit.

image.png

Then Scroll DOWN to the bottom to find Policies section to add binding a traffic policy:

image.png
image.png
Select the traffic policy we just created, for example named as vpn_tf_pol, then bind it with a high Priority value like 63000

image.png

CLI Configuration Guide:

Demo configuration commands follows:

//Creating traffic policy with SSO enabled

add vpn trafficaction vpn_tf_act http -SSO ON

add vpn trafficpolicy vpn_tf_pol true vpn_tf_act

//Binding traffic policy to XenMobile Gateway Virtual server

bind vpn vserver _XM_XenMobileGateway -policy vpn_tf_pol -priority 63000

Related:

  • No Related Posts

Error “cannot connect to the hypervisor at object reference not set to an instance of an object” when running the XDSW

When running the XenDesktop Setup Wizard, it can fail with the following error:

“cannot connect to the hypervisor at <ADDRESS> object reference not set to an instance of an object”

The string <ADDRESS> will contain the actual URL of the vCenter Server.

This issue can appear when the DataCenter name on the VMWare side has a comma character anywhere in the name.

For example notice the use of the comma character in the following screenshot:

User-added image

Related:

  • No Related Posts

Users unable to relaunch the published applications, error “Citrix workspace will try to reconnect…”

Keep Alive policy settings:

https://docs.citrix.com/en-us/xenapp-and-xendesktop/7-15-ltsr/policies/reference/ica-policy-settings/keep-alive-policy-settings.html

Session reliability policy settings:

https://docs.citrix.com/en-us/xenapp-and-xendesktop/7-15-ltsr/policies/reference/ica-policy-settings/session-reliability-policy-settings.html

Session reliability on Citrix ADC high availability pair:

https://docs.citrix.com/en-us/citrix-adc/current-release/ns-ag-appflow-intro-wrapper-con/session-reliablility-on-citrix-adc-ha-pair.html

Related:

  • No Related Posts

Error: “SSL Error 61: You have not chosen to trust ‘Certificate Authority’…” on Workspace App for Mac

Important! This article is intended for use by System Administrators. If you are experiencing this issue and you are not a System Administrator, contact your organization’s Help Desk for assistance and refer them to this article.

Update to the Latest Receiver Version

  • Upgrade to the latest version of Receiver to verify if this resolves the issue.
  • If you are using SHA2 certificates then the older version of Receiver does not support these certificate. Refer to CTX200114 – Citrix Receiver Support for SHA-2 to view the Receiver versions which supports SHA-2 certificates.

If this does not resolve the issue then proceed to the next section.

For information on Receiver feature updates refer to – Citrix Receiver Feature Matrix.

Missing Root/Intermediate Certificate

This error message suggests that the Mac client device does not have the required root certificate/intermediate certificate to establish trust with the certificate authority who issued the Secure Gateway/NetScaler Gateway server certificate.

Complete the following steps to resolve this issue:

For Big Sur, please refer to Add certificates to a keychain using Keychain Access on macOS Big Sur

For Catalina, please refer to Add certificates to a keychain using Keychain Access on macOS Catalina


The default File Format should be Certificate (.cer).

Note: You might need to rename the certificate to a .CRT extension for the client to properly identify the certificate.

Save the certificate to the ApplicationsCitrix ICA Clientkeystorecacerts folder (create this folder if it does not exist):

User-added image

Related:

  • No Related Posts