• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 78
  • Last Modified:

Windows Search (Indexing) on 2012 Servers

I got bit again. I was so disgusted with what indexing did to the speed of servers back with Server 2003 I just shut it off. It was a mess. But I got bit again on a Server 2012.

I was at a customer's yesterday and she showed me on her Windows 7 computer that when she opened up Documents that it displayed the warning "Some library features are unavailable due to unsupported library locations". I figured it was a indexing issue and went to the server and added the location of their redirected folders to indexing. Didn't think much about.

On that same day I had to re-subnet their network and boy did I start getting calls. Adding attachments to emails was slow, opening and saving Excel was slow, it was a mess. I started looking at the re-subnetting until it dawned on me that I indexed the redirected folders location.  The server was on its knees.

This is a small network (20 workstations) with a decent 15K SAS server and 16GB memory. Yet once again the Indexing caused problems. So where does indexing stand on 2012 servers? Do people actually use it? Do they  index the location of redirected folders? Why does it still bring the server to it's knees?
1 Solution
Adam BrownSr Solutions ArchitectCommented:
Windows search will peg your drives while it builds the index, since it goes through every file and their contents to build the search database. If you have a lot of files, it can take a really long time to do that, too, so it's definitely best to avoid enabling search on high-usage servers during business hours. If you start the index after EoB on Friday, it *should* be complete by Monday morning (depending on how many files you have).

It will continue to use additional resources as it examines new files and adds them to the database, while removing deleted files from the database, but will not use as many resources as when it originally builds the database the first time. The ongoing usage depends heavily on how many files are created/deleted.

It's useful to have search enabled on servers that have large file stores like redirected folders, but if it uses too many resources for people to be comfortable with, it isn't strictly necessary to have it running.

If you want to get rid of that error message for your user without enabling search, make sure she's accessing the actual documents folder instead of the Documents library.
LockDown32OwnerAuthor Commented:
Yes, just like XP, that message is indicative of not being in a indexed location. I get the same warning (but don't really care) and when I indexed my RedirtectedFolders it went away. The whole indexing thing is a mess. Has been since inception. I'll try shutting it down and see if the complaining about the speed goes away.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now