The Virtual Desktop is Unable to Register with Controllers in Multiple Domain Environments
The Virtual Desktop is Unable to Register with Controllers in Multiple Domain Environments The Virtual Desktop is Unable to Register with Controllers in Multiple Domain Environments
Citrix states:
The Virtual Desktop is Unable to Register with Controllers in Multiple Domain Environments
productFamilyKey3 = "xd"; topics3 = "General"; productFamilyKey = productFamilyKey3.replace("/","--") + "/"; topics = topics3.replace("/","--") + "/";
Symptoms
When the Active Directory (AD) account for a desktop is in a different domain from the farm organizational unit (OU), the desktop always appears as "Not registered" in the Access Management Console.
The following error appears in the Windows Event Log on the desktop computer:
Event Type: Error
Event Source: Citrix Desktop Delivery Controller
Event Category: None
Event ID: 1190
User: N/A
Computer: <Desktop machine name>
Description: Unauthorized request received from <Controller domain>\<Controller machine name>$.
This occurs on Windows 2000 Native and Windows 2003 Active Directory deployments.
Cause
One cause of these symptoms is that the controller communicating with the Virtual Desktop Agent is not a member of the Controllers group in the farm OU. This should be checked first.
The cause discussed in this article is that the Controllers security group in the farm OU has an inappropriate scope. This cause is specific to cross-domain deployments.
The Controllers group contains the accounts of all controllers in the farm. It is used by the Virtual Desktop Agent to perform access checks on all communication received from controllers. If the Controllers group is configured so that it cannot be used for access checks on other domains, the registration of the Virtual Desktop Agent with the controller fails.
When the Active Directory Configuration Wizard is used to create the farm OU, the Controllers security group is created with a scope of Domain Local. Domain Local groups cannot be used to perform access checks on other domains.
Note: In Windows 2000 mixed mode forests, the Active Directory Configuration Wizard creates the group with a scope of Global and therefore operates correctly.
Resolution
Create the farm OU manually or modify the Controllers group after creation using the Active Directory Configuration Wizard. Details on how to create the OU and choose the appropriate scope for the Controllers group can be found in Knowledge Center article CTX117262 – How to Manually Configure an Organizational Unit in Active Directory for use by XenDesktop.
Note that in order to modify a group scope from ‘Domain Local’ to ‘Global’, the group must first be changed from ‘Domain Local’ to ‘Universal’ and then from ‘Universal’ to ‘Global’. Restart the Desktop Delivery Controller after making the change to the group scope.
This document applies to:
User login
Who's new
- japhabept
- Rullydery
- eagenorce
- rittaarier
- swasseZex