Shared database of Network Drives?

[woodgrain]

Hi All,

New to this software.

I am running a Windows 2012 R2 server at home with multiple mapped drives (F: Files, M: Music, P: Photos, etc), can I install and run this software on the server with the database stored in a shared location, and then have the desktops/laptops use that database (preferably in a read only fashion) for searching those mapped drives?

Thanks.

[void]

Please share your Everything.db folder on your server, for example:
\\server\EverythingDB

Your Everything.db should be located in %LOCALAPPDATA%\Everything
You can change this in Everything -> Tools -> Options -> Indexes -> Database location.

Please try running the following on your clients:

Everything.exe -db \\server\EverythingDB\Everything.db -read-only

Help on these command line options:
-db \\server\EverythingDB\Everything.db
-read-only

Please also consider filelists or folder indexing.

A server / client model is planned for the next major version of Everything.

[woodgrain]

ooh, that's exciting.

And I assume I'd have to have the same mappings on the server that I have on the PC's and index the mapped drives on the server?
That is, map the M: drive on the server itself for music, and then on the server index the M: drive rather than the local disk?

[woodgrain]

A server / client model is planned for the next major version of Everything.

*drools at the prospect*
Any rough ETA?

[void]

And I assume I'd have to have the same mappings on the server that I have on the PC's and index the mapped drives on the server?

Correct.
Use subst on the server and then use a mapped network drive on the clients.

To exclude your C: drive from the Everything index on the Server:

• In Everything, from the Tools menu, click Options.
• Click the NTFS tab on the left.
• Select C:
• Uncheck Include in database.

If you did want to search your C: drive on your server with Everything, consider using multiple instances.



To force Everything on the server to update the Everything.db on disk:

• Run Everything with the -update command line option:
  Everything.exe -update

You will need to restart clients in order for them to use the latest Everything.db

I'm working on the client/server model, no ETA yet.

[Alfa]

I'm working on the client/server model

Great idea. The tools on the market esp. MS indexer sucks resp. does not work on very large file systems.

Very interesting feature would be:
- client server connection http based webservice (firewall issues)
- search result filtered according the user rights of the domain user

and may a business version supporting DFS.

and may a open source version to contribute?

[NotNull]

- client server connection http based webservice (firewall issues)

Different from the embedded HTTP Server?

- search result filtered according the user rights of the domain user

Do you have a suggestion how that should work?
(I have thought about it in the past, but saw too many challenges like checking the ACL's - including nested ACE's - for millions of files every search query)

[Alfa]

Different from the embedded HTTP Server?

No, exactly this solution. Didnt see the http server options.

Do you have a suggestion how that should work?

Hmm, unf. not. Motivated I've just read some internet articles about it. Ohje, it is absolute not trivial.


May it is usefull to start with a lightway server indexer version.
The end user can configure on server side one AD-user, which the files are craweld.
I would configure the user with less rights, e.g. no access to sales directories,...

May more than one crawler AD user can configured. For each configured one index (table) is build.


The full version, including content indexing, years later
The ACL (aclParent, aclAccess, aclDeny) have to stored in additional columns. Can get via powershell (get-acl FILENAME).

If like this arcticle (url posting allowed?)
searchtechnologies.com/blog/search-engine-security

[NotNull]

(url posting allowed?)

Yes, use the link button:

2019-10-12 21_13_04-voidtools forum - Post a reply.png (6.31 KiB) Viewed 8971 times

Everything You Ever Wanted to Know about Search Engine Security

Simpler version:
https://www.searchtechnologies.com/blog ... e-security

This is how that is shown when editing your message (one line):

Code: Select all

[url=https://www.searchtechnologies.com/blog/search-engine-security]
Everything You Ever Wanted to Know about Search Engine Security[/url]

Simpler version:

Code: Select all

[url]https://www.searchtechnologies.com/blog/search-engine-security[/url]

Thanks for that link, Alfa. Interesting read, although there is room for improvement (especially regarding Windows security), but all relevant issues (that I can think of) are being discussed. Very thorough.


Beside an embedded HTTP Server, Everything has also the possibility for a ETP Server. That is a client/server Everything solution where you can use the 'normal' Everything GUI client-side.
I guess it should be possile to run multiple ETP servers side-by-side (never tested that) to cater to multiple usergroups.


Thanks for your thoughts!

[woodgrain]

Regardless of the searching and indexing, share/security permissions will still apply when the user tries to access the folder and contents. So unless you're naming your files with secure information, which would be weird, there shouldn't be any issues. It'd surely be impossible to restrict search results based on ACL's, they can change at any time not to mention group based membership changes.