Deploying Search Connectors
Search connectors must be installed on computers running Windows 7 before they can be used. To install a search connector, you need the .osdx file that creates that connector. There are three ways of deploying .osdx files:
- Pull Method The administrator either sends the OSDX file to the user by using a method such as e-mailing it as an attachment or directs the user to a location (such as a Web page or a network share) from which the user can obtain and install the .osdx file. The user is then responsible for installing the search connector by opening the OSDX file, by clicking a link on a Web page, or by some other method.
- Push Method The administrator uses either Group Policy preferences (the preferred
method) or a logon script to perform the following actions on the user's computer automatically:
- Copies the *.searchConnector-ms file to the %UserProfile%\Searches folder on the user's computer to install the search connector on the computer
- Creates a shortcut (.lnk file) to the %UserProfile%\Links folder on the user's computer to expose the search connector in the Favorites area of the navigation pane of Windows Explorer
User Configuration\Policies\Administrative Templates\Windows Components\Windows Explorer\Pin Libraries Or Search Connectors To The "Search Again" Links And The Start Menu - Imaging Method Before deploying desktop computers to users, the administrator
modifies a master installation of Windows 7 by performing the following actions:
- Copies the *.searchConnector-ms file to the C:Users\Default\Searches folder on the master computer to install the search connector on the computer
- Creates a shortcut (.lnk file) to the % C:Users\Default \Links folder on the master computer to expose the search connector in the Favorites area of the navigation pane of Windows Explorer
The administrator then syspreps the master computer, uses the Windows Automated Installation Kit (Windows AIK) to capture an image of the master computer, and then deploys this image onto destination computers using WDS or some other deployment method. When the user logs on to her computer for the first time, the user's profile is created from the default profile that the administrator has configured.
More Info For additional information on how Federated Search works and how to implement it, see the Windows 7 Federated Search Provider Implementer's Guide, which can be downloaded from http://www.microsoft.com/downloads/details.aspx?FamilyID=c709a596-a9e9-49e7-bcd4-319664929317&DisplayLang=en.
In this tutorial:
- Managing Search
- Search and Indexing Enhancements
- Search in Windows XP
- Search in Windows Vista
- Search in Windows 7
- Understanding the Windows Search Versions
- Search Versions Included in Windows 7 and Windows Vista
- Search Versions Included in Windows Server 2008
- Search Versions Available for Earlier Versions of Windows
- How Windows Search Works
- Understanding Search Engine Terminology
- Windows Search Engine Processes
- Enabling the Indexing Service
- Windows Search Engine Architecture
- Understanding the Catalog
- Default System Exclusion Rules
- Understanding the FANCI Attribute
- Default Indexing Scopes
- Initial Configuration
- Understanding the Indexing Process
- Modifying IFilter Behavior
- How Indexing Works
- Rebuilding the index
- Viewing Indexing Progress
- Understanding Remote Search
- Managing Indexin
- Configuring the Index
- Configuring the Index Location Using Group Policy
- Configuring Indexing Scopes and Exclusions Using Group Policy
- Configuring Offline Files Indexing
- Configuring Indexing of Encrypted Files
- Configuring Indexing of Encrypted Files Using Control Panel
- Configuring Indexing of Similar Words
- Configuring Indexing of Text in TIFF Image Documents
- Other Index Policy Settings
- Using Search
- Configuring Search Using Folder Options
- Configuring What to Search
- Configuring How To Search
- Using Start Menu Search
- Searching Libraries
- Advanced Query Syntax
- Using Federated Search
- Deploying Search Connectors
- Troubleshooting Search and Indexing Using the Built-in Troubleshooter