KevinGW

In my options there is no listing of mapped networked drives for indexing. Is there a reason for this. How do I get mapped drives to be indexed so they can be searched

Re: Windows Desktop Search Development Indexing Mapped Drives

Eric Wolz - MSFT

What version of WDS are your using

On 3.x we only index fixed disks due to the fact that we rely on the NTFS change journal to detect modified files. To index network locations, please upgrade to 3.01 (http://support.microsoft.com/kb/917013). Indexing network locations is now included in the updated version. You can add these locations by going into the Indexing Configuration control panel. The last tab on the right allows you to enter network paths.






Re: Windows Desktop Search Development Indexing Mapped Drives

Gerald Haslhofer

If you have a mapped network drive, you should also see it in the Indexed Locations control panel with a network share symbol. Please let us know if you don't.




Re: Windows Desktop Search Development Indexing Mapped Drives

Caillin

Yes, the version I am running is definitely 3.01

I downloaded and installed it the day before I posted that question. Is there any way to double-check the installed version through any of the menus I couldn't find any.

When I add either \\server\share or "G:" (Mapped drive letter to UNC path) to the "Default Indexed Paths" group policy setting, and run "gpupdate" then "Share on Server" appears in the "Included Locations" list in the Indexing Options, but it doesn't actually index that location.

When I click Modify, and it allows you to manaully tick locations, the "share on server" is at the top, but the box isn't ticked.

Before I roll this out to production terminal servers, I need to make sure that I can preconfigure the indexing settings via group policy reliably.

Am I the only person who is seeing this problem

Edit:  Found the version in Add/Remove prgorams, it's definitely 3.01. This is the latest version




Re: Windows Desktop Search Development Indexing Mapped Drives

Gerald Haslhofer

If you add a path using group policy, you need to use the following format:

ofts://{*}/server/path/*

Does this work






Re: Windows Desktop Search Development Indexing Mapped Drives

Gerald Haslhofer

Also, when you open the event log, do you see warning / error messages in the "Application" part of the event viewer for source "Windows Search Service", category "Gatherer", possibly event ID 3036 If yes, what do they say






Re: Windows Desktop Search Development Indexing Mapped Drives

Caillin

The only event error is Gatherer: 3024.

"The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.

Context: Windows Application, SystemIndex Catalog"


I've tried every combination of the otfs formatting, but none of it works. Is there any kind of documentation or examples of how the path should be formatted in GP

Surely someone else out there has tried to get the GP working with default indexed paths




Re: Windows Desktop Search Development Indexing Mapped Drives

Gerald Haslhofer

To trouble shoot this, would you mind

-setting the appropriate GP

- forcing an update (gpupdate /force)

- exporting a section of your registry (HKLM/Software/Microsoft/Windows Search/CrawlScopeManager) to a txt(!) file and sending this to gerald.haslhofer at microsoft dot com






Re: Windows Desktop Search Development Indexing Mapped Drives

Caillin

Which "path" setting do you want me to try for exporting of the keys:

G:\
G:\*
file:///g:\
file:///g:\*
\\server\share
\\server\share\*
ofts://{*}/server/path/
ofts://{*}/server/path/*
otfs://{*}\<servername>\<path>\
otfs://{*}\<servername>\<path>\*

These are all the different ways I've tried to get the default indexed path to work. Between this thread and my other one, I've gotten so many different formatting options for this one entry.




Re: Windows Desktop Search Development Indexing Mapped Drives

Gerald Haslhofer

Please use

otfs://{*}/<servername>/<path>/*

-Gerald






Re: Windows Desktop Search Development Indexing Mapped Drives

Caillin

This did the trick Gerald, thanks for your help.

Can I make a suggestion for the new Administrator's guide, that you can put in an example of the format needed for this field

Or even better yet, whoever is in charge of putting in the descriptions in the ADM templates, to say that they need to be in the format of otfs://{*}/<servername>/<path>/*

I doubt I'd be the only person that assumed it would be in the format of "G:" or "\\servername\share" considering these options both work when manually selecting the index path in the client.

Thanks again for your help.




Re: Windows Desktop Search Development Indexing Mapped Drives

DavideValenti

Well, Gerarld, it seems I have the same problems here; the difference is that for me the format otfs://{*}/<servername>/<path>/* is not working.


the only one which at least makes something (I see the paths in the Indexed paths in WDS options) is the following:

otfs://{*}\<servername>/<path>/*

(Backslash on before the servername)

But even in this case, the path is not indexed. What's wrong with me Please help!

Even in the administration guide, the use of forward and backslach are puzzling: sometimes they use forward slash, sometimes backslash!!!!

Default Indexed Paths

Enabling this policy allows you to specify a list of paths to index by default. The user may override these paths and exclude them from indexing.

The format of the paths URLs are:

Protocol://site/path/file

An example of a local machine path is file:///C:\*

An example of a network share is

otfs://{*}\<servername>\<path>\*

otfs://localhost/<drive>/<path>/* (for the <drive> part it should be specified as ¡°c¡± not ¡°c:\¡±

Note You would only use this with a local drive if it were a FAT drive instead of NTFS.

OS: Windows XP, Windows Server 2003

Default Excluded Paths

Enabling this policy allows you to specify a list of paths to exclude from indexing by default. The user may override these paths and include them in indexing.

The format of the paths URLs are:

Protocol://site/path/file

An example of a local machine path is file:///C:\*

An example of a network share is ofts://{*}/server/path/*

OS: Windows XP, Windows Server 2003