Today we decided to setup the indexing of a 1TB windows share containing MS-Office documents using Federated Search.
We had setup the index files to reside in a large drive (allocated letter "D") on the Application server.
Unfortunatly, later in the day, we noticed the C drive of our Application Server had run out of space, and that it was taken up with a large amount of data in:
Why would the file crawler service fill our C drive, and not use the D drive as configured?
How might we overcome this issue?
Any advice gratefully received.