How to index and search files within a shared folder using Windows Server 2012 R2 and Windows 10?Server 2012 R2 Essentials Search not working on “Shared Folders”Windows 2012 Shared Drives Odd Latency IssueWindows Search in Outlook 2013 on Remote Desktop Service Windows Server 2012R2Group Policy: Mapped Drives failing to load, Windows Server 2012 Active Directory and Windows Pro 10Slow writing speed to Windows Server 2012What is needed to allow searching of file contents on remote 2012 R2 shareWindows Search doesn't return all results from parent folderWindows index search on Server 2012 R2 fails randomlyServer 2012 R2 Essentials Search not working on “Shared Folders”Access denied connecting to a share using Windows 10Windows search cannot find files in current directory
Where to draw the line between quantum mechanics theory and its interpretation(s)?
What is the closest airport to the center of the city it serves?
It is as simple as ABC
Can my 2 children, aged 10 and 12, who are US citizens, travel to the USA on expired American passports?
Is it normal for gliders not to have attitude indicators?
Does "Captain Marvel" contain spoilers for "Avengers: Infinity War"?
Why does sound not move through a wall?
Should I mention being denied entry to UK due to a confusion in my Visa and Ticket bookings?
Typeset year in old-style numbers with biblatex
Are the Night's Watch still required?
My first c++ game (snake console game)
What was Bran's plan to kill the Night King?
Agena docking and RCS Brakes in First Man
Is any special diet a treatment of autism?
Are there terms in German for different skull shapes?
How can internet speed be 10 times slower without a router than when using the same connection with a router?
Endgame puzzle: How to avoid stalemate and win?
A factorization game
Why aren't nationalizations in Russia described as socialist?
Has the United States ever had a non-Christian President?
What are the advantages of luxury car brands like Acura/Lexus over their sibling non-luxury brands Honda/Toyota?
Handling Null values (and equivalents) routinely in Python
To kill a cuckoo
Latex & Markdown files
How to index and search files within a shared folder using Windows Server 2012 R2 and Windows 10?
Server 2012 R2 Essentials Search not working on “Shared Folders”Windows 2012 Shared Drives Odd Latency IssueWindows Search in Outlook 2013 on Remote Desktop Service Windows Server 2012R2Group Policy: Mapped Drives failing to load, Windows Server 2012 Active Directory and Windows Pro 10Slow writing speed to Windows Server 2012What is needed to allow searching of file contents on remote 2012 R2 shareWindows Search doesn't return all results from parent folderWindows index search on Server 2012 R2 fails randomlyServer 2012 R2 Essentials Search not working on “Shared Folders”Access denied connecting to a share using Windows 10Windows search cannot find files in current directory
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
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?
windows-server-2012-r2 windows-10
asked Nov 25 '15 at 11:40
DanielDaniel
5,13922153
|
show 4 more comments
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?
windows-server-2012-r2 windows-10
asked Nov 25 '15 at 11:40
DanielDaniel
5,13922153
Why would you want a server based index?
– Jim B
Dec 11 '15 at 14:21
50 computers regularly scanning hundreds of thousands of files on a network share will stress the file server out and put an unnecessary load on the network. It's cheaper to have the file server index the files and just make the database available for queries.
– Daniel
Dec 11 '15 at 16:52
so hundreds of network queries are OK to the some index per desktop search (remember any typing starts search) but 50 PCs looking for new files will "stress the fileserver". Hopefully you are running top of the line fileservers and I would expect minimum Gb Ethernet to handle that kind of load from 50 clients. I think you have your idea of "expensive" completely backwards.
– Jim B
Dec 11 '15 at 17:52
Well, you think wrong.
– Daniel
Dec 12 '15 at 18:41
1
@JimB I came here looking for an answer to that exact question, so that makes us at least two. I got a 2012 fileserver that's supposed to quickly return some search results to clients that aren't necessarily in the network permanently. It doesn't make sense to have the clients index all these files and on the other hand searching these files is a rather seldom activity. I don't quite get how you can argue that tiny search query and results would amount to more than constant file scanning of 50 clients...
– Markus Hütter
Jan 6 '16 at 19:28
|
show 4 more comments
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?
windows-server-2012-r2 windows-10
asked Nov 25 '15 at 11:40
DanielDaniel
5,13922153
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?
windows-server-2012-r2 windows-10
windows-server-2012-r2 windows-10
asked Nov 25 '15 at 11:40
DanielDaniel
5,13922153
asked Nov 25 '15 at 11:40
DanielDaniel
5,13922153
edited Nov 25 '15 at 11:46
Daniel
asked Nov 25 '15 at 11:40
DanielDaniel
5,13922153
asked Nov 25 '15 at 11:40
DanielDaniel
5,13922153
asked Nov 25 '15 at 11:40
DanielDaniel
5,13922153
5,13922153
Why would you want a server based index?
– Jim B
Dec 11 '15 at 14:21
50 computers regularly scanning hundreds of thousands of files on a network share will stress the file server out and put an unnecessary load on the network. It's cheaper to have the file server index the files and just make the database available for queries.
– Daniel
Dec 11 '15 at 16:52
so hundreds of network queries are OK to the some index per desktop search (remember any typing starts search) but 50 PCs looking for new files will "stress the fileserver". Hopefully you are running top of the line fileservers and I would expect minimum Gb Ethernet to handle that kind of load from 50 clients. I think you have your idea of "expensive" completely backwards.
– Jim B
Dec 11 '15 at 17:52
Well, you think wrong.
– Daniel
Dec 12 '15 at 18:41
1
@JimB I came here looking for an answer to that exact question, so that makes us at least two. I got a 2012 fileserver that's supposed to quickly return some search results to clients that aren't necessarily in the network permanently. It doesn't make sense to have the clients index all these files and on the other hand searching these files is a rather seldom activity. I don't quite get how you can argue that tiny search query and results would amount to more than constant file scanning of 50 clients...
– Markus Hütter
Jan 6 '16 at 19:28
|
show 4 more comments
Why would you want a server based index?
– Jim B
Dec 11 '15 at 14:21
50 computers regularly scanning hundreds of thousands of files on a network share will stress the file server out and put an unnecessary load on the network. It's cheaper to have the file server index the files and just make the database available for queries.
– Daniel
Dec 11 '15 at 16:52
so hundreds of network queries are OK to the some index per desktop search (remember any typing starts search) but 50 PCs looking for new files will "stress the fileserver". Hopefully you are running top of the line fileservers and I would expect minimum Gb Ethernet to handle that kind of load from 50 clients. I think you have your idea of "expensive" completely backwards.
– Jim B
Dec 11 '15 at 17:52
Well, you think wrong.
– Daniel
Dec 12 '15 at 18:41
1
@JimB I came here looking for an answer to that exact question, so that makes us at least two. I got a 2012 fileserver that's supposed to quickly return some search results to clients that aren't necessarily in the network permanently. It doesn't make sense to have the clients index all these files and on the other hand searching these files is a rather seldom activity. I don't quite get how you can argue that tiny search query and results would amount to more than constant file scanning of 50 clients...
– Markus Hütter
Jan 6 '16 at 19:28
Why would you want a server based index?
– Jim B
Dec 11 '15 at 14:21
Why would you want a server based index?
– Jim B
Dec 11 '15 at 14:21
50 computers regularly scanning hundreds of thousands of files on a network share will stress the file server out and put an unnecessary load on the network. It's cheaper to have the file server index the files and just make the database available for queries.
– Daniel
Dec 11 '15 at 16:52
50 computers regularly scanning hundreds of thousands of files on a network share will stress the file server out and put an unnecessary load on the network. It's cheaper to have the file server index the files and just make the database available for queries.
– Daniel
Dec 11 '15 at 16:52
so hundreds of network queries are OK to the some index per desktop search (remember any typing starts search) but 50 PCs looking for new files will "stress the fileserver". Hopefully you are running top of the line fileservers and I would expect minimum Gb Ethernet to handle that kind of load from 50 clients. I think you have your idea of "expensive" completely backwards.
– Jim B
Dec 11 '15 at 17:52
so hundreds of network queries are OK to the some index per desktop search (remember any typing starts search) but 50 PCs looking for new files will "stress the fileserver". Hopefully you are running top of the line fileservers and I would expect minimum Gb Ethernet to handle that kind of load from 50 clients. I think you have your idea of "expensive" completely backwards.
– Jim B
Dec 11 '15 at 17:52
Well, you think wrong.
– Daniel
Dec 12 '15 at 18:41
Well, you think wrong.
– Daniel
Dec 12 '15 at 18:41
1
1
@JimB I came here looking for an answer to that exact question, so that makes us at least two. I got a 2012 fileserver that's supposed to quickly return some search results to clients that aren't necessarily in the network permanently. It doesn't make sense to have the clients index all these files and on the other hand searching these files is a rather seldom activity. I don't quite get how you can argue that tiny search query and results would amount to more than constant file scanning of 50 clients...
– Markus Hütter
Jan 6 '16 at 19:28
@JimB I came here looking for an answer to that exact question, so that makes us at least two. I got a 2012 fileserver that's supposed to quickly return some search results to clients that aren't necessarily in the network permanently. It doesn't make sense to have the clients index all these files and on the other hand searching these files is a rather seldom activity. I don't quite get how you can argue that tiny search query and results would amount to more than constant file scanning of 50 clients...
– Markus Hütter
Jan 6 '16 at 19:28
|
show 4 more comments
2 Answers
2
active
oldest
votes
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
answered Dec 8 '15 at 13:49
Pascal SaulierePascal Sauliere
493
Unfortunately not. From what I read, file shares can only be indexed if they are made available offline.
– Daniel
Dec 8 '15 at 14:54
add a comment |
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:
- Install "Windows Search Service" by going to Server Manager -> Manage -> Add Roles and Features -> Select "Windows Search Service" on the features page -> install
- Create a shared folder at "C:\Shared FoldersCompany Files" with the required permissions to access the folder from a client computer
- Open "Indexing Options" and click modify to add the "C:\Shared Folders" to the indexing list and click advanced and select "Index Properties and File Contents" for searching inside the documents
- To access this folder over the network from a client computer go to "\ServerCompany Files" and the client computer will utilize the servers index to complete the search. You can monitor the progress of the index in the servers "Indexing Options". Note that you should not have the options "Advanced options"-> "File Content" selected on the client computer. Also it will take some time to complete the indexing and there is a way to remove the limit on the indexer for faster indexing of files.
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
answered Apr 19 '18 at 13:16
Radar5000Radar5000
168
1
How is this different to what Pascal wrote? Which didn't answer my question, by the way. If you really got it working -- which I doubt very much -- how did you share the server-side index with the clients?
– Daniel
Apr 19 '18 at 14:34
@Daniel you may doubt all you want but it does not change the facts. I just did what I answered and there is no client side configuration needed at all due to the client server relationship that is already established. The client computers are searching >800,000 files over the network with near instant results and using the servers index. I would have expected you to have found this by now but if you really haven't and are still interested tell me which part you feel I left out and I will clarify.
– Radar5000
Apr 19 '18 at 18:59
Also would like to add that the count was >800,000 files when last checked and that is for indexing file names and the content of the files.
– Radar5000
Apr 19 '18 at 19:39
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f738882%2fhow-to-index-and-search-files-within-a-shared-folder-using-windows-server-2012-r%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
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
answered Dec 8 '15 at 13:49
Pascal SaulierePascal Sauliere
493
Unfortunately not. From what I read, file shares can only be indexed if they are made available offline.
– Daniel
Dec 8 '15 at 14:54
add a comment |
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
answered Dec 8 '15 at 13:49
Pascal SaulierePascal Sauliere
493
Unfortunately not. From what I read, file shares can only be indexed if they are made available offline.
– Daniel
Dec 8 '15 at 14:54
add a comment |
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
answered Dec 8 '15 at 13:49
Pascal SaulierePascal Sauliere
493
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
answered Dec 8 '15 at 13:49
Pascal SaulierePascal Sauliere
493
answered Dec 8 '15 at 13:49
Pascal SaulierePascal Sauliere
493
answered Dec 8 '15 at 13:49
Pascal SaulierePascal Sauliere
493
answered Dec 8 '15 at 13:49
Pascal SaulierePascal Sauliere
493
493
Unfortunately not. From what I read, file shares can only be indexed if they are made available offline.
– Daniel
Dec 8 '15 at 14:54
add a comment |
Unfortunately not. From what I read, file shares can only be indexed if they are made available offline.
– Daniel
Dec 8 '15 at 14:54
Unfortunately not. From what I read, file shares can only be indexed if they are made available offline.
– Daniel
Dec 8 '15 at 14:54
Unfortunately not. From what I read, file shares can only be indexed if they are made available offline.
– Daniel
Dec 8 '15 at 14:54
add a comment |
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:
- Install "Windows Search Service" by going to Server Manager -> Manage -> Add Roles and Features -> Select "Windows Search Service" on the features page -> install
- Create a shared folder at "C:\Shared FoldersCompany Files" with the required permissions to access the folder from a client computer
- Open "Indexing Options" and click modify to add the "C:\Shared Folders" to the indexing list and click advanced and select "Index Properties and File Contents" for searching inside the documents
- To access this folder over the network from a client computer go to "\ServerCompany Files" and the client computer will utilize the servers index to complete the search. You can monitor the progress of the index in the servers "Indexing Options". Note that you should not have the options "Advanced options"-> "File Content" selected on the client computer. Also it will take some time to complete the indexing and there is a way to remove the limit on the indexer for faster indexing of files.
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
answered Apr 19 '18 at 13:16
Radar5000Radar5000
168
1
How is this different to what Pascal wrote? Which didn't answer my question, by the way. If you really got it working -- which I doubt very much -- how did you share the server-side index with the clients?
– Daniel
Apr 19 '18 at 14:34
@Daniel you may doubt all you want but it does not change the facts. I just did what I answered and there is no client side configuration needed at all due to the client server relationship that is already established. The client computers are searching >800,000 files over the network with near instant results and using the servers index. I would have expected you to have found this by now but if you really haven't and are still interested tell me which part you feel I left out and I will clarify.
– Radar5000
Apr 19 '18 at 18:59
Also would like to add that the count was >800,000 files when last checked and that is for indexing file names and the content of the files.
– Radar5000
Apr 19 '18 at 19:39
add a comment |
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:
- Install "Windows Search Service" by going to Server Manager -> Manage -> Add Roles and Features -> Select "Windows Search Service" on the features page -> install
- Create a shared folder at "C:\Shared FoldersCompany Files" with the required permissions to access the folder from a client computer
- Open "Indexing Options" and click modify to add the "C:\Shared Folders" to the indexing list and click advanced and select "Index Properties and File Contents" for searching inside the documents
- To access this folder over the network from a client computer go to "\ServerCompany Files" and the client computer will utilize the servers index to complete the search. You can monitor the progress of the index in the servers "Indexing Options". Note that you should not have the options "Advanced options"-> "File Content" selected on the client computer. Also it will take some time to complete the indexing and there is a way to remove the limit on the indexer for faster indexing of files.
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
answered Apr 19 '18 at 13:16
Radar5000Radar5000
168
1
How is this different to what Pascal wrote? Which didn't answer my question, by the way. If you really got it working -- which I doubt very much -- how did you share the server-side index with the clients?
– Daniel
Apr 19 '18 at 14:34
@Daniel you may doubt all you want but it does not change the facts. I just did what I answered and there is no client side configuration needed at all due to the client server relationship that is already established. The client computers are searching >800,000 files over the network with near instant results and using the servers index. I would have expected you to have found this by now but if you really haven't and are still interested tell me which part you feel I left out and I will clarify.
– Radar5000
Apr 19 '18 at 18:59
Also would like to add that the count was >800,000 files when last checked and that is for indexing file names and the content of the files.
– Radar5000
Apr 19 '18 at 19:39
add a comment |
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:
- Install "Windows Search Service" by going to Server Manager -> Manage -> Add Roles and Features -> Select "Windows Search Service" on the features page -> install
- Create a shared folder at "C:\Shared FoldersCompany Files" with the required permissions to access the folder from a client computer
- Open "Indexing Options" and click modify to add the "C:\Shared Folders" to the indexing list and click advanced and select "Index Properties and File Contents" for searching inside the documents
- To access this folder over the network from a client computer go to "\ServerCompany Files" and the client computer will utilize the servers index to complete the search. You can monitor the progress of the index in the servers "Indexing Options". Note that you should not have the options "Advanced options"-> "File Content" selected on the client computer. Also it will take some time to complete the indexing and there is a way to remove the limit on the indexer for faster indexing of files.
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
answered Apr 19 '18 at 13:16
Radar5000Radar5000
168
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:
- Install "Windows Search Service" by going to Server Manager -> Manage -> Add Roles and Features -> Select "Windows Search Service" on the features page -> install
- Create a shared folder at "C:\Shared FoldersCompany Files" with the required permissions to access the folder from a client computer
- Open "Indexing Options" and click modify to add the "C:\Shared Folders" to the indexing list and click advanced and select "Index Properties and File Contents" for searching inside the documents
- To access this folder over the network from a client computer go to "\ServerCompany Files" and the client computer will utilize the servers index to complete the search. You can monitor the progress of the index in the servers "Indexing Options". Note that you should not have the options "Advanced options"-> "File Content" selected on the client computer. Also it will take some time to complete the indexing and there is a way to remove the limit on the indexer for faster indexing of files.
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
answered Apr 19 '18 at 13:16
Radar5000Radar5000
168
edited Apr 24 '18 at 17:12
answered Apr 19 '18 at 13:16
Radar5000Radar5000
168
answered Apr 19 '18 at 13:16
Radar5000Radar5000
168
answered Apr 19 '18 at 13:16
Radar5000Radar5000
168
168
1
How is this different to what Pascal wrote? Which didn't answer my question, by the way. If you really got it working -- which I doubt very much -- how did you share the server-side index with the clients?
– Daniel
Apr 19 '18 at 14:34
@Daniel you may doubt all you want but it does not change the facts. I just did what I answered and there is no client side configuration needed at all due to the client server relationship that is already established. The client computers are searching >800,000 files over the network with near instant results and using the servers index. I would have expected you to have found this by now but if you really haven't and are still interested tell me which part you feel I left out and I will clarify.
– Radar5000
Apr 19 '18 at 18:59
Also would like to add that the count was >800,000 files when last checked and that is for indexing file names and the content of the files.
– Radar5000
Apr 19 '18 at 19:39
add a comment |
1
How is this different to what Pascal wrote? Which didn't answer my question, by the way. If you really got it working -- which I doubt very much -- how did you share the server-side index with the clients?
– Daniel
Apr 19 '18 at 14:34
@Daniel you may doubt all you want but it does not change the facts. I just did what I answered and there is no client side configuration needed at all due to the client server relationship that is already established. The client computers are searching >800,000 files over the network with near instant results and using the servers index. I would have expected you to have found this by now but if you really haven't and are still interested tell me which part you feel I left out and I will clarify.
– Radar5000
Apr 19 '18 at 18:59
Also would like to add that the count was >800,000 files when last checked and that is for indexing file names and the content of the files.
– Radar5000
Apr 19 '18 at 19:39
1
1
How is this different to what Pascal wrote? Which didn't answer my question, by the way. If you really got it working -- which I doubt very much -- how did you share the server-side index with the clients?
– Daniel
Apr 19 '18 at 14:34
How is this different to what Pascal wrote? Which didn't answer my question, by the way. If you really got it working -- which I doubt very much -- how did you share the server-side index with the clients?
– Daniel
Apr 19 '18 at 14:34
@Daniel you may doubt all you want but it does not change the facts. I just did what I answered and there is no client side configuration needed at all due to the client server relationship that is already established. The client computers are searching >800,000 files over the network with near instant results and using the servers index. I would have expected you to have found this by now but if you really haven't and are still interested tell me which part you feel I left out and I will clarify.
– Radar5000
Apr 19 '18 at 18:59
@Daniel you may doubt all you want but it does not change the facts. I just did what I answered and there is no client side configuration needed at all due to the client server relationship that is already established. The client computers are searching >800,000 files over the network with near instant results and using the servers index. I would have expected you to have found this by now but if you really haven't and are still interested tell me which part you feel I left out and I will clarify.
– Radar5000
Apr 19 '18 at 18:59
Also would like to add that the count was >800,000 files when last checked and that is for indexing file names and the content of the files.
– Radar5000
Apr 19 '18 at 19:39
Also would like to add that the count was >800,000 files when last checked and that is for indexing file names and the content of the files.
– Radar5000
Apr 19 '18 at 19:39
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f738882%2fhow-to-index-and-search-files-within-a-shared-folder-using-windows-server-2012-r%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Why would you want a server based index?
– Jim B
Dec 11 '15 at 14:21
50 computers regularly scanning hundreds of thousands of files on a network share will stress the file server out and put an unnecessary load on the network. It's cheaper to have the file server index the files and just make the database available for queries.
– Daniel
Dec 11 '15 at 16:52
so hundreds of network queries are OK to the some index per desktop search (remember any typing starts search) but 50 PCs looking for new files will "stress the fileserver". Hopefully you are running top of the line fileservers and I would expect minimum Gb Ethernet to handle that kind of load from 50 clients. I think you have your idea of "expensive" completely backwards.
– Jim B
Dec 11 '15 at 17:52
Well, you think wrong.
– Daniel
Dec 12 '15 at 18:41
1
@JimB I came here looking for an answer to that exact question, so that makes us at least two. I got a 2012 fileserver that's supposed to quickly return some search results to clients that aren't necessarily in the network permanently. It doesn't make sense to have the clients index all these files and on the other hand searching these files is a rather seldom activity. I don't quite get how you can argue that tiny search query and results would amount to more than constant file scanning of 50 clients...
– Markus Hütter
Jan 6 '16 at 19:28