May there is a possibility to add user / pass of each network share
for scenarios where
Everything indexing and client installed as service on a server
(index a networkshare, provide an ETP server, local clients access the results {same mount drive name}).
Its little bit tricky to set credentials for mounted network share and indexing-service.
In v1.4 this setup works.
But in 1.5 I had no luck. Seems (console) indexing works but nothing is stored in database.
Thx
Alfa.
Network Share Credentials
Re: Network Share Credentials
So you:
- have a folder on the server: D:\data\Sales
- share that as X:\ to the clients
- configured the clients to have access to X:\ through Explorer (without providing extra credentials)
- mapped the D:\data\Sales folder as X:\ on the server too
- Index X:\ on the server
?
In that case it should not be necessary to provide credentials for users on PCs that run the ETP client.
Or are you running Everything as administrator on these client PCs?
Network mappings are per-user, so it is very likely that the elevated admin account does not have the same X:-mapping.
- have a folder on the server: D:\data\Sales
- share that as X:\ to the clients
- configured the clients to have access to X:\ through Explorer (without providing extra credentials)
- mapped the D:\data\Sales folder as X:\ on the server too
- Index X:\ on the server
?
In that case it should not be necessary to provide credentials for users on PCs that run the ETP client.
Or are you running Everything as administrator on these client PCs?
Network mappings are per-user, so it is very likely that the elevated admin account does not have the same X:-mapping.
Re: Network Share Credentials
Nearly.
There is a NAS with fileshare and an AD (user accounts).
Each client has mounted the fileshare to x:\.
Than there is a Windows VM hosting the Everthing solution like an server; 2 services - indexer and client (hosting the ETP).
At this host the fileshare is also mount as x:\ and use an AD user account with lowest user-rights (e.g. no sales access so that indexer do not crawl this folders).
In V1.4 this drive is added as "folder".
The indexer service runs also with these limited rights user-account. '
The everthing-client service runs with default system-account.
On the clients side Everthing is running and connected via ETP to server with linked-type "c" so that results like x:\folder\file1.pdf works.
That works pretty good for V1.4.x
But same setup do not work with V1.5.
In V1.5 saw the new option "network share".
I see the dvantages using user & pass for each network share and skip complex configuration setup.
br
Alfa
There is a NAS with fileshare and an AD (user accounts).
Each client has mounted the fileshare to x:\.
Than there is a Windows VM hosting the Everthing solution like an server; 2 services - indexer and client (hosting the ETP).
At this host the fileshare is also mount as x:\ and use an AD user account with lowest user-rights (e.g. no sales access so that indexer do not crawl this folders).
In V1.4 this drive is added as "folder".
The indexer service runs also with these limited rights user-account. '
The everthing-client service runs with default system-account.
On the clients side Everthing is running and connected via ETP to server with linked-type "c" so that results like x:\folder\file1.pdf works.
That works pretty good for V1.4.x
But same setup do not work with V1.5.
In V1.5 saw the new option "network share".
I see the dvantages using user & pass for each network share and skip complex configuration setup.
br
Alfa
Re: Network Share Credentials
Everything doesn't have an option to specify credentials for network shares.
You'll need to do this with Windows Credentials.
Everything on the Server is not seeing your X: drive.
Does running the Everything ETP/FTP server as a normal logged in user work?
Verbose debug logs will help find the issue.
Could you please send logs to support@voidtools.com
You'll need to do this with Windows Credentials.
Everything on the Server is not seeing your X: drive.
Does running the Everything ETP/FTP server as a normal logged in user work?
Verbose debug logs will help find the issue.
Could you please send logs to support@voidtools.com