#BYPASS SYMANTEC ENCRYPTION DESKTOP UPGRADE#
#BYPASS SYMANTEC ENCRYPTION DESKTOP WINDOWS 10#
#BYPASS SYMANTEC ENCRYPTION DESKTOP ZIP#

We are considering the Bypass approach where checks will be conducted on the laptops to know whether PGP encryption is present or not and then based on this condition execute the bypass script. Its either the Task Sequence doesn’t continue until a user manually logs in or fails completely because the deployment kept referencing the PGP encryption key bases during the process.

#BYPASS SYMANTEC ENCRYPTION DESKTOP UPGRADE#

We have tried to deinstall PGP > run in place upgrade > reinstall PGP during a test deployment on sample laptops but that seem to have failed during the process. Some of the Laptops which required this upgrade have PGP encryption installed on them. We have designed an SCCM2012 task sequence which performs an upgrade from Windows WIN 7 and/or older versions of 10 to Win 10 1803. I’m looking for something that works the same way for Encryption Management Server, with the added recovery key for backup purposes. If I create a share on a server and restrict it to members of “My Group” then as long as the user is a member of that group, they can access it.

In terms of describing what I’m looking for – it’s similar to the way Active Directory works. We’d also like for a recovery key to be included in the event that Users A, B, C, and D all leave the company so that we can still decrypt the file.Įven better would be if we could add users, for example “User E”, after the fact and that person can open the PGP Zips encrypted to the group as long as they are a member of the group.

#BYPASS SYMANTEC ENCRYPTION DESKTOP ZIP#

If we implement EMS, we’d like our keys to be centrally managed by the key server AND we would like the ability to encrypt to a group (could be verified by the key server).įor example, if “User A” encrypts a PGP Zip file, we’d like to be able to encrypt it to a group that would consist of (for example) “User B”, “User C”, “User D” using their individual, personal keys. Right now, we manage our PGP keys manually, by sharing the key files amongst the team, and we encrypt the PGP Zip files using these keys. My team uses the Symantec Encryption Desktop application for creating PGP Zip files. Details on EOS can be found here.I’m looking for clarification on if the Symantec Encryption Management Server can do what I’m hoping it can do. Since SED 10.4.2 had reached EOS, I needed to have the SED encryption server to be upgraded to 10.5.

#BYPASS SYMANTEC ENCRYPTION DESKTOP WINDOWS 10#

This got me looking into SED and that is when I learnt that SED needed to be upgraded to version 10.4.2 and later to allow automated In-place upgrade of Windows 10 OS to take place. After analysing the setupact, setuperr, diagerr.xml logs I could see some references to WRITE action being blocked against certain sections of the DISK. The resultant behavior was that the OS would just rollback after the first reboot. It took me some man hours to identify that SED needed to be upgraded because Windows 10 20H2 setup did not flag SED as a blocker during comaptibility scans or even during the upgrade. However, with 3rd party security solutions, one will need to check for compatibility. Now, Microsoft security solutions like Defender, Bitlocker are natively compatible with newer Windows 10 OS versions and support In-place upgrades out of the box. Recently I worked on a project that involved upgrading Windows 10 OS version to 20H2 on devices encrypted by Symantec Encryption Desktop.

Bypass symantec encryption desktop