We are currently rolling out SEE v11.0.1MP1 to our enterprise. We have a few machines that have created incident tickets in which the encryption process paused at various completion percentagages. A few were resolved by using the CLI command after running Chkdsk (fix errors), however we have had a few in which this did not work and we could not resume the process.
Is there a documented process or solution for this issue? What is the recommended procedure to remediate the problem and get the disk encrypted completely?
Most probaly the hard disk is going fail. Decrypt and backup all the file. Then encrypt again, but please remember that is good to keep a backup as the hard disk may fail any time.
When the encryption process hangs or pauses it is beacause it found a bad sector. The follow steps are recommended to get past the bad sector.
Run decrypt command from the Symantec Endpoint Encryption Management Server (SEEMS)
Run checkdisk with the following switches: /f /R
Run defrag on the device
Re-encrypt the device
if re-encrypt fails go to next step
Re-install and re-encrypt the device
Replace hard drive or device
Do not waste your time on the Decrypting ---------
Open up the Windows Event Logs --- in the Application Logs ----
Both Symantec Endpoijnt Encryption and Whole Disk Encryption will write a log for the failure reason ------
Typically BAD sectors or Blocks on disk --- too many and it will pause and stop encrypting.
Best best scrap the device ---- by doing a full reformat of the drvie and re-image --------
If it the drive is in use have the user move all critical files to a share ------ and re-image.