Guest User!

You are not Sophos Staff.

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

SDE/FDE managed by SEC - policy comparison failure

QC

Hello,

during the 5.1 Beta tests I have encrypted a laptop (client version is 5.61.0.22) and recently "moved" it to the production server by pointing it to the production CID (where FDE is 5.61.0.25). The client is reporting correctly to SEC (including the User Machine Assigment) but policy comparison fails.

Is this because the client is running the Beta version - if so, how could it be updated other than uninstalling/decrypting - reinstalling (which is, as I am aware, the recommended way for Betas)?

Christian

:29207


This thread was automatically locked due to age.
  • 0

    Hi QC,

    as you already mentioned, re-installing would be the correct attempt as the machine is still running the Beta build of SDE 5.61.

    Have you tried to re-protect the machine (select the machine, choose "Protect Computers..." followed by choosing "Encryption software" again) and running the 5.61.0.25 install over the Beta build? 

    Regards,

    ChrisD

    :29213
  • 0

    Hello ChrisD,

    thanks for the quick reply. Have you tried to re-protect the machine - well, I was thinking about it but figured I better ask first :smileywink: (even this being only a test machine). 

    Christian

    :29223
  • 0

    Hm ... upgrading by reprotecting the client from the console worked like a charm. Unfortunately it did not resolve the policy issue. Wonder what caused the failure in the first place - not enough data available to make an educated guess :smileyhappy:. 

    Is there anything else to try except the complete install and [de|en]crypt cycle? Apart from that - what does comparison failure signify with respect to SEA?

    Christian

    :29249
  • 0

    As SafeGuard has several (forgive the pun) safeguards built into it I decided not to hack around any more - although it'd probably have been an informative experiment - instead I took the long path. Uninstalled (no problems here, though it's more than just a single step and naturally takes some time), reprotected and it's now in the final stages of encryption. All seems well.

    Christian

    :29687
Unfiltered HTML