No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


There hasn’t configured the global catalog in the AD causes the users can’t login in the VM via the WI

Publication Date:  2012-11-13 Views:  135 Downloads:  0
Issue Description
After the administer distributing users for the “preassinged” type of virtual machine in the ITA system successfully, the users login in their own virtual machines via the WI but there prompting  the error “connecting failed”, and they can’t login in their virtual machines.
Alarm Information
Handling Process
1. Login in the AD server via the “administrator” account, select “Start > All Programs > Administrative Tools > Active Directory Sites and Services”.
2. Respectively, right-click the “NTDS Settings” in the name of the spare AD computer, select “Properties”, and then in the ejecting window, select the tab “General” and choose the “Global Catalog” . Then we have configured the global catalog.
3. Restart the user’s virtual machine, and the user can login in the virtual machine via the WI.

Root Cause
1. After creating the virtual machine successfully and distributing the users normally, but the users can’t login normally. Check the associated information between the virtual machines and the users on the DDC server, open “desktop delivery controller”, we find the registering status of the new associated virtual machine is “unregistered”, while it should be “idle” or “used” normally.
2. Login in the virtual machine via OmsPortal to check the system logs, we find the event ID “1215” is wrong, its source is “Citrix Desktop Service”. Open the detail information of the error, it prompts “Failed to start WCF services, can’t find the global catalog in the“””.

3. “Can’t find the global catalog in the domain” is related to the fact that there hasn’t configured the global catalog in the “Properties” of the “NTDS Settings” in the AD server. We check the AD server and find there hasn’t configured the global catalog property indeed.