VM's Power State Does Not Update And Shows As “Unknown” After vCenter Server Reboots

This is an issue with Citrix hypervisor communication library plugin since version Xenapp/XenDesktop version 7.16.

When vCenter server goes alive after reboot i.e “https://<vCenter FQDN>/sdk” becomes accessible, BrokerHostingPlugin still fails to login the vCenter server with exception “The session is not authenticated.”.

CDF Traces from Delivery Controller

,BrokerHostingPlugin,,0,,1,Information,”Attempting connection”,””

,BrokerHostingPlugin,,0,,1,Information,”***** Get Hypervisor Certificate for Connection to ‘https://<vCenter FQDN>/sdk​​​​​​​’ *****”,””

,BrokerHostingPlugin,,0,,1,Information,”Certificate is untrusted: False”,””

,BrokerHostingPlugin,,0,,1,Information,”Time elapsed to get the hypervisor certificate: xxms”,””

,BrokerHostingPlugin,,0,,1,Information,”***** Login Connection – 0 to ‘​​​​​​​https://<vCenter FQDN>/sdk’ as ‘#login_name#‘ *****”,””

,BrokerHostingPlugin,,0,,1,Information,”VMware plugin initialisation times: create service xms, content time xxxms, total xxxms”,””

,BrokerHostingPlugin,,0,,1,Information,”Connected to ‘VMware vCenter Server #vCenter version info#’“,””

,BrokerHostingPlugin,,0,,1,Error,”System.Web.Services.Protocols.SoapException: The session is not authenticated.

,BrokerHostingPlugin,,0,,1,Information,”Connection attempt threw exception System.Web.Services.Protocols.SoapException: The session is not authenticated.

,BrokerHostingPlugin,,0,,1,Information,”Connection is still down”,””

,BrokerHostingPlugin,,0,,1,Information,”Sleeping for 00:00:30 before trying to reconnect again”,””

Related:

  • No Related Posts

How to Create Machine Catalog using MCS in Azure Resource Manager

Pre-requisites

  • Access to the XenApp and XenDesktop Service of Citrix Cloud.
  • An Azure Subscription.
  • An Azure Active Directory (Azure AD) user account in the directory associated with your subscription, which is also co-administrator of the subscription.
  • An ARM virtual network and subnet in your preferred region with connectivity to an AD controller and Citrix Cloud Connector.
  • “Microsoft Azure” host connection
  • To create an MCS machine catalog, XenDesktop requires a master image that will be used as a template for all the machines in that catalog.

User-added image

Creating Master Image from Virtual Machine deployed in Azure Resource Manager

Create a virtual machine (VM) in Azure using the Azure Resource Manager gallery image with either the Server OS or Desktop OS (based on whether you want to create Server OS catalog or Desktop OS catalog).

Refer to Citrix Documentation – install Citrix VDA software on the VM for more information.

Install the applications on the VM that you want to publish using this master image. Shutdown the VM from Azure Portal once you have finished installing applications. Make sure that the power status for the VM in Azure Portal is Stopped (deallocated)

User-added image

When creating MCS catalog we need to use the .vhd file that represents OS disk associated with this VM as master image for the catalog. If you have the experience of using Microsoft Azure Classic connection type in XenDesktop, you would have captured specialized image of the VM at this stage, but for Microsoft Azure connection type you don’t have to capture the VM image, you will only shutdown the VM and use the VHD associated with the VM as master image.

Create MCS Catalog

This information is a supplement to the guidance in the Create a Machine Catalog article. After creating master image, you are all set to create MCS catalog. Please follow the steps as described below to create MCS catalog.

  1. Launch the Studio from your Citrix Cloud client portal and navigate to Machine Catalogs in the left hand pane.

  2. Right click Machine Catalogs and click on Create Machine Catalog to launch the machine creation wizard.

  3. Click Next on the Introduction page.

    User-added image

  4. On the Operating System page Select Server OS or Desktop OS based on what type of catalog you want to create and click Next.

    User-added image

  5. On the Machine Management page, select Citrix Machine Creation Service (MCS) as the deployment technology and select the Microsoft Azure hosting resource and click Next.

    User-added image

