Add a non-indexed UNC as a library===========================1. Create a folder on your hard drive for shares. i.e. c:\share2. Create another folder in the above share. i.e. c:\share\music2. 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\music5. Done. Now you have non-indexed UNC path as a library.
If the network folder you're trying to include is stored on a computer that's running an older version of Windows, you might be able to make it compatible with Windows 7 libraries by installing Windows Search 4.0 on the computer, and then indexing it.
index of windows 7
Download File: https://vittuv.com/2vE9oK
Contrary to all of the posts that I've found on forums regarding adding network folders as libraries and then having them fail to index, it is possible to do this within Windows 7. I managed to fix mine today by using a combination of symbolic links and Windows Media Centre. Obviously this works best if you are trying to include a folder containing Music, Pictures, Videos or Movies etc. although you can also do this for your Documents folder if you like. To include a network folder in a library and have it indexed by Windows 7, follows these instructions:
Btw, I accidentally indexed the same folder twice while doing this so make sure you don't do the same thing! If you do you'll need to go back into Windows Media Centre and select the Remove folders from library radio button.
The original question was how to index a network share but I assume that for most people this is required to add this share into libraries. As I discovered yesterday there seems to be a third way by editing the xml files that contain the information about the libraries.
I've also struggled with this on a small network with Windows 7 clients and a new Server 2008 R2 server. I wanted to include various documents, pictures, etc...into each workstation's library. The main frustration I had was understanding what an "indexed network location" really means...after fighting with indexing services and playing with indexing options on the workstations, I found something that worked. It would be great if Microsoft could actually document this somewhere!
1) On Windows 2008 R2 server, do NOT install the indexing service! It's a Server 2003 version that is not recognized by Windows 7 clients. Instead, install the "Windows Search Service" - you can only pick one or the other so make sure you select Windows Search Service - it's one of the roles under File Services.
2) The install wizard should ask you which folders/drives you want to index - choose any data drive (recommend NOT selecting the system/boot drives) that contains files you want to include in your Windows 7 library on the workstations. If you missed this during the install, you can go back to CONTROL PANEL and type "indexing" into the search box to find the indexing options and customize it there (exactly the same way you do with Windows 7).
3) As soon as the drives have been added, you can now include any locations on those drives in your Windows 7 workstation libraries (even before the server finishes indexing). You will no longer get any warnings that "some locations are not indexed"...everything works as it should!
Add a non-indexed UNC as a library===========================1. Create a folder on your hard drive for shares. i.e. c:\share2. Create another folder in the above share. i.e. c:\share\music2. 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\music5. Done. Now you have non-indexed UNC path as a library.
I want my network locations indexed, and could care less if they are in a Library. Who gives a ____ if they are in a Library if they are not indexed? That is like asking the librarian for a book and they take you to a room with jumbled piles of books and say...well, it is somewhere in here...good luck!
Nevertheless, I did install the hotfix and created the DWORD value, but these do not appear to change anything. NAS drives are still not available for indexing, although, quite uselessly, they are in the Library (added with the "Windows 7 Library Tool".
d. Now, the mystery: (my win7 computer was "indexing" in the background all this time) WHEN I DID A SEARCH FOR "bingo" ...the "bingo.txt" file was at the top of the list... I "right clicked" on it to check the properties (thinking the index has just located the shortcut on my desktop maybe)...BUT THE PROPERTIES ...showed the "networked location" on my desktop downstairs.
e. IN CONCLUSION: I now have the capability to INDEX folders/files ON OTHER NETWORKED COMPUTERS from my "win7 x64 laptop" WITHOUT HAVING TO MAP THE NETWORK DRIVE!!! (maybe because the index catches the "bingo folder" being CURRENTLY ACCESSED INDIVIDUALLY when I pull up the "Bingo.txt" by clicking it's shortcut on my laptop....
you guys can play around with this... DON'T KNOW WHY the "index" didn't show "bingo.txt" (residing on my desktop downstairs) until I placed a "shortcut" to the "Recent Places" folder on my laptop desktop screen... might have something to do with the "complex index parameters" of Win 7, etc... but I don't have the time to try an trace it down, or test it, etc.
... The win 7 indexing system MAY INDEX ANY SHARED FOLDER from another networked computer WHEN IT'S BEING ACCESSED LIVE on the win 7 computer... is probably what's happening... so I didn't have to "map the network drive" but I did have to "BE ACCESSING A FOLDER from another computer" for it to INDEX THAT FOLDER... now I don't, for example, know whether the INDEX system of my win7 laptop (running in the background) might not index a folder IF IT WAS DOING SOMETHING ELSE IN A BRIEF TIME that I was accessing the folder from the other computer.
I had no problems doing what you suggested above on my Win7-64bit Ultimate workstation. Now I have two shares from my NAS showing up under libraries. That is to say, I now have tow UNC paths showing up as libraries.However, neither of these libraries / shares are indexing.
Or were you implying that, although the UNC path shares would now be in a library, they would remain unindexed by saying above, "5. Done. Now you havenon-indexed UNC path as a library." 2ff7e9595c
Commentaires