Windows 7 search not showing results from mapped Server 2008 R2 share

Given that you're trying to search a server and not your local system, it's probably not related to indexing as you shouldn't have all your clients indexing a file server.

What happens on the system that doesn't work if you login as a completely different user and try to search the sever? If you get results, try the steps laid out on this site

There's a registry key:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced

In this key there are two values (both hex dword)

Start_SearchFiles Start_SearchPrograms

Uninstalling Windows Search sets the value of both of these to zero, when they default to something else. However, reinstalling Windows Search does not restore them to their default setting like it probably should. By manually setting both of them to 1, it re-enabled the windows search function from the start menu. Somebody might want to notify one of the Microsoft software engineers that they should correct this issue so that reinstalling Windows Search properly configures this registry key back to its default setting, that way if anybody else does what I just did they'll avoid the same headache I went through. (I don't know how to contact them myself.)

Another thing to try would be to try the steps outlined on this site


Go to Home Group on the Windows 7 machine in control panel (I know, but bear with me...). Click on "change advanced sharing options" and in the public section, turn ON network discovery (or toggle it off, apply, on, apply, if already on). Re-index and reboot.

This is just a suggestion. Also, do you notice if the shared network drive appears with an X on it, even for a brief time period, when the machine is turned on? Win 7 has a habit of giving up indexing a network share if it is not available immediately on bootup, even if it subsequently becomes available, like in 30 seconds.

I suspect that this is something to do with the Home Group interaction, even if you have it turned off. I have spent literally days getting machines to be visible when, for no apparent reason, they are immediately available to other machines on the same OS. All these cases involve some type of Windows 7 "homegroup" issue.


Try going in from the client PC and right click on the mapped drive. Make sure that "allow files on this drive to have contents indexed..." is checked.

The other option that I would check would be: double click the mapped drive, select all folders and then right click on them, click advanced, then make sure that "folder is ready for archiving" is checked and "allow files in this folder to have contents indexed" is checked.

I think that these settings are usually set on a per pc basis, not taken from the server's settings.


I got this working at a site I look after, where they have a need to search in specific folders on the network for scanned documents, and to search text within PDF files. Works beautifully. From a collection of about 70,000 files, they can search almost instantly over the network for filenames and PDF documents containing specific text. Sorry, this doesn't address your exact problems, but hopefully you, or someone, benefits from my efforts. I emailed someone my results so as to tell them about it and to document it. Now shared here :)

Cheers.

||||>>

Two hours of ****** around and a further two hours of searching and I finally find this:

http://sourcedaddy.com/windows-7/understanding-remote-search.html

This is exactly what I'm looking for!! Why couldn't I find a single MS website telling me this **?!?

... users of Windows 7 can also search content stored in shared folders on the network. To do this, the following prerequisites are required: The remote computer must be running Windows 7, Windows Vista, Windows Server 2008, Windows Server 2008 R2, or Windows XP or have Windows Server 2003 with WDS 4.0 installed. The Windows Search (WSearch) service must be running on the remote computer (on Windows Server 2008, you can enable the search service by installing the File Services role and then enabling the Windows Search role service within that role). The shared directory on the remote computer must be included in the indexed scope on the remote computer. Note To provide an optimal experience for remote search, Microsoft recommends that computers running older installed versions of Windows with WDS 2.6.6 or WDS 3.01 be upgraded to WDS 4.0. For more information concerning support for WDS, see the section titled "Understanding the Windows Search Versions" earlier in this tutorial.

Remote search performed from the local computer uses the Windows Search service on the remote computer to perform the query against the index on the remote computer.