There is an intentional pause in the startup of TeleFlow Server when the computer first comes up.
This is in response to issues wherein starting too quickly didn't give the telephony hardware services adequate time to properly start themselves. When TeleFlow would come up too soon, and attempt to use functionality depending on those board services, the functions would fail, and TeleFlow would try again and again, and in some cases, this prevented those board services from ever finishing initializing.
It is possible this is what you are experiencing. To test it, give the system a full 5 minutes after reaching the Windows log-in screen before checking to see if TFServer has started properly. If it hasn't, it would help to see some logs of the issue.
To generate the appropriate logs:
1) Turn on All Events logging for up to 20 application instances in your TAL file.
2) Stop TFServer, and ensure your log directory is empty.
3) Restart the computer, and wait a full five minutes before logging in.
4) Verify that TFServer still hasn't started.
5) Stop TFServer, and provide a zip of the resulting log files to us by sending it to
support@engenic.com. We will respond in this thread.
