Windows Search (Indexing) on 2012 Servers
Posted on 2016-08-26
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?