Consider the following scenario:

• You run Microsoft SharePoint Server 2010 in a single-server environment. (This is known as a stand-alone installation.)
• You try to start the User Profile Synchronization service.
• You provide a password for the NT Authority\Network Service account.

In this scenario, the User Profile Synchronization service does not start.

reference: https://technet.microsoft.com/en-us/library/ff681014.aspx

How to check server role of SharePoint:

HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\14.0\WSS\ServerRole

-SINGLESERVER : Stand-alone
-WFE : Farm Stand-alone
-APPLICATION : Farm Complete

reference: https://technet.microsoft.com/en-us/library/cc298578.aspx

All current versions of Microsoft Office were designed, tested, and configured to run as end-user products on a client workstation. They assume an interactive desktop and user profile. They do not provide the level of reentrancy or security that is necessary to meet the needs of server-side components that are designed to run unattended.

Microsoft does not currently recommend, and does not support, Automation of Microsoft Office applications from any unattended, non-interactive client application or component (including ASP, ASP.NET, DCOM, and NT Services), because Office may exhibit unstable behavior and/or deadlock when Office is run in this environment.

Single Label Domains

Because 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.

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.

Affected Office SharePoint products include the following

• Office SharePoint Server 2010 (https://office.microsoft.com/en-us/sharepoint-server-help/getting-started-with-sharepoint-server-2010-HA010371435.aspx?CTT=3)
• Office SharePoint Server 2007 (https://office.microsoft.com/en-us/sharepoint-server-help/introduction-to-microsoft-office-sharepoint-server-2007-HA010173217.aspx?CTT=1)
• Office SharePoint Server 2003 (https://office.microsoft.com/en-us/technet/overview-of-sharepoint-portal-server-2003-HA001164862.aspx?CTT=1)
  
  

Unsupported scenarios

When you work with custom site definitions or custom area definitions, the following scenarios are not supported:

• You modify one of the default site definitions or one of the default area definitions that are included in SharePoint.
  
  We do not support modifying the default set of site definitions or area definitions that are installed when you install SharePoint. Additionally, we do not support modifying the .xml files or the .aspx files in the default site definition or in the default area definition.
• You modify a custom site definition or a custom area definition after you deploy the custom site definition or the custom area definition.
  
  We do not support modifying a custom site definition or a custom area definition after you create a new site or a new portal area by using that site definition or area definition. Additionally, we do not support modifying the .xml files or the .aspx files in the custom site definition or in the custom area definition after you deploy the custom site definition or the custom area definition.
• You modify the Webtemp.xml file or the Webtempsps.xml file that is located in the following folder:
  Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\Template\LCID\XML
  
  or
  
  Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\LCID\XML
  
  or
  
  Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\Template\LCID\XML
• We do not support modifying files that reside in the _layouts folder. We reserve the right to update these files in software updates or service packs at a later date. This may cause the custom changes to be lost. You must always back up files that you have changed so that you can restore them at a later date.

People picker is unable to resolve users in a trusted forest if the only domain controller SharePoint can access is read-only.

Any web application which does not have a site collection and web provisioned at the root (/) is not supported unless every site collection is a host header site collection in the web application.

Using a wildcard inclusion managed path at the root of a web application in WSS 3.0 and MOSS 2007 has limited support, it is recommended to migrate the affected sites away from this structure.

Using a wildcard inclusion managed path at the root of a web application in SharePoint Foundation 2010 or in SharePoint Server 2010 is not supported. This configuration is not explicitly blocked by the user interface or the command line tools, however there are several features in the products which will not work properly in this configuration.

This configuration is not supported even if the web application is using classic Windows authentication and will not use claims authentication in the future.

It is not supported to in-place upgrade a WSS 3.0 or MOSS 2007 farm which has a root wildcard inclusion managed path, however this is not explicitly blocked. It is advised to resolve this problem before attempting the upgrade. It is not supported to upgrade a WSS 3.0 or MOSS 2007 content database using the database attach method which was using a root wildcard inclusion managed path, although this is not explicitly blocked by the product.

Examples of unsupported database changes include, but are not limited to, the following:

• Adding database triggers
• Adding new indexes or changing existing indexes within tables
• Adding, changing, or deleting any primary or foreign key relationships
• Changing or deleting existing stored procedures
• Calling existing stored procedures directly, except as described in the SharePoint Protocols documentation (https://msdn.microsoft.com/en-us/library/cc339475.aspx)
• Adding new stored procedures
• Adding, changing, or deleting any data in any table of any of the databases for the products that are listed in the "Applies to" section
• Adding, changing, or deleting any columns in any table of any of the databases for the products that are listed in the "Applies to" section
• Making any modification to the database schema
• Adding tables to any of the databases for the products that are listed in the "Applies to" section
• Changing the database collation
• Running DBCC_CHECKDB WITH REPAIR_ALLOW_DATA_LOSS (However, running DBCC_CHECKDB WITH REPAIR_FAST and REPAIR_REBUILD is supported, as these commands only update the indexes of the associated database.)