Time synchronization is essential for accurate Scheduling. When the Video Server and Stream Studio are not in sync unexpected events can appear.

We found a specific scenario where schedules got lost when the server time as ahead.


Recorder time 10:58 AM

Server time 11:01 AM

Schedule start today at 11:00 AM

In case a sync task is ran exactly in this time difference a few moments before a recording should start, the following actions will cause the schedule to get deleted before it started

  • the future schedules are retrieved from the server (11:01 or later)
  • This excludes the 11:00 schedule, since it is in the past
  • The recorder detects 11:00 is not in the schedule list anymore, while it is still 10:58
  • The recorder deletes upcoming schedule 11:00 before the recorder time is 11:00

Hence no recording is made.

In some exceptional cases the time service on Windows 10 is not working as supposed to.

  1. the time service failed to start because the recorder booted too fast (no IP address assigned yet)
  2. the firewall is closed for accessing default time servers as time.windows.com

To check if the time service is up and running on your recorder PC you can run the following command in a dos prompt (with elevated rights):

w32tm /config /update /manualpeerlist:time.windows.com

In case this results in an error the time service is not running, indicating time service issues. Next try starting the service before updating time:

net start w32time & w32tm /config /update /manualpeerlist:time.windows.com

If this works, you might have ran into  issue 1.

Run the following commands to start the time service delayed and disable the windows scheduled task to start the service.

schtasks.exe /Change /TN "\Microsoft\Windows\Time Synchronization\SynchronizeTime" /Disable

net start w32time & w32tm /config /update /manualpeerlist:time.windows.com

sc config w32time start=delayed-auto

Windows uses UDP port 123 for the time service. To check if the port is not blocked you can run

netstat -an 1 | find ":123"