Comments on: Adobe Reader 9.3.3 Deployment http://www.the-d-spot.org/wordpress/2010/07/07/adobe-reader-9-3-3-deployment/ Tickle your Deployment needs. Mon, 30 Jan 2012 13:31:44 +0000 hourly 1 http://wordpress.org/?v=3.1.3 By: The D-Spot (The Deployment Spot) » Adobe Reader X Deployment (specific language) http://www.the-d-spot.org/wordpress/2010/07/07/adobe-reader-9-3-3-deployment/comment-page-1/#comment-1645 The D-Spot (The Deployment Spot) » Adobe Reader X Deployment (specific language) Tue, 04 Jan 2011 15:15:38 +0000 http://www.the-d-spot.org/wordpress/?p=590#comment-1645 [...] Create two extra registry keys in the Registry-tab. The same keys as we created for Reader 9. [...] [...] Create two extra registry keys in the Registry-tab. The same keys as we created for Reader 9. [...]

]]> By: The D-Spot (The Deployment Spot) » Adobe Reader X Deployment http://www.the-d-spot.org/wordpress/2010/07/07/adobe-reader-9-3-3-deployment/comment-page-1/#comment-1526 The D-Spot (The Deployment Spot) » Adobe Reader X Deployment Thu, 23 Dec 2010 13:23:55 +0000 http://www.the-d-spot.org/wordpress/?p=590#comment-1526 [...] the new Reader! Here at the D-spot we blogged about deploying and slipstreaming Adobe Reader in previous posts. Time to update to version [...] [...] the new Reader! Here at the D-spot we blogged about deploying and slipstreaming Adobe Reader in previous posts. Time to update to version [...]

]]> By: demo http://www.the-d-spot.org/wordpress/2010/07/07/adobe-reader-9-3-3-deployment/comment-page-1/#comment-1492 demo Thu, 16 Dec 2010 13:37:43 +0000 http://www.the-d-spot.org/wordpress/?p=590#comment-1492 I wonder if there is no way to upgrade the production Adobe.Reader.X I wonder if there is no way to upgrade the production Adobe.Reader.X

]]> By: Ryan http://www.the-d-spot.org/wordpress/2010/07/07/adobe-reader-9-3-3-deployment/comment-page-1/#comment-1023 Ryan Fri, 08 Oct 2010 01:28:37 +0000 http://www.the-d-spot.org/wordpress/?p=590#comment-1023 Just an update. The transform was being applied. I'm no sure what happened but it took a reboot after the initial log in to Windows. I went to check the registry settings after a reboot and sure enough. I already knew that it takes a reboot for registry changes to apply thus the necessary reboot after installing a new program. BUT I swear to God that I had done that and it hadn't worked yet the EULA was being suppressed. So, in the case anyone else encounters this, just let them know to NOT run the Adobe Reader initially otherwise you will NOT get the wanted registry settings applied. So make sure you reboot at least once after the workbench has deployed your new Windows install. Just an update. The transform was being applied. I’m no sure what happened but it took a reboot after the initial log in to Windows. I went to check the registry settings after a reboot and sure enough. I already knew that it takes a reboot for registry changes to apply thus the necessary reboot after installing a new program. BUT I swear to God that I had done that and it hadn’t worked yet the EULA was being suppressed. So, in the case anyone else encounters this, just let them know to NOT run the Adobe Reader initially otherwise you will NOT get the wanted registry settings applied. So make sure you reboot at least once after the workbench has deployed your new Windows install.

]]> By: Ben De Vriese http://www.the-d-spot.org/wordpress/2010/07/07/adobe-reader-9-3-3-deployment/comment-page-1/#comment-1022 Ben De Vriese Thu, 07 Oct 2010 07:51:28 +0000 http://www.the-d-spot.org/wordpress/?p=590#comment-1022 Ryan, maybe the transform file isn't applied using SCCM? A colleague has had a similar issue (with another package). His transform file couldn't be found. You can try using a batch file (in SCCM Console; Programs > command line box), and put the "msiexec /i ..."-command inside the batch file. Or use %~dp0 to specify the current path. Google your way out :-) Maybe your path to the transform file contains spaces or is to long? Try to use dubble quotes (TRANSFORMS="path\acroread.mst"). You could generate a log file to investigate where it goes wrong. Here is the msiexec syntax for verbose logging: /l*v c:\acroread.log Keep us posted! Ryan, maybe the transform file isn’t applied using SCCM? A colleague has had a similar issue (with another package). His transform file couldn’t be found.

You can try using a batch file (in SCCM Console; Programs > command line box), and put the “msiexec /i …”-command inside the batch file. Or use %~dp0 to specify the current path. Google your way out :-)

Maybe your path to the transform file contains spaces or is to long? Try to use dubble quotes (TRANSFORMS=”path\acroread.mst”).

You could generate a log file to investigate where it goes wrong. Here is the msiexec syntax for verbose logging: /l*v c:\acroread.log

