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

Why Sophos Safeguard Enterprise 6.0 Breaks MBR?

We use sophos safeguard 6.0 and once in a while we get a PC with a corrupt MBR where we have to use the sophos boot disc to fix it, and its very time consuming as we can't re-image the device. My question is why this happens, and is there a way to prevent this , is there  a quicker fix?

Thanks,

:44067


This thread was automatically locked due to age.
Parents
  • I wouldn't go as far as to say its Sophos that is breaking the MBR, it changes things but these changes are not something that with time suddenly go faulty.

    When a MBR becomes corrupt or has issues in most cases, it can be cuased by one or more bad sectors on the disk. Sophos requires a spotless MBR and running a Chkdsk for scan disk can assist in finding these errors. These scans are benifical to the OS and to Sophos. It is not recommened to use Boot managers as this can cause conflicts. In some cases imaging software can cuase MBR changes or issues that will result in failure.

    Virus attacks can also cause damage to the MBR which will also cuase issues...

    There is a multitude of scinarios where the MBR can become corrupt its hard to really pinpoint the source. If you are having to do this often to endpoints, you might want to consider replacing the hard drive in these systems. It is not so much Sophos that is causing these issues.

    In the instance of where Sophos is present on the machine, Sophos writes to the MBR and modifies addresses to boot in specific way, in your situation using the Sophos MBR recovery is the best practiced solution and using anything else will not result in success.

    :44073
Reply
  • I wouldn't go as far as to say its Sophos that is breaking the MBR, it changes things but these changes are not something that with time suddenly go faulty.

    When a MBR becomes corrupt or has issues in most cases, it can be cuased by one or more bad sectors on the disk. Sophos requires a spotless MBR and running a Chkdsk for scan disk can assist in finding these errors. These scans are benifical to the OS and to Sophos. It is not recommened to use Boot managers as this can cause conflicts. In some cases imaging software can cuase MBR changes or issues that will result in failure.

    Virus attacks can also cause damage to the MBR which will also cuase issues...

    There is a multitude of scinarios where the MBR can become corrupt its hard to really pinpoint the source. If you are having to do this often to endpoints, you might want to consider replacing the hard drive in these systems. It is not so much Sophos that is causing these issues.

    In the instance of where Sophos is present on the machine, Sophos writes to the MBR and modifies addresses to boot in specific way, in your situation using the Sophos MBR recovery is the best practiced solution and using anything else will not result in success.

    :44073
Children
No Data