Launch the RemoteSchedulingService.exe file to install the Scheduling Service on a non-IDI server.
On a first time install/re-install, the user is prompted for an IDI applications directory. As with the Universal Installer, an eFrameNET directory (and any other future directories) is created beneath the main one to contain all IDI platform software.
Click Next. This displays the Choose Info Directions Applications Directory form.
If you wish to choose another Destination Folder, click Browse to locate the folder and click Save.
Click Next. This displays the Specify Host Protocol Information form.
Enter the CG Host information. Enter the socket configuration information to use to talk to a specific Host service. This information is substituted in the %COSTGUARDHOSTINFO% string of the SchedulingHost.exe.config file. Locate the appropriate string from the .exe.config file in the NetClientApps directory on the IDI server that this installation of the scheduling service is to work with the .
Click Next. The Specify Web Proxy URL form is displayed.
Enter the URL of the Web Proxy. The URL corresponds to the virtual directory of the application server running the Web Proxy. This is the location that the Scheduling Service contacts in order to download the requisite client files. This URL is used to substitute the %COSTGUARDWEBPROXYURL% string the SchedulingHost.exe.config file.
Click Next. File transfer begins. Installed to the eFrameNET directory along with the SchedulingHost.exe and SchedulingHost.exe.config are the bare minimum set of dependent files need to install and start the service. The Installing IDI Scheduling Service… form is displayed.
The installation process is complete.
Installing the IDI Scheduling Service as a Standalone
- Published on Aug 10, 2026
Was this article helpful?