Exporteren (0) Afdrukken
Alles uitvouwen

Extending Windows Search

Bijgewerkt: juni 2008

Van toepassing op: Windows Server 2008

You can extend Windows Search 4.0 with add-ins. Protocol handlers, property handlers, and filters enable indexing additional data stores and file types. Preview handlers enable users to get a preview of the content of a result item without opening the item’s associated application. Toolbars provide easy access to searches. Extending Windows Search in these ways enables you to perform the following tasks:

  • Search additional file types, such as Adobe PDF files or IBM Lotus Notes files.

  • Search additional data repositories from third-party applications, such as your customer relationship management (CRM) database.

  • Integrate search results into your third-party applications, such as importing new Outlook contacts into your CRM system.

This section contains the following topics:

Windows Search Add-Ins

For a list of supported add-ins and third-party filters, property handlers, and protocol handlers that can be integrated with Windows Search, visit the Windows Search Add-Ins Web page. After you install an add-in and the computer is idle, Windows Search indexes the new file types. Some add-ins require a computer restart.

If you have .NET 3.0 installed (this is the default in Windows Vista but not Windows XP), the .NET 3.0 IFilter is included so .xps files are can be indexed. If you have Windows XP and .NET 3.0 is not installed, you can install the XPS Essentials Pack IFilter instead.

Alternatively, you can create your own add-ins. For more information about how to extend Windows Search by creating your own protocol handlers, property handlers or filters, visit the Windows Search Developer Guide on MSDN.

Disabling Unwanted Protocol Handlers

Administrators can disable installed protocol handlers using Group Policy.

  1. Identify the name of the protocol:

    1. In the Registry Editor, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows search\ProtocolHandlers.

    2. Locate the protocol handler you want to disable and note its protocol Name.

      Example protocol names: Mapi, OneIndex, SomeProtocol

  2. Add a URL path for that protocol to the Prevent Indexing Certain Paths policy as <protocol name>://{*}/*.

    Example: SomeProtocol://{*}/*

For more information on Group Policy, refer to Group Policy for Windows Search.

Adding Functionality with Toolbars

If you are interested in providing desktop search entry points in Microsoft Office Outlook 2003 or Microsoft Internet Explorer, your users can use Windows Live Toolbar. From this toolbar, Windows XP and Server 2003 users can add another toolbar to Outlook 2003 to start searches from within Outlook. The underlying search is powered by Windows Search.

Earlier versions of Windows Search supported the MSN Search Toolbar; however, this product is no longer supported by Microsoft.

Microsoft Office Outlook 2007 or later has instant search powered by Windows Search and does not require installation of a separate toolbar.

File Types Indexed by Default

Filters (implementations of the IFilter interface) are required to index the properties and contents of file types. Common filters include those that are already in Microsoft Office™ and that let you index, view, and search file names, metadata, and the contents of .doc or .xls files, for example.

For files with no extension, only basic properties like filename are indexed. On the Indexing Option -> Advanced -> File Types tab, you can add a new extension with just the dot “.” as the value and then choose whether to index properties only or properties and content. As many different types of files may not have a file name extension associated with them, you need to be cautious when indexing the content of such files (for example, if users have a lot of binary files without a file name extension).

In addition, more custom file types can be interpreted and viewed in your preferred format when you create filters or protocol handlers. For file attachments, a limited number of file types are inherently enabled for preview in the Windows Search results window. For additional control, the IT administrator can specify via policy additional file types that are allowed to be previewed via the Windows Search results window.

Windows Search has a filter to index virtually any file type as text, including the file name, the metadata, and the contents of the file. Windows Search indexes some popular file types as text and excludes others, as described below. Users can change these defaults on the on the File Types tab in the Advanced Options dialogue from the Indexing Options Control Panel. For additional control, IT administrators can also prevent certain file types from being indexed via Group Policy.

By default, the following file types are indexed as text:

.a, .ans, .asc, .asm, .bas, .bat, .bcp, .c, .cc, .cls, .cmd, .cpp, .cs, .csa, .cxx, .dbs, .def, .dic, .dos, .dsp, .dsw, .ext, .faq, .fky, .h, .hpp, .hxx, .i, .ibq, .dl, .idq, .inc, .inf, .ini, .inl, .inx, .jav, .java, .js, .kci, .lgn, .log, .lst, .m3u, .mak, .map, .mdb, .mk, .odh, .odl, .pl, .prc, .rc, .rc2, .rct, .reg, .rgs, .rul, .s, .scc, .sol, .sql, .tab, .tdl, .tiff, .tlh, .tli, .trg, .txt, .udf;udt, .usr, .vbs, .viw, .vspscc, .vsscc, .vssscc, .wri, .wtx

Windows search can also index .xps files as text if the application that created the files does not rasterize the file.

By default, the following file types are excluded from the index:

.386, .aps, .bin, .bk1, .bk2, .bkf, .blf, .bsc, .btr, .cat, .cfg, .cgm, .chk, .ci, .crwl, .cur, .dat, .dbg, .dct, .dir, .dl_, .el, .evt, .ex_, .exp, .eyb, .fnt, .fon, .ghi, .gthr, .hqx, .icm, .idb, .idx, .ilk, .imc, .in_, .ini, .inv, .ipp, .jbf, .lib, .local, .log, .log1, .log2, .m14, .mac, .man, .manifest, .map, .MAPIMail, .mmf, .mui, .muimanifest, .mv, .ncb, .obj, .oc_, .ocx, .onecache, .onetoc, .onetoc2, .ost, .pch, .pdb, .pds, .pf, .pic, .pma, .pmc, .pml, .pmr, .pst, .res, .rmp, .rpc, .rsp, .sbr, .sc2, .sit, .sr_, .sy_, .sym, .tlb, .tlh, .tmf, .tmp, .ttc, .ttf, .ufm, .vbx, .vxd, .wll, .wlt, .xbm, .xix, .z96, .ZFSendToTarget

File Systems and Removable Media Support

Windows Search indexes all drives that specify themselves as either DRIVE_FIXED or DRIVE_REMOVABLE from the WIN32 API GetDriveType Function, except floppy drives. Windows Search can also index digital cameras, card readers, thumb drives, and firewire drives as long as they identify themselves as removable drives.

Natively, WS indexes NTFS drives with notifications, which means that a notifications provider notifies Windows Search that data on the drive has changed so Windows Search can update its index. Windows Search also natively supports FAT drives, but without notifications. In this case, Windows Search periodically crawls the drive looking for changes in data.

If you install the optional Add-in for Files on Microsoft Networks (a UNC/FAT protocol handler), Windows Search indexes UNC shares, FAT32 drives and FAT drives with notifications.

For a list of downloadable add-ins, visit the Windows Desktop Search: Personalize It page.

See Also

Vindt u dit nuttig?
(1500 tekens resterend)
Bedankt voor uw feedback

Community-inhoud

Toevoegen
Weergeven:
© 2014 Microsoft