Windows 10: Windows 10 v1909 does not search a network drive mapped to Windows Server 2016 UNC path

• All Windows 10 computers on this network can index local files. They have the most recent 1909 build.
• Only local disks and libraries appear in the 'selected locations' list and there's no option in Indexing Options to add a new target to the list.
• The Windows 2016 file server hosting the share has the Windows Search service installed. Indexing is complete with more than 658,000 items including the target share the end user wants to search.
• A search for a string in the pdf file on the server yields the desired results
• A search for a string in the pdf file name on the Win 10 v1909 workstation yields no results

How are people searching shared drives in business environments since the changes from earlier versions of Windows? How can I give my end-users complete search functionality?

:)

 

Windows search returns UNC path to a searched file instaed of mapped drive while search service is enabled on the server.

Hello, here's a description of an issue I've stumbled upon after migrating my file server from 2003 to 2012R2.

I've added the search service feature on the 2012 server for it to index the files and their inside text, so that users could search for key words on the mapped shared folders as drives.

But the thing backfired at me when some users reported that the path to the searched files are now returning a very long string of the path to file ("\\server\sharename-that_could_be several_folders_long\folder\subfolder\file.ext") instead of short path
("X:\folder\subfolder\file.ext")

So when I stop the search service on the server, users are able to search on the mapped drives only for the file name and the path is short with a drive letter.

When the service is running on the server users can search inside the files but the path to file returns long as UNC.

Is there a way to make the search service run on the server and that the clients will be able to search for files and their content but receiving a short path ?

The reason is that there's a program that uses pointers to files and it's limited to 100 characters, with the long path the users are unable to point to the files they wish inside the program.

 

Drive Letter Mapping reverts to UNC path

When I use a mapped drive letter in an icon in Windows 10, if I check the Run as Administrator on the icon properties, the icon then reverts to UNC path instead of using the drive letter mapping. Of course, if I don't run as Administrator, I don't have
the permissions I need to run my program accessed by the icon.

 

Windows 10 Cannot Search Using Network Drive Letter, But UNC Path Work

On one PC running Windows 10 Version1903, searches on the C: drive are successful, but searches on mapped network drives fail. When you type a search string, such as *.txt, nothing happens. However, if you replace the drive letter in the full path with the corresponding \\<server>\<share>, the search succeeds. At first all network drives were showing a red "X", so I tried various solutions to resolve that issue. The red "X" no longer appears, but the problem persists. Thank you in advance for your thoughts on how to resolve this issue.