Sunday, December 23, 2012 12:00 AM
Since I migrated a file server to Server 2012 I am experiencing a disturbing issue:
I am unable to get the Windows Search Service working to index shares. I searched the web and was unable to find its replacement on Server 2k12
This is really annoying because I cannot add shares from my Win2k12 server to librairies (This network location can't be included because it is not indexed). Making that folder available offline is not an option as it's huge. Search queries do also take a lot of time now.
Could anyone give me a hint how to get this working again? This feature seems to be gone...
Sunday, December 23, 2012 12:11 AM
My bad, found it!
Windows Search Service has moved from File Server role to feature, that's why I got confused.
Sadly it requires the whole GUI... DAMN I was so happy with my server core file server.
- Marked As Answer by FuN_KeY Sunday, December 23, 2012 12:11 AM
Tuesday, December 25, 2012 6:55 AMModerator
Neither the Windows Search Service role service nor the older Indexing Service can be installed on Server Core. This is by design.
In addition, if we need to search for files or folders on disk volumes on Server Core, we must do it using one of the following two ways: by using the Dir command with the /s switch to search all subdirectories on a volume, or by using grep search in Windows Explorer running on a remote computer.
Hope this helps and Happy Holidays!
TechNet Community Support
Saturday, February 02, 2013 1:45 AMI thought the Windows Search Service feature was needed on file servers in order for clients to search efficiently, and, e.g., to prevent clients from complaining that the Documents folder "doesn't support all features" (or something to that effect). That is, I didn't think it was just for performing local searches. Is there a different feature that enterprise file servers should be using instead to keep the clients happy?