I could not find anything useful on that topic, so I am once again turning to you.
I want to be able to search files on a shared folder using Windows 10. The shared folder is on a file server running Server 2012 R2.
- The shared folder should be indexed.
- The search must use an index (fast, cheap) and not search the file system (slow, expensive).
- The index must be made available by the server and not be created by the client (expensive if having many clients).
- Must work out-of-the-box or with Microsoft-Tools. No 3rd-Party applications.
I found information that I could add mapped drives to the indexed paths list, but mapped drives do not show up in the selection. Besides, it would violate #3.
I know about the Windows Search feature in Server 2012. I haven't found information on how to use it in cooperation with the clients.
How would I achieve that?
Install the Windows Search Index Service on the server. Then, in the Control Panel, open the Index Options, and and the file shares to the indexed locations.
This should do it.
Pascal
I know this is an old question but I want to answer this as it is still relevant today.
When the server has the "Windows Search" feature installed through the server manager it will be capable of indexing files that it is sharing with the domain/network(in other words stored on its hard drives) and allow a windows 10 computer to utilize the index for search purposes. In the control panel of the server you can access the "Indexing Options" and configure the indexing locations (on the server hard drive that will be shared over the network), the indexing types (i.e. .PDF, .docx ...), content indexed(file name or file name and file contents), and other settings. It is a very strait forward implementation and I would agree that there is a lack of good documentation on this subject.
To answer your question, if you have correctly setup the search on the server then you don't need to do anything on the client to use the servers index assuming that the client is a standard installation and has access to the server shared folder.
Example:
ISSUE: there is a condition on windows server 2012 r2 essentials that I have not found the resolution to in which the client computer will not use the index on the server. The condition is if you are using the "Shared Folders" in the address like "//fileserver/Shared Folders/Company" instead of "//fileserver/Company" which will utilize the index on the server. I have created a new question to try to resolve this here