Recommended Posts

I've been struggling with this for real long, and as i skimmed through some posts, others seem to be as well. When i try to add a folder which is on my NAS drive in any of the 4 default libraries, i get the following error message:

'This folder cannot be included because it is on a share that is not indexed'

Anyone figure out how to get by this, as i remember Microsoft has said, you can add network locations in Libraries.

online helps says ou can but searches wil be slow asince it can't be indexed so it might be a bug.. or not added as a fucntion yet.

otherwise you coudl try mounting the network folder and try to add that...

Mounting the network folder, you mean mapping it as a drive?

i've already done that

My situation is a bit different to yours but I've had no problems adding shares on my WHS to my libraries. The difference is that the server is running Windows and the shares are all indexed.

I've really been looking forward to Libraries because I typically keep all my documents, music, videos, etc. on the WHS and Vista didn't handle replacing the default documents locations with network shares that elegantly. The new setup works perfectly for me.

My situation is a bit different to yours but I've had no problems adding shares on my WHS to my libraries. The difference is that the server is running Windows and the shares are all indexed.

I've really been looking forward to Libraries because I typically keep all my documents, music, videos, etc. on the WHS and Vista didn't handle replacing the default documents locations with network shares that elegantly. The new setup works perfectly for me.

They're indexed on the server. They're not indexed for your win7 computer, it doesn't have access to the serves index database,

They're indexed on the server. They're not indexed for your win7 computer, it doesn't have access to the serves index database,

That's not true actually. With Desktop Search 4.0 Windows can use indexes across the network. As a result Windows7 can use the index on the server to improve local search results.

I have a wireless NAS plugged into my router. I can map the drive fine, but it won't show up in the list of locations you can choose to index. Since you can't index it, Explorer won't let me add it to any Library. According to BrandonLive, there are no plans in place to implement indexing of network locations, which is pretty depressing. The workaround offered is to add these locations to your Library from within Windows Media Player.. just do the regular "Manage Libraries" and it won't complain when you pick the network drive.

The problems here are that the locations are still not indexed, so browsing in Explorer doesn't work as well as it should, and also this method only makes sense if you're dealing with Pictures, Music and Video. I can't add my Documents on the external drive to the Library.

BrandonLive also said that if the networked location is on a Vista PC you can index it and Windows 7 will pick it up (why it works on jakem1's WHS), but this useless for a simple networked hard drive.

The relevant quotes, for those interested:

The help text hasn't yet been finished. At this point, libraries only support indexed locations. There are ways around this (if you add it via WMP it will get added to your library, but it will severely degrade the Explorer libaries experience).

If the network share is on a Windows PC, you can install Windows Search 4 on it and index the share on the server side. Then your Win7 machine will be able to remotely query that index to provide the full rich libraries experience.

Another option that works for any network share is to use the Offline Files feature, which creates a local cache of the files that will always be indexed.

It's not planned to change at this time but we know it's a common concern. If you'd like to create one of those Win7 Taskforce pages for it (if there isn't one already) and give me the link, that may help track how many people want to use such functionality (basically, being able to index network shares).

At this point my recommendation would be to get a USB, Firewire, or eSATA drive.

In my case, I use a Windows Home Server PC that has its content indexed with WS4.

I can confirm that adding network location in Libraries for Music, Video and Pictures works through Windows Media Player. But still no luck for Documents library, which in my case is the most important!

Am sure there must be some workaround for Documents Library as well, just need to dig around!

I have a NAS using local network too. I have the same problem.

Since Windows Desktop Search 4 (for XP), it is possible to add remote locations to indexation list. However, Vista's default indexation engine does not allow that anymore.

Microsoft released an update for Windows Vista, allowing network indexation. It makes Windows Desktop Search look like XP's, with a UNC option.

This patch has no equivalent for Windows 7 yet. However, you shall be able to install it over official beta 1, as I did.

Evidence:

post-278494-1232150608_thumb.jpg

Afterwoods, my indexed places look like:

post-278494-1232150599_thumb.jpg

So that solves one part of the problem, but not all of it: even if you index your network shares, windows won't realize it, and you still won't be able to add them to any library...

One more thing: network indexation used to run smoothly over XP, but seems to be a little bit buggy over 7. Explorer.exe is likely to crash if you use the start menu real-time search.

