Studio couldn’t be launched if one Delivery Controllers goes down

A rapid post about a really strange situation I’ve encountered at a customer site. On a XenDesktop 7.5 site with 2 or more delivery controllers we have detected that if one DC goes down, the site administration via Studio or Powershell is not possible from the other Delivery Controllers.

Even if I’ve encountered the problem on a XD 7.5, the problem exists in version 7.6.

This is due to the status of the Delivery Controller in the site database. In order to fix this problem there is 2 solutions:

• Citrix is currently working on a patch for XenDesktop 7.5 and 7.6
• You could set the status of the failed DC on the SQL database with this script:

UPDATE [SiteDatabase].[StorefrontSchema].[Services] SET CurrentState=0 WHERE MachineName LIKE ‘FailedDC’

UPDATE [SiteDatabase].[ADIdentitySchema].[Services] SET CurrentState=0 WHERE MachineName LIKE ‘FailedDC’

UPDATE [SiteDatabase].[ConfigLoggingSiteSchema].[Services] SET CurrentState=0 WHERE MachineName LIKE ‘FailedDC’

UPDATE [SiteDatabase].[ConfigurationSchema].[Services] SET CurrentState=0 WHERE MachineName LIKE ‘FailedDC’

UPDATE [SiteDatabase].[DAS].[Services] SET CurrentState=0 WHERE MachineName LIKE ‘FailedDC’

UPDATE [SiteDatabase].[DesktopUpdateManagerSchema].[Services] SET CurrentState=0 WHERE MachineName LIKE ‘FailedDC’

UPDATE [SiteDatabase].[EnvTestServiceSchema].[Services] SET CurrentState=0 WHERE MachineName LIKE ‘FailedDC’

UPDATE [SiteDatabase].[HostingUnitServiceSchema].[Services] SET CurrentState=0 WHERE MachineName LIKE ‘FailedDC’

UPDATE [SiteDatabase].[Monitor].[Services] SET CurrentState=0 WHERE MachineName LIKE ‘FailedDC’

GO

You should replace SiteDatabase and FailedDC with the corresponding values.

Hope this help 😉

Sam