Deployment Guide › File Scanning Agent (FSA) › Deploy FSA Remote Connectors › Why Deploy an FSA Remote Connector?
Why Deploy an FSA Remote Connector?
If you want to scan Microsoft SharePoint items, you must deploy an FSA Remote Connector on the machine hosting the SharePoint site.
For other scanning jobs, it may be necessary for reasons of security or efficiency to run the scanning job on the remote machine. For example:
- If scanning a large database, it may be more efficient to install the FSA Remote Connector on the machine hosting the DBMS, rather than retrieving database records across the network to the FSA for analysis.
- If you need to scan sensitive folders on a remote machine that cannot be accessed by a UNC path you will need to deploy an FSA Remote Connector on that machine. In effect, this allows you to run a local scan on that machine. Scanned items that require policy processing are sent back across the network to the FSA.
- If a scanning job is configured to exclude a large proportion of files, then it is more efficient to identify these exclusions on the host machine, rather than retrieving all files across the network to the FSA for analysis.