Indexing contents of ReadyNAS for search?

I assume that your ReadyNAS shares are mapped to Windows drive letters, and your "searches for content" are initiated through the built-in Windows Search. I would imagine that in that situation, the Windows indexing service would work on your NAS shares as well as on all your other drives. Is that not true (or have I misunderstood your basic setup)?

fastfwd wrote:
I assume that your ReadyNAS shares are mapped to Windows drive letters, and your "searches for content" are initiated through the built-in Windows Search. I would imagine that in that situation, the Windows indexing service would work on your NAS shares as well as on all your other drives. Is that not true (or have I misunderstood your basic setup)?

Microsoft indexing doesn't work on network drives on Windows 7 or later.

There is a solution here: http://www.intraipsum.se/blog/2013/02/0 ... r-windows/ I haven't tried it, so I have no recommendation about it though.

Also, there is a risk to leaving network folders mapped - cryptolocker affects mapped drives, but it doesn't affect network shares that aren't mapped. I'm not saying you shouldn't map them, just pointing out the threat.

StephenB wrote:
Microsoft indexing doesn't work on network drives on Windows 7 or later.

Ah, didn't know that. Thanks.

StephenB wrote:
Microsoft indexing doesn't work on network drives on Windows 7 or later.

I thought so as well, but as I was digging I kept coming up with tips on how to do just that. So something clearly wasn't right. Why didn't it work for me when it did for them?

I finally found the answer. It turns out it can be done, but only on NTFS-based shares. Here's the how-to; pretty standard stuff.

So it does work... just not for us :(

Thanks,
Jeff Bowman
Fairbanks, Alaska

InteXX wrote:

StephenB wrote: Microsoft indexing doesn't work on network drives on Windows 7 or later. I thought so as well, but as I was digging I kept coming up with tips on how to do just that. So something clearly wasn't right. Why didn't it work for me when it did for them? I finally found the answer. It turns out it can be done, but only on NTFS-based shares. Here's the how-to; pretty standard stuff. So it does work... just not for us :(

The folks on your how-to thread also say that even with shares mounted from other windows systems they could only get it to work with photos, not with videos or music.

You can put get nas shares into your library folders with some effort (though they aren't indexed). Though I might be ok with that on a desktop, I don't think its the best idea on a laptop or surface. It'd be too easy to put something on the NAS that you'd intended to access locally.

StephenB wrote:
The folks on your how-to thread also say that even with shares mounted from other windows systems they could only get it to work with photos, not with videos or music.

Right... I saw that right after posted. I was hoping you wouldn't catch it, but... you don't miss a trick, do you? ;)

StephenB wrote:
You can put get nas shares into your library folders with some effort (though they aren't indexed).

I managed to get that far with mklink, but since my end goal is indexing the shares into search results I ditched the effort when I found that tip.

StephenB wrote:
Though I might be ok with that on a desktop, I don't think its the best idea on a laptop or surface. It'd be too easy to put something on the NAS that you'd intended to access locally.

I thought of that when I made my mklink; I put it in an obscure location for that reason. But it didn't work out in the end, so it didn't really matter either way.

Thanks,
Jeff Bowman
Fairbanks, Alaska

StephenB wrote:
fastfwd wrote: There is a solution here: http://www.intraipsum.se/blog/2013/02/0 ... r-windows/ I haven't tried it, so I have no recommendation about it though.

Good find, thanks. I can use that EnableLinkedConnections for something else I'm working on, too.

Thanks,
Jeff Bowman
Fairbanks, Alaska