![]() IP 10:47:26 Setting logging level to: normal (Sanitized copy of the log.) *A 10:47:26 - Encryption Desktop started. After restarting pgptray and reviewing the log, the log level is still 'normal' versus '0x3FFFF'. ![]() The change doesn't seem to be taking affect. successfully create the dword and string values.successfully create the 'Debug' registry key.I leveraged a script I created a while back to enable debug logging, and while it works to: I checked the pgplog.txt in “%appdata%\PGP Corporation\PGP\” but didn’t see anything interesting in there. I’m seeing a good number of non-successful results like ‘BUFFER OVERFLOW’ and ‘FILE LOCKED WITH ONLY READER’ in procmon so I need to dive deeper. somewhere in the mdidle pgptray.exe is also launched.runs for at most 2 seconds before terminating.I haven’t finished analyzing the procmon results but: I tried your suggestion and things have taken a dive slightly: When I launch SED, I’m not receiving the prompt but SED is also not loading. I had half a dozen other people test the upgrade with both similar and different hardware and they’re all reporting the same. This is not unique to this account or this computer.Installing the new version of PGP on a freshly imaged machine works fine.Installing the current production version of PGP on a freshly imaged machine works fine.I can also add new users, create a PGP zip so it seems to be working. This same account was working fine up until the upgrade.Īfter the upgrade, the machine was still encrypted, I’m still prompted for credentials on boot, single sign-on works.This is a normal user account that has historically reliably worked.Some more information in response to your query: Is this a benign error or an indicator of a potentially larger issue? (What's really scary is that after reinstalling, they had to re-encrypt their drive and they swore up & down it was fully encrypted prior to the upgrade.) (e.g.: encrypting new disks, decrypting, adding/removing users, updating passphrases, new pgp zip etc.).Īside from that, one persons' machine was suddenly no longer prompting for credentials on boot after the upgrade requring them to uninstall & reinstall PGP. no one is doing much testing in the SED application.no one's updated their password to confirm SSO works.While the upgrade process largely works everyone has the same problem (per-se) when launching the Symantec Encryption Desktop after the upgrade:īoth the SED application and the encryption process as a whole appears to be functional, although admittedly: I'm simply doing a normal silent install, passing a single PGP parameter: PGP_INSTALL_DISABLESSOENROLL=0 I have no insight into how that MSI was created and what properties have been set. Our security team recenlty stood up a new Symantec Encryption Management Server and handed me an MSI to upgrade our existing Windows 7 SP1 Enterprise 圆4 clients from 10.3.0 Build 9060 to 10.3.2 MP9 Build 16620.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |