Elczar Adame's Shared Points on SharePoint

Archive for August, 2008

Microsoft Office 14 Alpha?


Upgrading to Microsoft Search Server 2008


 

As I have mentioned in my previous piece, Microsoft Search Server 2008 (MSS) and Microsoft Search Server 2008 Express (MSSX) are built on Windows SharePoint Services 3.0. It is designed for an organization who wants to benefit from the power of search without having Microsoft Office SharePoint Server 2007. There are times, however, that we need to upgrade our existing MSS 2008 or MSSX 2008 to MOSS 2007, or moving our existing WSS 3.0 to MSS 2000 or MSSX 2008.

Before performing any upgrade process, however, it is recommended to read first the Microsoft Search Server 2008 Upgrade Path provided by Microsoft and consider the tables below.

The following are supported paths:

 

FROM

TO

Windows SharePoint Services 3.0 with Microsoft SQL Server

Microsoft Search Server 2008 or Microsoft Search Server 2008 Express with Microsoft SQL Server

Windows SharePoint Services 3.0 with Microsoft SQL Server Desktop Edition

Microsoft Search Server 2008 or Microsoft Search Server 2008 Express Microsoft SQL Express

Microsoft Search Server 2008 Express with Microsoft SQL Server

Microsoft Search Server 2008 with Microsoft SQL Server

Microsoft Office SharePoint Server 2007 with Microsoft SQL Server

Microsoft Search Server 2008 Express with Microsoft SQL Express

Microsoft Search Server 2008 with Microsoft SQL Express

Microsoft Search Server 2008 with Microsoft SQL Express

Microsoft Office SharePoint Server 2007 with Microsoft SQL Server

The following are unsupported paths:

 

FROM

TO

Microsoft Search Server 2008 or Microsoft Search Server 2008 Express BETA or RC

Microsoft Search Server 2008 or Microsoft Search Server 2008 Express RTM

Microsoft Office SharePoint Server 2007 or previous versions

Microsoft Search Server 2008 or Microsoft Search Server 2008 Express

Microsoft Search Server 2008 or Microsoft Search Server 2008 Express with Microsoft SQL Express

Microsoft Office SharePoint Server 2007

Microsoft Search Server 2008 or Microsoft Search Server 2008 Express with Microsoft SQL Server

 

Thanks…

Administering Microsoft Search Server 2008


 

Microsoft Search Server 2008 is distributed with significant features and key investment areas – including simplified installation process, enhance search administration interface, innovative federation capabilities, and performance enrichments. With its Search Administration dashboard, administering MSS 2008 becomes completely uncomplicated.

This piece will attempt to provide us the elements necessary to administer Microsoft Search Server 2008. Under the crawling section are:

 

Content Sources

Facility to manage content sources and crawls.

Crawl Rules

Facility to include or exclude paths from being crawled.

Crawl Log

Displays the crawled content status.

Default Content Access Account

Facility to provision an account to use as the default account when crawling content.

File Types

Facility to specify file types to include in the content index.

Reset All Crawled Content

Facility to erase the content index.

Crawler Impact Rules

Facility to define the number of documents to request simultaneously and the amount of time to wait between requests during an update of a content source.

Proxy and Timeouts

Facility to define the proxy server settings, timeout settings, and SSL certificate warning configuration.

Under the queries and results section are:

Authoritative Pages

Facility to specify authoritative Web pages. Authoritative pages are those that link to the most relevant information. Search uses this list to calculate the rank of every page in the index.

Federated Location

Facility to define simultaneous search capability in search content in the search index on this server, as well as in other locations, such as database systems, internet search engines and specific scopes on this server.

Metadata Properties

Facility to create and modify managed properties and map crawled properties to managed properties.

Server Name Mappings

Facility to define how URLs are shown in search results.

Search Result Removal

Facility to define the URLs to be removed from search results.

Under the usage reports section are:

Queries Report

Displays queries, top query origin site collection, queries per scope, and top queries.

Results Report

Displays search results top destination pages, queries with zero results, most clicked best bets, queries with zero best bets, and queries with low clickthrough.

Navigating to Search Administration page requires only two strides. First, let us open SharePoint 3.0 Central Administration > Application Management. Below is the illustration.

