Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 5 subscribers
  • Views 9407 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.
Parents
  • 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
Reply
  • 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
Children
No Data
Unfiltered HTML