I did nothing to test the disks, just deployed.  I have ~40 notebooks and 6
desktops.
If something had come up, I would've given a loaner to a user, fixed the
problem and moved on.

On Tue, Feb 23, 2010 at 4:43 PM, David Lum <[email protected]> wrote:

>  So I’ve demo’d PGP and reading their documentation ran across this: ” PGP
> Corporation deliberately takes a conservative stance when encrypting drives,
> to prevent loss of data. It is not uncommon to encounter Cyclic Redundancy
> Check (CRC) errors while encrypting a hard disk. If PGP WDE encounters a
> hard drive or partition with bad sectors, PGP WDE will, by default, pause
> the encryption process. This pause allows you to remedy the problem before
> continuing with the encryption process, thus avoiding potential disk
> corruption and lost data. To avoid disruption during encryption, PGP
> Corporation recommends that you start with a healthy disk by correcting any
> disk errors prior to encrypting. &#1048697;
>
>
>
> Before you attempt to use PGP WDE, use a third-party scan disk utility that
> has the ability to perform a low-level integrity check and repair any
> inconsistencies with the drive that could lead to CRC errors. *****Microsoft
> Windows' check disk (chkdsk.exe) utility is not sufficient for detecting
> these issues on the target hard drive*** *(emphasis mine). Instead, use
> software such as SpinRite or Norton Disk DoctorTM. These software
> applications can correct errors that would otherwise disrupt encryption
>
>
>
> What would you guys recommend? I have 260 laptops to encrypt, dozens of
> them not even in the same state I am in. Initially I was thinking CHKDSK /R
> but PGP says that is insufficient…
>
> *David Lum** **// *SYSTEMS ENGINEER
> NORTHWEST EVALUATION ASSOCIATION
> (Desk) 971.222.1025 *// *(Cell) 503.267.9764
>
>
>
>
>
>
>
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to