MOSS Search – Customer Proof of Concept Scoping and Typical Tasks

Hi all,

There are a lot of customers today that want to engage in a Proof of Concept or Pilot with MOSS 2007 Search. These customers would like to setup MOSS Search, configure it, index and crawl all their content and then present the results to their end users. The great thing about MOSS Search is that it is easy to setup MOSS and configure the Search to allow customers to see how this works in their environment with their content.

So I get pulled in a lot to scope out Pilots or Proof of Concepts for customers around MOSS 2007 Search. Below, I have included a sample on a typical MOSS 2007 Search POC. At the beginning, I have mentioned some of the areas that I like to investigate before starting to scope the POC.  These questions can be asked from the customer before the POC starts. Once you have these answers, then those answers will then decide how long the POC might last, what work needs to be done, what the success factors are and what the tasks are in each week.

Hope that helps,

 Discussion points for the pre-POC call:

  • What is their current SharePoint or CMS infrastructure/deployment today? Do they want to search any of these systems?

  • What is their Authentication/Authorization requirements for this POC? 

  • Do they have any database content that they want to search in MOSS?  

  • What type of hardware, network, load balancing system do they have that can be used for the POC?

  • Can we install Office 2007 Client bits on some client hardware for the POC?

  • Where is your majority of content? Web sites? SharePoint sites? File system? Exchange folders?  Lotus Notes?  Other areas?  

  • What are the type of content you have? Office Documents? PDFs? Images? Videos? Others?

  • Do they want to index and search any back end applications?  

  • Where else can we point MOSS to, for indexing and searching of content? SAP? Siebel? PeopleSoft? ASP.Net applications? Other databases? 

  • What is the success factor for this POC?

  • What are the requirements around people search?

  • Any already existing search products today?

  • Any requirements around presentation of results to end users?

  • Other questions that will determine the tasks for the POC

 Here is a sample MOSS Search POC task breakdown:

  • Installing MOSS and Office 2007

  • Setting up SSP, Web Applications, and Site Collections

  • Setting up Authentication and Authorization

  • Importing User Profiles into MOSS for index/searching

  • Building Site Collections and sites and assigning users to these

  • Indexing HTTP/SharePoint content in MOSS

  • Setting up the Search site to return results

  • Configuring Search web parts and other search related areas

  • Setting up and creating BDC definitions for external content to be searched such as SAP or Siebel

  • Configuring search to include BDC data

  • Customize the Advanced Web Part and/or add People Search to MOSS

  • Build MOSS master pages, content types and page layouts

  • Create styles, import images and build the look and feel of MOSS

  • Have BDC and People Search configured and working

  • Setup Keywords for the content

  • Setup up Best Bets

  • Modify the synonyms and thesaurus for Search

  • Write web parts for custom queries and custom searches

  • Write other web parts as needed

  • Work on relevancy of content

  • Setup searching of other data such as PDF

  • Customize search reports

  • Improve search performance

  • Build XML and XSLT for custom results

  • Other MOSS related areas

  • POC Closure and Recap

Comments (11)

  1. Qi says:

    The thesaurus doesn’t work. I went into tsenu, tseng and tsneu xml files in both the root and the application directories, un-commented out, created some synonyms, and restarted the search service. There seems to be absolutely no mention of thesaurus in MOSS 2007 help documentation.

  2. Beginning Wednesday, February 14th, TechNet will launch the Plan, Deploy and Manage Microsoft Search

  3. bob says:

    Qi – are you using a custom query via FullTextSqlQuery or the default search interface (search center) ?  If you’re using the latter, it could be that the search core results web part does not generate the SqlFt statements required to use the thesaurus.  Can anyone confirm ?

  4. Hi Mike,

    I am making a work of conclusion of the graduation about recovery of information using BDC of SharePoint. And I have some subjects on how it is the operation of the indexation part and search. They are them:

    Which model of recovery of information done use?

    How is the process of generation of the indexation terms?

    To the end of the indexation with the terms are stored?

    In what algorithm the search system is based?



  5. ramakrishna says:

    check out my blog for Customer Proof of Concepts Tricks, Tips and Links

  6. Ron says:

    Mike – I work for a partner and I will be executing a Search POC for a client next week. This will be my third POC, but the first time that I’ll need to set up a Siebel BDC. Can you point me to some resources for configuring the Siebel BDC? I’m having difficulty finding information on this. Thanks – Ron

  7. Saurabh Mishra says:

    Is it possible to search on the same keywords and best bets across various site collections?

  8. dasy says:

    We have a POC site set up for our customer. Almost looks great. The issue is, the customer is using Sharepoint’s document conversion to publish a good bit of content. They want the search results to show the search term highlighted in the summary portion of the search core results. This works great for the shorter articles, but for their longer articles it does not show the summary at all. ANY idea of what is going on or where we could look for an answer would be greatly appreciated.

  9. shrinivas says:

    Please give us MOSS project best and recommneded practices, we have an upcomimg MOSS application coming up

  10. Devanathan says:

    Please provide some screen shots that related to the task breakdown so that it will be easy for the us to identify what we need to do.


Skip to main content