Deploying Adobe Reader 11.0.4 via SCCM 2012

[Guest]

Hello members,

I am looking to deploy the latest version of Reader to our workstations both during OS build and also on existing machines.

I have successfully created a custom install using the Adobe Customization Wizard I’m leaning towards the use of the .exe / bootstrapper

Double clicking the exe works just fine on my lab computers however getting this to work over a SCCM (2012) deployment is proving troublesome

As SCCM admins would know the SCCM client downloads the content to C:\windows\ccmcache\randomfoldername

SCCM then runs the command specified in the deployment you created, I appear to be having issues with the exe not knowing to look in the same directory for the MST MSP and setup.ini file,Being a randomly generating folder name this can’t be specified in the deployment unless I change the ‘Installation start in’ option

Sometimes the install is ignoring my custom install settings (disable updates and online features etc)

My setup.ini contains:

[Startup]

RequireMSI=3.0

CmdLine=/sall /rs

[Product]

msi=AcroRead.msi

PATCH=AdbeRdrUpd11004.msp

CmdLine=TRANSFORMS="CompanyName.mst"

[MSI Updater]

Path=http://ardownload.adobe.com/pub/adobe/reader/win/8.x/8.0/misc/WindowsInstaller-KB893803-v2-x86.exe

Am I missing something simple ?

[SubratoNamata]

You have done all the things right. I don't see any issues in your deployment. You say that sometimes your custom transforms are getting applied to some of the machines but not always.

Which makes me believe that that the Reader 11.0.04 installers are working as expected. I guess, It's the deployment and the distribution of packages which is causing this intermittent issue.

WHat i understand is that, while applying the setup.exe, it's somehow ignoring to apply the custom mst by not reading the setup.ini file

My suggestions,

1. Cleanup your existing package and deployment related to Reader 11.0.04

2. Recreate package and deplyment related to Reader 11.0.04 using some other folder

3. If you are not cleaning up your existing package and deployments. Ensure you have the transform file and setup.ini file in the same folder as the package folder (where it contains setup.exe and other necessary files)

and then update distribution points

4. Make the source directory shared

[Guest]

Thanks for the tips I agree it does sound more like a SCCM / content issue -

I was also interested to hear what people are using I have experimented with the MSI + MSP install using the msiexec command but I found the bootstrapper to be easier to work with

[GCrookshanks]

Here's what my vendor told us to do regarding Adobe Reader.  We have a batch file that contains the following...

***Batch file contents begins***

REM This will install Adobe Reader 11.0.0

msiexec /i "%~dp0AcroRead.msi" TRANSFORMS="%~dp0TEICustom.mst" /qn

REM This will install the 11.0.4 MSP Update file

msiexec /update "%~dp0AdbeRdrUpd11004.msp" /qn

***Batch file contents ends***

Obviously the AcroReader.msi and AdbeRdrUpd11004.msp files reside in the same folder as the Reader.bat file.  In addition, we also have a custom.mst file that alters the settings of Adobe Reader 11.

Hope this helps!

[EnterpriseHelp]

cmd line docs: http://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/cmdline.html

hth,

Ben