Master Image Selection – This page provides a tree view which you can navigate to select the master image VHD. At the topmost level are all the resource groups in your subscription except those which represent the MCS catalog created by XenDesktop. When you select and expand a particular resource group, it shows the list of all storage accounts for the Azure Umanaged Disks in that resource group. If there are no storage accounts in that resource group, there will not be any child items under that resource group. If you have manually created number of resource groups and storage accounts to host your manually created VMs in your subscription, the master image page will show all those resource groups, storage accounts, containers and VHDs even though not all those VHDs are master images that you want to use for the provisioning. Select the storage account that has your master image. When you expand the storage account, it shows list of containers inside the storage account. Expand the container that has master image VHD and select the VHD that you want to use as master image for the catalog.

User-added image

In the case of Azure Unmanaged Disk, you need to know the VHD path in order to select it. If you have stood up a VM in Azure and prepared it to be used as a master image and you want to know the VHD path, follow the steps below:

  1. Select the resource group that has your master image VM.

  2. Select the master image VM and click Settings

  3. Click on Disks then Click OS Disks and copy the disk path.

    User-added image
    User-added image

  4. OS disk path is structured as https://<storage account name>.blob.core.window.net/<container name>/<image name>.vhd

  5. You can use the disk path obtained in the step above to navigate the tree view to select image.

In the case of Azure Managed disk, it will be available directly under the Resource Group that you had created or as a part of the Virtual Machine’s Resource Group, as show below:

Note: If you don’t shutdown the master image VM and select the corresponding VHD to create a catalog, the catalog creation will fail. So make sure if you are selecting the VHD which is attached to running VM instance, the VM is in Stopped(deallocated) state.

  1. Storage type selection – XenDesktop supports Locally Redundant Standard or Premium storage for provisioning VMs in Azure. Your master image VHD can be hosted in any type of storage account, but for the VMs to be provisioned in Azure, XenDesktop will create new storage accounts based on storage type you selected.

    User-added image

  2. XenDesktop will provision maximum 40 VMs in single storage account due to IOPS limitations in Azure. For example if you want to create 100 VM catalog, you will find 3 storage accounts created and VM distribution in each storage account will be 40, 40 and 20.

  3. VM instance size selection – XenDesktop will show only those VM instance sizes which are supported for the selected storage type in the previous step. Enter number of VMs and select the VM instance size of your choice and click Next.

    User-added image

  4. Network Card Selection – Select network card and the associated network. Only one network card is supported.

    User-added image

  5. Select resource location domain and enter machine naming scheme.

    User-added image

  6. Enter credentials for your resource location Active Directory.

    User-added image

  7. Review the catalog summary, enter the catalog name and click Finish to start provisioning.

    User-added image

  8. Once the provisioning is complete, you will find new resource group created in your Azure subscription which hosts, all the VMs, storage accounts and network adapters for the catalog you provisioned. The default power state for the VMs after provisioning is Stopped(deallocated).

    User-added image

Once the provisioning is complete, you will find new resource group created in your subscription that has VM RDSDesk-01 as per the naming scheme we provided, NIC corresponding to that VM and a storage account that XenDesktop created to host the OS disk and the identity disk for the VM. The VM will be hosted on the same network as that of the selected hosting resource during catalog creation and the default power state of the VM will be Shutdown(deallocated).

The resource group created by XenDesktop during the MCS provisioning will have following naming convention

citrix-xd-<ProvisioningSchemeUid>-<xxxxx>

