SafeGuard Disk Encryption - Error 00000052

Hello FK,

this is not a solution, rather some a recount of issues experienced and remarks based on findings with both the Beta and the productions version:

During the Beta I found that some errors "persisted". For example the client constantly returned an error for the installation started task - turned out that a previous run had failed and the client immediately reported the error at the start of the current run (although this then completed successfully). Another was that the client initially failed to send the machine keys but the error wasn't cleared when the subsequent attempt succeeded. I think all this has been corrected for the production release.

Nevertheless, from later tests it seems that errors "stay" longer than one would expect. I don't have a precise record but on one occasion I also had the Pending key issue, after removing it and running Protect again the error did not clear immediately. Didn't watch the client, but when I returned to it later I found the the install was complete and encryption had already started. Checking the console again the error had "disappeared" (perhaps the logic waits for a success from a later step).

When I "moved" one Beta client to the production server it started to display "Comparison failure" on the encryption policy. Moving it back did not resolve the issue. Re-protecting it with the production SDE client worked like a charm but did not resolve the issue. Thus eventually I uninstalled SDE (which needs some time as it has to decrypt the volume but is otherwise practically no effort) and the re-protected the client from SEC. This client also has a quite eventful history, at one point I more or less deliberately FUBARed the SDE kernel (details available on request by PM), recovered the volume (which was not encrypted though) with the PE disk and re-protected it with SDE. So it's quite robust.

SDE is intended to be simple and using it should not involve manually running the .msi. Uninstalling is, as said, not an effort, especially if it has not started encrypting or even completed the install (although it's not required I wouldn't use the client during the decryption though but even this would make the machine is unavailable for not more than half a day or so). From my experience the uninstall does a pretty good job of cleaning up.

I'd first try to run Protect from SEC again - it should not fail and maybe the client processes the policy as it should. If the client reports its status correctly but still refuses to comply with the policy then uninstall (both) SDE (components) and re-protect. It is supposed to work then. Won't fantasize about potential errors before you have tried :smileywink:

Christian

Hello FK,

this is not a solution, rather some a recount of issues experienced and remarks based on findings with both the Beta and the productions version:

During the Beta I found that some errors "persisted". For example the client constantly returned an error for the installation started task - turned out that a previous run had failed and the client immediately reported the error at the start of the current run (although this then completed successfully). Another was that the client initially failed to send the machine keys but the error wasn't cleared when the subsequent attempt succeeded. I think all this has been corrected for the production release.

Nevertheless, from later tests it seems that errors "stay" longer than one would expect. I don't have a precise record but on one occasion I also had the Pending key issue, after removing it and running Protect again the error did not clear immediately. Didn't watch the client, but when I returned to it later I found the the install was complete and encryption had already started. Checking the console again the error had "disappeared" (perhaps the logic waits for a success from a later step).

When I "moved" one Beta client to the production server it started to display "Comparison failure" on the encryption policy. Moving it back did not resolve the issue. Re-protecting it with the production SDE client worked like a charm but did not resolve the issue. Thus eventually I uninstalled SDE (which needs some time as it has to decrypt the volume but is otherwise practically no effort) and the re-protected the client from SEC. This client also has a quite eventful history, at one point I more or less deliberately FUBARed the SDE kernel (details available on request by PM), recovered the volume (which was not encrypted though) with the PE disk and re-protected it with SDE. So it's quite robust.

SDE is intended to be simple and using it should not involve manually running the .msi. Uninstalling is, as said, not an effort, especially if it has not started encrypting or even completed the install (although it's not required I wouldn't use the client during the decryption though but even this would make the machine is unavailable for not more than half a day or so). From my experience the uninstall does a pretty good job of cleaning up.

I'd first try to run Protect from SEC again - it should not fail and maybe the client processes the policy as it should. If the client reports its status correctly but still refuses to comply with the policy then uninstall (both) SDE (components) and re-protect. It is supposed to work then. Won't fantasize about potential errors before you have tried :smileywink:

Christian