Hi - I've been trying this on my workstation and it works great.
I'd like to try it on our fileserver at work. It runs on Windows Server 2007. My idea is then colleagues can use it to search for files through their web browser; would be much quicker than the usual Windows search. Couple of questions:
Any reason it won't work on Server 2007?
Is it possible for it to return UNC paths?
Being able to customize the UNC paths would a very useful feature.
I'm trying to find ways to help my team seach for files quicker and Everything has some real potential here. However there is the issue of network/mapped drives vs. local drives. It may cause more usability issues than it solves, with people getting confused over the drive letter that Everything returns is different from their mapped drive letter.
Some people are Google searchbar and Microsoft search, both tend to put quite a load on their workstations (I know they index content as well). But I like the fact that Everything is a central database and is much lighter resources than many other search solutions.
On top of this I have a mix of Mac and Windows users (both accessing the same Windows fileserver), hence I was thinking that the http output would most user-friendly here, although that would need the UNC output.
I may try testing it on a archive server we have set up for old completed jobs.
In the meantime, I'm very impressed with the program and will follow its development with interest.