Steps to reproduce:
1. When an ingest server is set up, it needs the scheduler service in cases where a capture agent is repeating an ingest operation to match the ingested data with the orginal recording.
2. Currently, the ingest profile needs to be deployed with the "real" implementation of the scheduler service, which means that there are multiple versions of the scheduler service in the system. Since currently each service instance has its own local search index, the ingest service will not be able to see the actual data and return empty results to its ingest service.
As a result, a remote implementation of the scheduling service needs to be created that can be deployed as part of the ingest profile.