Adobe Reader 9.4.0
Hi, I've just downloaded this today. I signed up for distribution, but could only find and EXE file (27 MBs). I wanted an MSI for SCCM distribution, so extracted the files to another location. Unfortunately the MSI and CAB file amount to a total of 109MBs, which is larger than expected for my network distribution.
Has anyone else had a go at deploying this yet, and have they found the same file sizes?
Has anyone else had a go at deploying this yet, and have they found the same file sizes?
0 Comments
[ + ] Show comments
Answers (11)
Please log in to answer
Posted by:
nheim
14 years ago
Posted by:
timread
14 years ago
I guess we can thank Adobe for releasing a full installer for 9.4.0 this time! A qualified thanks, though - why don't they put the enterprise MSI up on the Enterprise deployment page too?!
Apologies for thread hijacking - Like donaghs, I started by downloading the Full EXE installer from the Enterprise Distribution page, ready to extract the MSI from it. Thanks for the direct link to the enterprise MSI Nick, very useful.
However I thought I'd share my experience from that point onwards, in the hope it will help some folks.
I created an AIP from the enterprise MSI Nick linked above (msiexec /a AdbeRdr940_en_US.msi), but when running the Adobe Customization Wizard 9.0.0 against the AIP to customize it for our enterprise deployment, it prompted that it could not find the Setup.ini file - and would not create the customized package. It doesn't look like the AIP was created properly.
Next, I went back to the beginning and extracted the MSI from the EXE the 'old fashioned' way - by running 'AdbeRdr940_en_US.exe -nos_o"Reader940" -nos_ne'. This created a better looking MSI source that I am able to run the Adobe Customization Wizard against.
Question is - is this the 'best' working method? Am I way off base here? It was fairly painful to work through all this. I'd be interested in other's experiences.
Apologies for thread hijacking - Like donaghs, I started by downloading the Full EXE installer from the Enterprise Distribution page, ready to extract the MSI from it. Thanks for the direct link to the enterprise MSI Nick, very useful.
However I thought I'd share my experience from that point onwards, in the hope it will help some folks.
I created an AIP from the enterprise MSI Nick linked above (msiexec /a AdbeRdr940_en_US.msi), but when running the Adobe Customization Wizard 9.0.0 against the AIP to customize it for our enterprise deployment, it prompted that it could not find the Setup.ini file - and would not create the customized package. It doesn't look like the AIP was created properly.
Next, I went back to the beginning and extracted the MSI from the EXE the 'old fashioned' way - by running 'AdbeRdr940_en_US.exe -nos_o"Reader940" -nos_ne'. This created a better looking MSI source that I am able to run the Adobe Customization Wizard against.
Question is - is this the 'best' working method? Am I way off base here? It was fairly painful to work through all this. I'd be interested in other's experiences.
Posted by:
Swipe
14 years ago
Posted by:
cgiles
14 years ago
Am I the only one who can't get the MST file created with the Customization Wizard to work with the MSI? I can open the MST file in the Wizard and see all of my changes but it installs with the defaults.
msiexec /i "msi location" /t "mst location"
I've done it this way with past versions of Reader, up until now.
msiexec /i "msi location" /t "mst location"
I've done it this way with past versions of Reader, up until now.
Posted by:
anonymous_9363
14 years ago
The '/T' is designed for use when advertising packages. For installing, you need to use the TRANSFORMS property.See TechNet for details.
Posted by:
nheim
14 years ago
Hi Tim,
just do it one time the suggested way from Adobe.
They use a few additional files with the CIW (setup.ini, amongst others).
Afterward, you can use the resulting transform for all later versions.
You don't need an expanded AIP for a corporate install.
Most of the time it's better to use an MSI with compressed files.
They use far less bandwidth on a mass deployment.
Regards, Nick
just do it one time the suggested way from Adobe.
They use a few additional files with the CIW (setup.ini, amongst others).
Afterward, you can use the resulting transform for all later versions.
You don't need an expanded AIP for a corporate install.
Most of the time it's better to use an MSI with compressed files.
They use far less bandwidth on a mass deployment.
Regards, Nick
Posted by:
deranjer
14 years ago
FYI, you should technically apply for the enterprise license from Adobe so you have the right to redistribute the msi installer...
http://www.adobe.com/products/reader/rdr_distribution1.html
http://www.adobe.com/products/reader/rdr_distribution1.html
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.