Single controller failure in multi controller setup may result in Desktop launch failure for up to 5 minutes

Single controller failure in multi controller setup may result in Desktop launch failure for up to 5 minutes

book

Article ID: CTX314102

calendar_today

Updated On:

Description

Single controller failure in multi controller setup may result in Desktop launch failure for up to 5 minutes

Environment

Caution! Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.

Resolution

If you want to decrease the heartbeat time between DDC and VDA, you can modify following key on all DDC servers.
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\DesktopServer
HeartbeatPeriodMs REG_DWORD

The default value for this key is 600000 (10 Minutes) which is twice the VDA heartbeat interval. Reducing this to 300000 will reduce the heartbeat interval to 2.5 minutes and will enable the VDA to re-register faster to the next DDC.

Note:
Decreasing the heartbeat interval would increase heartbeat traffic.

Problem Cause

Virtual Desktop Agent (VDA) sends a heartbeat ping to Desktop Delivery Controller (DDC) periodically to ensure that the Controller is up and running. By default, VDA sends the heartbeat ping to DDC every 5 minutes. If the heartbeat test fails, the VDA will attempt to register with the next delivery controller.

Assuming that DDC1 went down just after a successful heartbeat request from VDA1, VDA1 will not realize that the DDC is down for the next 5 minutes (Default Heartbeat interval). After 5 minutes, it detects the failure and will attempt to register with DDC2.

Powered by Wolken Software