I notice the scheduler strangeness from two different aspects. One, I can see in the Netcam client that motion detection is on for a camera that has it scheduled to be off, or vice-versa, depending on the behavior. Two, I have triggers setup on these cameras to capture time-lapse video during motion events and these cameras are capturing the time-lapse video during times when the motion detection is scheduled to be off.
When it does go wrong, it usually stays wrong until I manually stop/start the motion detection or stop/start the Netcam service.
I do not believe I have anything else running that changes the clock. I am pretty meticulous in knowing what is running on my system, since I am an IT professional.
I almost never run the NCS X executable, since I mainly run this as a service, so that it survives logoff’s and other users logging into the system. I only generally run NCS X when I want to modify camera configurations, since I have observed camera configurations don’t seem to stay persistent when I change them using the client. So unfortunately, I can’t speak to whether this behavior is exhibited with NCS X.