Microsoft Office SharePoint compatibility with Single Label Domains, Disjointed Namespaces, and Discontiguous Namespaces
This article describes the compatibility of Microsoft Office SharePoint with Single Label Domains, Disjoint Namespaces, and Discontiguous Namespaces.
Warning The information in this article has not been confirmed or tested by Microsoft. Use the information in this article at your own risk. Microsoft provides this information "as is" without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
Single Label DomainsFor a description of Single Label Domains, see the Single Label Domains topic in the Microsoft DNS Namespace Planning Solution Center.
Disjoint NamespacesFor a description of Disjoint Namespaces, see the Disjoint Namespaces topic in the Microsoft DNS Namespace Planning Solution Center.
Discontiguous NamespacesFor a description of Discontiguous Namespaces, also known as a non-contiguous namespaces, see the Discontiguous Namespaces topic in the Microsoft DNS Namespace Planning Solution Center.
Microsoft Office SharePoint
Single Label DomainsBecause the use of SLDs is not a recommended practice, SharePoint products are not extensively tested in this scenario. Therefore, there may be incompatibilities when SharePoint products are implemented in an SLD environment: this includes single label domains or single label forests, in either the SharePoint server's domain or the SharePoint end user's domain. Although most features will work, it is known that the Profile Import feature will not work against an SLD.
Microsoft SharePoint Server 2010 has the known following incompatibilities:
- Cannot import users from Active Directory containers that contain space in a single label domain.
- Configuring user profile import in a single label domain environment produces an error.
- Microsoft SharePoint Server 2016
- Microsoft SharePoint Server 2010
- Microsoft Office SharePoint Server 2007
- Microsoft Office SharePoint Server 2003
Disjoint NamespacesWhen you install the FAST Search Server 2010 for SharePoint in a disjointed network environment, the Post Setup Configuration of FAST Search Server 2010 for SharePoint fails. A supported hotfix is available from Microsoft. For more information see Microsoft Knowledge Base Article http://support.microsoft.com/kb/2308915.
Applies to:This article also applies to Microsoft SharePoint Server 2016.
Article ID: 2379373 - Last Review: 03/11/2016 21:12:00 - Revision: 9.0
Windows Server 2008 R2 Datacenter, Windows Server 2008 R2 Enterprise, Windows Server 2008 R2 Foundation, Windows Server 2008 R2 Standard, Microsoft SharePoint Server 2013, Microsoft SharePoint Server 2010, Microsoft Office SharePoint Server 2007, Microsoft Office SharePoint Portal Server 2003
- kbinfo kbpubtypekc kbsurveynew kbdomain KB2379373