Indexing Service
<templatestyles src="Module:Hatnote/styles.css"></templatestyles>
| A component of Microsoft Windows | |
|---|---|
The Indexing Service Query Form, used to query Indexing Service catalogs, hosted in Microsoft Management Console.
|
|
| Details | |
| Type | Desktop search |
| Included with | Windows NT 4.0 Option Pack[1] Windows 2000[2] Windows XP[3] Windows Server 2003[3] Windows Server 2008[4] |
| Replaced by | Windows Search |
| Service name | Indexing Service |
| Description | Indexes contents and properties of files on local and remote computers; provides rapid access to files through flexible querying language. |
Indexing Service (originally called Index Server) was a Windows service that maintained an index of most of the files on a computer to improve searching performance on PCs and corporate computer networks. It updated indexes without user intervention. In Windows 7, it has been replaced by Windows Search.
History
Indexing Service was a desktop search service included with Windows NT 4.0 Option Pack[1] as well as Windows 2000 and later.[2][3][5] The first incarnation of the indexing service was shipped in August 1996[1] as a content search system for Microsoft's web server software, Internet Information Services.[citation needed] Its origins, however, date further back to Microsoft's Cairo operating system project, with the component serving as the Content Indexer for the Object File System. Cairo was eventually shelved, but the content indexing capabilities would go on to be included as a standard component of later Windows desktop and server operating systems, starting with Windows 2000, which includes Indexing Service 3.0.[citation needed]
In Windows Vista, the content indexer was replaced with the Windows Search indexer which was enabled by default. Indexing Service is still included with Windows Server 2008 but is not installed or running by default.[4]
Indexing Service has been deprecated in Windows 7 and Windows Server 2008 R2.[6] It has been removed from Windows 8.
Search interfaces
Comprehensive searching is available after initial building of the index, which can take up to hours or days, depending on the size of the specified directories, the speed of the hard drive, user activity, indexer settings and other factors. Searching using Indexing service works also on UNC paths and/or mapped network drives if the sharing server indexes appropriate directory and is aware of its sharing.
Once the indexing service has been turned on and has built its index it can be searched in three ways. The search option available from the Start Menu on the Windows Taskbar will use the indexing service if it is enabled and will even accept complex queries. Queries can also be performed using either the Indexing Service Query Form in the Computer Management snap-in of Microsoft Management Console, or, alternatively, using third-party applications such as 'Aim at File' or 'Grokker Desktop'.
Microsoft Index Server 2.0 does not detect changes to a catalog if the data is located on a mounted partition. It does not support mounted volumes because of technical limitations in the file system.[7]
References
- ↑ 1.0 1.1 1.2 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 2.0 2.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 3.0 3.1 3.2 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 4.0 4.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
