SharePoint 2010 user profile synchronization on a ‘Standalone’ environment

http://support.microsoft.com/kb/983061/ 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: http://technet.microsoft.com/en-us/library/ff681014.aspx…


SharePoint with SQL replication scenario

Some SQL Server 2008 technologies, such as transactional replication, cannot be used with SharePoint Products and Technologies because the replication technology requires that a database have a primary key column on all tables. Before you implement replication technologies, ensure that the technology is supported for both SQL Server 2008 and Office SharePoint Server 2007. reference:…


[Support Policy] Considerations for server-side Automation of Office

http://support.microsoft.com/kb/257757 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….


[Support Policy] Support policy for Microsoft Exchange APIs with the .NET Framework applications

http://support.microsoft.com/kb/813349 API DLL Name Managed Code Support Policy System.Web.Mail   Supported WebDAV   Supported WMI   Supported CDOSYS CDOSYS.DLL Supported, but System.Web.Mail is recommended CDOEXM CDOEXM.DLL Supported by using a COM interop assembly EXOLEDB   Supported by using a COM interop assembly CDOEX CDOEX.DLL Supported by using a COM interop assembly CDO 1.2x CDO.DLL Not…


[Support Policy] Microsoft Office SharePoint compatibility with Single Label Domains, Disjointed Namespaces, and Discontiguous Namespaces

http://support.microsoft.com/kb/2379373 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…


[Support Policy] Supported and unsupported scenarios for working with custom site definitions and custom area definitions in SharePoint 2003, 2007 and 2010

http://support.microsoft.com/kb/898631 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…


[Support Policy] Supportability of a wildcard inclusion managed path at the root of a web application

http://support.microsoft.com/kb/2590492 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…


[Support Policy] Support for changes to the databases that are used by SharePoint

http://support.microsoft.com/kb/841057 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…

2