Sign in to follow this  
Followers 0
capr

indexing network drive?

12 posts in this topic

Hey, I want windows 7 search to index my network drives so I can search them quicker (they are large with tons of c**p that changes everyday). I looked under windows search/indexing options and they don't let me pick a network drive as a destination. 

 

I saw that making the drive available offline might help but I really don't' want to do that for various reasons. 

 

Ideas? Is there a 3rd party program that will help index the drives (google desktop was it?)?  

Share this post


Link to post
Share on other sites

It was removed in windows 7 for some reason, Your files have to be on a windows box to get indexing now.

Share this post


Link to post
Share on other sites

I use locate32 to create a index of my network shares.

http://sourceforge.net/projects/locate32/

Yes there is a 64bit version. I just have it update the database once a day in the morning, etc.

Share this post


Link to post
Share on other sites

If you create a new library and add the network drive's folders to it then it'll index it automatically.  In 8.1 you'll have to go to view in Windows Explorer to make Libraries available to view. 

Share this post


Link to post
Share on other sites

If you create a new library and add the network drive's folders to it then it'll index it automatically.  In 8.1 you'll have to go to view in Windows Explorer to make Libraries available to view. 

that didn't work. Windows only allows indexed folders to be added as libraries. 

 

 

I use locate32 to create a index of my network shares.

http://sourceforge.net/projects/locate32/

Yes there is a 64bit version. I just have it update the database once a day in the morning, etc.

creating the .db right now. I am googling a way to point windows search at this so it can be integrated. 

 

OMG i love locate32. small db size and super quick 

Edited by capr

Share this post


Link to post
Share on other sites

Yup its SUPER quick -- would I steer you wrong ;)

Share this post


Link to post
Share on other sites

Hello,

would I steer you wrong ;)

:laugh:

Share this post


Link to post
Share on other sites

My understanding (and am happy to be shot down here) was that you index the files on the SERVER, and then the client, when searching, searches said index?

Share this post


Link to post
Share on other sites

Well yeah how else would it work?

 

Locate32 finds files and directories based on file and folder names stored in a database. Locate32 saves to a database the names of all files on your hard drives. Once the file indexing has occurred, you can locate files quickly by using the application's search form. It works like "updatedb" and "locate" commands in Unix. In other words, it uses databases to store information about directory structures and uses these databases in searches. The use of these databases provides very fast searching speed. The software includes a dialog-based application as well as console programs that can be used to update and access the databases. Locate32 is not primarily meant to find text or data within files, but it has a primitive feature to do this.

Share this post


Link to post
Share on other sites

Well yeah how else would it work?

 

The attitude is not necessary, but it is generally expected.

 

How else would it work?  Well it COULD work by the client having an index.  It'd be a ridiculous idea, but I was making the difference known.

Share this post


Link to post
Share on other sites

Attitude? [longer comment snipped upon not wanting to upset the 13 year old girls around here with comments that might offend ;) Dude your mistaken, I was in no way trying to be smartass or lippy or condescending, your reading tone into it if that is your take.  I was simply agreeing with you and asking a question]

 

The db is on the client..  I think your not misunderstanding where the db is maybe?  How you worded it would be the client creates the index(db) and then yeah he searches it.  Then you go to say "Well it COULD work by the client having an index" which is exactly what you said the first time.

 

Where do you think the db is stored?  The client running locate32 is the one creating the db, so it would be stored where ever you configured the software to store it, and it searches mapped drives just like it would a local drive.

 

Now there is a tool search everything http://www.voidtools.com/ that runs on the server and indexes its files - and then you can query that..

Share this post


Link to post
Share on other sites
Dude your mistaken, I was in no way trying to be smartass or lippy or condescending, your reading tone into it if that is your take.  I was simply agreeing with you and asking a question

 

Then I humbly apologise.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.