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

Computer could not be contacted

Dheald

When trying to install Sophos from the Enterprise Console, using the "Protect Computers" option from the menu, I have had some install successfully, but a few have come up with the error message: Computer could not be contacted. [0x0000002e] Any ideas what this is about? The machines are online and reachable.

:7991


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

    HI,

    If the posted links didn't shed any light on it and you've managed to protect some of your Windows 7 machines from SEC: I suspect this is a problem which I've been told will be addressed in SEC 4.7.  Apparently there is a new Microsoft API for creating scheduled tasks in the newer Windows operating systems but the older API as used by SEC should also work and it clearly has worked on a few of your Window 7 machines, so it's a bit mysterious as to know why some of the machines behave differently?  Are they different variants of Windows 7?

    From what I know the scheduled job file gets created but then doesn't run.  Is this what you see?  

    For example if you check the clients directory:

    \windows\tasks\

    and ensure it's clear of Sophos install job files and then protect the machine again from SEC, does the job file get created but doesn't run?  I would expect if you manually run it, it works?

    If it creates the job file, at least you know the machine is set-up correctly to receive and create it and you myst be suffering this problem on the machines it doesn't run on.  If so, for the short term I would suggest taking the deployment string by copying it from the job file and run it on the remaining machines either using: AD start-up scripts, maybe login scripts if the users have admin rights, PSEXEC to remotely deploy or another application you might have such as SMS to run the command.

    As it should be a one time task hopefully you haven't got many machines with this problem at least until SEC 4,7.

    Regards,

    Jak

    :8003
Reply
  • 0

    HI,

    If the posted links didn't shed any light on it and you've managed to protect some of your Windows 7 machines from SEC: I suspect this is a problem which I've been told will be addressed in SEC 4.7.  Apparently there is a new Microsoft API for creating scheduled tasks in the newer Windows operating systems but the older API as used by SEC should also work and it clearly has worked on a few of your Window 7 machines, so it's a bit mysterious as to know why some of the machines behave differently?  Are they different variants of Windows 7?

    From what I know the scheduled job file gets created but then doesn't run.  Is this what you see?  

    For example if you check the clients directory:

    \windows\tasks\

    and ensure it's clear of Sophos install job files and then protect the machine again from SEC, does the job file get created but doesn't run?  I would expect if you manually run it, it works?

    If it creates the job file, at least you know the machine is set-up correctly to receive and create it and you myst be suffering this problem on the machines it doesn't run on.  If so, for the short term I would suggest taking the deployment string by copying it from the job file and run it on the remaining machines either using: AD start-up scripts, maybe login scripts if the users have admin rights, PSEXEC to remotely deploy or another application you might have such as SMS to run the command.

    As it should be a one time task hopefully you haven't got many machines with this problem at least until SEC 4,7.

    Regards,

    Jak

    :8003
Children
No Data