Zzzz ... had to rush back, since I figured out the last question too. :) Media Center can add "unindexed" networked locations simply because Windows Media Center is one of the default indexing locations in Corntrol Panel ... so when you add them to Media Center, they are not "unindexed" at all.
Can we now take a coffee break?
In fact, some good new postings have shown up here. Yes, the original question was how to add a network folder to a library but the indexing topic has been raised later and has been a part of this thread all the time. I cannot see anything wrong about this.
I can confirm, that one can add network drives to a library within Windows Media Player/Media Center without using additional software (like the Zorn Software Library Tool).
That means, you can use Windows Media Player/Media Center or 3rd party software such as the free Library Tool to overcome this windows limitation.
Anyway, that still doesn't mean it would index these network drives. Yes, this was not the original question but quite some people are interested in that part...
Media Center do index (as default -> Control Panel / Indexing) anything within its "libraries". But you don't need to use the "Media Center" solution for folders you have no intention to use within Media Center. As I pointed out, simple go to Control Panel / Indexing and add any folder on your hard disk that you want to share, and where the "client" want to add this share to their Windows Explorer Libraries.
People with shares on servers that does not support "Win7/Win2k8R2" indexing, cannot add shared folders to Windows Explorer Libraries, unless they use the offline-technique. So this might be a problem for NAS etc.
No, this is not correct and has been discussed dozens of times now. How many times do I have to repeat that tools such as the Zorn Library Tool exists and DOES allow you to add any folder to a Windows Library?
Zorn Software - Simplicity is the Essence of Good Design
And, once again, on Windows 7 64 Bit, these folders in the library (however you added them) will not be indexed. All this has been clarified before, and more than once.
What's the point of reiterating all the facts that have already been clarified? This discussion is really running in circles now and I am getting tired of it.
The point of my post are to clarify the many wrong statemants by many posters in this thread. Instead point out facts. It was time to do this, since noone had done it previously.
Indexing and Libraries works exactly like intended by Microsoft. There is no mystery behind this.
All that I have written is 100% correct, and you don't need any 3-party tools (like any Zorn software), nor any registry hack or anything, to add networked shares to (Windows 7) Explorer Libraries. All you need to do, is make sure the shares are indexed in the server end - by using Indexing in Control Panel. If you run Windows Server 2008 R2 (as the server of shares), note the indexing is not installed by default, so you need to install it in Server Manager.
I have a feeling you don't understand this. If you try to add shares into a library, of course they won't be indexed just because of that. You cannot in the client index an unindexed share of the server, but you CAN in the server end, i.e. you must do the indexing in the SERVER end. If you still have trouble getting it to work, make sure you have the correct file security (for the user) set in the server end. People miss often on this point.
But be my guest and install Zorn & Co, if you want to be complicated. I, on the other hand, has learned during my soon 40 years in the business as everything from programmer to systems admin, that the less "extra" toosl you use, the better and more stable your systems run. If there is a built-in solution you should use it. Always.
Well, technically you are correct - however you should see that "SevenForums" refers to the CLIENT operating sytem Windows 7. How many users that are participating in this thread do use a Client/Server infrastructure with a Server running 24/7 to index folders on Clients?
I do not. And I am sure many others want to add network drives to their CLIENT libraries (where the Zorn tool, MediaCenter and what not comes in) AND also run Windows Search over them (which is not possible for Windows 7 64 Bit).
I think the points have been made now. I am just seeing the issue from a slightly different point.
"Server" in my posts refer to any machine sharing resources. Might be a Windows 7 box, or Windows Server 2008 R2. So what I wrote also apply to a plain Windows 7 network.
You were talking about Windows 2008 before (see previous posts) and Windows 7 is not a Server, but a Client operating system.
Sorry to repeat, but the typical Windows 7 home user does not run servers or a myriad of Windows 7 client computers to share stuff with each other.
Can we please get back to the topic? We have outlined how to add network shares to a library using 3rd party tools and pointed out that their content is NOT being indexed in a pure client environment.
Is there any new information or are we just reiterating the same known facts again and again?
Sigh, the issue has nothing to do with client or server operating systems. Libraries work on both. But the issue was about SHARES. This WAS the topic. And their content IS being indexed in a pure client (Windows 7) environment. Stop taking trash ... have you even tried checking indexing and its settings on a Windows 7 box? Open up your control panel already ... I am adding shares to Libraries between Windows 7 boxes this very moment. Without any 3rd party software.
This topic is solved and closed.
Seriously, I don't know what you are talking about.
As a matter of fact, UNC shares can NOT be added to a library using integrated OS functions (workarounds have been discussed in this thread, again and again!) and no, they are NOT being indexed on Windows 7 Client computers.
Just to repeat this again (and again): the old UNCFAT plugin for Windows Search 4.0 does not work on Windows 7 64 Bit. However, this would be required.
And no, this topic is not resolved and not closed. Your question whether I had checked my indexing settings isn't more than a joke for me.
The situation remains: Windows 7 64 Bit Client computers cannot index UNC shares or tweaked Windows Libraries that contain UNC shares without a Server OS or 3rd party software.
If you think, you have better information, then share it as lots of people will appreciate it. Apart from that, please stop restarting this discussion from scratch, I am getting tired of it after around 2 years now.
Quote