I got so excited when you said the Vista patch worked for you... until you said "Windows won't realize it". Regardless, since I already added stuff to my Libraries via WMP, I'll try it and see what happens.

Were you able to add a network location in your Documents Library?

Were you able to add a network location in your Documents Library?

No.

I downloaded the patch and it installed, then my mapped drive showed up in the index locations list. It looked nothing like Alvine's; I just got an extra checkbox. See:

post-275646-1232240537_thumb.png

However I'm not sure that indexing is actually occuring at all. You can see the screenshot says 'indexing complete', and I'm not sure if the network stuff was ever done. I don't have a way to see when it's actually indexing; I'd try that desktop gadget but 1) gadgets won't work for me and 2) I had to turn off my video driver and Aero.

Back to your question, when I try to add one of these locations to the Library, I get the same error as always (not indexed location). Also, when I try to do things with the WMP-added folders (Pictures, for eg.) like Arrange by Tag, it still tells me that the location is slow.

I dunno what to do man. Here's a thread on Channel 9 that seems to give evidence of what Microsoft was thinking when they left this out: http://channel9.msdn.com/forums/Coffeehous...ommentID=453315

Edited by burnblue
  • 2 weeks later...

To add a non-indexed UNC as a library to Windows 7 Beta:

1. Create a folder on your hard drive for shares. i.e. c:\share

2. Create another folder in the above share. i.e. c:\share\music

2. Link the Library to this folder.

3. Delete the folder.

4. Use the mklink in a command window(administrator access needed) to make a symbolic link. Name the link the same as the folder you created above. i.e - mklink c:\share\music \\server\music

5. Done. Now you have non-indexed UNC path as a library.

If you use symbolic links at a local folder and have the local indexing service work that ... you will increase network traffic possibly in an unefficient way.

Thnik like having your av-shield traversing local folders which are really remote.

But may be it can work if the indexer is optimized to understand that its working a networked and not local file system.

Usually it will not be so.

Mapped network drives are working as local volumes thus network traffic not optimized. So thats why mapped drives have performance issues and shares (networked file system) should be used instead (dynamic performance and can be configured in several ways for better performance either way).

Anyway - use process monitor to find out if indexer scans the network like it was local (if so you need to disable the links - or put those links on a local volume excluded from local indexer)

To add a non-indexed UNC as a library to Windows 7 Beta:

1. Create a folder on your hard drive for shares. i.e. c:\share

2. Create another folder in the above share. i.e. c:\share\music

2. Link the Library to this folder.

3. Delete the folder.

4. Use the mklink in a command window(administrator access needed) to make a symbolic link. Name the link the same as the folder you created above. i.e - mklink c:\share\music \\server\music

5. Done. Now you have non-indexed UNC path as a library.

FYI

About Windows Search 4.0 network performance (so the search services can be configured and are optimized for network traffic) ...

However, Windows Search services work client/server - and if you use symbolic links you make trick it into local file system performance behaviour and pay a penalty.

However, it would be smart if such services would discover using the network redirector across the link and go to network mode. I don't if they do that somehow - but know that last year my kaspersky Antivirus definitely did not do so when it walked the symbolic links to remote shares as if were local file system.

Anyone knows for sure?

Ref. Admin Guide 4.0:

http://technet.microsoft.com/en-us/library/cc770334.aspx

Network Performance

Enabling users to index network shares may temporarily increase the network traffic to these locations. The greatest impact on servers is seen building the initial index, and less impact is seen during subsequent incremental updates. Windows Search uses back-off logic to mitigate network traffic, and Group Policy further controls what Windows Search can index. For example, you can set a policy that disables indexing network paths to high volume servers.

  • 2 weeks later...
4. Use the mklink in a command window(administrator access needed) to make a symbolic link. Name the link the same as the folder you created above. i.e - mklink c:\share\music \\server\music

Hi.

Have you tried do that yourself?

I have the same problem, and unfortunately mklink cannot works with shares.

cmd> mklink C:\Users\Godfather\Libraries\Music \\Server\Music

The syntax of the command is incorrect.

The same said here, for example.

Hi.

Have you tried do that yourself?

I have the same problem, and unfortunately mklink cannot works with shares.

The same said here, for example.

Have you tried

mklink /d <target> <source>

?

