Bit of advice on dealing with Windows Search.
We have 5 Xenapp servers 7.6 running on Server 2012 R2.
We have around 16 users on each server during the day. Looks like the Windows Search Service has been installed.
We are finding on a daily bases the searchindexer.exe processes hammering the CPU for around 30 seconds periodically. users notice this and see a detrimental performance of the system when it occurs.
We plan on adding an extra core to the servers to help deal with this.
We also have an issue that the searchindexer.exe process continues to grow during the course of the day taking up the memory. Unless the server is rebooted it just continues to grow, so have now set the server to reboot at 4am every day to help combat this. With this in mind I am proposing we remove the Windows Search service feature.
What is the recommended approach, the main reason I believe it is installed is so they can quickly find e-mails in Outlook. but i'm not sure if this is feasible for a terminal server environment.
If I remove it will I then get users calling in saying they cannot search fro e-mail.
Anyone come across this scenario?