Can't add folder on network share to library

I know this is not exactly what this thread is about, but as far as indexing mapped drives goes, I gave-up on Windows' indexing, and found a program that will let me do that: It's called "Everything" (just Google that word), and is running happily on my Windows Server 2008 R2 box, and I can query it from my Windows 7 Ultimate box.

It's not perfect, but I like it better than Windows Search in some ways, for several reasons:

1. The results are returned instantaneously.
2. The index is updated in real time (I'm not exaggerating, it's instantaneous).
3. Its database is tiny (less than 3 MiB for over 1 million files on my machine, compared to several GiB for the Windows one).

There are a few things that are not so good, like it doesn't index file contents, picture tags, etc., it has to run as an admin, and a few other things; but I like it and it's worked for me so far.

Wanted to map music folder on another Homegroup Computer and I got the error.

The below assumes you have a local networka dn the 2 PC are in a Homegroup

(Suggestion RDP to Source PC from Remote PC then follow below. saves the moving around.)

Steps to FIX

On the PC with the source drive
1. Go to C:\Users\[yoursuername]\My Music
2. Right Click > Properties > Location
3. Move the folder to some where other then the C:\Users folder ie: external HD
4. After the move is complete
5. Right Click New Location > Share > Homegroup (Read/Write)

On the remote PC
1. Network > Source PC
2. Right Click Folder > Map Network Drive
3. Go to Music Library
4. Locations > Add > Newly Mapped Drive

KyserSosai

Just Get It Done

Microsoft have obviously STILL not fixed this inherent problem I highlighted in the Release Candidate. May be we have to wait for a Service Pack (or three).

jessicah said:

Hi,

How can I add a folder on a network share to my library? I get an error saying that the network share needs to be indexed. But I can't find a way to turn this on.

I'm on a domain, and I have my home drive (H:), and I want the folder inside called Documents added to my library (and then set as default save location).

Thanks,

Jessica

I think it's important to point out that Homegroups or Library's are not made to work in a VPN or a Domain. It's made for Home networks only. I never have any problems adding network shares to my Homegroup folders. :)

I was researching the inability to add 2003 domain network folders to a Windows 7 machine (which is the title of this thread). I am receiving the same "unable 'cause not indexed' option. I checked the 2003 server control panel "Indexing Options" and, sure enough, the folder which I want to add was not in the list.

I added it and it is indexing now (using Windows Search 4 as that was an earlier suggestion). The index will take awhile and will post back after confirming this "fix".

Confirmed. Even though a folder properties may state "May be indexed", it will not be unless it (or a folder higher in the hiearchy) is listed within the server's control panel Indexing options.

Once there, a Windows Pro 7 workstation can browse the server folders, select the folder to add, Right click on the folder name and then Add To Library.

Lots of discussions but all this has already been known for a long time now.

To summarize this:

1) Microsoft may or may not know about the problem and may or may not fix the problem at some stage. I am not aware of any official statement from Microsoft about this or any formal bug report by an authorized Microsoft customer. Having reported the issue in some RC version is not very relevant here, sorry.

2) The workarounds debated in this forum are only relevant (if at all) for environments where you have multiple machines/servers running all the time and where you want to have files and folders of the other machines available through search as well.

Users with NAS and other storage devices running proprietary operating systems (e.g. Linux on QNAP) are not affected by that part of the discussion.

3) The fact, that you need to add your custom folders to the list of folders to be indexed (control panel) is just obvious in my opinion. I am sure that most watchers of this thread have done this.

So now for the next months of standby...maybe some time in the future, there will be some real news about this issue except for the same debates again and again.

gosh, sorry!

I found this solution on the ms site:

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

So, in other words the very simple, very effective, very easy to use search function which was inherent in Windows XP has been ruined by an incompetent Operating System manufacturer.