How do I get Windows 7 to search contents on a Windows 2003 Server?

Question

Our network consists of several Windows 7 64-bit clients and a Windows 2003 R2 64-bit file server. I would users to be able to search the contents of the file server in an efficient manner. I have installed Windows Search 4.0 on the file server and told
it to index the folders I am sharing. But when I go back to the Windows 7 client and do a search, I notice two things:
#1 - If i try to search the mapped network drive, Windows 7 does nothing. The search never starts.
#2 - If I search using the UNC path, Windows 7 searches but does so very slowly.
I thought the point of installing Windows Search on the server was for the server to build the index, and for the Windows 7 clients to use that index. That doesn't appear to be working.

Answer 1

Leo Wang, 
This is specificaly an issue with Windows 7 64-bit all versions.
We need a way to index network locations and at this time, there are a few things that have been proposed/attempted, but none that  work:
1. KB2268596. 
The "Search programs and files" box on the Start menu does not search files on network locations that are not indexed in Windows 7 or in Windows Server 2008 R2
This does not apply to 64-bit an gives a message saying that it is not applicable to this type of computer, or something of the sort.
2.KB918996.
Windows Desktop Search: Add-in for Files on Microsoft Networks
This Protocol Handler indexes your shared network directories and FAT drive(s) allowing you to easily find your specific content. 
By downloading this Add-in, you will have the ability to search your shared network directories and FAT drive(s) via selection in your Windows Desktop Search Advanced Options.
Does not work on Win7 64-bit, which is the primary OS in corporate environments.
3. Symbolic Links
1. Create a folder on your hard drive for shares. i.e. c:\share
2. Create another folder in the above share. i.e. c:\share\music
2. Link the Library to this folder. 
3. Delete the folder.
4. Use the mklink in an elevated command prompt to make a symbolic link. Name the link the same as the folder you created above. 
i.e - mklink /d c:\share\music \\server\music
5. Done. Now you have non-indexed UNC path as a library.
The last line sums it up... it is a non-indexed UNC path.
We need a solution!!! There has to be a solution... If there is the abiity to solve it for 32-bit machines, there has to be a way to create it for 64-bit machines. 
Christopher Parsons