Guest User!

You are not Sophos Staff.

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

Recovery key is not valid after upgrade from 5.50 tp 5.50.8 stand alone version

Tyler

Hi Guys


I have tried to use the recovery key from v5.50 which I saved before to unlock a laptop, but it says the recovery key is not valid after we upgrade from 5.50 to 5.50.8 stand alone version. Do you guys know why is that?

We have 20  v5.50 safeguard encrypted laptops. Now we can't unlock them with 5.50.8. Is there any way to unlock them? Thanks.

:8257


This thread was automatically locked due to age.
  • 0

    Hi Tyler,

    welcome to the forum!

    With regards to your description I can tell you that his is an unknown issue. Please be so kind and raise a new ticket so that we can have a closer look and this and try to reproduce.

    When opening the ticket please provide as much information as possible such as did you use the keys before? How did you update? Any other things that you changed during the update?

    Thank you very much!

    Regards

    Dan

    :8529
  • 0

    Dan,

    This problem is well known for versions upgraded from 5.40.x to 5.50.x. Keys generated in this older versions then subsequently the client upgraded through 5.50.0, 5.50.8 won't have or generate valid XML key files. I originally raised this way back when 5.50.0 was released and it was found to be a 'feature' and should be known to tech support.

    Tyler, was your standalone policy generated in a prior version to 5.50 i.e. 5.40.x policy editor and you simply ugraded through from 5.40.x to the 5.50 versions or even just used the 5.40.x polciy on a 5.50.x client? If so, you'll need to uninstall and reinstall 5.50.8 and recreate a new stanalone policy in a 5.50.x policy editor.

    I can confirm that a policy generated in 5.50.0.116 policy editor works fine in 5.50.8 and I've also tested a challenge response on 5.50.0.116 policy editor from a locked out 5.50.8 client.

    Matt

    :9019
Unfiltered HTML