When using Citrix DaaS with a customer-managed StoreFront, advanced health check has the added benefit that it retrieves additional information about what VDAs are in the same zone as the cloud connector. 
In the event that the cloud connectors are unable to contact Citrix Desktops as a Service, cloud connectors use their local host cache to facilitate connections to VDAs that are co-located.
StoreFront uses the additional information from the advanced health check results to contact the most appropriate online connector to launch apps and desktops.

Without advanced health check enabled, launch requests during local host cache may be routed to the wrong Cloud Connector resulting in failed local host cache launches.

How to Identify Misconfigured StoreFront Servers

Customers can use the Get-ConfigMisconfigurationReport cmdlet to obtain information on all misconfigurations in XML format.

To do this:

• On the machine with the Citrix DaaS Remote PowerShell SDK installed, open PowerShell as Administrator.
• Invoke the cmdlet: Get-ConfigMisconfigurationReport
• You can save the output to a file.
• Search the output for the tag: SfAdvHealthCheckNotConfigured

Example:

  <SfAdvHealthCheckNotConfigured Message="Storefront advanced health check not configured">

    <Zone ZoneUid="f11bc0b6-4d1e-49d6-ad5a-d3b1fc787d46" ZoneName="zone1" ResourceLocationId="f11bc0b6-4d1e-49d6-ad5a-d3b1fc787d46">

      <StoreFrontServer>SFX.xd.local</StoreFrontServer>

      <StoreFrontServer>SFY.xd.local</StoreFrontServer>

    </Zone>

  </SfAdvHealthCheckNotConfigured>

The data under the StoreFrontServer tag specifies the name of the Storefront server which is misconfigured. Ex: SFX.xd.local

This document helps customers identify if their on-premises StoreFronts are properly configured for launches in Local Host Cache (LHC) mode, specifically regarding the Advanced Health Check setting.