Xendesktop Domain Controller
It selects one of the controllers specified in the policy which lists the controllers in site 2.
Xendesktop domain controller. The xendesktop controller validates the user credentials with a domain controller. After a successful validation the xendesktop controller checks which resources have been published to this user within its database. To use the xendesktop setup wizard in a registry based installation where no farm ou is configured in ad complete the following steps.
I would like to install xendesktop on an active directory domain controller and came across the following excerpt in the xendesktop installation guide. Staying on the server selected to be the desktop controller navigate to the location of the xendesktop installer media and launch using autoplay. Do not change the computer name or the domain membership of a delivery controller after the site is configured.
These credentials are validated against domain controller by xml service on delivery controller. Deployments in which the user accounts and computer accounts exist in domains in a single active directory forest. This does not affect the domain functional level.
Requirements for xendesktop a domain controller running active directory. When the vda successfully registers with a controller in site 2 it receives the site 2 listofddcs and policy information which has auto update enabled by default. This does not affect the domain functional level which can still be windows 2000 native or higher.
By pre populating the listofsids the resolution from dns names to sids can be skipped. Install the xendesktop setup wizard. The vda ignores the list of controllers it receives because auto update is disabled.
If using a service account to install the desktop controller ensure that the user account has elevated. Before the auto update feature was introduced in xenapp and xendesktop 7 6 the listofsids was used to reduce the load on domain controllers. To use policy modeling the domain controller must be running on windows server 2003 to windows server 2012 r2.