Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 0 subscribers
  • Views 20086 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

Sophos Enterprise Console is not communicating with client PCs

F2Andy

This has been an on-going problem that I am only now trying to solve. Windows XP machines are fine, some Wndows 7 are too, but most are not. They appear in the list greyed out. Some have errors ("The installation could not be started" or "Computer s not yet managed"), but most are just blank. If I look at computer details, all it can show is the name, OS, domain and IP address.

PCs I have looked at seem to be running Endpoint okay, and update just as they should (hence I have not worried to much about the console not working).  Endpoint was installed from the local machine during installation in every case.

Endpoint version 10.3
Enterprise Console 5.2.0.644 running on Windows Server 2011 SBS

ETA: Also just noticed the policy set up in Enterprise Console has not been distributed.

:55138


This thread was automatically locked due to age.
  • 0

    Hello F2Andy,

    this suggests an issue with RMS. Please see Enterprise Console reports installation failed: Error fffffffd computer not managed for a start.

    Christian

    :55141
  • 0

    Thanks, I have gone through that and set up new Group Policies (it seems a little outdated by the way; some policies have different names and I kind of guessed what it meant). Having done that, I checked the gpresult on my PC and confirmed GP was working. However, it is still not communicating.

    I am getting 3 different error responses.

    In some cases there is no error code at all (and at least one PC like this is not updating)

    In others I see ffffffd

    In yet others I see 0000002b, which is saying the credentials are wrong (and yet it accepted them when I typed them in, so the user and password must be right, and I have checked the user is an adminstrator on both client and server)

    :55156
  • 0

    Hello F2Andy,

    there are just three articles on 0000002b which might (or might not) help.

    On the ones with fffffffd - is RMS installed (details on how to proceed are in article 117766)? Feel free to post snippets of the logs if necessary. Could be the same issue on those without an error code.

    For the not updating one(s) please check the AutoUpdate log (link also in the aforementioned article)..

    Christian

    :55160
  • 0

    The third article was for Windows 2000

    The second was suggesting putting in the right password and username. Yeah, I had thought of that myself.

    The first was slightly more useful. It looks like the console is failing to create a task on the client. However, I was able to create a task from the command prompt on the server, using the same username and password. It did not then say what to do from there. that looks like the fault is in So[phos to me.

    By the way, schtasks command works better with the IP address.

    :55162
  • 0

    Hello F2Andy,

    schtasks command works better with the IP address

    what exactly is works better? SEC uses one of the Windows APIs (but don't ask me for details). If schtasks seems to behave "abnormal" this could indicate some problem (perhaps AD/DNS) which eventually causes the scheduling from SEC to fail. Anyway, Protect Computers is not essential unless you intend to use Active sync with automatic deployment.

    What about the other endpoints and the potential issue with RMS?

    Christian

    :55176
Unfiltered HTML