Re: using XP Search Companion to search remote index server, and, how to specify catalog?

WenJun (and anyone who has a solution for this),

I have configured a remote indexing server as per the example provided and it works. I can query //myserver/user as in the example
from a remote PC.

However, it does not fully address my situation.

I want to configure index server to index network shared locations, and then search them using the Search Companion.

I do know how to configure index server to index the location, namely by entering the UNC into the 'Path' field of during 'Add
Directory'. I have already created such a 'proof of concept' catalog, named POC_Catalog, stored on the index servers local D:
drive in D:\Catalogs\POC_Catalog\catalog.cwi

What I can't figure out is whether it is possible to query my POC_Catalog using Search Companion.

I am able to query it remotely using other tools:

If I opening in MSIE this file: C:\WINDOWS\Help\ciquery.htm#machine=myserver,catalog=POC_Catalog it lets me query the remote catalog
successfully.

If I use the tool called 'AimAtFile' (http://www.aimingtech.com/aimatfile/index.htm), I can search the remote catalog if I use this
syntax to specify the catalog:

query://myserver/POC_Catalog

And I understand it is possible to write VB, VBA, ASP, etc code to search remote index servers that have indexed UNC content.

But, I really would like to be able to query my remote index server catalog using Search Companion.

I have tried a few different ways of providing the remote catalog to the search companion, using differnt syntaxes (including the
one that AimAtFile uses: query://myserver/POC_Catalog), but I'm guessing here, and it doesn't work.

Has anyone solved this?

Thanks Much

Malcolm Cook

Hi Malcolm,

The searching companion has the ability to automatically comunicate with
remote server's indexing service and look up if the query is included in a
catalog. If true, then the indexed data will be returned rapidly. Please
refer to the following instructions:

Starting with Windows 2000, File Server search performance can be enhanced
by using the Indexing Service to return search results from client requests.

Windows Clients also have the Indexing Service installed. It is NOT
necessary to add the remote file share to the local Index Server catalog.
In fact, the Indexing Service does NOT have to be running on the client
computer.

A file search from a Windows 2000 or XP client will interogate the File
Server's Index Server configuration and attempt to match up the file share
name with a UNC Alias specified in the Index Server Catalog's directory
configuration. If a match is found, then Index Server will be used to
return the results. If not, then the slower file scan will be performed.

The following procedure demonstrates how to configure Index Server catalog
on a file server to provide this functionality.

1) Create a home directory for the users named C:\Users with at least
Read and List permissions. An existing directory can also be used.
2) Share the directory as "Users" with a minimum of Read permissions.
3) Create a new directory named C:\Catalogs\User_Catalog.
4) Run the Computer Management MMC, COMPMGMT.MSC.
Expand "Services and Applications"
Expand "Indexing Service"
5) Right-click on "Indexing Service" and select "All Tasks" -> "Tune
Performance"
Select "Dedicated"
6) Right-click on "Indexing Service" and select New -> Catalog.
Name: USER_Catalog
Location: C:\Catalogs\User_Catalog
A message will be displayed stating that the Indexing Service must be
restarted. Ignore for the moment.
7) Expand the User_Catalog catalog, right-click on Directories and select
New -> Directory.
In the "Add Directory" box, enter the following information.
Path: C:\Catalogs\User_Catalog
Alias (UNC): \\servername\users <- This must be
specified and it must match the share name.
8) Right-click on "Indexing Service" and select "Stop".
9) Right-click on "Indexing Service" and select "Stop".
10) Click on "Indexing Service" wait for the "Documents to Index" to reach
0, then test the remote search.

The directories can be moved to any drive, as long as the appropriate
permissions are provided.

The following changes will cause a file scan to be performed.
- The Index Server Catalog directory does not have a UNC Alias.
- If a UNC Alias is not specified and the "Add Network Share Alias
Automatically" is checked, when the Indexing operation completes, a second
entry for the directory, which is a slight green color, will be added with
the network share name.

The following changes will cause the client search to display "There are no
results to display".
* The Index Server Catalog directory contains only the server name.

============================================================================
========
Articles that describe this functionality (very briefly)

File server role: Configuring a file server
http://technet2.microsoft.com/WindowsServer/en/Library/72ad1371-25c2-458f-96
39-77889d78a9761033.mspx
Indexing Service creates indexes of the contents and properties of
documents located on your local hard drive or on shared network drives.
These indexes enable users to perform faster, easier searches. Indexing
Service can slow down the server, so use it only if users frequently search
the contents of files on this server.

Windows 2003 - Disk and file management features
http://technet2.microsoft.com/WindowsServer/en/Library/f9ab004e-09b7-4e3f-8e
f8-13d699de67061033.mspx
You can use Indexing Service to provide a fast, easy, and secure way for
users to search for information locally or on the network. Users can
search in files in different formats and languages, either through the
Search command on the Start menu or through Hypertext Markup Language
(HTML) pages that they view in a browser.

Best Regards,

WenJun Zhang

Microsoft Online Community Support

==================================================

Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at:

http://msdn.microsoft.com/subscriptions/support/default.aspx.

==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.



.

Relevant Pages

  • RE: Search Functiopn stopped working
    ... your topology page, uncheck the index server option, and delete and rebuild ... Index server or detach the Job process please - not sure how to do either ot ... Stop and restart the search service. ... I've tried clicking on "Configure Search and Indexing" on our servers Site ...
    (microsoft.public.sharepoint.portalserver)
  • Re: Index server - Sharepoint - migration
    ... Why would you need the old indexing product? ... Microsoft Application Center & Index Server Support ... |> sharepoint portal server and indexing services are different products ...
    (microsoft.public.inetserver.indexserver)
  • Re: Search Functiopn stopped working
    ... your topology page, uncheck the index server option, and delete and rebuild ... "Mike Dower" wrote: ... Index server or detach the Job process please - not sure how to do either ot ... I've tried clicking on "Configure Search and Indexing" on our servers Site ...
    (microsoft.public.sharepoint.portalserver)
  • Re: Moving Index funtion to a new server
    ... indexing functionality seems to have worked, I am unable to carry out any ... though there is an issue with the indexes propogating from the index server ...
    (microsoft.public.sharepoint.portalserver)
  • RE: SharePoint and Server 2003 service pak
    ... The last two days I have been working on restoring the indexing ... After installing W2K3 SP1 the ... web/search server, one indexing/job server and one SQL server. ... It turns out that before SP1 was installed the user which is connecting to ...
    (microsoft.public.sharepoint.portalserver)
Loading