Partager via

The Infrastructure Update

  • Article

The Infrastructure Update is a set of product improvements and prescriptive guidance for Windows SharePoint Services 3.0 and Microsoft Office SharePoint Server 2007. Our favorite features (and the ones we’ve written the most about) include federated search, Kerberos authentication for the SSP infrastructure, and content database ID and change log retention.

Federated search

An important feature of the Infrastructure Update is support for federated search, which is also included in Microsoft Search Server 2008. Federated search enables end users to issue queries that search multiple sources and display results in separate Web Parts on a single search results page. Displaying the results in separate Web Parts can help users distinguish where content is located, making it easy to identify which content is local. Understanding where content is located can also help users determine which results are most likely to be relevant. Using federated search enables you to provide more extensive query results for users without having to devote server resources to crawling and indexing content.

For more information about federated search, see Plan for global enterprise search. The operations content for federated search in Microsoft Office SharePoint Server is coming soon, but for now, feel free to refer to Working with federation, written for Microsoft Search Server.  

Kerberos authentication for the SSP infrastructure

Another important feature of the Infrastructure Update is support for configuring the Office SharePoint Server 2007 Shared Services Provider (SSP) infrastructure for Kerberos authentication. The Infrastructure Update includes a new, custom-format Service Principal Name (SPN) for Kerberos authentication for the SSP infrastructure. For Kerberos authentication to work correctly, you must create SPNs in Active Directory. If the services to which these SPNs correspond are listening on non-default ports, the SPNs should include port numbers. This is to ensure that the SPNs are meaningful. It is also required to prevent the creation of duplicate SPNs. When you use Kerberos authentication, accurate authentication functionality is dependant in part on the behavior of the client that is attempting to authenticate using Kerberos. The browser is the client used when browsing to a Web page in an Office SharePoint Server 2007 Web application. When Office SharePoint Server 2007 performs tasks such as crawling the local Office SharePoint Server 2007 content sources or making calls to the SSP infrastructure, the .NET Framework is functioning as the client. When a client attempts to access a resource using Kerberos authentication, the client must construct an SPN to be used as part of the Kerberos authentication process. If the client does not construct an SPN that matches the SPN that is configured in Active Directory, Kerberos authentication will fail, usually with an “access denied” error. In a farm running Office SharePoint Server 2007, by default the .NET Framework does not construct SPNs that contain port numbers. This is why Search cannot crawl Web applications using Kerberos authentication if those Web applications are hosted on IIS virtual servers that are bound to non-default ports. This is also why Kerberos authentication cannot be correctly configured and made to work for the SSP infrastructure unless the Infrastructure Update is installed.

To configure the Office SharePoint Server 2007 SSP infrastructure for Kerberos authentication you have to:

  • Register new custom-format SPNs for your SSP service account in Active Directory.
  • Run the Stsadm command-line tool to set the SSP infrastructure to use Kerberos authentication.
  • Add a new registry key to all of your servers running Office SharePoint Server 2007 to enable the generation of new custom-format SPNs.
  • Confirm Kerberos authentication for root-level shared Web service access.
  • Confirm Kerberos authentication for shared Web service access at the virtual directory level.

For more information about Kerberos authentication for Office SharePoint Server 2007, see Configure Kerberos authentication (Office SharePoint Server).

For more information about authentication for SharePoint Services 3.0 and Office SharePoint Server 2007, see the Authentication Resource Center for SharePoint Products and Technologies.

Content database IDs and change logs

If you are running the Infrastructure Update, the identifier (ID) of each content database is retained when you restore or reattach the database by using built-in tools. Change logs are also retained by default in some cases. Default change log retention behavior when using built-in tools is as follows:

  • The change logs for all databases are retained when you restore a farm.
  • The change log for a content database is retained when you reattach the database.
  • The change log for a content database is not retained when you restore just the content database

What does this mean to you? Fewer full crawls after restoring or reattaching. When a database ID and change log are retained, Search continues crawling based on the regular schedule defined by crawl rules—if an incremental crawl is scheduled, an incremental crawl is what you get.

If you’d like to manually manage how change logs and content IDs are retained for a specific content database, see the following articles:

Restore: Stsadm operation (Office SharePoint Server)

Addcontentdb: Stsadm operation (Office SharePoint Server)

Other changes 

There are many other improvements that are part of the Infrastructure Update, including:

  • Scalability and performance improvements to support Search incremental crawl.
  • A new Search Administration page to streamline administration. 
  • Improvements in the time it takes to patch and upgrade Windows SharePoint Services 3.0 sites.
  • Stability improvements when upgrading or patching a farm with a large number of host-header named site collections.
  • The Business Data Catalog (BDC) can be configured to explicitly allow anonymously authenticated users to access the BDC.

For a full list of the topics updated to include information about the Infrastructure Update, see:

As you can see, we think the Infrastructure Update has great features in it, and strongly encourage you to install it. For information about downloading and installing, see the Updates Resource Center for SharePoint Products and Technologies.

Douglas Goodwin, Writer
SharePoint Server UA team

Comments

  • Anonymous
    January 01, 2003
    PingBack from http://kintespace.com/rasxlog/?p=1604

  • Anonymous
    October 14, 2008
    One thing to add here is; if you apply the WSS Patch, make sure you apply the Infrastructure Patch and vice versa as you will begin to see erros in both SharePoint and the Event Viewer.  Most of what we have seen has revolved around Search.

  • Anonymous
    January 16, 2009
    I have applied Project Server Infrastructure update and August Cumulative update. Now I am having more problems than earlier...

  1. On PWA home page, I can't have remiders webpart.
  2. From Manage Queue, I can not see any job information.
  3. I can not do force checkin, it throws an error. In server logs, I also found erros such as System.Data.SqlClient.SqlError: Could not find stored procedure 'MSP_WEB_PWS_GetRiskListIds' System.Data.SqlClient.SqlError: Procedure or function MSP_ProjQ_Get_Status_Of_Jobs_List has too many arguments specified. Any help in this regard is much appreciated.