- #Symantec encryption desktop 10.3.2 build 16620 how to#
- #Symantec encryption desktop 10.3.2 build 16620 drivers#
- #Symantec encryption desktop 10.3.2 build 16620 upgrade#
- #Symantec encryption desktop 10.3.2 build 16620 full#
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.)
![symantec encryption desktop 10.3.2 build 16620 symantec encryption desktop 10.3.2 build 16620](https://rest.kb.iu.edu/image/a091n.png)
#Symantec encryption desktop 10.3.2 build 16620 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.
#Symantec encryption desktop 10.3.2 build 16620 full#
Recently, I’ve had a few customers who use full disk encryption from Symantec (Symantec PGP, Symantec Endpoint Encryption, or Symantec Desktop Encryption) on client computers instead of Microsoft BitLocker.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. “Why?”… well… it’s most likely that they have a really good Symantec sales rep. Either that or they implemented prior to BitLocker being ready for prime time and never bothered to change the solution. And yes, I prefer the Microsoft solution for its ease of management and integration points. The most recent customer was running Windows 7 with Symantec Desktop Encryption (complete with the server component for management) for full disk encryption. Their goal was to upgrade all Windows 7 clients to Windows 10 (Current Branch) without decrypting the volume, if possible. They also use SCCM for endpoint management, software deployment and OSD. Our solution needs to leverage SCCM and an In-Place Upgrade Task Sequence.
#Symantec encryption desktop 10.3.2 build 16620 how to#
To achieve the goal, we have some options available to us (there may be more than I’ve listed here, but you get it): How to update symantec encryption desktop 10.3.2 to 10.4.1 upgrade# Nuke and Pave (treat it like bare metal or replacement scenario).Capture user files and data to a network location (USMT).Delete all partitions on the physical disk.Restore user files and data from network location (USMT).
#Symantec encryption desktop 10.3.2 build 16620 drivers#
Include the encryption drivers by modifying the setup command-line.Leverage the “/ReflectDrivers” command-line option.Use a varying combinations of the above options.A healthy and functional Configuration Manager Hierarchy.ĭecryption takes waaayyyy too long, and isn’t a valid option with the requirements given by the customer.īased upon the customer requirements and the options chosen, we will need the following items to build our solution.Symanted Encryption Server didn’t have an option to suspend encryption.“Nuke and Pave” might take additional dev time to determine “What is user data?” for USMT to be right.Ultimately, we chose option F (a combination of options B and E).
![symantec encryption desktop 10.3.2 build 16620 symantec encryption desktop 10.3.2 build 16620](https://3.bp.blogspot.com/-6Mdm3o3vGEA/VWL7oILgeoI/AAAAAAAAIsE/_CAvAlZUSOo/s1600/icon320x320.png)
![symantec encryption desktop 10.3.2 build 16620 symantec encryption desktop 10.3.2 build 16620](https://it.ucsf.edu/sites/it.ucsf.edu/files/6.confirm.png)
$FSO = New-Object -ComObject Scripting.FileSystemObject $PGPDest = “$( $env:SystemDrive) PGPTemp” $PGPSrc = “$( $env:windir) System32drivers” How to update symantec encryption desktop 10.3.2 to 10.4.1 drivers#