546 Part II Administrating and Configuring Your Implementation type. Then, if you run a search query against that search scope, all content based on the content type of Document will be returned in the search results. Search scopes can be created either through the Search Settings configuration page in Shared Services for an entire Web application or through the Search Scopes configuration on the root site of a site collection. For example, if you’d created a content type, Teamsta- tus, for Team Status reports and then wanted the ability to be able to search explicitly on Team Status reports for team members, you could establish a search scope for that con- tent type. To create a search scope on the root site (Litware) of the Litware site collection and base the search scope on the Teamstatus content type, do the following: Note You must be an administrator on the server to perform this action. 1. Open the Site Settings page for the root site and click the Search Settings link under Site Collection Administration. 2. Ensure that the Enable Custom Scopes And Search Center Features checkbox is selected as shown in Figure 15-29. Figure 15-29 Enabling custom search scopes on a site 3. Go back to the Site Settings page and click the Search Scopes link under Site Col- lection Administration to open the View Scopes page. Chapter 15 Managing Content Types 547 4. From the toolbar on the View Scopes page, click New Scope. 5. On the Create Scope page, shown in Figure 15-30, type a name for the search scope in the Title box, in this case Forms, along with a description. Figure 15-30 Create Scope configuration page 6. In the Display Groups section of the New Scope page, select both the Search Drop- down and Advanced Search check boxes. Selecting Search Dropdown includes the custom search scope name in the search drop-down list, as shown in Figure 15-31. Figure 15-31 Search Dropdown including content type search scope 548 Part II Administrating and Configuring Your Implementation Selecting the Advanced Search option includes the custom search scope name on the Advanced Search page as an additional scope that you can use in your search queries, as shown in Figure 15-32, in this case Forms. Figure 15-32 Advanced Search page including a content type search scope 7. Click OK to return to the View Scopes page. 8. Back on the View Scopes page, locate the Forms search scope and, from the Forms contextual drop-down menu, select Edit Properties and Rules. 9. On the subsequent Scope Properties and Rules page, click on New Rule. 10. On the Add Scope Rule page, in the Scope Rule Type section, select the Property Query option. 11. In the Property Query section under the Add Property Restrictions list, select Con- tentType, as shown in Figure 15-33. Chapter 15 Managing Content Types 549 Figure 15-33 Select content type for a query parameter 12. In the Equal To field, type the content type you want to run a search against and then click OK. In this case, type Teamstatus so that you can search for Team Status reports entered by employees. SharePoint updates the new search scope and index content for that scope in the next scheduled crawl update. 13. Type the query on the Advanced Search page to run the search against the new Forms search scope. Note You can also run the search from the drop-down search box on the home page of the Litware site. On the Advanced Search page, the new content type search scope, Forms, is included, and you can add search criteria against this new search scope. 14. In the All Of These Words box, type the name Christine. 15. Under Narrow The Search, Only The Scope(s), select the Forms search scope check box. Click Search. 550 Part II Administrating and Configuring Your Implementation The search returns two records, both of which are Team Status reports. One report has been submitted by Christine Koch; the other report has been submitted where Christine Koch is the Manager. (See Figure 15-34.) Figure 15-34 Search results based on a content type search scope This example demonstrated how you can run search queries against content types. The Teamstatus content type was used to create a custom search scope and run a query on any forms associated with that content type. This is just one example of how you can use content types to enhance your search capabilities. Chapter 15 Managing Content Types 551 Summary This chapter has provided an overview of content types and demonstrated how you can effectively create and implement content types to more effectively manage your content and documents. You have learned how to configure content types for use throughout SharePoint Server 2007 sites and lists, including associating custom metadata and cus- tom settings to content types, such as workflow. You have also seen how content types can be used to manage e-mail messages and extend search functionality. Part III Search, Indexing, and Shared Services Provider Chapter 16: Enterprise Search and Indexing Architecture and Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555 Chapter 17: Enterprise Search and Indexing Deployment . . . . . . . . . . . 619 Chapter 18: Administrating Shared Services Providers . . . . . . . . . . . . . 637 [...]... the search engine that is installed with a Windows SharePoint Services 3.0—only implementation and an SharePoint Server 2007 implementation Table 16- 1 Feature Comparison between Windows SharePoint Services 3.0 and SharePoint Server 2007 Feature Windows SharePoint Services 3.0 SharePoint Server 2007 Content that can be indexed Local SharePoint content SharePoint content, Web content, Exchange public folders,... for including a content item in the result set Chapter 16 Enterprise Search and Indexing Architecture and Administration Search indexes the anchor text from the following elements: ■ HTML anchor elements ■ Windows SharePoint Services link lists ■ Office SharePoint Portal Server listings ■ Office Word 2007, Office Excel 2007, and Office PowerPoint 2007 hyperlinks URL Surf Depth Important or relevant content... big improvement in SharePoint Server 2007 is the Continuous Propagation feature Essentially, instead of copying the entire index from the Index server to the Search server (using SharePoint Portal Server 2003 terminology here) every time a change is made to that index, now you’ll find that as information is written to the Content Store on the Search server (using SharePoint Server 2007 terminology now),... Simple Syndication (RSS) from result set Yes Yes The “Did You Mean….?” prompt Yes Yes Chapter 16 Enterprise Search and Indexing Architecture and Administration Table 16- 1 Feature Comparison between Windows SharePoint Services 3.0 and SharePoint Server 2007 Feature Windows SharePoint Services 3.0 SharePoint Server 2007 Duplicate collapsing Yes Yes Scopes based on managed properties No Yes Best Bet No Yes... is not propagated to the query servers Instead, it is directly written to the SSP’s Search SQL database ■ There are no registry entries to manage, and these configurations are hardcoded Propagation uses the NetBIOS name of query servers to connect Therefore, it is not a best practice to place a firewall between your Query server and Index server in SharePoint Server 2007 due to the number of ports... up correctly 577 578 Part III Search, Indexing, and Shared Services Providers Figure 16- 8 Edit Shared Services Provider page—lower portion Managing Index Files If you’re coming from a SharePoint Portal Server 2003 background, you’ll be happy to learn that you have only one index file for each SSP in SharePoint Server 2007 As a result, you don’t need to worry anymore about any of the index management... Architecture and Components of the Microsoft Search Engine Search in SharePoint Server 2007 is a shared service that is available only through a Shared Services Provider (SSP) In a Windows SharePoint Services 3.0-only implementation, the basic search engine is installed, but it will lack many components that you’ll most likely want to install into your environment Table 16- 1 provides a feature comparison... source in each SSP—the Local Office SharePoint Server Sites content source—Search provides two default crawl rules that are hard coded and can’t be changed These rules are applied to every http://ServerName added to the default content source and do the following: ■ Exclude all aspx pages within http://ServerName ■ Include all the content displayed in Web Parts within http://ServerName For all other content... to individual sites in your organization SharePoint Server 2007 allows you to set primary (first-level), secondary (second-level), and tertiary (third level) sites, as well as sites that should never be considered authoritative Determining which sites should be placed at which level is probably more art than science and will be a learning process over time 563 564 Part III Search, Indexing, and Shared...5 56 Part III Search, Indexing, and Shared Services Providers Understanding the Microsoft Vision for Search The vision for Microsoft Search is straightforward and can be summarized in these bullet points: ■ Great results every time ■ Search integrated across familiar applications ■ Ability to index content regardless of where it is located One difficulty with SharePoint Portal Server 2003 . 16- 1 Feature Comparison between Windows SharePoint Services 3.0 and SharePoint Server 2007 Feature Windows SharePoint Services 3.0 SharePoint Server 2007 Content that can be indexed Local SharePoint content SharePoint. Administration Table 16- 1 Feature Comparison between Windows SharePoint Services 3.0 and SharePoint Server 2007 Feature Windows SharePoint Services 3.0 SharePoint Server 2007 560 Part III Search,. elements ■ Windows SharePoint Services link lists ■ Office SharePoint Portal Server listings ■ Office Word 2007, Office Excel 2007, and Office PowerPoint 2007 hyperlinks URL Surf Depth Important or