Install FAST Search Server 2010 for SharePoint

Published: May 12, 2010 This article describes how to install Microsoft FAST Search Server 2010 for SharePoint and the required software prerequisites. As part of this process, you will also download the installation package, enable Windows PowerShell scripts to run and set up permissions for Microsoft SQL Server. Before you start the installation, make sure that the system meets the requirements in Review hardware and software requirements (FAST Search Server 2010 for SharePoint) and Install Microsoft SharePoint Server 2010 and Microsoft SQL Server 2008 (FAST Search Server 2010 for SharePoint). In this article: 1. 2. 3. 4. 5. 6. 7. Download the installation package Open the FAST Search Server 2010 for SharePoint Start page Install prerequisites Enable Windows PowerShell scripts to run Install FAST Search Server 2010 for SharePoint Install updates Set up permissions for Microsoft SQL Server

Note: Perform the steps in the following sections as a user who is a member of the local Administrators group.

Download the installation package

Log in to MSDN Subscriber Downloads, expand the Servers menu, and then click FAST Search Server 2010 to download FAST Search Server 2010 for SharePoint. The installation package contains a selfextracting exe file that will open a Start page (splash.hta) and extract the installation files to the following folder: \Program Files (x86)\MSECache\FastSearchServer2010\ (Disregard the fact that the files are extracted to Program Files (x86). FAST Search Server 2010 for SharePoint is still a 64 bit system.)

Open the FAST Search Server 2010 for SharePoint Start page
When you download the installation package, the FAST Search Server 2010 for SharePoint Start page opens automatically. The Start page provides links to product documentation and to the installation wizards. However, after any restarts of the server during the installation process, the Start page does not open automatically. Double-click the splash.hta to reopen the FAST Search Server 2010 for SharePoint Start page.

Install prerequisites
The Prerequisite Installer checks your server for required components and updates, and then downloads and installs the required components and updates if they are not already present on the system. Which prerequisites are required depends on your operating system.

Note:

