Network Index Include Only Remapping

[verviers]

The Everything Server

I have some troubles with this feature. There are two instance in my case:
1) Server (PC1). "Everything" is installed, server is running, two volumes (F, H) are included in "shared" index. These volumes are also shared for network users.


2) Client (PC2). "Everything" is installed, network index is set as connected in settings. Volumes (F, H) from PC1 are mapped as network drives (standard Windows feature) and managed drive letters for these disks - F, H.

When I run "Everything" software on PC2, it starts to index disks F, H despite of setting to include only disk "С" in local index (Options->Indexes->NTFS->). It may look logical, because they are networked.


But I need to use shared index from PC1 for mentioned volumes. As far as I understand, Exclude list (Options->Exclude->Exclude folders) functions as global. And if I include F, H folders here, there they don't show up in Everything at all.

Maybe i missed smth... Is it possible to exclude such a double indexing work?

[NotNull]

Are these network drives listed under Menu:Tools > Options > Indexes > Network Drives too?
In that case:
- remove them
- Disable Automatically include new mapped network drives

[verviers]

Are these network drives listed under Menu:Tools > Options > Indexes > Network Drives too?

Yes, they are. But checkboxes for including these drives into database are not set.






I have found out, that indexing process status shows "Indexing properties" in my case. And settings of properties to index (Options->Indexes->Properties) in PC1 index differ from settings of properties in PC2. So may it be the reason or bug?

[void]

It sounds like a mapping issue.

What Include only settings are you using on the server?
It looks like you are not remapping F:, H: to anything.

On the Everything Server, please try mapping F: to \\server\F
(if you share the F: drive as F)


-or-

Add each share:
Please try mapping F:\share1 to \\server\share1
Please try mapping F:\share2 to \\server\share2




On the clients, please leave the Include only field empty.
This will use your server remappings.

[verviers]

It sounds like a mapping issue.

I don`t know, cause I am newbie to such unusual functions of Everything. I read this topic for example, but still do not understand sequence of settings in my case. So let's start from the beginning. These are my options:

Server

1.png (19.7 KiB) Viewed 1401 times

2.png (19.3 KiB) Viewed 1401 times

3.png (22.49 KiB) Viewed 1401 times

[verviers]

Client

4.png (17.15 KiB) Viewed 1399 times

5.png (19.72 KiB) Viewed 1399 times

6.png (20.13 KiB) Viewed 1399 times

[verviers]

Sorry for my slowness. I can attach only three images to a post.

So as a result
Server

10.png (1.71 KiB) Viewed 1395 times

Client

9.png (6.73 KiB) Viewed 1395 times

[void]

Please ignore Allow custom remapping of file paths.
This is unrelated to the Everything Server.

On the server, what volumes are you indexing under Tools -> Options -> NTFS? (eg: K)
On the server, what volumes are you sharing? (eg: \\server\K)

On the client, are you using mapped network drives? (eg: K: => \\server\K)

With the above information I can help with your Everything Server setup.



The Everything Server does not provide properties to clients yet.
Only filenames, size, date modified, date created and file attribute information is provided.
A property server is on my TODO list.
You can still index properties on all clients.
However, each client will maintain its own database of properties.