Skip to main content
Participant
April 20, 2009
Question

Acrobat reader distribution

  • April 20, 2009
  • 4 replies
  • 6960 views

I wish to avoid having the 11000 pc's in my organization going out on the internet to get acrobat reader updates?  Is there any way of creating a distribution point for acrobat reader updates within my organization that would operate in a similar manner to Microsoft's Software Update Server (WSUS), whereby all pc's would look to a local server within my organization for updates instead of going out to Adobe servers on the internet?

Any help would be appreciated.

Thank you.

This topic has been closed for replies.

4 replies

Participant
March 2, 2016

If you use SCCM for windows updates, you can use SCUP to import the adobe updates and distribute them using the same method.

AVA-Huep
Participating Frequently
March 2, 2016

Dear essaym,

I did it

As a part of a deployment system that can install and update silently a consistent number of programs over n PCs running Windows, I have been able to do what you are asking for Adobe Reader XI, Adobe Reader DC, Acrobat XI Standard and Pro, Acrobat DC.

This deployment system:

  • is totally independent from WSUS, SMS, SCCM or whatever you might have
  • compared to WSUS (where the user must interact to install updates), happens in a totally silent manner
  • does not require any additional server or service
  • can be implemented in domain or workgroup as per your preferences
  • has been testing in my system since 3 years now (85 clients at the moment)
  • works fine on Win7, 8, 8.1, 10 32&64 bit.

Additionally the upscaling limit to 11000 pc would also not be a problem, as the whole deployment system has been designed not to have limits with the number of PCs from the very beginning.

If the topic is still interesting for you, feel free to contact me.

Participant
June 1, 2009

There is a way to create an admin install of Reader and then apply the patches to the admin install.  Each time you apply a patch to the admin install you run a commandline to update the client installations.

admin install command:  msiexec /a "<path to admin install>\AcroRead.msi" (run once)

This will extract the files and place them on a network share

patch command:  msiexec /a "<path to admin install>\AcroRead.msi" /p "<path>\AcroRead.msp" (run once for each msp file)

This will integrate the patch into the installation            

update client command:  msiexec /fvomus "<path to admin install>\AcroRead.msi" (run on each client to update the installation with the latest patch)

this will update the client with any new patches

Once the admin install is updated to the latest patch you can use this link to customize the install with a transform: http://blog.stealthpuppy.com/deployment/deploying-adobe-reader-9-for-windows

- or -

You could also for example install the base 9.0 bits and download patches from here:

http://www.adobe.com/support/downloads/product.jsp?product=10&platform=Windows

I believe these type of MSP files can be deployed with WSUS.  I have not tried it but here is a reference URL: http://www.microsoft.com/technet/scriptcenter/scripts/sus/server/default.mspx?mfr=true

Mike

essaymAuthor
Participant
June 2, 2009

Hi,

Thank you for the information. I'll take a look at the WSUS method and hopefully give some feedback on the Adobe forum.

Thanks

Riaz Essay

University of KwaZulu-Natal

Information & Communication Technology

Technical Services Section

Durban

South Africa

Tel: +27 31 2601522 / 2477

Fax: +27 31 2602125

E-mail: essaym@ukzn.ac.za

>>> mikeniccum <forums@adobe.com> 6/1/2009 8:02 PM >>>

There is a way to create an admin install of Reader and then apply the patches to the admin install. Each time you apply a patch to the admin install you run a commandline to update the client installations.

admin install command: msiexec /a "<path to admin install>\AcroRead.msi" (run once)

This will extract the files and place them on a network share

patch command: msiexec /a "<path to admin install>\AcroRead.msi" /p "<path>\AcroRead.msp" (run once for each msp file)

This will integrate the patch into the installation

update client command: msiexec /fvomus "<path to admin install>\AcroRead.msi" (run on each client to update the installation with the latest patch)

this will update the client with any new patches

Once the admin install is updated to the latest patch you can use this link to customize the install with a transform: http://blog.stealthpuppy.com/deployment/deploying-adobe-reader-9-for-windows

- or -

You could also for example install the base 9.0 bits and download patches from here:

http://www.adobe.com/support/downloads/product.jsp?product=10&platform=Windows

I believe these type of MSP files can be deployed with WSUS. I have not tried it but here is a reference URL: http://www.microsoft.com/technet/scriptcenter/scripts/sus/server/default.mspx?mfr=true

Mike

Participant
May 20, 2009

Do you have SMS 2003, or SCCM 2007?

If you do you can distribute the reader that way.

Set up a folder on your distrobution point for example 8.1.3 full install or 9.1.1 full install, customize the package to your liking using the cutomization wizard 8 or 9 for example turn off the updater supress and accept eula's ect. Create a package, then an advertisement.

If not I do not think you can use wsus for this application.