Keep us posted!

]]> By: Ryan http://www.the-d-spot.org/wordpress/2010/07/07/adobe-reader-9-3-3-deployment/comment-page-1/#comment-1018 Ryan Wed, 06 Oct 2010 23:59:57 +0000 http://www.the-d-spot.org/wordpress/?p=590#comment-1018 What if I can get suppress EULA to work but not disable auto updates? Every single setting I've tried will not disable updates. The thing is if I manually run the installation via the command line on a new PC -- it works. If I use a deployment tool like SCCM + WDT, it does not work. Any ideas? What if I can get suppress EULA to work but not disable auto updates? Every single setting I’ve tried will not disable updates. The thing is if I manually run the installation via the command line on a new PC — it works. If I use a deployment tool like SCCM + WDT, it does not work. Any ideas?

]]> By: Ben De Vriese http://www.the-d-spot.org/wordpress/2010/07/07/adobe-reader-9-3-3-deployment/comment-page-1/#comment-816 Ben De Vriese Wed, 01 Sep 2010 10:25:30 +0000 http://www.the-d-spot.org/wordpress/?p=590#comment-816 Back from vacation :-) Thanks for your comment Scott, I updated the post with your suggestions. Back from vacation :-)

Thanks for your comment Scott, I updated the post with your suggestions.

]]> By: Scott http://www.the-d-spot.org/wordpress/2010/07/07/adobe-reader-9-3-3-deployment/comment-page-1/#comment-696 Scott Wed, 04 Aug 2010 18:31:59 +0000 http://www.the-d-spot.org/wordpress/?p=590#comment-696 Thank you so much for documenting this. If I might make a suggestion, the instructions would really be idiot-proof if you made the path names and file names match between steps 1 & 2 and steps 4 & 5. At the beginning you use C:\temp\reader933\..., but then reference C:\temp\adobereader\... in the later steps. Plus, when I used the customization wizard, the filename of the transform it made by default was "AdbeRdr930_en_US.mst", not "AcroRead.mst" as you have listed. Therefore I had to alter the command in the Deployment to fit my situation. Thank you so much for documenting this. If I might make a suggestion, the instructions would really be idiot-proof if you made the path names and file names match between steps 1 & 2 and steps 4 & 5. At the beginning you use C:\temp\reader933\…, but then reference C:\temp\adobereader\… in the later steps.

Plus, when I used the customization wizard, the filename of the transform it made by default was “AdbeRdr930_en_US.mst”, not “AcroRead.mst” as you have listed. Therefore I had to alter the command in the Deployment to fit my situation.

]]> By: Ben De Vriese http://www.the-d-spot.org/wordpress/2010/07/07/adobe-reader-9-3-3-deployment/comment-page-1/#comment-596 Ben De Vriese Thu, 15 Jul 2010 06:47:25 +0000 http://www.the-d-spot.org/wordpress/?p=590#comment-596 It seams you don't applied the 9.3.2 and 9.3.3 patches (.msp) to the 9.3.0 sources. Can you try one more time, using another admin point? It's a three step process: 1. Extract the 9.3 MSI using the /a parameter (create an admin point) 2. Apply 9.3.2 MSP (patch) to the admin point using the /p parameter (then you have slipstreamed the 9.3.2 sources into 9.3.0) 3. Apply 9.3.3 MSP to the admin point, same way as step 2. Let me know. It seams you don’t applied the 9.3.2 and 9.3.3 patches (.msp) to the 9.3.0 sources.

Can you try one more time, using another admin point?

It’s a three step process:
1. Extract the 9.3 MSI using the /a parameter (create an admin point)
2. Apply 9.3.2 MSP (patch) to the admin point using the /p parameter (then you have slipstreamed the 9.3.2 sources into 9.3.0)
3. Apply 9.3.3 MSP to the admin point, same way as step 2.

Let me know.

]]> By: Hector http://www.the-d-spot.org/wordpress/2010/07/07/adobe-reader-9-3-3-deployment/comment-page-1/#comment-595 Hector Wed, 14 Jul 2010 18:45:36 +0000 http://www.the-d-spot.org/wordpress/?p=590#comment-595 Ben, I have followed all your steps and then run the command to test before creating the SCCM package, and it tries to install 9.3 and not 9.3.3. I went and ran the MSI itself and same thing. How does the MSI know it has to install 9.3.3 and not 9.3.0? I see multiple folders created during the slipstream, but did not find an msi in there. I am thinking the msi was updated with the commands above, but I guess not. Any suggestions? Ben,

I have followed all your steps and then run the command to test before creating the SCCM package, and it tries to install 9.3 and not 9.3.3. I went and ran the MSI itself and same thing. How does the MSI know it has to install 9.3.3 and not 9.3.0? I see multiple folders created during the slipstream, but did not find an msi in there. I am thinking the msi was updated with the commands above, but I guess not. Any suggestions?

]]>