Reply to thread

Message

Hi MM,

Logon via terminal service is just one. I am using the server to serve video files, music, etc and set the powerscheduler to not shutdown the server when there is network traffic. Anyhow, I have the impression that the standby timeout in the configuration tells powerscheduler to keep the machine alive for x more minutes after the machine becomes idle. I thought that should include all the conditions that powerscheduler allows me to configure i.e. network traffic, file shares, processes.

While modifying the _lastUserTime may not be the right way to fix the issue, powerscheduler not updating the standby time after a valid activity is still a problem.

Take my case as an example. I set the timeout to 60 minutes. If I play a video file that is 120 minutes long, by the time the video end, I have already passed the timeout (because the timeout doesn't get updated as I play the file/generating network traffic). When I finish the current video, powerscheduler only gives a final 2minutes of "grace period" for me play another file in order to prevent the machines from being shutdown by the scheduler. This is obviously a problem.

Regards,

Edward

<blockquote data-quote="Edward Cheung" data-source="post: 1194123" data-attributes="member: 159714">Hi MM,Logon via terminal service is just one. I am using the server to serve video files, music, etc and set the powerscheduler to not shutdown the server when there is network traffic. Anyhow, I have the impression that the standby timeout in the configuration tells powerscheduler to keep the machine alive for x more minutes after the machine becomes idle. I thought that should include all the conditions that powerscheduler allows me to configure i.e. network traffic, file shares, processes.While modifying the _lastUserTime may not be the right way to fix the issue, powerscheduler not updating the standby time after a valid activity is still a problem.Take my case as an example. I set the timeout to 60 minutes. If I play a video file that is 120 minutes long, by the time the video end, I have already passed the timeout (because the timeout doesn't get updated as I play the file/generating network traffic). When I finish the current video, powerscheduler only gives a final 2minutes of &quot;grace period&quot; for me play another file in order to prevent the machines from being shutdown by the scheduler. This is obviously a problem.Regards,Edward</blockquote>

[QUOTE="Edward Cheung, post: 1194123, member: 159714"] Hi MM, Logon via terminal service is just one. I am using the server to serve video files, music, etc and set the powerscheduler to not shutdown the server when there is network traffic. Anyhow, I have the impression that the standby timeout in the configuration tells powerscheduler to keep the machine alive for x more minutes after the machine becomes idle. I thought that should include all the conditions that powerscheduler allows me to configure i.e. network traffic, file shares, processes. While modifying the _lastUserTime may not be the right way to fix the issue, powerscheduler not updating the standby time after a valid activity is still a problem. Take my case as an example. I set the timeout to 60 minutes. If I play a video file that is 120 minutes long, by the time the video end, I have already passed the timeout (because the timeout doesn't get updated as I play the file/generating network traffic). When I finish the current video, powerscheduler only gives a final 2minutes of "grace period" for me play another file in order to prevent the machines from being shutdown by the scheduler. This is obviously a problem. Regards, Edward [/QUOTE]