Compatible with Server 2007?

If you are experiencing problems with "Everything", post here for assistance.
Post Reply
brip
Posts: 2
Joined: Sun Mar 22, 2009 11:43 pm

Compatible with Server 2007?

Post by brip »

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?
Cheers.
David
Developer
Posts: 430
Joined: Tue Mar 17, 2009 1:42 am

Re: Compatible with Server 2007?

Post by David »

I have not tested Everything on Windows Server 2007.
However, "Everything" should be compatible with Windows Server 2007.

> Is it possible for it to return UNC paths?

For the HTTP client this is not possible yet.

For the ETP client this is possible by disabling 'use FTP links'.
However, "Everything" uses hard coded UNC paths.

For example, on the server you might have the file:
C:\Windows\Notepad.exe

Everything will show this as \\server\C\Windows\Notepad.exe

So you will need to share your C: drive as C

I can understand if you do not want to do this.

Customizing the UNC paths is planned for a future release of "Everything".
brip
Posts: 2
Joined: Sun Mar 22, 2009 11:43 pm

Re: Compatible with Server 2007?

Post by brip »

Thanks for your reply David.

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.
Post Reply