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

SUM "Failed the checksum validation step"

Hi all,

I'm building a new installation of SEC 5.1, using a couple of SUM distribution points plus the SUM server itself.

So, SUM gets its updates from an upstream server (this works fine). Subscriptions to windows v10 recommended and OSX 8 recommended.

There are two "software distribution points" configured. Excluding real names, they are:

\\Server1.domain.local\sophossource

\\Server2.domain.local\sophossource

Both servers have the same ACLs set up (NTFS/NTFS share), and both are configured in SUM to use the same specific set of credentials for updating (said credentials allow modify access to the above locations, and I have tested this).

So what happens...

Software is distributed to both server1 and server2. I can see it happening, and can even install the endpoint sec client from both locations successfully (and update from). However, I get this error repeatedly in the SUM log:

"Deployment to share \\Server1.domain.local\SophosSource\CIDs\S000 failed the checksum validation step"

On the face of things this seems to mean nothing, but this is a new installation and I don't want to leave spurious errors when it goes live!

Any ideas please?

Thanks

Rob

:35141


This thread was automatically locked due to age.
Parents
  • Hi Christian,

    Yes that's exactly right. I think the trace logs were what I was looking for... never had to go quite that deep before :)

    I looked through and it twigged....

    You'll love this...

    ServerA still had a broken shh/updater-B version of the client, so it was detecting the distributed files as viruses and deleting them.......

    On-access scanning turned off and now working fine... new client to roll out to that one soon.

    Thanks

    Rob

    :35195
Reply
  • Hi Christian,

    Yes that's exactly right. I think the trace logs were what I was looking for... never had to go quite that deep before :)

    I looked through and it twigged....

    You'll love this...

    ServerA still had a broken shh/updater-B version of the client, so it was detecting the distributed files as viruses and deleting them.......

    On-access scanning turned off and now working fine... new client to roll out to that one soon.

    Thanks

    Rob

    :35195
Children
No Data