Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 28 replies
  • Subscribers 1 subscriber
  • Views 28172 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

AV client push scheduled task doesn't run in Windows 7

kevindv10

Hello.

I have Enterprise Console (4.5 I think) running on Windows 2008 64-bit, trying to push out to Windows 7 clients. About 60% of the clients receive and install ok, but the rest don't. I thought their group policies were the same but maybe not.

Anyway, I can see the scheduled task being created on the client, but it doens't run. If I run it manually the client installs fine and updates with Enterprise Console, but I can't manually run the task on hundreds of clients.

I've spent a lot of time trying to find a group policy that might be restricting the remotely created scheduled task from running (with everything up to and including domain admin credentials) but I'm empty handed. Anyone know what the problem might be?

A tech from Sophos helped me at least figure out that the task was being created and could be run manually. It was a pleasure working with a support person that actually seemed to care!! Made the best of a frustrating situation.

Thanks in advance.

:5156


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

    Hi,

    From looking at the properties of the scheduled task created with SEC 5.1 (you can export to XML), 5.1 sets the property of the task to be:

          <RunLevel>HighestAvailable</RunLevel>

    Where as 4.7 and 5.0 with the above key don't set this run level. So in the future this should avoid the UAC prompt I would think.  

    With that being said, before SEC 5.1 comes out of Beta, you'll have to switch back to taskscheduler 1 interface (remove or set the key to 1) or follow articles such as:

    http://www.sophos.com/support/knowledgebase/article/111180.html

    which tell you disable UAC.

    For tasks failing to deploy with the new task scheduler, you may want to check that the target Win 7 machine isn't running on batteries when you deploy as I also notice:

    <DisallowStartIfOnBatteries>true</DisallowStartIfOnBatteries>   

    <StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>

    Regards,

    Jak

    :22369
Reply
  • 0

    Hi,

    From looking at the properties of the scheduled task created with SEC 5.1 (you can export to XML), 5.1 sets the property of the task to be:

          <RunLevel>HighestAvailable</RunLevel>

    Where as 4.7 and 5.0 with the above key don't set this run level. So in the future this should avoid the UAC prompt I would think.  

    With that being said, before SEC 5.1 comes out of Beta, you'll have to switch back to taskscheduler 1 interface (remove or set the key to 1) or follow articles such as:

    http://www.sophos.com/support/knowledgebase/article/111180.html

    which tell you disable UAC.

    For tasks failing to deploy with the new task scheduler, you may want to check that the target Win 7 machine isn't running on batteries when you deploy as I also notice:

    <DisallowStartIfOnBatteries>true</DisallowStartIfOnBatteries>   

    <StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>

    Regards,

    Jak

    :22369
Children
No Data