To find out which resource group in the Azure portal corresponds to the catalog you created from studio, follow the steps below.

  1. Connect to your XenApp and XenDesktop service using Remote PowerShell SDK. Please visit this link to find our how to interact with your Citrix Cloud environment using Remote PowerShell SDK.
  2. Run command Get-ProvScheme -ProvisioningSchemeName <Catalog Name>
  3. Note down the ‘ProvisioningSchemeUid’ from the output of the above command.
  4. Go to the Azure portal and search for the resource group name that contains ‘ProvisioningSchemeUid’ you obtained in step 3.
  • Note:

    As a best practice you should always create a copy of your master image and use the copied image as input to the provisioning process. In future if you want to update the catalog, you can start the master image VM and make necessary changes, shut it down and again create a copy of the image which will be your update image. This helps you to use the master image VM to create multiple image updates.

    Remember to shutdown the master image VM from Azure portal before starting to create the catalog. The master image needs to be copied into catalog’s storage account once provisioning starts, so we need to make sure it is not in use by any VM, otherwise it will lead to image copy failure and eventually provisioning failure.

  • Make sure you have sufficient cores, NIC quota in your subscription to provision VMs. You are most likely going to run out of these two quotas. You may not be able to check your subscription quota limits,
  • If your master image VM is provisioned in the Premium storage account then just shutting down the VM from the portal isn’t enough. You also need to detach the disk from the VM to use it as master image in provisioning. But in Azure Resource Manager you can not detach the disk while the VM is still available. So you need to delete the VM from the portal, this will only delete the VM but keep the OS disk in the storage account. The NIC corresponding to the VM also needs to be deleted separately.
User-added image

Related:

Citrix ADC Deprecated Classic Policy Based Features and Functionalities FAQs

Q. Which all Classic policy based features and functionalities are being removed from Citrix ADC?

Answer: All the features and functionalities mentioned in “Feature Description” column in Table 1 below are being removed from Citrix ADC. These features were deprecated in 12.0 builds and will be removed in a future release (targeted NetScaler GA release in Q2 2020).

Citrix recommends that all Citrix ADCcustomers take steps to switch from the following deprecated features & functionalities to corresponding feature replacements as suggested in Table 1.

Table 1. Classic policy based features & functionalities deprecated with feature replacement.

Feature Description Deprecation Initiated Feature Replacement
Citrix ADCfeatures and its functionalities: –

  • SureConnect (SC)
  • Priority Queuing (PQ)
  • HTTP Denial of Service Protection (HDoSP)
12.0.41.16 AppQoE
SPDY 12.0.41.16 HTTP/2
HTMLInjection 12.0.41.16 AppFlow with Client-Side Measurements
Filter 12.0.41.16 Responder (for ERRORCODE, or DROP or RESET on the request side), Rewrite (for ADD or CORRUPT, or DROP or RESET on the response side), or Content Switching (for FORWARD).
Q and S prefixes in Advanced expressions 12.0.41.16 HTTP.REQ and HTTP.RES
Pattern function in Rewrite action 12.0.56.20 -Search Rewrite action parameter
Classic Named (policy) expression 12.0.56.20 Advanced policy expression
Application Firewall Classic policy 12.0.41.16 Application Firewall Advanced policy
Compression Classic policy 12.0.41.16 Compression Advanced policy
Classic Cache Redirection policy 12.0.41.16 Advanced Cache Redirection policy
Content Switching Classic policy 12.0.41.16 Content Switching Advanced policy
SSL Classic policy 12.0.41.16 SSL Advanced policy
Classic Audit SYSLOG policy 12.0.41.16 Advanced Audit SYSLOG policy
Classic Audit NSLOG policy 12.0.41.16 Advanced Audit NSLOG policy
Classic AAA Pre-authentication policy 12.0.56.20 Advanced AAA Pre-authentication policy
Authentication Local policy

RADIUS Authentication policy

LDAP Authentication policy

Authentication Certification (cert) policy

TACACS Authentication policy

Authentication Negotiate policy

SAML Authentication policy

Delegation Forms Authentication (DFA) policy

Web Authentication policy
12.0.56.20 Advanced Authentication policy (“add Authentication policy”)
Classic Authorization policy 12.0.41.16 Advanced Authorization policy
Classic Traffic Management Session policy 12.0.41.16 Advanced Traffic Management Session policy
Classic Tunnel Traffic policy 12.0.56.20 Advanced Tunnel Traffic policy
Classic VPN Traffic policy 12.0.41.16 Advanced VPN Traffic policy
Classic VPN Session policy 12.0.41.16 Advanced VPN Session policy
Trace Classic expression 12.0.41.16 Trace Advanced expression
SYS.EVAL_CLASSIC_EXPR Classic function 12.0.41.16 Converting function to Advanced, replacing SYS.EVAL_CLASSIC_EXPR
Q. How do I convert deprecated Classic policy based features & functionalities to Advanced policy based features and functionalities?