Search Service

Secondly, under the Search section of our Application Management page, click Manage Search Service. And there we are, we will be redirected to Search Administration dashboard. We could start now administering our Microsoft Search Server 2008.

Search Administration

Thanks…

Configuring Microsoft Search Server 2008


 

In my previous piece, I have demonstrated the process of deploying Microsoft Search Server 2008. To continue the process, we need to configure the search server. Below are the required and optional configurable items:

1. Required

 

Search Index Server

The server that will provide search indexing services.

Default Account for Services

Serves as the service account for the search service, the Help search service, and the Web application identity of the search administration site.

Search Center Account

It is used as the application pool account for the Search Center site.

Search Contact E-Mail

The e-mail address of the search server administrator.

Below is the illustration.

Required

2. Optional

 

Search Center Site

An option whether to create a Search Center site.

Index File Location

The path on the index server where the index will be located.

Search Services Administration Account

It is used for Web services, communication between services, and timer jobs in surrogate to the default account for services.

Database for Search Administrative Settings

The database used to store query logs and administrative settings associated with the search service.

Search Service Account

This is used as the log on identity of the Search Service surrogate to the default account for services.

Database for Search Service

The database used to store search-related data that frequently changes.

Help Search Service Account

It is used as the log on identity of the Help Search Service surrogate to the default account for services.

Database for the Help Search Service

The database used to store data for the service that indexes Help content.

SSL for Web Services

An option whether to use Secure Sockets Layer to help protect communications to and from servers using Web Services.

Below is the illustration.

Optional

Upon confirmation of the settings we have defined, the configuration process will proceed.

Configuring

After the configuration process, a Welcome to Microsoft Search Server 2008 page will be displayed.

Welcome

From the welcome page, we could now navigate to the Search Administration page.

Administration

Thank you very much.

Installing Microsoft Search Server 2008


 

By opening the Microsoft Enterprise Search 2008 site, we will be clutched by a statement that describes the essence of this technology: “Search doesn’t have to be complicated. You can deliver search solutions to your organization quickly and easily with Microsoft Search Server 2008.”

Microsoft Search Server 2008 (MSS) and Microsoft Search Server 2008 Express (MSSX) are built on Windows SharePoint Services 3.0. It is designed for an organization who wants to benefit from the power of search without having Microsoft Office SharePoint Server 2007. As a constituent of the huge spectrum of MOSS 2007, either MSS or MSSX is the right technology for an enterprise who only wants to have its information searchable. If we are running Windows SharePoint Services 3.0 and want to enjoy the power of enterprise searching, therefore, we need MSS or MSSX. Microsoft has provided us guide to compare and identify which search product is right for us.

NOTE: The same is the case of Microsoft Office Forms Server 2007 with MOSS 2007 and WSS 3.0 for InfoPath Form Services.

Before implementing Microsoft Search Server 2008, we primarily need to determine the hardware requirements, plan to deploy, plan for administrative and service accounts, plan to crawl content, plan the search experience, plan for redundancy, and plan for availability.

To upgrade our WSS 3.0 to MSS or MSSX, moreover, we need first to read the guide provided by Microsoft that presents instructions and considerations on the upgrade process. And to enable MSSX features in WSS 3.0, Mike Walsh has provided us a comprehensive guide.

Enough with the introduction and we will start our journey in installing Microsoft Search Server 2008.

1. Upon being prompted by the Start dialog, as illustrated below, let us click the Run the Search Preparation Tool under the Install section. This will check installation of prerequisites.

Start

2. After the completion of the first step, we will proceed with the installation by clicking the Install Search Server under the Install section. Notice that the installation process is almost the same with Microsoft Office SharePoint Server 2007 and Microsoft Office Forms Server 2007.

3. During the installation we will be prompted to provide our 25-character Product Key. Below is the illustration.

Key

4. Next is the facility where we need to identify the installation type. For demonstration purposes, we will select Advance installation. Below is the illustration.

Type

5. Next is the facility to define the Server Type. For our purpose, we will select Complete. It will install all components and we will give us the capability to add servers to form a farm. Below is the illustration.

Server Type

