Joining new DDC to Multi-Zone CVAD Site fails

Joining new DDC to Multi-Zone CVAD Site fails

book

Article ID: CTX465177

calendar_today

Updated On:

Description

New DDC join process to a multi-zone CVAD site (spread across different datacenters) fails. This happens at the step when each service on the new DDC tries to register with Citrix Configuration service.

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

Set the below registry value on the new DDC to be joined and restart the Citrix Configuration Service - 

Location : HKLM\Software\Citrix\Config
Name : IsmInitialSuspensionDurationSeconds 
Type : Reg_Dword
Value : 60 (or a suitable value matching with the number of DDCs in the site and the latency between the DDC where the Studio is running and the other DDCs).

IMPORTANT: The HKLM\Software\Citrix\Config registry key does not exist so it has to be created manually (this note was added to avoid a confusion with existing HKLM\Software\Citrix\Configuration key which is not applicable to this scenario).

Problem Cause

The suspension period of a DDC after not giving the site details was short. Due to this, the same DDC was contacted again after the suspension period was over. Increasing the suspension period forced the new Broker to contact another DDC in the site and resolved the issue.
Powered by Wolken Software