Answer: You can use the Citrix ADC proprietary nspepi tool to convert commands, expressions, and configurations. nspepi tool helps to convert all the Classic expressions in the Citrix ADCconfiguration to the Advanced policy. More details about nspepi tool is available at: https://docs.citrix.com/en-us/netscaler/12/appexpert/policies-and-expressions/ns-pi-intro-pol-exp-wrapper-con/ns-pi-pe-to-pi-conversion-tool-wrapper-con.html

Q. From which Citrix ADC release will Classic policy based features and functionalities not be supported?

Answer: Citrix ADC GA,2020 releases onwards.

Q. What actions do I need to take when I will be moving from a build where a feature mentioned in Table 1 is supported (example, Citrix ADC 11.0) to a build where the feature is not supported (example, Citrix ADC 13.1)?

Answer: Citrix recommends to replace the Classic policy based features and functionalities with the replacement features and functionalities mentioned in Table 1 above before upgrading to 13.1.

Q. What actions do I need to take when I will be moving from a build where a feature mentioned in Table 1 is deprecated (example, Citrix ADC 12.0.56) to where a build where the feature is not supported (example, Citrix ADC 13.1)?

Answer: Citrix recommends to replace the Classic policy based features and functionalities with the replacement features and functionalities mentioned in Table 1 above before upgrading to 13.1.

Q. I am using a build on which a feature mentioned in Table 1 is supported and have no immediate plans of upgrade, how long will I have support for deprecated feature?

Answer: Citrix will support the policy based features and functionalities as per current software support guidelines. For more details please refer to : https://www.citrix.co.in/support/product-lifecycle/product-matrix.html

Q. What is recommended when I am adding a new deprecated configuration or modifying existing deprecated configs on the builds where Classic policy expressions are deprecated (e.g. 12.0.56)?

Answer: Citrix recommends not to use deprecated policies and expressions. Please use the above Table 1 for finding the replacement features.

Q. Do I have to re-boot the Citrix ADC instance after converting configuration file?

Answer: Yes, you have to reboot the NetScaler instance after successful conversion of ns.config file.

Related:

  • No Related Posts

Citrix UPS Printers are not visible via Control Panel, Devices And Printers


This is an known issue with printers provided by Citrix Universal Printer server on windows operating systems Windows Server 2019, Windows Server 2016, Windows 10, Windows Server 2012r2, Windows Server 2012.

Citrix is working with Microsoft to correct this interaction between Microsoft operating systems and Citrix universal print server print provider.


Citrix Documentation:

This issue has been documented in our XenApp/XenDesktop documentation since 7.5

  • Universal Print Server printers selected in the virtual desktop do not appear in the Devices and Printers window in Windows Control Panel. However, when users are working in applications, they can print using those printers. This issue occurs only on Windows Server 2012, Windows 2012 R2 , Windows 10 and Windows 8 platforms. [#335153]

Microsoft Documentation:

The Device Setup Manager service is discussed in the following article from Microsoft it applies to both Windows 8 and Windows 2012.

Device setup user experience in Windows 8

Microsoft released a hotfix for server 2012r2 which partially addressed some issues with 3rd party print provider visibility in newer windows releases.

However this was not a complete solution, and printers provided by Citrix Universal Print Server remained not visible.​

https://support.microsoft.com/en-us/help/2966038/printer-managed-by-custom-print-providers-is-not-visible-in-devices-an

Related:

  • No Related Posts

Supported Databases for XenApp and XenDesktop Components

Citrix is committed to ensuring that our products function with the latest Microsoft SQL databases. Citrix supplies best 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.

This document will be updated periodically as new information becomes available.

What has changed from the last release of the matrix

  • Updated support for Virtual Apps and Desktops (XenApp/XenDesktop) 7 1906
Supported Databases Virtual Apps and Desktops (XenApp/XenDesktop) 7.15LTSR / 1811 / 1903 / 1906 XenApp/XenDesktop 7.6 LTSR Provisioning Services 7.15 LTSR / 1811 / 1903 / 1906 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:

Smart Scale to Autoscale Migration

Manual migration involves manually configuring the Autoscale user interface in Citrix Studio by associating the Smart Scale user interface per Delivery Group.

1. Select Delivery Groups in the Studio navigation pane on the Manage tab.

2. In the Actions panes, select the Delivery Group and then click Edit Delivery Group.

3. On the Autoscale page, select the Autoscale check box to enable Autoscale.

4. On a separate tab in your browser window, go to Citrix Cloud > Smart Tools > Smart Scale.

5. On the Virtual Apps and Desktops Sites page, locate the Site for that Delivery Group.

6. Click View Site and then click Configure.

7. On the Smart Scale configuration page, select that Delivery Group.

8. Migrate the data including machine cost, capacity buffer, and power-off delay from Smart Scale to the applicable fields in Autoscale.

9. On the Autoscale page, create schedules equivalent to those defined in Smart Scale. For more information about how to create schedules, see How Autoscale power manages machines.

10. After your data migration completes, click Apply. After that, the data is saved to Autoscale successfully.

11. On the Smart Scale configuration page, click the Smart Scale Enabled toggle button to disable Smart Scale for the Delivery Group you selected.

12. Repeat the steps above to migrate the data for other Delivery Groups.

Note:

  • Migrating capacity buffer. Smart Scale has only one field for capacity buffer. On the Delivery Group page of Smart Scale, click Advanced to see the configured capacity buffer. However, Autoscale lets you determine the capacity buffer separately for peak and off-peak times. On the Autoscale page, you can either fill in the two capacity buffer fields with the value referenced from Smart Scale or define different values for peak and off-peak times.
  • Merging schedules. When migrating the schedules, you might need to merge your schedules if applicable. This is because Smart Scale allows the same day to be included in multiple schedules, but Autoscale does not. For more information, see Overlapping schedules in this article.
  • Migrating session count. To migrate session count (the maximum number of sessions), use Group Policy. For more information, see Session count in this article.

Back to top

Related:

  • No Related Posts

Unable to Create catalog using c5.xlarge instance type, using Citrix DDC 7.15 with AWS as hosting unit.

  • Nothing will get created on the AWS.
  • Cloud DDC will throw an exception “Failed to create preparation VM.

Studio Exception

Error Id: XDDS:0DAA3833

Exception:

Citrix.Console.Models.Exceptions.ProvisioningTaskException An error occurred while preparing the image. At

Citrix.Console.PowerShellSdk.ProvisioningSchemeService.BackgroundTasks.ProvisioningSchemeTask.CheckForTerminatingError(SdkProvisioningSchemeAction sdkProvisioningSchemeAction) at Citrix.Console.PowerShellSdk.ProvisioningSchemeService.BackgroundTasks.ProvisioningSchemeTask.WaitForProvisioningSchemeActionCompletion(Guid taskId, Action`1 actionResultsObtained) at Citrix.Console.PowerShellSdk.ProvisioningSchemeService.BackgroundTasks.ProvisioningSchemeCreationTask.StartProvisioningAction() at Citrix.Console.PowerShellSdk.ProvisioningSchemeService.BackgroundTasks.ProvisioningSchemeCreationTask.RunTask() at Citrix.Console.PowerShellSdk.BackgroundTaskService.BackgroundTask.Task.Run()

DesktopStudio_ErrorId : ProvisioningTaskError

ErrorCategory : NotSpecified

ErrorID : FailedToCreateImagePreparationVm

TaskErrorInformation : Terminated

InternalErrorMessage : Timed out waiting for: Creating machine ‘Preparation – c5-xlarge-test – Xm0N7wPqkkCAdpjgoHyY4Q’ with pre-existing ENIs: eni-0a516a250b296fc92

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