6. With the first few steps, we can now monitor the progress while it is installing. Below is the illustration.

Progress

7. Since MSS or MSSX runs on WSS 3.0, we will be prompted by a dialog box that directs us to run SharePoint Product and Technologies Configuration Wizard to complete its installation. Below is the illustration.

8. As illustrated below, we will also be prompted by a message box that some services will be restarted or reset during the configuration.

Message

9. Additionally, we will be asked to Connect to Server Farm. In our case, we will create a new server farm. Below is the illustration.

Connect

10. Before the configuration process, we need to specify the configuration database settings where Database Server, Database Name, and Service Account must be defined. Below is the illustration.

Settings

11. The configuration process could be monitored from the next dialog that will appear. Below is the illustration.

Configuring

12. Finally, we will be prompted by a dialog box that we have successfully configured our server. Below is the illustration.

Finish

With this we could now launch the SharePoint Central Administration and start performing necessary setting for our Microsoft Search Server 2008. Thanks you very much.

PHIWUG Newsletter – Released!


 

Port 445, the official newsletter of Philippine Windows Users Group, is now available. The newsletter, according to Jay-R Barrios, the President of PHIWUG, will serve as an information hub for the members and the entire technical community. Inside the first issue are:

1. President’s Corner where Jay-R Barrios welcomes everybody to the first edition of Port 445.

2. On On One With where Elczar Adame, the PHIWUG Vice President, featured his conversation with Maria Green, an IT PRO Evangelist for Microsoft Asia Pacific, on Microsoft’s programs for user groups, IT professionals, and developers.

3. Meet the Philippines MVPs where Jay Paloma, a former PHIWUG President, featured Philip and Joanne Ortiz, the Philipppines XBOX MVPs and SEA’s first MVP couple.

4. TechTalk where a Technology Solutions Professional : Windows Client of Microsoft Asia Pacific, Jay Paloma, discussed on Windows Vista Deployment Tools and Resources.

5. Certified where Mon Salvador, the Special Interest Group Head for Training and Certification, provided inputs in preparing and obtaining MCTS certification.

Download a copy here.

Thank you very much.

Moving MOSS 2007 Content Database by STSADM Command-Line Tool


 

Windows SharePoint Services 3.0 or Microsoft Office SharePoint Server 2007 implementation practically requires moving the content database from one environment to another – from development, to staging, to production. Microsoft has provided us several ways to do this. It could be done using Central Administration facilities, or by STSADM command-line tools. In this piece, I will complete the task using the later approach.

In our source server, let us do the following steps:

1. In the Command Prompt, let us change to the directory where the STSADM command-line tool is located. By default, it is on C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN.

2. The next step is to prepare our content database before moving it by setting up the profile and membership synchronization service. It prevents the synchronization service from failing and losing related settings. To do this, let us type the following command, and then press Enter:

STSADM –o preparetomove –contentdb <content database name>

Prepare

 

3. Now, let us detach our content database by executing the command below. We have to take note, however, that removing the content database simply removes the association of the database with our SharePoint Web application and does not exactly delete the database.

STSADM -o deletecontentdb –url <URL name> -databasename <database name> -databaseserver <database server name>

Delete

4. Let us open our Microsoft SQL Server 2005 Management Studio, and detach the content database. Finally, we will copy the corresponding .mdf and .ldf files to our destination server.

In our destination server, let us do the following steps:

NOTE: It is assumed that you have created a corresponding Web site in you destination server and deleted its content database – like what we have did in steps 2 and 3. With this, we are now ready to restore/move the content database of our source server to the destination server. Thanks Amlan for the comment.

5. Let us open our Microsoft SQL Server 2005 Management Studio, and attach the content database that we transferred in the previous step.

6. In the Command Prompt, let us change to the directory where the STSADM command-line tool is located. By default, it is on C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN.

7. Now, to add the content database to our destination server, let us type the following command, and then press Enter:

STSADM –o addcontentdb –url <URL name> -databasename <database name> -databaseserver <database server name>

Add

 

8. And finally let us start a full crawl. We must be aware, moreover, that a full crawl will occur the first time even if the next crawling scheduled is set to incremental mode in the content database we have restored.

Tag Cloud