I'm just an end user as part of a company that uses EEP v5.1. Recently got a BSOD and rebooted to the following error:
"endpoint encyrption error: 0xe0050001
Endpoint Encryption for Pc is not installed"
My net research seems to indicate that I may have a corrupt MBR and would need to recover it via tools that I don't have access to such as Safeboot and Wintech. My IT department basically states that all they can support is a re-image. I dont want to do that and want to see if there's anything that can be done to recover my data. Other thoughts:
1. Is there another way to restore my MBR?
2. Can I connect this current hard drive to another system that has encryption enabled to decrypt my original content?
3. If I were to acquire Safeboot would that even help me out? Seems I'd need more keys,etc, that would be only accessible by managed service customers.
4. Any ideas on what I can do?
While I'm here, I thought I'd ask something else. My company claims they got a special build that doesn't support the ability to use Wintech or Safeboot utilities. Are they giving me a bunch of lies or would they really pigeon hole us like that?
Secondly, is it possible to get support from McAfee as an enduser to obtain things like Safeboot, Wintech, and the daily token?
Thanks for your understanding and time.
to get support from McAfee you must have GRANT CODE, if yes than you can get support from McAfee.
and to recover data you will require Safetech and/or wintech (which is not big deal)
but you must require the SDB file (the key) from EEM center. without this you can not perform Safetech and wintech procedure.
The .sdb file sounds like the only thing I'll be unable to really acquire. I'm not familiar with the EEM center. Is this a file that resides on an encrypted system? For instance, if I were to reimage another machine with the same EEP package, could I then locate this .sdb file? Or is it something that is generated elsewhere?
Thanks for understanding. I wish I could just hand this to IT to figure it out, but it sounds like this is something they don't want to support. Too bad, as the actual procedure sounds very straightforward and simple given the developed tools!
EEM is the console where the Safeboot is centrally managed and all encryption and other information stored on the server. Here i am talking about Manage Safeboot. IT people must have recovery key.
Thanks. Despite how terrible it sounds, I suspect my company will not have this information.
If this is the case, do I really have any other options or is the data gone for good? Is it possible to copy the encrypted data or slave the disk onto another system working system utilizing the same EEP package?
slaving the drive where same package installed will not help as every time it generates unique encryption key.
As per I know without key recovery is not possible.Message was edited by: Ram Dudani on 12/8/10 12:28:04 AM CST
I'm assuming there's no basic way of simply fixing the MBR? No, i don't have a backup. I figure if that was straightened out, everything else would fall into place.
No, as here you require SBR (not MBR) and Safeboot Boot records for this machine can be only restored with SDB file (in some case Hp recovery key)