Scenario: An organization has two XenDesktop sites. Each site has its own Delivery Controller. Users logging on to the Receiver for Web site report that applications and desktops from both sites are i

Simply adding controllers to a shared server list does not differentiate between sites, so StoreFront cannot attribute failures to a specific XenDesktop site for investigation.

Changing XML ports affects communication channel configuration but does not address multi-site aggregation or help isolate which site is responsible for the intermittent unavailability.

Creating separate stores per site would fragment the user experience into multiple logins rather than providing a unified view, and does not help investigate intermittent failures within a single Receiver for Web site.

Adding each Delivery Controller as a unique delivery controller type in the Receiver for Web site tells StoreFront to treat each site independently, allowing it to enumerate and aggregate resources from both controllers separately. This configuration enables StoreFront to continue serving resources from one site even if the other is unavailable, and it surfaces per-site communication errors for investigation. Without this distinction, StoreFront cannot properly report which site is causing the intermittent failures.