>The ideal behind using the Windows Scheduler is NOT to have to run the client PC. And you are saying to "leave the client machine running." Or, are you talking about your own made Windows Scheduler?

There are two ways to do it:
1) Run on the server. Not every company we sell our software to desires this. In fact, probably 80% refuse to run anything on the server whatsoever, and 10% will only run software if you convince them it's not malware by showing them source code, documenting things, etc. For those clients, we have to have a client machine left on when they want to run something, and then the software runs from the client.

2) Run on the client. Requires leaving a client machine on, or having a wake on lan remote access, so it will start up at the appropriate time by a signal from the server. In either case, the update runs on the client accessing the server traditionally.

In both cases, they use the Task Scheduler or our custom scheduler service, and launch apps at indicated times with indicated options.