This is all rubbish. If PGP works a file system filter driver (Microsoft's API for AV etc for hooking into disk read/writes) then either PGP is corrupting the files (unlikely since you never had this problem before), or some other FSF driver is causing the problem (again unlikely, since you've never had this problem before), or something else is causing the problem. Other than outsourced Exchange, what else has changed?
Cheers Ken -----Original Message----- From: David Lum [mailto:[email protected]] Sent: Saturday, 1 October 2011 2:45 AM To: NT System Admin Issues Subject: RE: Outsourcing Exchange We have talked about Bitlocker, but there's no guarantee that will be any better. Heck our Exchange provider didn't know PGP was an issue, and 'll bet PGP is more prevalent than Bitlocker. We're being steered to Win7/Office 2010/Remove PGP as all being needed to help resolve these issues. At 500 employees at least 450 are on XP / Office 2007 and 300+ have PGP on them. The Win7/2010 end state is desirable, it's the compressed timeframe that isn't. Dave ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