Verify that the server has Internet access and Windows Firewall open on port 80. The Prerequisite Installer downloads com server does not have Internet access, see Run the Prerequisite Installer in offline mode (FAST Search Server 2010 for Sh

The Windows Update service must be running when you run the Prerequisite Installer. If not, the Prerequisite Installer w

To run the Prerequisite Installer 1. On the FAST Search Server 2010 for SharePoint Start page, click Install software prerequisites. 2. 3. On the Welcome to the FAST Search for SharePoint prerequisite installer page, click Next. On the License page, verify that you accept the license terms and then click Next. The prerequisites are installed. Note: The Prerequisite Installer may require restarting the server during installation. 4. 5. On the Installation Complete page, click Finish. Restart the server.

For a multiple server deployment, repeat the procedure for all servers that will run FAST Search Server 2010 for SharePoint. Tip:

The Prerequisite Installer adds the Web Server (IIS) role to the server, but without the IIS Management Console service. T you enable the IIS Management Console in Server Manager.

Enable Windows PowerShell scripts to run

After the server restart in the previous procedure, change the policy for running Windows PowerShell scripts remotely (execution policy). The post-setup configuration wizard that you will run later must be able to run scripts during configuration. To enable the scripts to run: 1. 2. From the Start menu, search for Windows PowerShell. Right-click the Windows PowerShell icon (do not use the one with x86) and select Run as administrator. At the command prompt, type the following command to enable scripts to run: Set-ExecutionPolicy RemoteSigned Answer Yes if you are asked whether you want to change the policy. For a multiple server deployment, repeat the procedure for all servers that will run FAST Search Server 2010 for SharePoint.

3.

Install FAST Search Server 2010 for SharePoint

This procedure describes how to install FAST Search Server 2010 for SharePoint by running the installation wizard. Before you run the installation wizard, the Prerequisite Installer must be completed. To install FAST Search Server 2010 for SharePoint 1. Go to \Program Files (x86)\MSECache\FASTSearchServer2010 and double-click the splash.hta to reopen the Start page after the server restart. 2. On the FAST Search Server 2010 for SharePoint Start page, click Install FAST Search Server 2010 for SharePoint. On the Welcome page, click Next. On the License Terms page, accept the license and then click Next. On the Destination Folder page, select the folder where you want to install FAST Search Server 2010 for SharePoint. Click Next. 6. 7. On the Ready to install page, click Install. On the page that says that the wizard is completed, click Finish.

3. 4. 5.

For a multiple server deployment, repeat the procedure for all servers that will run FAST Search Server 2010 for SharePoint.

Install updates
After you have run the installation wizard, make sure that the product is up to date: 1. 2. On the FAST Search Server 2010 for SharePoint Start page, click Visit Windows update. Download and install all relevant updates.

For a multiple server deployment, repeat the procedure for all servers that will run FAST Search Server 2010 for SharePoint.

Set up permissions for Microsoft SQL Server

You must install SQL Server 2008 before you install FAST Search Server 2010 for SharePoint. When you run the post-setup configuration wizard to configure the server(s), FAST Search Server 2010 for SharePoint creates a database in SQL Server and needs access to the database server. Therefore, before you run the post-setup configuration wizard, make sure that the FAST Search Server 2010 for SharePoint user (the user who is entered in the wizard) has permissions to create the database. To set up permissions for SQL Server: 1. If you have installed SharePoint Server in stand-alone mode, you must install SQL Server Management Studio. For more information, seehttp://msdn.microsoft.com/library/ms365247.aspx In the SQL Server Installation Center, click Installation, and then click New SQL Server standalone installation or add features to an existing installation. Installation type isPerform a new installation of SQL Server 2008. On the server where SQL Server is installed, open SQL Server Management Studio.

2.

3.

4. 5.

In the Object Explorer, move to Security. Right-click Logins and select New Login In the Login New dialog box, on the General page, enter the FAST Search Server 2010 for SharePoint user as the Login name. In the Select a page pane, select Server Roles Select the DBCreator role. Click OK.

6. 7. 8.

After you have run the post-setup configuration wizard, you can remove the DBCreator role. However, make sure that the FAST Search user can still read and write to the database that was created. In SQL Server Configuration Manager, also follow these steps: 1. Verify that the main SQL Server service and the SQL Server Browser service are running. If the services are not running, start them by using Control Panel. Click Turn Windows features on or off, click Configuration, and then click Services. 2. In SQL Server Network Configuration, click Protocols for <instance name>, and verify that TCP/IP is enabled. Follow the steps in: How to: Configure a Server to Listen to a Specific TCP Port.

3.

Configure a stand-alone deployment or a multiple server deployment (FAST Search Server 2010 for SharePoint)
Updated: June 28, 2011 This article describes how to configure either a stand-alone deployment (single server deployment) or a multiple server deployment by running the post-setup configuration wizard. Before you can run the post-setup configuration wizard to do the initial configuration of the servers, follow the steps in Install FAST Search Server 2010 for SharePoint. Select one of the following: 1. Configure a stand-alone deployment (single server deployment) or 2. Configure a multiple server deployment A stand-alone deployment is useful when you want a deployment for product evaluation or demonstration, a small-scale deployment with minimal administrative overhead, or a development environment or test environment. A stand-alone deployment is an installation of FAST Search Server 2010 for SharePoint on a single server. All required components are installed on this server. A multiple server deployment is recommended for most production environments, except small deployments without any fault-tolerance requirements. A multiple server deployment is an installation of FAST Search Server 2010 for SharePoint services on multiple servers. During configuration, one server is defined as the administration server, which is the server where the

administrative services are installed and run. The deployment is scaled out by adding one or more non-administration servers. A non-administration server does not have the administrative services set up, but connects to a running administration server in a multiple server deployment. The non-administration server runs services such as query matching, indexing and document/item processing.

Configure a stand-alone deployment (single server deployment)

This section describes how to configure a stand-alone deployment (single server deployment) by running the configuration wizard. In this section: 1. 2. Configure a stand-alone deployment Verify that all modules are running

Configure a stand-alone deployment 1. From the Start menu, run Microsoft FAST Search Server 2010 for SharePoint Configuration Wizard as a local administrator. 2. 3. On the Welcome page, click Next. On the Select the deployment type page, select Single server (stand-alone) and then click Next. On the Enter the user name and password page, enter the user name and password for the FAST Search Server 2010 for SharePoint user. This user must be a domain user. Refer toRequired permissions for more information. On the Enter a certificate password page, enter a certificate password of your choice. This password will be used to protect the general purpose FAST Search certificate (see alsoManage certificates (FAST Search Server 2010 for SharePoint)). You will need this password to install certificates on other servers. Retype the password and then click Next. On the Server settings page, enter the fully qualified domain name of the server and the base port. A deployment file will be generated automatically with all the settings configured. Note:

4.

5.

6.

If you require a specific setup, you can create and use a custom deployment file. If you want to do this, select Use a theDeployment file location. Refer to deployment.xml reference for more information. 7. On the Database settings page, enter connection information to the SQL database that you installed and created before you installed FAST Search Server 2010 for SharePoint. Enter the Database connection string in the format <ServerName>\<DBInstanceName> (Example: mysqlserver1.contoso.com\myinsta nce). To determine the database connection string: On the server where the SQL Server is installed, open SQL Server Configuration Manager from the Start menu. Under SQL Server Services, you see the SQL Server main service. The service name contains the connection string in parentheses. Enter the Database name and Database port. The database will be created when you complete the configuration wizard. Click Next.

8.

On the Click-through relevancy settings page, add the desired relevancy click-through settings. Click-through relevancy enables automatic relevancy tuning based on how search users click on results. Select the relevant Microsoft SharePoint Server 2010 installation type.

If you have installed SharePoint Server 2010 using the Standalone option, specify the Fully Qualified Domain Name (FQDN) of the SharePoint Server 2010. If you have installed SharePoint Server 2010 using the Server Farm option, specify the user who is running the Microsoft SharePoint 2010 Timer Service. This user is specified in the SharePoint Server 2010 post-setup configuration. If you do not want click-through relevancy, or if you do not have the necessary information, select Do not enable click-through relevancy.

Click Next. 9. On the Configuration settings summary page, review the settings and then click Configure. Wait while the configuration finishes. 10. On the Post-setup configuration was successful page, click Finish. Note: If the configuration fails, you will see an error message with a link to the relevant log file if possible. For information seeInstallation: Configuration wizard fails (FAST Search Server 2010 for SharePoint). 11. Before you restart the server, make sure that administrative permissions are defined. Update the local FASTSearchAdministrators group (which was created by the configuration wizard) to include either the user who will administer the FAST Search Server 2010 for SharePoint farm, or the domain group of your FAST Search Administrators. 12. Restart the server. Verify that all modules are running 1. Log in as a user who is a member of the local FASTSearchAdministrators group. 2. 3. 4. On the Start menu, click All Programs. Click Microsoft FAST Search Server 2010 for SharePoint. Right-click Microsoft FAST Search Server 2010 for SharePoint shell and select Run as administrator. At the Windows PowerShell command prompt, type the following command:

5.

nctrl status
6. Make sure that all modules have the status Running.

Next step
You have now completed the initial configuration of a stand-alone deployment. To be able to crawl content by using the connector framework provided by SharePoint Server, follow the steps inCreate and set up the Content Search Service Application (FAST Search Server 2010 for SharePoint) to create and set up the FAST Search Content Search Service Application (Content SSA).

Configure a multiple server deployment

This section describes how to configure a multiple server deployment by running the configuration wizard. For more information about how to plan your farm topology, see Plan search topology (FAST Search Server 2010 for SharePoint). In this section: 1. 2. 3. 4. 5. Prepare the deployment file Configure the administration server in a multiple server deployment Verify that all modules are running on the administration server Configure the non-administration server(s) in a multiple server deployment Verify that all modules are running on the non-administration server

Prepare the deployment file The deployment file, deployment.xml, specifies the distribution of components and services across servers in a FAST Search Server 2010 for SharePoint farm. Each FAST Search Server 2010 for SharePoint farm has one deployment file. Each server in the farm can read the deployment file and determine the services that run locally on that server. Each server also determines the location of other services that it communicates with. The deployment file is a required input parameter when you run the configuration wizard (or configuration script) on the administration server. Non-administration servers will download the deployment file from the administration server, determine which services should run on the local server, and start these services. An example deployment.xml template is shown later in this document: Deployment.xml template. You can also find example deployment.xml templates directly under <FASTSearchFolder>\etc\, where <FASTSearchFolder> is the path of the folder where you have installed FAST Search Server 2010 for SharePoint, for example C:\FASTSearch. For information about how to prepare the deployment file, see deployment.xml reference. The completed deployment file to be used for the installation must be named deployment.xml. The FAST Search Server 2010 for SharePoint administrator can reconfigure the deployment by adding or removing servers or services in the deployment file. For more information about reconfiguring, see Reconfigure the farm deployment (FAST Search Server 2010 for SharePoint). Deployment.xml template The following template shows a multiple server deployment file, with three servers.

<?xml version="1.0" encoding="utf-8" ?> <deployment comment="FAST Search Server three node deployment example" xmlns="http://www.microsoft.com/enterprisesearch"> <instanceid>FASTSearchMultiNodeDemo</instanceid> <!-NOTE: Host names "fastserver1.contoso.com", "fastserver2.contoso.com" and "fastserver3.contoso.com" must be changed to the actual server names in use -->

<connector-databaseconnectionstring /> <host name="fastserver1.contoso.com"> <admin /> <indexing-dispatcher /> <content-distributor /> <webanalyzer server="true" link-processing="true" lookup-db="true" /> <document-processor processes="2" /> </host> <host name="fastserver2.contoso.com"> <searchengine row="0" column="0" /> </host> <host name="fastserver3.contoso.com"> <searchengine row="1" column="0" /> <query /> </host> <searchcluster> <row id="0" index="primary" search="true" /> <row id="1" index="none" search="true" /> </searchcluster> </deployment>
Configure the administration server in a multiple server deployment This section describes how to configure a server as the administration server in a multiple server deployment by running the configuration wizard. The administration server must be configured and running before you can add one or more non-administration servers to the deployment. Make sure to follow these steps as a user who is a member of the local Administrators group. 1. 2. Prepare a deployment file as described in the deployment.xml reference document. From the Start menu, run the Microsoft FAST Search Server 2010 for SharePoint Configuration Wizard. On the Welcome page, click Next. On the Select the deployment type page, select Admin server and then click Next. On the Enter the user name and password page, enter the user name and password for the FAST Search Server 2010 for SharePoint user. This user must be a domain user. On the Enter a certificate password page, enter a certificate password of your choice. This password will be used to protect the general purpose FAST Search certificate (see alsoManage certificates (FAST Search Server 2010 for SharePoint)). You will need this password to install certificates on other servers. Retype the password and then click Next.

3. 4. 5.

6.

7.

On the Server settings page, enter the fully qualified domain name of the server and the base port. Make sure that the server name is the same as the administration server that is defined in deployment.xml. In the Deployment file location box, enter the path of the deployment.xml file that you created. If there is an error in your deployment.xml file, you will get a warning. If no warnings or errors appear, your deployment.xml file syntax is correct. Click Next.

8.

On the Database settings page, enter the connection information to the SQL database that you installed and created before you installed FAST Search Server 2010 for SharePoint. Enter the Database connection string in the format <ServerName>\<DBInstanceName> (Example: mysqlserver1.contoso.com\myinsta nce). Enter the Database nameand Database port. The database will be created when you complete this configuration wizard. Click Next. On the Click-through relevancy settings page, add the desired relevancy click-through settings. Click-through relevancy enables automatic relevancy tuning based on how search users click on results. Select the relevant SharePoint Server 2010 installation type.

9.

If you have installed SharePoint Server 2010 using the Standalone option, specify the Fully Qualified Domain Name (FQDN) of the SharePoint Server 2010. If you have installed SharePoint Server 2010 using the Server Farm option, specify the user who is running the timer service in SharePoint Server 2010. This user is specified in the SharePoint Server 2010 post-setup configuration. If you do not want click-through relevancy, or if you do not have the necessary information, select Do not enable click-through relevancy.

Click Next. 10. On the Configuration settings summary page, review the settings and then click Configure. Wait while the configuration finishes. 11. On the Post-setup configuration was successful page, click Finish. Note: If the configuration fails, you will see an error message with a link to the relevant log file if possible. For information seeInstallation: Configuration wizard fails (FAST Search Server 2010 for SharePoint). 12. Before you restart the server, make sure that administrative permissions are defined. Update the local FASTSearchAdministrators group (which was created by the configuration wizard) to include either the user who will administer the FAST Search Server 2010 for SharePoint farm, or the domain group of your FAST Search Administrators. 13. Restart the server. Verify that all modules are running on the administration server 1. Log in as a user who is a member of the local FASTSearchAdministrators group. 2. On the Start menu, click All Programs.

3. 4.

Click Microsoft FAST Search Server 2010 for SharePoint. Right-click Microsoft FAST Search Server 2010 for SharePoint shell and select Run as administrator. At the Windows PowerShell command prompt, type the following command:

5.

nctrl status
6. Make sure that all modules have the status Running.

Configure the non-administration server(s) in a multiple server deployment By default, all servers in a multiple server deployment, except the administration server, are nonadministration servers. In this section, you will configure each non-administration server that is specified in your deployment file as a non-administration server by running the configuration wizard. As part of this configuration process, the server will connect to the administration server to join the FAST Search Server 2010 for SharePoint farm. First, verify that the newly configured administration server is running, by following the steps in Verify that all modules are running on the administration server. On each non-administration server, do the following: 1. 2. Log in as a user who is a member of the local Administrators group. On the Start menu, right-click Microsoft FAST Search Server 2010 for SharePoint Configuration Wizard, and select Run as administrator. On the Welcome page, click Next. On the Select the deployment type page, select Non-admin server and then click Next. On the Enter the user name and password page, enter the user name and password for the FAST Search Server 2010 for SharePoint user. This must be the same user as you specified for the administration server during post-setup configuration. On the Enter a certificate password page, enter the certificate password. Use the password that was used for the certificate in the administration server post-setup configuration. Click Next. On the Server settings page, enter the fully qualified domain name of the server. Make sure that the server name is the same as the corresponding server name that is defined indeployment.xml. Enter the fully qualified domain name and the base port of the administration server and then click Next. 8. On the Configuration settings summary page, review the settings and then click Configure. Wait while the configuration finishes. 9. On the Post-setup configuration was successful page, click Finish. Note: If the configuration fails, you will see an error message with a link to the relevant log file if possible. For information seeInstallation: Configuration wizard fails (FAST Search Server 2010 for SharePoint).

3. 4. 5.

6.

7.

10. Before you restart the server, make sure that administrative permissions are defined. Update the local FASTSearchAdministrators group (which was created by the configuration wizard) to include either the user who will administer the FAST Search Server 2010 for SharePoint farm, or the domain group of your FAST Search Administrators. 11. Restart the server. Important:

Skip this step if you perform this procedure during recovery after an indexer server failure (the procedures described failed backup indexer server). Verify that all modules are running on the non-administration server 1. Log in as a user who is a member of the local FASTSearchAdministrators group. 2. 3. 4. On the Start menu, click All Programs. Click Microsoft FAST Search Server 2010 for SharePoint. Right-click Microsoft FAST Search Server 2010 for SharePoint shell and select Run as administrator. At the Windows PowerShell command prompt, type the following command:

5.

nctrl status
6. Make sure that all modules have the status Running.

Create and set up the Content Search Service Application (FAST Search Server 2010 for SharePoint)
Published: May 12, 2010 To be able to crawl content with the indexing connectors integrated in Microsoft SharePoint Server 2010, you must prepare the FAST Search Content Search Service Application (Content SSA). The Content SSA will crawl content and feed it into the FAST Search Server 2010 for SharePoint back-end. After you have created the Content SSA and before you add a content source and configure crawling with the Content SSA, you must enable SSL communication between FAST Search Server 2010 for SharePoint and Microsoft SharePoint Server 2010. This is mandatory; you will not be able to feed content to FAST Search Server 2010 for SharePoint without enabling SSL communication. In this article:

Create and set up the Content SSA Configure SSL enabled communication Add a content source

Create and set up the Content SSA

Important:

Make sure that the Windows Service called SharePoint 2010 Administration (SPAdminV4) is running on Microsoft SharePo

The install_info.txt file contains information to help you configure the Content SSA. The file is located directly under <FASTSearchFolder> (the folder where you have installed FAST Search Server 2010 for SharePoint, for example C:\FASTSearch) on the administration server or single server.

1.

On SharePoint Server 2010, on the Central Administration Home page, click Application Management and then click Manage Service Applications. On the Manage Service Applications page, click New and then click Search Service Application. On the Create New Search Service Application page, in the Name section, provide a unique name for the Service Application. Example: FASTContent

2.

3.

4. 5.

In the FAST Service Application section, select FAST Search Connector. Set the Search Service Account. Note that the Search Service Account is the same across all Search Services. If you set this account to something other than the default value, it will affect all Search Services. If you want to change the Search Service Account later, go to the Central Administration Home page. Click Security and then click Configure Service Accounts. Change the user who runs Windows Service - SharePoint Server Search. By default, the user specified in the Search Service Account is used to access the content sources that will be crawled. If a certain content source should be crawled by a different user, this can be specified with a crawl rule for that content source.

6.

In the Application Pool for Search Admin Web Service section, select either an existing application pool under Use existing application pool, or select Create new application pool and give it a unique name. Example: FAST_Content_App_Pool. If you create a new application pool, select a security account. This security account is used to run the application pool for the administrative Web service. Through this service, an administrator will communicate all search administration operations such as starting crawls and creating crawl rules.

7.

In the Content Distributors and Content Collection Name sections, enter the connection information to the FAST Search Server 2010 for SharePoint installation. Use theinstall_info.txt file as a reference for the location of the content distributor. Important: The default FAST Search Server 2010 for SharePoint content collection is named sp.

8.

For example:

Content Distributors: fastsearch1.contoso.com:13391 If you have more than one, use a semicolon as separator.

Content Collection Name: sp

9.

Click OK. It may take a while to finish. When finished, you will receive a confirmation that your new Content SSA is created. The Content SSA is added to the list of Service Applications. Note:

If the Content SSA creation fails, you must enter new unique names for the Content SSA and the application pool. O data. You have now created the Content SSA. To be able to feed content to FAST Search Server 2010 for SharePoint, you must configure SSL enabled communication between Microsoft SharePoint Server 2010 and FAST Search Server 2010 for SharePoint. Continue with Configure SSL enabled communication.

Configure SSL enabled communication

Warning: Configuring SSL enabled communication is mandatory. Secure Sockets Layer (SSL) communication is required to feed content from SharePoint Server 2010 to FAST Search Server 2010 for SharePoint. To enable secure communications, configure the Content SSA to use an SSL certificate for FAST Search Server 2010 for SharePoint. FAST Search Server 2010 for SharePoint generates a self-signed certificate during post-setup configuration. This section describes how to use this certificate to enable SSL communication using the self-signed certificate. It is recommended to use certificates issued by a proper Certificate Authority in production environments, refer to Manage certificates (FAST Search Server 2010 for SharePoint) for advanced instructions. The following procedure has to be followed at least one time, to enable SSL communication between the SharePoint Server 2010 server that runs the Content SSA crawl component and the FAST Search Server 2010 for SharePoint back-end. If your environment contains additional SharePoint Server 2010 servers running a Content SSA crawl component, additional steps are required to enable SSL communication for those servers. Refer to Multiple server deployment of the Content SSA (FAST Search Server 2010 for SharePoint) for more information. Important: This procedure includes copying sensitive information. Ensure that the certificate information is kept private. 1. Copy the script securefastsearchconnector.ps1 from the FAST Search Server 2010 for SharePoint administration server to the SharePoint Server 2010 server. Thesecurefastsearchconnector.ps1 script is in the <FASTSearchFolder>, under installer\scripts\. Copy the certificate file FASTSearchCert.pfx from the FAST Search Server 2010 for SharePoint administration server to the SharePoint Server 2010 server. The certificate file is in the<FASTSearchFolder>, under data\data_security\cert\. Open a Microsoft SharePoint 2010 Management Shell with the Run as administrator option on the SharePoint Server 2010 server. Navigate to the directory where you copied the securefastsearchconnector.ps1 script and run it, replacing the necessary parameters with the values for your environment. The domain and user name should reflect the details of the user running the SharePoint Server Search 14 (OSearch14) service. .\SecureFASTSearchConnector.ps1 certPath "path of the certificate\certificatename.pfx" ssaName "name of your content SSA" username domain\username

2.

3.

When prompted to enter the certificate password, enter the certificate password that you supplied when you ran the post-setup configuration of FAST Search Server 2010 for SharePoint. Important:

The script verifies the connection to FAST Search Server 2010 for SharePoint. Therefore, make sure that all servers i running before you run this script. You have now configured the Content SSA to use SSL communication. You should now add at least one content source to the Content SSA to be able to verify the installation. Continue with Add a content source.

Add a content source

This section describes the steps to add a content source to the FAST Search Content SSA. A content source is a set of options that you can use to specify what type of content is crawled, what URLs to crawl, and how deep and when to crawl. You must create at least one content source before a crawl can occur. In order to feed content to the FAST Search Server 2010 for SharePoint content collection using the integrated indexing connectors, you should add at least one content source to the FAST Search Content SSA. The default content collection name is sp. The FAST Search Content SSA can have up to 500 content sources in it, and each content source can have a different configuration. Note:

It is not necessary to configure the FAST Search Content SSA and set up a content source when you choose to deploy one or indexing connectors: the FAST Search Web crawler, the FAST Search database connector and/or the FAST Search Lotus Note different configuration procedures. To verify a successful FAST Search Server 2010 for SharePoint installation, we recommend that you add a small content source to the Content SSA and start a full crawl. This can be one folder in a file share for example, or one Web site. Navigate to the Manage Content Sources page 1. Verify that the user account that is performing this procedure is a service application administrator for the FAST Search Content Search Service Application. 2. In Central Administration, in the Application Management section, click Manage service applications. On the Manage Service Applications page, click your FAST Search Content Search Service Application. On the Search Administration Page, in the Crawling section, click Content Sources.

3.

4.

To create a content source 1. On the Manage Content Sources page, click New Content Source. 2. On the Add Content Source page, in the Name section, in the Name box, type a name for the new content source. In the Content Source Type section, select the type of content that you want to crawl. We recommend that you pick a small content source to verify the installation. You can add additional content sources, or edit or delete this content source after you have completed the installation.

3.

Warning:

You can only crawl one type of content per content source. That is, you can create a content source that contains UR file shares. However, you cannot create a single content source that contains URLs to both SharePoint sites and file s 4. In the Start Addresses section, in the Type start addresses below (one per line) box, type the URLs from which the crawl should start. In the Crawl Settings section, select the crawling behavior that you want. In the Crawl Schedules section, to specify a schedule for full crawls, select a defined schedule from the Full Crawl list. A full crawl crawls all content that is specified by the content source, regardless of whether the content has changed. To define a full crawl schedule, click Create schedule. To specify a schedule for incremental crawls, select a defined schedule from the Incremental Crawl list. An incremental crawl crawls content that is specified by the content source that has changed since the last crawl. To define a schedule, click Create schedule.You can change a defined schedule by clicking Edit schedule. Tip: It is recommended to complete a manually started full crawl cycle before scheduling more crawls. This ensures that not shorter than the time that is required to run a full crawl. 7. To prioritize this content source, in the Content Source Priority section, on the Priority list, select Normal or High. To immediately begin a full crawl, in the Start Full Crawl section, select the Start full crawl of this content source check box, and then click OK.

5. 6.

8.

Create and set up the Query Search Service Application (FAST Search Server 2010 for SharePoint)
Published: May 12, 2010 This article describes how to create a FAST Search Query Search Service Application (Query SSA) in SharePoint Server Central Administration. The FAST Search Query SSA provides query results from all content sources. Note:

The Query SSA may also be used to provide people search results. You must then add a content source for people to the Que Search Server index and route people queries to Search Server. Before you create the FAST Search Query SSA, follow the steps in Create and set up the Content Search Service Application (FAST Search Server 2010 for SharePoint). In this article:

Create and set up the FAST Search Query SSA Verify user access to FAST Search Server 2010 for SharePoint administrative services

Connect the FAST Search Query SSA to your web application(s)

Create and set up the FAST Search Query SSA

Important:

Make sure that the Windows Service called SharePoint 2010 Administration (SPAdminV4) is running on Microsoft SharePo The install_info.txt file, located directly under the FASTSearch installation folder on the FAST Search Server 2010 for SharePoint administration server or single server (defaultc:\FASTSearch\install_info.txt), contains the URLs for configuring the SSA. 1. On SharePoint Server 2010, on the Central Administration Home page, click Application Management and then Manage Service Applications. On the Manage Service Applications page, click New and then Search Service Application. On the Create New Search Service Application page, in the Name section, provide a unique name for the Service Application. Example: FAST Query SSA Warning: If the SSA creation fails, you must enter a new unique name for this field. Otherwise, it will fail again and you must re-enter all data. 4. 5. In the FAST Service Application section, select FAST Search Query. Set the Search Service Account. Note that the Search Service Account is the same across all Search Services. If you set this account to something other than the default value, it will affect all Search Services. If you want to change the Search Service Account later, go to the Central Administration Home page. Click Security and then click Configure Service Accounts. Change the user who runs Windows Service - SharePoint Server Search. 6. In the Application Pool for Search Admin Web Service section, select either an existing application pool under Use existing application pool, or select Create new application pool and give it a unique name. Example: FAST_Query_Admin_SSA_App_Pool. If you create a new application pool, select a security account. The security account is used to run the SSA Admin Web service. Select Configurable, and enter the user account. The default is the managed service account. 7. In the Application Pool for Search Query and Site Settings Web Service section, select either an existing application pool under Use existing application pool, or selectCreate new application pool, and give it a unique name. Example: FAST_Query_SSA_App_Pool. If you create a new application pool, select a security account. The security account is used to run the Web service for Search Query and Site Settings. Select Configurable, and enter the user account. 8. In the Query Service Location, Administration Service Location and Resource Store Location sections, enter the connection information to the FAST Search Server 2010 for SharePoint installation. The location (URLs/port numbers) of the services is included in

2. 3.

the install_info.txt file. The examples here assume a base port of 13000 for FAST Search Server 2010 for SharePoint.

Query Service Location: http://fastsearch1.contoso.com:13287 or https://fastsearch1.contoso.com:13286 (If you have enabled HTTPS for queries)

Administration Service Location: http://fastsearch1.contoso.com:13257 or https://fastsearch1.contoso.com:13258 (If you have enabled HTTPS for queries.)

9.

Resource Store Location: http://fastsearch1.contoso.com:13255 Account for Administration Service: domain\user.

Click OK. It may take a while to finish. When finished, a new SSA is added to the list of Service Applications.

10. Review the redundancy and availability requirements for the Query SSA. For planning considerations, see Recommendations: Redundancy and availability (FAST Search Server 2010 for SharePoint). For deployment details, see Multiple server deployment of the Query SSA (FAST Search Server 2010 for SharePoint).

Verify user access to FAST Search Server 2010 for SharePoint administrative services
The user who runs the Application Pool for the web application in which you will configure FAST Search Server 2010 for SharePoint, is the user who will communicate with the FAST Search Server 2010 for SharePoint administration server. Therefore, make sure that the user who runs this Application Pool is a member of the FASTSearchAdministrators group on the FAST Search Server 2010 for SharePoint administration server: 1. On SharePoint Server 2010, on the Central Administration Home page, under Security, select Configure Service Accounts. Each web application has a separate Web Application Pool. Select the relevant component, typically Web Application Pool - SharePoint - 80. Make sure that the user account for this component is a member of the FASTSearchAdministrators group on the FAST Search Server 2010 for SharePoint administration server.

2.

3.

Limit access to keyword management only In a parent and child farm scenario, the child farm web application account must be authorized to access the FAST Search Server 2010 for SharePoint (back-end) keyword service. The account can be authorized by adding it to the FASTSearchKeywordAdministrators group on the FAST Search Server 2010 for SharePoint administration server. TheFASTSearchKeywordAdministrators group is not automatically created during installation, but can be created manually if you want to use this level of authorization.

You can also select to give the account full access to the FAST Search Server 2010 for SharePoint administrative services by adding it to the FASTSearchAdministrators group.

Connect the FAST Search Query SSA to your web application(s)

Important:

The following steps require that at least one web application was created. For information about how to create web applicatio application. 1. On SharePoint Server 2010, on the Central Administration Home page, select Application Management. Under Service Applications, click Configure service application associations. Click the Application Proxy Group that you want to change, typically default. Make sure that the Query SSA (for example FAST Query SSA) is the default and only selected Search Service Application Proxy, and then click OK. Verify that the correct Query SSA is associated with the web application.

2. 3. 4.

5.

All the default search service applications should now point to FAST Search Server 2010 for SharePoint.

Enable queries from Microsoft SharePoint Server (FAST Search Server 2010 for SharePoint)
Updated: January 7, 2011 This article describes how to enable queries from Microsoft SharePoint Server 2010 on the FAST Search Server 2010 for SharePoint. You must configure claims authentication, which means that you export a certificate from SharePoint Server 2010 and import it on all query servers in FAST Search Server 2010 for SharePoint. If you want to help secure query traffic by enabling HTTPS (optional), you must perform some additional steps. Before you enable queries as described in this article, follow the steps in Create and set up the Query Search Service Application (FAST Search Server 2010 for SharePoint). In this article:

Configure claims authentication Enable HTTPS (optional)

Configure claims authentication

This section describes how to transfer a Microsoft SharePoint Server 2010 STS certificate (MOSS_STS) from SharePoint Server 2010 to all FAST Search Server 2010 for SharePoint query servers to provide security trimmed queries. Security trimming, or item level security, limits user access to items in search results that the user who submitted the query is authorized to see. On SharePoint Server 2010, export the SharePoint STS certificate:

1. 2. 3. 4.

On the Start menu, click All Programs. Click Microsoft SharePoint 2010 Products. Right-click SharePoint 2010 Management Shell, and select Run as administrator. At the Windows PowerShell command prompt, type the following command(s):

$stsCert = (GetSPSecurityTokenServiceConfig).LocalLoginProvider.SigningCertificate $stsCert.Export("cert") | Set-Content -encoding byte MOSS_STS.cer

The file MOSS_STS.cer is created in the directory from which you run the commands. 5. Copy MOSS_STS.cer to a location that is available to the FAST Search Server 2010 for SharePoint query servers.

On each FAST Search Server 2010 for SharePoint query server, import the SharePoint STS certificate: 1. 2. 3. On the Start menu, click All Programs. Click Microsoft FAST Search Server 2010 for SharePoint. Right click Microsoft FAST Search Server 2010 for SharePoint shell and select Run as administrator. At the Windows PowerShell command prompt, browse to <FASTSearchFolder>\installer\scripts\, where <FASTSearchFolder> is the path of the folder where you have installed FAST Search Server 2010 for SharePoint, for example C:\FASTSearch. Type the following command:

4.

.\InstallSTSCertificateForClaims.ps1 -certPath <"full path of MOSS STS certificate">

Where:

<"full path of MOSS STS certificate"> is the path of the location where you copied the MOSS_STS.cer file.

After finishing these steps, you have completed the configuration of the FAST Search Server 2010 for SharePoint query server. Repeat for all query servers if you have more than one.

Enable HTTPS (optional)

If you want to help secure query traffic by using HTTPS, you must perform some additional optional steps. With FAST Search Server 2010 for SharePoint, you can choose between HTTP and HTTPS for query traffic. HTTP is used as a default.

HTTP: All query traffic from the SharePoint Server 2010 search application to FAST Search Server 2010 for SharePoint will be sent via HTTP requests. The information is not encrypted. However, this

communication channel is faster than HTTPS. Use HTTP if your documents do not contain sensitive information, or if you want maximum query performance. This is the default method.

HTTPS: All query traffic from the SharePoint Server 2010 search application to FAST Search Server 2010 for SharePoint will be sent via secured requests. The information is encrypted so that no one can access sensitive information that is contained in the query traffic. Use HTTPS if your documents contain sensitive information.

Note:

This configuration step is optional. Follow this procedure only if you decide to use HTTPS for queries between FAST Search Se HTTPS for query traffic require server-specific SSL certificates. Each query server in FAST Search Server 2010 for SharePoint must have a certificate where one of the following must be true:

The certificate subject property is set to the FQDN of the query server. The subject alternate name (SAN) property contains the FQDN of the query server.

We recommend that you use your company's existing public key infrastructure (PKI) to generate these SSL certificates. On each query server in FAST Search Server 2010 for SharePoint, follow these steps: 1. Import the server-specific SSL certificate into the certificate store. The certificate must be saved under Certificates(Local Computer)\Personal. Grant the FASTSearchAdministrators group full access to the certificate, by using winhttpcertcfg or the Microsoft Management Console (MMC) Certificates snap-in. To grant access by using the MMC snap-in: a. b. c. 2. Click Start, type mmc in the Search programs and files box, and then press ENTER. Right-click the certificate, click All tasks, and then click Manage Private Keys. Click Add, add the FastSearchAdministrators group and select Full control.

Configure the query server to use the certificate on base port + 286. a. b. c. On the Start menu, click All Programs. Click Microsoft FAST Search Server 2010 for SharePoint. Right click Microsoft FAST Search Server 2010 for SharePoint shell and select Run as administrator. At the Windows PowerShell command prompt, type the following command(s):

d.

netsh http add sslcert ipport=0.0.0.0:<baseport+286> appid={a5455c786489-4e13-b395-47fbdee0e7e6} certhash=<Cert_Thumbprint>

Where:

<baseport+286> is the actual port number. Example: If the base port is 13000, the actual port number will be 13286 (ipport=0.0.0.0:13286). <Cert_Thumbprint> is the thumbprint of the certificate.

On the SharePoint Server 2010 server, follow these steps: 1. Enable a trust relationship in SharePoint Server 2010 for the SSL certificate(s) that you created for each query server. Do this by importing the public certificate of the signing authority of the SSL Certificate(s) into SharePoint Server 2010: a. b. c. d. On the Start menu, click All Programs. Click Microsoft SharePoint 2010 Products. Right-click SharePoint 2010 Management Shell, and select Run as administrator. At the Windows PowerShell command prompt, type the following command(s):

$trustCert = Get-PfxCertificate '<SSL_CA_Public_Cert>.cer' New-SPTrustedRootAuthority "FASTSearchHostQuerySSLCert" -Certificate $trustCert

Where:

<SSL_CA_Public_Cert> is the name of the certificate from the signing authority of the SSL certificate(s).

You will typically export this certificate from the Trusted Root Store on the query server. 2. Change the Query Service Location configuration setting for the Query Search Service Application (SSA) to use the HTTPS endpoint. See Create and set up the Query Search Service Application (FAST Search Server 2010 for SharePoint) for detailed information.

Create a FAST Search Center site (FAST Search Server 2010 for SharePoint)
Published: May 12, 2010 This article describes how you can create a FAST Search Center site, which means that you set up a SharePoint Server 2010 site to use the FAST Search Query SSA.

Before you create the FAST Search Center site, follow the steps in Enable queries from Microsoft SharePoint Server (FAST Search Server 2010 for SharePoint). 1. 2. Open the SharePoint Server 2010 Web application where you want to create a new site. Enable features unless this has already been done: a. b. Click Site Actions, then click Site Settings, and then click Site collection features. Make sure that the following are enabled:

3.

SharePoint Server Publishing Infrastructure SharePoint Server Enterprise Site Collection features

Create a new site: a. b. c. Click Site Actions and then click New Site. Select the FAST Search Center template. Click Create. A FAST Search Center is created at the specified URL.

Verify successful installation (FAST Search Server 2010 for SharePoint)

Published: May 12, 2010 This article describes some procedures that you can use to verify that the system is set up correctly. Note: All procedures are optional. In this article:

Verify that all services are running Feed and query test documents Check the Event Log

Verify that all services are running

On each server in the FAST Search Server 2010 for SharePoint farm: 1. 2. 3. On the Start menu, click All Programs. Click Microsoft FAST Search Server 2010 for SharePoint. Click Microsoft FAST Search Server 2010 for SharePoint shell.

4.

At the Windows PowerShell command prompt, type the following command:

nctrl status
5. Verify that all services have the status running.

Feed and query test documents

Verify that you can feed a document and do a search that returns that document. This task can be divided in two parts:

Test integration between FAST Search Server 2010 for SharePoint and SharePoint Server by testing feeding and searching from SharePoint Server 2010 using FAST Search Server 2010 for SharePoint as the back-end. See Test integration between FAST Search Server 2010 for SharePoint and SharePoint Server. Test feeding and searching directly on FAST Search Server 2010 for SharePoint. See Test feeding and searching on FAST Search Server 2010 for SharePoint.

By testing feeding and searching in this two-step process, you can narrow down any potential problems. If the first step fails, but the second step succeeds, there is a problem with the integration between SharePoint Server 2010 and FAST Search Server 2010 for SharePoint. If the second step fails, the installation or configuration of FAST Search Server 2010 for SharePoint is incorrect. Test integration between FAST Search Server 2010 for SharePoint and SharePoint Server After you completed the steps in Create and set up the Content SSA, a Content SSA with a content source should have been created and some items should have been crawled. 1. Verify that documents have been fed to FAST Search Server 2010 for SharePoint: a. b. c. On the Start menu, click All Programs. Click Microsoft FAST Search Server 2010 for SharePoint. Right click Microsoft FAST Search Server 2010 for SharePoint shell and select Run as administrator. At the Windows PowerShell command prompt, type the following command:

d.

Get-FASTSearchContentCollection -Name "sp"

2. Verify that one or more documents are displayed in the search result from the FAST Search Center site: a. Open the FAST Search Center site that you created, and do a search for the documents that you fed to FAST Search Server 2010 for SharePoint. Verify that one or more of the documents that you fed to FAST Search Server 2010 for SharePoint are returned in the search results.

b.

Test feeding and searching on FAST Search Server 2010 for SharePoint Follow these steps on a FAST Search Server 2010 for SharePoint server that has the query processing component (query role in the deployment.xml file). By default, single server deployments have this component. Refer to deployment.xml reference for more information. 1. 2. 3. On the Start menu, click All Programs. Click Microsoft FAST Search Server 2010 for SharePoint. Right click Microsoft FAST Search Server 2010 for SharePoint shell and select Run as administrator. At the Windows PowerShell command prompt, type the following command to feed a single document:

4.

Docpush -c sp <filename>
Where <filename> is the full path to a test document that can be indexed by FAST Search Server 2010 for SharePoint. Use any text document, Office document or HTML document. 5. Verify that the document or documents were indexed correctly, by running the following command:

Get-FASTSearchContentCollection -name "sp"

6. Open a browser on the FAST Search Server 2010 for SharePoint server that has the query processing component and go to the page: http://localhost:<baseport + 280>. The baseport is the base TCP/IP port for the FAST Search Server 2010 for SharePoint farm. In a default deployment, the base port is 13000. Replace <baseport + 280> with the actual port number. Note:

This is a test search page that is only accessible via localhost on the FAST Search Server 2010 for SharePoint serve 7. In the FQL Query field, type a word that you know exists in the document(s) that you previously fed. Click Search. Verify that the XML test result page returns an item (document) that contains the content of your test document. To remove all the documents that you added, run the following command:

8.

9.

Clear-FASTSearchContentCollection name "sp"

Warning: This command will erase the content index. Be careful not to use this command in a production environment unless

Check the Event Log

1. 2. 3. On the FAST Search Server 2010 for SharePoint administration server, open the Event Log. Browse to Applications and Services Logs and FAST Search Farm. Verify that no error messages are displayed.

Manage certificates (FAST Search Server 2010 for SharePoint)

Updated: February 10, 2011 FAST Search Server 2010 for SharePoint uses certificates for authentication and encryption purposes. The certificates are used both for communication between servers in a multiple server FAST Search Server 2010 for SharePoint deployment, and between FAST Search Server 2010 for SharePoint and Microsoft SharePoint Server. Each server in a FAST Search Server 2010 for SharePoint deployment potentially has three certificates which serve different functions and which must be configured and replaced separately:

General purpose FAST Search certificate (used for internal communication, administration services, and feeding from Microsoft SharePoint Server) Server-specific certificate for query traffic using HTTPS (only on query servers that have HTTPS query traffic enabled). Claims certificate (only on query servers).

Note that the two first certificates may be combined into one certificate if the requirements that are listed under General purpose FAST Search certificate are fulfilled. However, you must perform certain configuration steps to replace each of these two certificates (for example, because of expiration or revocation). In this section:

General purpose FAST Search certificate Query HTTPS certificate Claims certificate

General purpose FAST Search certificate

During initial installation, FAST Search Server 2010 for SharePoint generates a self-signed certificate. The self-signed certificate has a one year expiration date from the time of configuration and is only meant to be used in test environments. There are several limitations to this certificate:

Self-signed certificates provide limited security because they cannot be revoked. This could allow an attacker to spoof identities or insert data into connections if the private key was compromised. The self-signed certificate cannot be used to enable queries over HTTPS. The self-signed certificate cannot be used to enable administration services over HTTPS.

To help achieve a very high level of security, FAST Search Server 2010 for SharePoint should use an existing public key infrastructure (PKI). Each server in a multiple server FAST Search Server 2010 for SharePoint deployment should have a separate certificate that is issued by a common certification authority (CA). The following requirements apply to each server certificate:

The subject name or subject alternative name (SAN) field must contain the fully qualified domain name (FQDN) of the server that the certificate is issued to. This is required to support queries over HTTPS and administration services over HTTPS.

The certificate that is issued to Microsoft SharePoint Server must have the same issuer as the certificates that are issued to servers in the FAST Search Server 2010 for SharePoint deployment. The FAST Search Server 2010 for SharePoint user must have access to the private key of the certificate.

The FAST Search Server 2010 for SharePoint distribution includes a Windows PowerShell script which must be run on each server in the deployment to replace the default self-signed certificate. The script can perform two separate tasks:

Create a new self-signed certificate with a one year expiration and configure FAST Search Server 2010 for SharePoint to use the new certificate. See Replace the self-signed certificate with a new self-signed certificate. Configure FAST Search Server 2010 for SharePoint to use an existing certificate that is signed by a certification authority (CA) by supplying a thumbprint to an already installed certificate. See Replace the self-signed certificate with a certificate signed by a certification authority (CA)

Replace the self-signed certificate with a new self-signed certificate To replace the default self-signed certificate with a new self-signed certificate, follow these steps: 1. Stop FAST Search Server 2010 for SharePoint on all servers in the farm, including the monitoring service. On the administration server, follow these steps: a. b. c. d. e. On the Start menu, click All Programs. Click Microsoft FAST Search Server 2010 for SharePoint. Right-click SharePoint 2010 Management Shell, and select Run as administrator. At the command prompt, browse to installer\scripts under the installation folder. Type the following command:

2.

.\ReplaceDefaultCertificate.ps1 -generateNewCertificate $true

f. 3. 4. Enter a password for the certificate.

Start FAST Search Server 2010 for SharePoint on the administration server. On each non-administration server, follow these steps: a. b. c. d. On the Start menu, click All Programs. Click Microsoft FAST Search Server 2010 for SharePoint Right-click SharePoint 2010 Management Shell, and select Run as administrator. At the command prompt, browse to installer\scripts under the installation folder.

e.

Type the following command:

.\ReplaceDefaultCertificate.ps1 -generateNewCertificate $true

f. 5. Enter the password you defined for the certificate on the administration server.

Start FAST Search Server 2010 for SharePoint on all non-administration servers.

The new self-signed certificate will have a one year expiration date. If FAST Search Server 2010 for SharePoint is already added as a back-end for Microsoft SharePoint Server, you must also redo the certificate steps in Configure SSL enabled communicationunder Create and set up the Content Search Service Application (FAST Search Server 2010 for SharePoint). Replace the self-signed certificate with a certificate signed by a certification authority (CA) To replace the default self-signed certificate with a certificate signed by a certification authority, follow these steps: 1. Stop FAST Search Server 2010 for SharePoint on all servers in the farm, including the monitoring service. On each server in the FAST Search Server 2010 for SharePoint farm:

2.

Make sure that the new certificate is installed correctly, and that the FAST Search Server 2010 for SharePoint user has access to the private key of the certificate. The certificate must be installed under Certificates(Local Computer)\Personal in the certificate store. The CA certificate of the certificate must be installed under Certificates(Local Computer)\Trusted Root Certification Authorities.

3.

On the administration server, follow these steps: a. b. On the Start menu, click All Programs. Click Microsoft FAST Search Server 2010 for SharePoint and then Microsoft FAST Search Server 2010 for SharePoint shell. At the command prompt, browse to installer\scripts under the installation folder. Type the following command:

c. d.

.\ReplaceDefaultCertificate.ps1 -thumbprint "certificate thumbprint"

You can determine the certificate thumbprint by opening the certificate store on the local server and locating the certificate. 4. 5. Start FAST Search Server 2010 for SharePoint on the administration server. On each non-administration server, follow these steps:

. a.

On the Start menu, click All Programs. Click Microsoft FAST Search Server 2010 for SharePoint and then Microsoft FAST Search Server 2010 for SharePoint shell. At the command prompt, browse to installer\scripts under the installation folder. Type the following command:

b. c.

.\ReplaceDefaultCertificate.ps1 -thumbprint "certificate thumbprint"

You can determine the certificate thumbprint by opening the certificate store on the local server and locating the certificate. 6. Start FAST Search Server 2010 for SharePoint on all non-administration servers.

The Microsoft SharePoint Server where the Content SSA is running also needs a certificate that is signed by the same CA to feed documents to FAST Search Server 2010 for SharePoint: 1. Install the certificate on Microsoft SharePoint Server under Certificates(Local Computer)\Personal in the certificate store. The CA certificate of the certificate must be installed underCertificates(Local Computer)\Trusted Root Certification Authorities. The next steps will help set the correct permissions on the certificates. Copy the script SecureFASTSearchConnector.ps1 from the FAST Search Server 2010 for SharePoint administration server to the SharePoint Server 2010 server which is running the FAST Search connector. The SecureFASTSearchConnector.ps1 script can be found in the installation folder, under \installer\scripts\. On the SharePoint Server 2010 server that is running the FAST Search connector, follow these steps: a. b. c. d. On the Start menu, click All Programs. Click Microsoft SharePoint 2010 Products. Right-click SharePoint 2010 Management Shell, and select Run as administrator. Browse to the directory where you copied the SecureFASTSearchConnector.ps1 script and run it, replacing the necessary parameters with the values for your environment. The domain and user name should reflect the details of the user running the SharePoint Server Search 14 (OSearch14) service:

2.

3.

If you know the thumbprint of your certificate, type the following command:

.\SecureFASTSearchConnector.ps1 -certThumbprint "certificate thumbprint" -ssaName "name of your content SSA" -username "domain\username"

If you do not know the thumbprint of your certificate, type the following command:

.\SecureFASTSearchConnector.ps1 -ssaName "name of your content SSA" -username "domain\username"

This command will return the thumbprint of the available certificates and a prompt asking whether you want to use the suggested certificate. Enter y for yes, and then click Enter.

Query HTTPS certificate

The query HTTPS certificate is used to encrypt query traffic. For initial setup, see Enable HTTPS (optional). Replace the query HTTPS certificate To replace the query HTTPS certificate, follow these steps on each FAST Search Server 2010 for SharePoint query server: 1. Import the new server-specific SSL certificate into the certificate store. The certificate must be saved under Certificates(Local Computer)\Personal. Grant theFASTSearchAdministrators group full access to the certificate. Delete the previous certificate binding from baseport+286: a. b. c. On the Start menu, click All Programs. Click Microsoft FAST Search Server 2010 for SharePoint. Right click Microsoft FAST Search Server 2010 for SharePoint shell and select Run as administrator. At the Windows PowerShell command prompt, type the following command(s):

2.

d.

netsh http delete sslcert ipport=0.0.0.0:<baseport+286>

Where:

3.

<baseport+286> is the actual port number.

Configure the query server to use the new certificate on baseport+286: a. At the Windows PowerShell command prompt, type the following command(s):

netsh http add sslcert ipport=0.0.0.0:<baseport+286> appid={a5455c786489-4e13-b395-47fbdee0e7e6} certhash=<Cert_Thumprint>

Where:

<Cert_Thumbprint> is the thumbprint of the new certificate. <baseport+286> is the actual port number.

In addition, if the new certificate was not signed by the same certification authority (CA) as the previous certificate, you must add the CA certificate to the Microsoft SharePoint Server: On Microsoft SharePoint Server: 1. Enable a trust relationship in Microsoft SharePoint Server for the SSL certificate(s) that you created for each FAST Search Server 2010 for SharePoint query server. Do this by importing the public certificate of the signing authority of the SSL Certificate(s) into Microsoft SharePoint Server: a. b. c. d. On the Start menu, click All Programs. Click Microsoft SharePoint 2010 Products. Right-click SharePoint 2010 Management Shell, and select Run as administrator. At the command prompt, type the following command(s):

e. $trustCert = Get-PfxCertificate '<SSL_CA_Public_Cert>.cert' f. New-SPTrustedRootAuthority "FASTSearchHostQuerySSLCert" -Certificate $trustCert

Where:

Claims certificate

<SSL_CA_Public_Cert> is the name of the certificate from the signing authority of the SSL certificate(s)

The claims certificate provides claims-based authentication. To replace this certificate, repeat the steps listed under Create a FAST Search Center site (FAST Search Server 2010 for SharePoint).

Enable Advanced Filter Pack (FAST Search Server 2010 for SharePoint)
Published: May 12, 2010 Advanced Filter Pack is a FAST Search Server 2010 for SharePoint feature that enables text and metadata extraction from several hundred file formats, complementing the document formats that are supported by the Microsoft Filter Pack. By default, the Advanced Filter Pack is disabled.

To enable the Advanced Filter Pack

On the FAST Search Server 2010 for SharePoint administration server (or single server), follow these steps: 1. 2. 3. On the Start menu, click All Programs. Click Microsoft FAST Search Server 2010 for SharePoint. Right click Microsoft FAST Search Server 2010 for SharePoint shell and select Run as administrator. At the command prompt, browse to installer\scripts under the installation folder. Type the following command:

4. 5.

.\AdvancedFilterPack.ps1 -enable
To disable the Advanced Filter Pack On the FAST Search Server 2010 for SharePoint administration server (or single server), follow these steps: 1. 2. 3. On the Start menu, click All Programs. Click Microsoft FAST Search Server 2010 for SharePoint. Right click Microsoft FAST Search Server 2010 for SharePoint shell and select Run as administrator. At the command prompt, browse to installer\scripts under the installation folder. Type the following command:

4. 5.

.\AdvancedFilterPack.ps1 -disable