We manage hundreds of Macs of which most are at 10.4.8.

We have both Acrobat Pro and Reader 7.0.8 installed on all Macs.

Sometime within the last few weeks something has changed on our systems (eg: upgrading from something under 10.4.8 to 10.4.8 ) that is causing Acrobat Pro and Reader to fight for the Safari.app/Contents/Frameworks/ folder. This folder contains aliases to either Pro or Reader frameworks within that Acrobat app's own frameworks folder (...Acrobat Pro.app/Contents/Frameworks/ )
This issue is that the end user is prompted to authenticate for either Reader or Pro to "repair itself" which it is just changing the aliases within the Safari Frameworks folder to point to their own frameworks.

If I set Preview as the default pdf viewer and then delete Acrobat Reader so that only Preview and Acrobat Pro are on the client, then it seems to work beautifully without authentication request. We would like to keep Reader on the systems though. We use Sassafras' Keyserver with a limited number of licenses for Acrobat Pro.

Has anyone else experienced this? Found a solution, etc?

Thanks!