Regarding the updates, they may have, or not, given the possibility to external machines to connect to their server (this is not common, but not impossible). So the options available depend on how the company owning that SEMS has configured the network environment and the encryption policy. It is hard to say, because if I understand it well, this SED client is managed by a Symantec Encryption Management Server (SEMS).
#FOLDER2ISO 3.1 NOT WORKING PASSWORD#
Last question: If I use Symantec Recovery Disk to decrypt my harddrive, will my username and password be sufficient? I no longer have technical support from the organization that originally encrypted the disk, and I'm worried that only the original admin password might allow the decryption. What I'm trying to say is this: If auto-updates for PGP were on, were they also on for SED? And if that's the case, shouldn't I be running 10.3.1.x? (Not 10.3.0.x)
#FOLDER2ISO 3.1 NOT WORKING UPDATE#
The upshot: The update happened a little over one year ago, which makes sense because it aligns with the publish dates on Symantec's release notification webpages for new versions of SED.
I remember because when I restarted and a different log-in screen appeared, I freaked out - SED requires you to type your log-in name and password (not just password like PGP), and at first I couldn't remember my log-in name (luckily, I did). And! I remember the moment my system updated form PGP Desktop (9.x?) to SED (10.x). I remember running PGP Desktop (presumably version 9) before my computer updated to SED. So my next question is: how does automatic update work for SED? I had also thought about building a WinPE with Hiren's (good idea!), but alas, again, I can't copy the files necessary to unlock the harddrive with a boot disk because I do not have those files. Unfortunately, I do not have access to another machine running SED. I was pretty sure my version was one of these because the log-in screen says SED. It is good to know that my version is either 10.3.0.x or 10.3.1.x.
0 kommentar(er)