default para is symbolic file link. you need to specify symbolic directory link with /d.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • With the current hardware prices Microsoft should lift the restriction. Then if you have the correct TPM then allow you to use X feature, if you don't have the correct TPM then don't but still actually let you run windows. 11. With a disclaimer during install that X features would be unavailable.
    • It's good for recycling of course. But commence inflation of a second hand RAM bubble and price gouging on DDR 4 inventory in 3... 2... 1...
    • Bypassed Windows 11 shows surprising stability on ancient, completely unsupported hardware by Sayan Sen When Windows 11 was first released, one of the most complained-about issues with the new desktop Microsoft OS was its higher system requirements, which pushed many relatively modern and powerful processors and devices onto the officially unsupported list. Thankfully, they have not been updated again for the base OS, though systems require four times the memory and storage if they want to run AI-powered apps and features. As such, Windows 11 technically runs on 4GB of memory, and there is no imposed restriction on the generation of memory it supports. Speaking of memory, prices are extremely high nowadays for hardware, especially DDR5 and DDR4 kits due to the current silicon shortage, and there are also reports of it affecting DDR2 as well, and it might only be a matter of time before even DDR1 gets affected. Before that could happen, an enthusiast took an ancient DDR1-based system and decided to try out Windows 11 on it to see how well the modern OS would fare on such hardware. The system runs an outdated graphics card interface standard based on AGP, or Advanced Graphics Port, called AGP 3.0 or AGP8x. AGP was essentially succeeded by the modern PCI Express (PCIe) bus standard. The user behind the experiment is retro hardware enthusiast Omores, who built the system around an ASRock ConRoe865PE motherboard based on Intel's i865PE chipset from way back in 2003, around the time when AGP was still in fashion. What made this board special back in the day was its unusual support for newer Core 2 Duo and even Core 2 Quad processors while still retaining older DDR1 memory support and an AGP8X graphics slot, making it an ideal bridge or link between two vastly different generations. Powering the machine was Intel's Core 2 Quad Q6600 alongside 3GB of DDR1 RAM and an ATI Radeon HD 4650 AGP graphics card, one of the final and most capable GPUs released for the aging AGP interface. While installing Windows 11 itself was relatively easy by bypassing Microsoft's hardware checks, getting the graphics card fully functional proved to be some challenge. Microsoft had quietly dropped native AGP support after the earliest releases of Windows 10, meaning newer versions of Windows no longer include the necessary Graphics Address Remapping Table (GART) drivers required for proper AGP acceleration. Without them, AGP graphics cards typically boot up, though with limited functionality, and can often throw a Code 43 error in Device Manager. To work around the limitation, Omores extracted Intel's legacy AGP440 SYS driver from an early Windows 10 release and paired it with a modified INF file so Windows 11 would correctly recognize the chipset. Following this and combined with AMD's final 64-bit Catalyst AGP drivers from 2012, the Radeon HD 4650 was able to operate with full AGP 8X acceleration intact. The result was said to be surprisingly usable for hardware that is over two decades old. Hardware-accelerated H.264 video playback worked correctly and benefited apps like Firefox, while legacy applications and games ran without major graphical issues. The system also successfully completed the 3DMark 2001 benchmark, although performance naturally lagged behind what the same hardware achieves under Windows 7, which is significantly lighter than Windows 11. There was, however, one unavoidable limitation as Microsoft's Windows 11 version 24H2 introduces a mandatory SSE4.2 CPU instruction requirement that cannot be bypassed through installer modifications or registry tweaks. Since no AGP-era processor supports SSE4.2, Windows 11 version 23H2 effectively becomes the final release capable of running on such systems. Regardless, it is still a very cool feat and quite fascinating to see just how stable Windows 11 turned out to be on such unfamiliar hardware. Source: Omores (Patreon) via O_MORES (Reddit)
    • That will only really help other players that are also responsible for creating the problem.
    • Well, it's good to know that they have found a workaround to a problem that they helped create, I guess...
  • Recent Achievements

    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
    • Week One Done
      NovaEdgeX earned a badge
      Week One Done
    • One Year In
      BA the Curmudgeon earned a badge
      One Year In
    • Conversation Starter
      rosiecharles earned a badge
      Conversation Starter
    • First Post
      KMilenkoski1202 earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      539
    2. 2
      +Edouard
      266
    3. 3
      PsYcHoKiLLa
      151
    4. 4
      Steven P.
      98
    5. 5
      macoman
      66
  • Tell a friend

    Love Neowin? Tell a friend!