Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 11 replies
  • Subscribers 1 subscriber
  • Views 5749 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

Windows 7 Schedule Task Fail

Dean_Curtis

Hi,

We have recently purchase Sophos and we have the following products:

- Sophos Enterprise Console v5.0.0.8

- Sophos Endpoint v10.0

We have installed Enterpise Console onto a Windows Server 2008 R2 machine and we are trying to deploy to Windows 7 Pro SP2 PCs. Intinal setup and configuration was fine but now we are coming across problems when trying to deploy Endpoint to our Windows 7 computers. Everytime we push out the software it seems like nothing is happening.

When taking a closer look we can see that the end hosts are getting a schedule task to run and install Sophos but they will not run that task, it seems like it just sits there doing nothing.

We have tried the following solutions which we have come across on other forums:

- Change the registery on Server (EnableTaskScheduler2 = set to 1)

- Make sure all required services are running: (Remote Registry = Automatic, Task Scheduler = Automatic, Windows Installer = Manual)

- We have turned off UAC on PCs

- We have make sure everyone has full access to the tasks folder in Windows to run schedules

However after trying all these changes we still cant get Sophos to deploy correctly.

Any suggestions would be gatefully recieved,

Dean

:24911


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

    Based on the XML, I'm not convinced the registry key is being used.  So it's still using the verison 1 interface.  This would explain the symptoms.

    Can you check that the key is correct, as you're 64-bit it should be under:

    HKLM\Software\Wow6432Node\Sophos\EE \

    DWORD

    EnableTaskScheduler2

    Value 1

    Once added restart the Sophos management service.  You could even check with Process Monitor the key is being read.

    Then check the task XML export on the client again after another reprotect.

    Regards,

    Jak

    :24935
Reply
  • 0

    Based on the XML, I'm not convinced the registry key is being used.  So it's still using the verison 1 interface.  This would explain the symptoms.

    Can you check that the key is correct, as you're 64-bit it should be under:

    HKLM\Software\Wow6432Node\Sophos\EE \

    DWORD

    EnableTaskScheduler2

    Value 1

    Once added restart the Sophos management service.  You could even check with Process Monitor the key is being read.

    Then check the task XML export on the client again after another reprotect.

    Regards,

    Jak

    :24935
Children
No Data