Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Administrators are unable to entitle users within another trusted domain (75279)

Last Updated: 1/19/2023Categories: TroubleshootingTotal Views: 8269Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

Administrators are not able to entitle users from another domain following standard practice and the connection server reports the following error:

"There was an error accessing the child domain"

Purpose

To highlight an issue with naming conventions with forest root and tree root domains that fit into Microsoft's definition of a child domain.

Cause

Within the Horizon dashboard, some domains are inaccessible if the domain nomenclature does not adhere to Microsoft Specifications.

As an example:

Connection Broker resides on contoso.com.

You try to entitle a user from east.contoso.com

The tree root domain, east.contoso.com was named in the manner of a child domain.

There is no parent-child relationship between the two domains.

East.contoso.com will not be accessible by the connection server, interpreted as a child domain.

In summary, the customer has an externally trusted domain (east.contoso.com) with DNS/X500 names that make it look like a child domain of the broker's forest root domain (contoso.com). In this scenario, View passes the domain context to an MSFT API to attempt to bind to the external domain. This mechanism used by View to bind to the domain is unable to determine that east.contoso.com is outside the broker's forest

This is a situation that can result from a merger or acquisition of an organization or restructuring.

Resolution

To resolve this issue, please adhere to Microsofts naming standards and conventions.
See  Assigning DNS Names to Create a Domain Hierarchy for MSFTs naming recommendation for domains.

Related Information

Configuring Domains and Trust Relationships

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
对运行 open-vm-tools 的 Linux 虚拟机执行挂起客户机操作可能会失败 (74722)

KB
•
NCP 2.5.0 がセキュリティ ポリシーの更新を NSX-T DFW に適用しないことがある (76650)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Horizon View

VMware Horizon

Related Versions:

VMware Horizon View 6.x Extended Support

Take Our Survey

Support Assistant