Can't add folder on network share to library

I did NOT say Windows XP was unable to index UNC drives, what I said was Search 4.0 does not work properly. I always get my users to remove Search 4.0 on XP and their search problems mainly disappear!!!

Libraries - HELLOOOOO - the topic thread IS "Can't add folder on network share to library", so YOU may not care about them, but they are there in Windows 7 and they dont work properly (at least in the RC version of Win7).

Microsoft - FIX Win 7 Libraries so they DO work and DITCH Search 4.0. You never have been any good at search. Remember the "known file types" registry bug of a few years ago!

Windows Search 4.0 works properly (with the limitation of the mentioned UNC issues) and the libraries work properly. These are facts.

I don't even want to know why you are still using a RC version of Windows 7 when the final versions are out for ages. You're probably even violating licensing conditions.

If you didn't notice, this thread is mainly about the indexing of UNC drives and not the libraries. The addition of UNC drives to a library was the workaround being discussed in this thread.

Fulanke,

I don't think you can see the wood for the trees - step outside and look at it from a user's view:

1) You said: "Windows Search 4.0 works properly (with the limitation of the mentioned UNC issues)" - ie: IT HAS AT LEAST ONE FAULT!!! - and that is ignoring it's poor usability which is the problem for most of my users.

2) The thread is entitled "Can't add folder on network share to library" - so the thread IS ABOUT libraries. If libraries worked properly, this thread would not have been started.

I don't use RC anymore - I gave up trying to use Windows 7 on a day-to-day basis because of all the bugs in RC. I am waiting for SP1 at least. When things as basic as mapping network drives are troublesome, it shows there is still some way to go before Microsoft get it right, which they won't do unless they LISTEN to their users.

Well...I already mentioned before: Windows Search 4.0 isn't Windows Search 4.0 - it primarily depends on the OPERATING SYSTEM it is running on. WDS 4.0 under XP is not WDS 4.0 under VISTA or 7 and is behaving in a totally different way! The OS is the issue and not so much WDS!

WDS under Windows XP had no issues with the indexing of UNC drives, as stated before, I have been using that for years, so it has NO FAULT in general but so does it under Windows 7 while Windows Vista does the job in combination with the UNCFAT extension.

The WDS code and the combination of Windows 7 is causing the problem. Only the developers of WDS / Windows 7 could comment where the UNC fault exists.

As for libraries, they do work for me and I've only been seeing them as a potential workaround for the WDS issue. There is no open problem with regards to the libraries for me otherwise.

Windows 7 in general, is just perfect. I don't know what mapped network drives problems you are talking about, I don't know them. I have around 10 mapped network drives to my NAS and haven't seen a single problem with that so far. It is reliable, fast and just works.

However, what's the point debating issues in a RC version then, this is a joke in my opinion. Test the final version, apply the updates and then you can make solid comments after your testing period.

Mmmm - Interesting - would the REAL Windows Search 4.0 please stand up and make yourself known.
So, Windows 7 OS IS the problem (at least the RC version was, the real release version seems a lot better (though I see it still has the domain joining bugs of Vista, but they are fairly easily resolved).

Time the WDS issue got fixed, it has been known about long enough.

Brainwashing is a wonderful thing - Windows 7 is not "just perfect" - see all the problems on the forum - it's good, I'll give you that, but NOT "just perfect" - Let's see how long before SP1 comes out and we read the release notes for that to see just how "perfect" the initial release was.

== This is how to search network files and index network files without having to store a copy on your own dam computer. ==

So after a long hard search i have found the answer to my own problem. (putting up with this for 3 months)

This patch allows you to add network files to the index without having to make them "always available offline".

It will add a tab in the Indexing Options menu called "Add UNC Location" this is where you add the path of the network folder.



UNCFATPHInstaller.msi

Download details: Windows Desktop Search: Add-in for Files on Microsoft Networks



To Add to Library

Zorn Software Blog Archive Win7 Library Tool - Simplicity is the Essence of Good Design



always available offline is not a real solution for network storage, you can't make 2TB available offline if you have a 200GB hard drive

Craigman,

I can't believe this - all this has been discussed before, the patch you are referring to is the outdated patch (dated 2008) for VISTA and not for Windows 7!

As discussed dozens of times, this patch does not help for Windows 7! It is installed on my private Windows 7 box as well as on my work machine, also all colleagues have installed it!

There is no new option "add UNC location", how often you may try it.

In fact, I was a bit excited this morning when I saw the email notification about your post but I was in for a rude awakening when I realized that you were referring to the crappy unsupported 2008s Vista patch again.

fulanke said:

Craigman,

In fact, I was a bit excited this morning when I saw the email notification about your post but I was in for a rude awakening when I realized that you were referring to the crappy unsupported 2008s Vista patch again.

You were not the only one

Forgive me if I'm not up to date on the issue being discussed, as I only skipped to the end to see if a solution had been found, but after a couple hours of googling around I just happened across a fix for my issue.

Trying to get my 7 client to add a network share to a library where the host is another Windows 7 box, all I had to do was set the drive to be indexed on the server end. Once the 7 "server" was set to index the drive, my 7 "client" could add its mapped network drive to a library. No desktop search clients or patches necessary.

I think these are not really news. You can have shares that are located on a different "server" (Windows 7 technically isn't a Server OS while it is just acting as one in this case) indexed, but this has been discussed before.

I think the majority of all home users do not run several PCs and shares on it but one PC and some sort of a NAS/SAN that is not using a Windows OS and where this approach doesn't help in any way.

Even if that worked, I certainly won't run 2 PCs at the same time just because I can get the folders indexed then. Then I could just copy all the 500 GB from my NAS to my local disk and index it from there, which would render the NAS useless.

Sorry, but this is just another episode in this never-ending thread. Will Microsoft ever notice this issue, comment on it or even fix it? Who is making the call?