Users are asked for admin password why?

[ball@adobeforums.com]

Hi,

I have about 250 computers with reader 6 installed, I wanted to push Reader 7 out but when a normal user(NonAdmin) launches it they are asked for the admin username and password.

What all locations does Reader 7 install too? I pushed out the Reader 7 folder in Applications and also Safari since it installed items there but its still asking....what else do I have to push out for this to run?

Also with Acrobat 7 I installed it on two new iMacs we got in and ran it as admin because of the problem above and it has ran fine for normal users until yesterday....they were being asked again for the admin username and password. Nothing has changed don't understand what happened....I don't wanna have the same thing happen with Reader 7 on 250 computers!

Any ideas on what gets installed and what locations the items are installed to for Reader 7? I would like to create a package and use ARD 2 to install it to my clients computers. ADOBE SHOULD BE MAKING PACKAGES INSTEAD OF CUSTOM INSTALLERS!!

Thanks,

Dan

[MikeKazlow@adobeforums.com]

When the package is first run, Reader is install software it needs to
run. Before any program can install files elsewhere it needs permission
to do so. Alas, I do not know what these programs/files are.

Mike

[MarkATS@adobeforums.com]

"By following these instructions, you accept the terms of the EULA on behalf
of your organization, represent that your organization has explicitly
granted you authority to do so, and agree that your organization will be
bound by its terms and conditions."

There are several files and/or folders that Reader is trying to install
the first time it runs. Some of these are in the user domain, but
others are in the machine domain and need authentication.

The solution involves pre-copying the particular files that Reader
would want to copy: specifically, the ones in the machine domain.
Reader will still finish its installation when the non-admin user first
runs it, but will find that it doesn't have to change anything in the
machine domain, so will not ask for authentication.

There are several constraints, though:

(1) Reader has to be installed in the same place on every machine: the
name of the volume it's installed on, and the path to the application,
has to be identical. This is because one of the files in the machine
domain includes a path to Reader.

(2) Before the user can see PDFs in Safari with Reader, they will need
to launch Reader once (outside of the browser) and accept the End-User
License Agreement.

The best way to make sure the correct files are in the correct place is
to use a staging machine that is identical to the users' machines, and
install and launch Reader once (and I recommend subsequently opening a
PDF in Safari to verify that it's installed correctly on the staging
machine).

Then collect the following files/folders from that staging machine, and
create a script (for use in Remote Desktop) that copies these files to
the same locations on the users' machines:

/Library/CFMSupport/eb1drv
/Library/Internet Plug-ins/AdobePDFViewer.plugin
/Library/Preferences/com.adobe.acrobat.pdfviewer.plist (has a path to
Reader in it)
/Applications/Safari.app/Contents/Frameworks (the entire folder)

You will also need to make sure the following folders exist on the
users' machine, and have permissions 777 (owner and group can be
whatever you want). If you have previously installed Adobe
applications, they probably already exist and are non-empty, you only
need to insist on those permission; if they don't exist, just create
them empty. It doesn't matter what's in them:

/Library/Application Support/Adobe
/Library/Application Support/Adobe/TypeSpt
/Library/Application Support/Adobe/Color

Once the above files and folders are copied/created/verified, Reader
should be able to launch on the user's machine. Remember that it needs
to launch once *outside* Safari -- and the EULA be accepted -- before
PDFs can be read inside Safari.