Month: March 2017

Citrix Delivery controller maintenance: Control number of enumerations made

Simple enough to implement but only required in the “hottest” of environments where thousands of requests are being made per second. From within the Storefront :

Specify the maximum number of concurrent requests to send to different Delivery Controllers. The default is 0 (No Limit).

Use the Advanced Settings task, select Maximum concurrent enumerations, enter a number, and click OK.

For more information on this and also a great overview of what goes on at logon take a look at Bas’s guide, really good read.

http://www.basvankaam.com/2016/12/19/demystifying-the-citrix-xenapp-logon-enumeration-and-launch-steps-new-details-included/

 

Advertisements

Citrix tip: Whats the “qfarm /load” equivalent in a XenApp 7.x environment?

Needless to say every  citrix administrator will need to use this at some time, like most activities is a powershell cmdlet so need to get into a Powershell session. Once in there type:

Get-BrokerMachine -SessionSupport MultiSession -Property ‘DnsName’,’LoadIndex’,’SessionCount’

Like before same values apply – load value 10000 means server is unavailable to take connections for example.

Citrix tip: troubleshooting local host cache issues in Citrix 7.x environments

With the release of XenApp 7.1 a change to the FMA architecture meant that the local host cache (LHC) was effectively done away with. Over the course of the many upgrades in the 7.x version (up to version 13 at time of writing) citrix more and more re-integrated the “features” that came with the original IMA local host cache. With version 7.12 effectively it was restored to its former glory.

That said, in order to troubleshoot issues relating to synchronization it was quite different from 6.x. With 7.x a few different tools were introduced. Following article gives a nice overview of the architecture.

https://docs.citrix.com/en-us/xenapp-and-xendesktop/7-12/manage-deployment/local-host-cache.html

Relating to troubleshooting tools the pertinent information :

CDF tracing: Contains options for the ConfigSyncServer and BrokerLHC modules. Those options, along with other broker modules, will likely identify the problem.

Report: You can generate and provide a report that details the failure point. This report feature affects synchronization speed, so Citrix recommends disabling it when not in use.

To enable and produce a CSS trace report, enter:

New-ItemProperty -Path HKLM:\SOFTWARE\Citrix\DesktopServer\LHC -Name EnableCssTraceMode -PropertyType DWORD -Value 1

The HTML report is posted at C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Temp\CitrixBrokerConfigSyncReport.html

After the report is generated, disable the reporting feature:

Set-ItemProperty -Path HKLM:\SOFTWARE\Citrix\DesktopServer\LHC -Name EnableCssTraceMode -Value 0

Export the broker configuration: Provides the exact configuration for debugging purposes.

Export-BrokerConfiguration | Out-File < file-pathname>

For example, Export-BrokerConfiguration | Out-File C:\BrokerConfig.xml.