“The Citrix Desktop Service cannot connect to the delivery controller ‘’ (IP Address ‘10.10.220.10’)Ĭheck that the system clock is in sync between this machine and the delivery controller.
Refer CTX117248 for further information.” Please ensure that at least one delivery controller is available for Virtual Desktop Agents to register with. The service retries registering with controllers in approximately 8 seconds. “The Citrix Desktop Service failed to register with any delivery controller. The service now tries to register with controllers at a reduced rate of every 2 minutes.” “The Citrix Desktop Service failed to register with any controllers in the last 2 minutes. The details of the four most recent event log entries are: Alternatively, these events can be found in Application event long. The VDA logs problems with registration in its event log, as shown in the following example:Ī custom view can be created by selecting Citrix Desktop Service and Citrix ICA service as Source. It is then not possible for XenDesktop to broker a connection to the virtual desktop in question, and the virtual desktop becomes a wasted resource. If communication fails for any reason, the VDA is said to have failed to register with a controller.
This state is referred to as the VDA being registered with a controller. XenDesktop relies upon a software component installed on each virtual desktop (the Virtual Delivery Agent) being in communication with one of the controllers in your XenDesktop site. This article contains information about Troubleshooting Virtual Delivery Agent Registration with Controllers in XenDesktop. Citrix Virtual Apps and Desktops, formerly XenDesktop, fits the enterprise need to bring both VDI and apps into a user-centric experience.
0 kommentar(er)
