We are piloting VSE 8.8 and we are getting the buffer overflow problem with Acrord32.exe. We did have the hotfix 613017 for vse 8.7 which worked. But we are now getting the buffer overflow error when using 8.8.
Is there any work around for this ? we have Acrord32.exe sent within the Bufferflow Overflow Protection policy but we are still getting the pop up when loading Acrord32.exe.
Have you looked for other culprits? On a XP test machine of mine, the exemption using 8.8 Prod works fine.
The settings I have:
Process Name: acrord32.exe
Other two options left blank.
We are running into the same problem. What I have found is that when the exception is first added, it works for 30 minutes or so. Later, if you try to run Reader X (10.0.1), Protected Mode will not run again. If you open the VirusScan Console, view the Properties of Buffer Overflow Protection where the exceptions are list, Reader X will then start opening in Protected Mode. This will work a short time before the problem returns.
Are you sure that's the problem? 10.0.1 doesn't require a BOP exemption to work correctly. There are other causes for the protected mode not working though.
As said in the other thread, there is a problem with how the ePO policies are applied for BOP exclusions.
When you open the properties & then it works for 30mins or so, this is because you are then correctly applying the exclusions locally... At the next agent policy enforcement, the 'broken' settings are written to the registry again & hence you get problems.
In saying that though.... 10.0.1 is working OK for me (and our 300 or so systems) sofar.
Then how are you making it work? I have tried both Acrord32.exe and "C:\Program Files\Reader 10.0\Reader\Acrord32.exe" as BOP exception via ePo, individually and together with the same result (it works if I look at the exception on the local machine, but as soon as ePo updated, it stops working again). I have tried leaving the exceptions empty in ePo and manually inputting the exception on the local client; again it works at first, but as soon as ePo updates, the exceptions are removed.
What version of Windows are you using? Our environment is Windows XP SP3 & Win7 Enterprise x64 based.
(though the Win7 x64 machines were never affected as VSE doesn't have BOP for 64bit platforms)