Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 1 subscriber
  • Views 1421 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to Automate Modification of Nightly Scheduled Scan to Wake Up Computer on 2300 computers

mcintoshs

Hello,

We run nightly scheduled scans on 2300 computers via the Sophos scheduled task. However, the task won't run if the computer is in power standby mode and the default scheduled task isn't configured to "Wake computer to run task" in the settings of the task properties.

How can I fix this issue? Ideally I want to automate (script) the modification of the scheduled task to wake the computer to run the task.

However, AFAIK neither the AT nor SCHTASKS utilities in XP are capable of modifying that property.

Any time-saving solutions/workarounds would be greatly appreciated.

Scott

:1702


This thread was automatically locked due to age.
Parents
  • 0

    Hi There,

    The recommended solution in an environment where you have managed Sophos endpoints would be to script something that does the following:

      

    1 - Wake on LAN the machines at a time 10-15mins before the scheduled scan is due to start

    2 - The scan will start automatically

    3 - Have something in the script check that the scan has finished then shutdown the machine

     

    Why dont we just use SCHTASKS to make the change?

    Generally for remote changes you can script something with the SCHTASKS /Change function (http://support.microsoft.com/kb/814596) which will push down the modification over the network.

    However, "Wake up the machine to run this task" cannot be set using SCHTASKS so in this situation it would not be an option .

    The most common other 'workaround' then for this would be to open the task on one machine, make the change, save it - then copy over the .job file to all of your other machines.

     

    However (again), even with this, we are not taking into consideration the possibility managed machines may try re-applying the original task set in the policy wiping out your change and the machines might also start reporting back to the Console as 'differing from policy' making for a messy Console.

     

    Any further information on this I would suggest contact support.

     

     

    Regards,

     

    MarkA

    :1707
Reply
  • 0

    Hi There,

    The recommended solution in an environment where you have managed Sophos endpoints would be to script something that does the following:

      

    1 - Wake on LAN the machines at a time 10-15mins before the scheduled scan is due to start

    2 - The scan will start automatically

    3 - Have something in the script check that the scan has finished then shutdown the machine

     

    Why dont we just use SCHTASKS to make the change?

    Generally for remote changes you can script something with the SCHTASKS /Change function (http://support.microsoft.com/kb/814596) which will push down the modification over the network.

    However, "Wake up the machine to run this task" cannot be set using SCHTASKS so in this situation it would not be an option .

    The most common other 'workaround' then for this would be to open the task on one machine, make the change, save it - then copy over the .job file to all of your other machines.

     

    However (again), even with this, we are not taking into consideration the possibility managed machines may try re-applying the original task set in the policy wiping out your change and the machines might also start reporting back to the Console as 'differing from policy' making for a messy Console.

     

    Any further information on this I would suggest contact support.

     

     

    Regards,

     

    MarkA

    :1707
Children
No Data
Unfiltered HTML