Local Host Cache (LHC), which was a key feature of the IMA architecture in XenApp 6.5 and earlier was reintroduced for the first time in the FMA based XenApp/XenDesktop 7.12 release.   You can learn more about LHC in detail in my previous blog on the topic.

Prior to 7.12, users were able to access resources (with some caveats) while experiencing site database loss using a feature known as Connection Leasing. When upgrading to 7.12 from an earlier release with Connection Leasing enabled, LHC is disabled by default.

To enable LHC run the following powershell command on the upgraded broker.

Set-BrokerSite -LocalHostCacheEnabled $true -ConnectionLeasingEnabled $false

The above command, enables Local Host Cache and disables Connection Leasing.

The Get-Brokersite cmdlet provides the current state of Local Host Cache (whether its enabled or disabled)

To disable Local Host Cache and enable Connection Leasing, run the following command:

Set-BrokerSite -LocalHostCacheEnabled $false -ConnectionLeasingEnabled $true

3 comments on “How to enable Local Host Cache in XenApp/XenDesktop 7.12”

  1. Can both Connection Leasing and LHC be enabled at the same within a Site or only one can be enabled at one time ?

    Lets say I have 2 Delivery Controllers and 50 VDAs – do I need to run the command on all 52 servers or only once on any server ?

    Firefox 53.0Windows 7 x64 Edition
    Mozilla/5.0 (Windows NT 6.1; WOW64; rv:53.0) Gecko/20100101 Firefox/53.0
  2. You can either have connection leasing on LHC enabled at the site level. Not both. The commands need to be run ONE TIME at the controller level and not all servers.

    Google Chrome 58.0.3029.110Windows
    Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36

Leave a Reply

Your email address will not be published. Required fields are marked *