Allowing staff to update Adobe Reader...?

[Kyle]

When logged onto the network the staff are locked down and have hardly any access to the c:drive. The problem i have is when things like Adobe Reader has an update. While on the network the updater pop up telling them they have an update butof course they have no permission to install?


Is there a simple way of getting round this without changing to many permissions. ie could i just give the staff (via GPO) permission to the c:\program files\adobe\ folder?

[Michael]

You could push out the latest Adobe Reader 8.1.2 MSI, which of course would overwrite the existing Adobe version your users have.

To do this, download Adobe Acrobat 8.1.2 to the root of your C:\ drive.

Now go to Start > Run and copy:

"C:\AdbeRdr812_en_US.exe" -nos_ne

You'll see the Adobe Setup appear with a progress bar, then disappear.

Now go to Start > Run and copy:

%temp%

They'll be a folder called Adobe Reader 8. Copy all the contents to a share, then distribute using Active Directory on a machine basis.

[pmassingham]

If it is an msi, just run an admin install using msiexec, e.g.

msiexec /a"\\servxxx\makemsi$\AdbeRdr812_en_US.exe"

then roll out as a software package to the relevant OUs.

[strawberry]

sorry to append to the chaps above, to install adobe you'll beed a license, its free, but you have to apply for it, once you've got it they give you the msi's.

[OverWorked]

Adobe supply the Adobe Customization Wizard for free. CustWiz.exe. Search their website for it. It allows you to create an mst for any Adobe product (I think). As strawberry said, you may have to register for the free redistribution license for it.

It's a while since I dabbled with it, but it'll probably allow you to create an mst to disable the auto update. You'd have to redeploy Adobe Reader with the new mst.

I created an mst for Adobe Reader just to remove the desktop shortcut.

Just deploy the msi via GPO with the mst you've created.

[TekkyMatt]

I've found that if you just remove the folder
C:\Program Files\Common Files\Adobe\Updater5
either via a script at startup or whatever your tipple, the updater will never bother you again

[Kyle]

I've found that if you just remove the folder
C:\Program Files\Common Files\Adobe\Updater5
either via a script at startup or whatever your tipple, the updater will never bother you again

Has anyone else tried this option

[Michael]

I haven't removed C:\Program Files\Common Files\Adobe\Updater5. There are good reasons to update to Adobe Reader 8.1.2 as it apparently contains fixes against vulnerabilities found with it.

[Kyle]

But for us, when staff are logged onto the network they have no access to the c: drive so can't update. I would rather manage the updates myself via GPO deployments.

[Geoff]

We using the customisation wizard, as mentioned above, combined with GPO deployments. The users are not nagged about updates.

[Michael]

You can distribute Adobe Reader under Computer Configuration instead of User Configuration. Of course you can only assign and not publish, but it will install and overwrite existing versions of Adobe Reader you have installed (which is what you want).

Just make sure your computer objects are under the OU where you wish to distribute Adobe Reader:

rootOU - CurriculumOU
subOU - Pupils
subOU - Workstations etc...

[fooby]

there is also the ability to grant full access to the program files\adobe folder through a group policy, although this may not help.

computer configuration\security

the installer / updater may need full local admin access.