39 Replies Latest reply on Aug 5, 2009 10:42 AM by mcbsys

    Applying 9.1.2 to existing admin install point

    bhicks14

      I am trying to patch my existing admin install point of Adobe Reader 9.1.1 to 9.1.2 but get this error:

      The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program.  Verify that the program to be upgraded exists on yoru computer and that you have the correct upgrade patch.

       

      I get the same error on my PC when I double click the msp file

       

      This is the msi log from when I tried to patch the existing admin install of 9.1.1:

      MSI (c) (00:58) [16:18:02:876]: Final Patch Application Order:
      MSI (c) (00:58) [16:18:02:876]: Other Patches:
      MSI (c) (00:58) [16:18:02:876]: Unknown\Absent: {AC76BA86-7AD7-0000-2550-7A8C40000912} - C:\CustomInstalls\AdobeReader\patches\adobe912.msp
      The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer an
      d that you have the correct upgrade patch.
      C:\CustomInstalls\AdobeReader\acroread.msi
      MSI (c) (00:58) [16:18:02:876]: Product: Adobe Reader 9.1.1 - Update '{AC76BA86-7AD7-0000-2550-7A8C40000912}' could not be installed. Error code 1642. Additional information is available in the log file c:\adobe.log.

       

      MSI (c) (00:58) [16:18:02:923]: Product: Adobe Reader 9.1.1 -- Installation failed.

       

      Any help is greatly appreciated.

        • 1. Re: Applying 9.1.2 to existing admin install point
          kwardle21

          I am having this *exact* same problem at our company on over 50 PCs.

           

          "I am trying to patch my existing admin install point of Adobe Reader 9.1.1 to 9.1.2 but get this error:

          The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program.  Verify that the program to be upgraded exists on yoru computer and that you have the correct upgrade patch.

           

          I get the same error on my PC when I double click the msp file"

           

          I'll post more details shortly.

          • 2. Re: Applying 9.1.2 to existing admin install point
            JoshTMA

            Same here.  I tried creating a new install point of just 9.1.0 and I could update that to 9.1.2.  Of course actually trying to update a 9.1.1 client from that new install point totally hosed the client.

             

            Oh and can't apply the MSP to an installed 9.1.1 client directly either.  Same error.

             

            Anyone have any better ideas?

            • 3. Re: Applying 9.1.2 to existing admin install point
              JonathanH_HUHS

              Running into the same problem here.  AIP was created with 9.1.1; when I try to apply the 9.1.2 patch it fails with "The upgrade patch cannot be installed by the Windows Installer service because  the program to be upgraded may be missing, or the upgrade patch may update a  different version of the program. Verify that the program to be upgraded exists  on your computer and that you have the correct upgrade patch."  The error in the Windows Installer log is 1642.

               

              Looks like the equivalent patch for Reader 8 has the same problem:

              http://forums.adobe.com/thread/445393?tstart=0

               

              If anyone has a fix, I'd love to hear about it.

              • 4. Re: Applying 9.1.2 to existing admin install point
                a dog named indy

                I initally had that problem.  What I ended up doing was creating a new admin install point with the 9.1.0 msi file.  I then patched that install point with the 9.1.2 and, voila, I had a patched version.  Now I just can't get it installed - it keeps telling me there is a current version installed....

                • 5. Re: Applying 9.1.2 to existing admin install point
                  bluewanderer

                  You may want to check out the thread about updating to 8.current version. It seems like the patch on that one only works for an older version, not the newer versions. Could be the same is happening here.

                   

                   

                  I was having a similar problem. I was able to update the admin share (msiexec /a shared.msi /p AdbeRdrUpd912_all_incr.msp) I then told AD to redeploy the package. On restarting test workstations, it said it was installing. On starting Adobe Reader it said "configuring Adobe Reader 9.1.2," but in the about screen, it said it was version 9.1.0. I would get the same error if I tried to apply the patch to the updated but still 9.1.0 installs.

                   

                  What seemed to work is if I added the 9.1.2 install as new software package, to be installed as an upgrade to 9.1.0, removing 9.1.0 before installing 9.1.2. I have not had any problems since.

                   

                  What surprisingly did not work was installing the patch on a 9.1.0 workstation and then moving the files in the "setup files" folder to the admin share. The patch did not touch those files and that just reinstalled 9.1.0.

                  • 6. Re: Applying 9.1.2 to existing admin install point
                    a dog named indy Level 1

                    I'll try installing 9.1.2 as a new package and see where that gets me.  Thanks.

                     

                    I'll also take a look at the version 8 thread.  Thanks.

                    • 7. Re: Applying 9.1.2 to existing admin install point
                      kwardle21 Level 1

                      Adobe please fix your patch to properly detect your own product!

                       

                      This is 100% an error in the 9.1.2 patch. As promised here are more details:

                       

                      What works:

                       

                      1. Fresh install of Adobe 9.1.0. > Install 9.1.1 .msp. > Install 9.1.2 .msp.  OR
                      2. Apply the 9.1.2 patch to the Adoble 9.1.0 installer, (msiexec /p <9.1.2.msp> /a <9.1.0.msi>) Fresh install.

                       

                      What does NOT work:

                       

                      50+ PCs on a corporate network were silently and remotely installed with Adobe Reader 9.1.0 minus Adobe Air with the 9.1.1 patch included. (msiexec /p <9.1.1.msp> /a <9.1.0.msi>) The updated .msi was then customized with the Adobe Customization Wizard 9 to silently accept the EULA, silently install, etc. Some of the steps in the process were followed from here:  (but not all)

                       

                      http://www.vatofknow.com/archives/249

                       

                      When you try to install the 9.1.2 patch to these systems, the following error message is displayed:

                       

                      "The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program.  Verify that the program to be upgraded exists on yoru computer and that you have the correct upgrade patch."

                       

                      So it's pretty simple: The product checking built into the 9.1.2 patch is simply NOT detecting the above mentioned 9.1.0 + 9.1.1 install. My guess is that the 9.1.2 patch is looking for a specific CLSID in the registry. And that CLSID is not written when reader 9.1.0 + 9.1.1 is installed via the above method.

                       

                      Adobe please fix your patch to properly detect your own freaking product!

                      • 8. Re: Applying 9.1.2 to existing admin install point
                        JonathanH_HUHS Level 1

                        What seemed to work is if I added the 9.1.2 install as new software package, to be installed as an upgrade to 9.1.0, removing 9.1.0 before installing 9.1.2. I have not had any problems since.    

                         

                        Not a bad workaround, but the downside is the time required - your clients have to uninstall 9.1.0 and install 9.1.2.  If the MSP worked, your clients could just replace existing files with the updated ones included in the patch.

                         

                        Adobe please fix your patch to properly detect your own freaking product!

                         

                        LOL, agreed!

                        • 9. Re: Applying 9.1.2 to existing admin install point
                          kwardle21 Level 1

                          Any fixes / updates from Adobe on this yet?

                          • 10. Re: Applying 9.1.2 to existing admin install point
                            emark1 Level 1

                            sorry, my point only applies to the Mac version of Reader, which has its own issues...sorry to muddy the waters

                             

                             

                            guys:

                             

                            Check to see if you have the file system is case-sensitive.

                             

                            For a while Adobe has had problems w/ case-sensitive HFS+ with CS (Creative Suite) products...now it appears that the same sloppy coding has leaked into Adobe Reader...even though there's no warnings on the download page and their installer will proceed on top of this volume without checking/testing it.  Can't be 100% certain it is the same problem for you, but check...

                            The reason this is taking many of us by suprise is that Reader has historically been able to work w/o issue on case-sensitive volumes for me going back to 10.4.

                             

                            I've uninstalled every peice of the app, the prefs, the apps support folder, repaired prefs, reinstalled the original 9.1, then applied 9.1.1, again repaired prefs,  and consistently fail at 9.1.2 install.

                             

                            Please report back if you have the same issues!

                             

                            see also:

                            http://forums.adobe.com/thread/447986;jsessionid=030B1F4A6BEDC405AB42263D9F518EF4.node0?ts tart=0

                             

                             

                            BTW: for those struggling to install 9.1.2:  if you can, test to see if you're able to open the application preferences please.  Seems that the problem may  extend to the application being unable to open its own preferences--if they fail to open due to an  "internal error" that seems to be related to the file system to and the  program not using case sensitive call to open it's own components?

                             

                            PPC 10.5.7

                            • 11. Re: Applying 9.1.2 to existing admin install point
                              ScienceSystems

                              All the latest patches from Adobe are screwed up this way. The Acrobar (Pro/Standard) 8.1.6 patches fail to apply to an 8.1.5 admin install point but do apply to the 8.1.3 one.

                              This is completely unexpected since previously their updates were incremental and therefore absolutely required that the previous version be used to apply the latest patch (e.g. could NOT go from 8.1.3 to 8.1.5 without first applying 8.1.4).

                               

                              Applying the reader 9.1.2 to a 9.1.0 rather than a 9.1.1 install point works - *HOWEVER* the customization wizard is not able to open the resulting package for customization!

                              Furthermore, previously created transforms for 9.1.1 do not work on the 9.1.2 MSI!

                               

                               

                              This is a serious screw up on Adobe's part.

                              • 12. Re: Applying 9.1.2 to existing admin install point
                                wbbigdave

                                I had the same error with the 9.1.1 patch when it came to install the fresh MSI, from the install point. I found the only way around this was at the command line run the installation as a repair not just an install

                                 

                                e.g

                                 

                                msiexec /f <AdminInstallPoint> TRANSFORMS="<TransformsFile>"

                                 

                                This only worked on 9.1 > 9.1.1 however, it does not seem to work for 9.1.1 > 9.1.2

                                 

                                Also I just noticed that in the add remove program list 9.1.2 is listed as 9.1.1 which seems like a big flaw to me, but it could be the patch was not successfully applied to the MSI and I need to go back and check my work so far. Grr adobe, Grr. Sort your apps out, but please don't release another patch, we are having headaches keeping up with this one!

                                 

                                As an aside this is generally patched via Group Policy for us so it isn't a massive problem but could prove tricky in the future for more patches.

                                 

                                !!EDIT!!

                                 

                                I have found the the comand line above works when the MST file from wise package studio is used. It seems the adobe Customization wizard does not work properly.

                                • 13. Re: Applying 9.1.2 to existing admin install point
                                  bhicks14 Level 1

                                  Well I can say that i'm "glad" I'm not the only one havign this problem.  Not really it would be nicer if Adobe would just make their patches correctly.

                                  Like a few others have said this isn't a major problem for a home user that just has to uninstall once and install the new version.  But when you're responsible for updating this on 10, 25, 100, 5000 PC's whatever your environment consists of its quite frustrating trying to keep these up to date when the patch releases are poor quality.

                                   

                                  At this point I've almost decided to create a custom action in the msi to uninstall 9.1 (Just in caee we have a few that haven't been upgraded) and 9.1.1 then install 9.1.2.  We're moving quite a bit of stuff into a new DFS structure so the timing works out.  Goign forward though I hope that Adobe fixes their patches, especially if they are planning monthly releases.

                                   

                                  If anybody has any better ideas on how they're handling these please let the rest of the forum know.  Hopefully Adobe can fix their own products if they're planning on doing "patch tuesdays."

                                  • 14. Re: Applying 9.1.2 to existing admin install point
                                    a dog named indy Level 1

                                    I had the same problem.  The fix was to start with 9.1, create a new install point and then patch it with 9.1.2.  I then deployed with Group Policy, ensuring I added the newly patched version to the same GPO that had the 9.1.1 and, using the advanced settings, telling it to update 9.1.1 (which removes that version and installs the new one).  I have now successfully installed it on over 100 (and counting) computers with nary a problem.

                                    • 15. Re: Applying 9.1.2 to existing admin install point
                                      wbbigdave Level 1

                                      Seems the way to do it (GPO set to upgrade all previous versions). I'm just fretting about some of the installs I have to supply via SMS to remote workers. I HOPE, that the MSI will work, as it is just going over the top of Reader 9.

                                       

                                      But you never can tell.

                                       

                                      Roll on the next patch and subsequent forum posts. -_-

                                      • 16. Re: Applying 9.1.2 to existing admin install point
                                        bhicks14 Level 1

                                        These solution work, I agree.  The problem is that it shouldn't be that involved and I, along with many others, don't want to create new completely patched installs and full deployment packages for each of these patches.  Other ompanies release msp based patches and don't have this problem, why can't Adobe figure their own products out???!!

                                         

                                        Not to put anybody down but if you're job role is just doing software deployments then this might not be bad, but when you're in somewhat of a jack of all trades position it gets tough to keep up when you have to reinvent the circle everytime updates are put out.  It would be nice to just apply the patch to our current admin install point, test it, then tell Group Policy to redeploy the software.  This is also quicker for the end user.  Doing an "upgrade" GP install takes 2 -3 times longer. They have to wait for the uninstall of the old version then the install of the new version.

                                        • 17. Re: Applying 9.1.2 to existing admin install point
                                          a dog named indy Level 1

                                          That's a very good point that can't be understated.  It did take me the better part of a day to get this package put together, tested and deployed.  It was deeply frustrating and I had other things to contend with ,like putting out a quicktime update

                                          • 18. Re: Applying 9.1.2 to existing admin install point
                                            Michichael

                                            JonathanH_HUHS wrote:

                                             

                                            Adobe please fix your patch to properly detect your own freaking product!

                                             

                                            LOL, agreed!

                                            QFT. This took me the better part of two hours to figure out. Not fun when I've got a bunch of other crap to work on.

                                            • 19. Re: Applying 9.1.2 to existing admin install point
                                              SRM1968

                                              Has anyone had luck getting updating an Administrative Install Point of Acrobat Pro 9?  It seems most of the workarounds here relate to Acrobat Reader.

                                               

                                              Here's what I've done:

                                               

                                              -Begin with new Admin Install point of Acrobat Pro 9.0.0

                                              -Successfully apply 9.1.0 Update

                                              -Successfully apply 9.1.1 Update

                                               

                                              Applying the 9.1.2 update fails with the message already mentioned in this thread.  I'm going to try applying the 9.1.2 patch to earlier revisions of my Install Point but I'm not having high hopes.

                                              • 20. Re: Applying 9.1.2 to existing admin install point
                                                wbbigdave Level 1

                                                The only way so far to do this is to install the MSP to the 9.1 install

                                                point NOT the 9.1.1

                                                 

                                                I am unsure if this is a problem with the 9.1.2 MSP or the 9.1.1 MSP,

                                                either way it's a big flaw in the update from adobe.

                                                 

                                                As I have said previously the best way for me was to create a new Admin

                                                install point from the 9.1.exe (without air) then use the 9.1.2 MSP and

                                                then use the customization tool, then use the new package to create a

                                                new GPO for testing, with uninstall previous versions set.

                                                 

                                                Took a while but it will be worth it

                                                 

                                                However I haven't tried this for Acrobat 9 yet. We don't have many users

                                                of full acrobat pro, but everyone has reader.

                                                • 21. Re: Applying 9.1.2 to existing admin install point
                                                  SRM1968 Level 1

                                                  ok, that worked:

                                                   

                                                  -Created brand new 9.0.0 Admin Install Point

                                                  -Applied the 9.1.0 patch

                                                  -Applied the 9.1.2 patch

                                                   

                                                  Now I'm going to attempt to use the Customization Wizard.

                                                  • 22. Re: Applying 9.1.2 to existing admin install point
                                                    wbbigdave Level 1

                                                    Good luck,

                                                     

                                                    I recommend you look at the instructions on www.vatofknow.com/archives/249 for some good suggestions to pull out of the registry, and don't neglect the Language and dictionary customization in the registry (HKCU>SOFTWARE>ADOBE>**PRODUCT**>9.0>ORIGINALS and >SPELLING

                                                     

                                                    I had to pull those from my current build.

                                                     

                                                    But like i said, Good luck   

                                                    • 23. Re: Applying 9.1.2 to existing admin install point
                                                      Michichael Level 1

                                                      Just going to point this out for everyone here... this stupid patch breaks "Display in Browser" as well. I think I've found the reason... If you check the registry,

                                                       

                                                      [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\acrobat\DefaultIcon]
                                                      @="C:\Program Files\Adobe\Reader 9.0\Acrobat\AcroRd32.exe"

                                                       

                                                      But if you look in your Program files, there's no Acrobat folder. It's reader.So change it to...

                                                       

                                                       

                                                      [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\acrobat\DefaultIcon]
                                                      @="C:\Program Files\Adobe\Reader 9.0\Reader\AcroRd32.exe"

                                                       

                                                      Using the Customization Wizard [If you went from AIP 9.1.0 -> 9.1.2] You should be able to edit in the registry key.

                                                       

                                                      Not sure if it works yet. but it's one of the bigger discrepancies I've found. Anyone else got any ideas?

                                                       

                                                      Edit:

                                                       

                                                      Yeah, that fixes it. My suggestion? Edit in the registry key via transform, then redeploy via GPO.

                                                      • 24. Re: Applying 9.1.2 to existing admin install point
                                                        roblandon

                                                        Has anyone heard of any plans by Adobe to release the msp file in a form that works properly? As mentioned earlier, I'm not sure how well these fixes are going to work for remote machines.

                                                        • 25. Re: Applying 9.1.2 to existing admin install point
                                                          rasczak

                                                          Not sure if you guys need this anymore but here was my fix.

                                                           

                                                          went through motions of installing AdbeRdr910_en_US.exe. before the installation starts i took five adobe files out of the %userprofile%/local settings/application data/adobe/setup files directory and placed them in a folder called adobe912 on C:.

                                                           

                                                          place 9.1.1 and 9.1.2 in C:\adobe912 directory as well.

                                                           

                                                          in CLI typed the following.

                                                           

                                                           

                                                          msiexec /a C:\adobe912\AcroRead.msi /p C:\adobe912\AdeRdrUpd911_all_incr.msp;C:\adobe912\AdeRdrUpd912_all_incr.msp

                                                           

                                                          although I could not verify if 9.1.1 actually installed, i am assuming it did since i received 0 errors. If anyone could verify it for me that would be terrific.

                                                           

                                                          Good Luck and I hope this helps.

                                                          • 26. Re: Applying 9.1.2 to existing admin install point
                                                            roblandon Level 1

                                                            I'm going to try your solution today.

                                                            rasczak wrote:

                                                             

                                                            Not sure if you guys need this anymore but here was my fix.

                                                             

                                                            went through motions of installing AdbeRdr910_en_US.exe. before the installation starts i took five adobe files out of the %userprofile%/local settings/application data/adobe/setup files directory and placed them in a folder called adobe912 on C:.

                                                             

                                                            place 9.1.1 and 9.1.2 in C:\adobe912 directory as well.

                                                             

                                                            in CLI typed the following.

                                                             

                                                             

                                                            msiexec /a C:\adobe912\AcroRead.msi /p C:\adobe912\AdeRdrUpd911_all_incr.msp;C:\adobe912\AdeRdrUpd912_all_incr.msp

                                                             

                                                            although I could not verify if 9.1.1 actually installed, i am assuming it did since i received 0 errors. If anyone could verify it for me that would be terrific.

                                                             

                                                            Good Luck and I hope this helps.

                                                            Has anyone tried this:

                                                             

                                                            http://www.microsoft.com/technet/scriptcenter/scripts/sus/server/default.mspx?mfr=true

                                                             

                                                            This is not the first time an msp file from adobe has made things difficult. I am thinking of changing my strategy in the future.

                                                            • 27. Re: Applying 9.1.2 to existing admin install point
                                                              WebRioter

                                                              Disregard, my post is in regards to invalid serial number on Pro/Standard after 9.1.2 to existing admin point.  Wrong forum.

                                                              • 28. Re: Applying 9.1.2 to existing admin install point
                                                                rasczak Level 1

                                                                rob,

                                                                 

                                                                I didn't need to go through WSUS (WSUS is a pain although that's another site and forum altogether ) Once I completed the referenced steps, I added the msi package to a GPO un computer settings > software installation. I refreshed the policy and restarted the computers. During the reboot adobe started to install. Worked flawlessly.

                                                                 

                                                                Good luck with that.

                                                                 

                                                                Joe

                                                                • 30. Re: Applying 9.1.2 to existing admin install point
                                                                  roblandon Level 1

                                                                  Thanks. I've had to do so many updates to Acrobat I was just hoping to find a different way to handle the updates without reworking the admin install point.

                                                                   

                                                                  Rob Landon, A, Net & MCP

                                                                  PC Support Specialist

                                                                  Clipper Magazine

                                                                  • 31. Re: Applying 9.1.2 to existing admin install point
                                                                    Ubuntu17 Level 1

                                                                    Ya I ran into the same issue with viewing a PDF in a browser. I thought I was good to push 9.1.2 out to our organization and then I find out pdf's wont open properly in browsers. Now i need to edit a regestry key.

                                                                     

                                                                    Adobe Reader is getting very frustrating to work with

                                                                    • 32. Re: Applying 9.1.2 to existing admin install point
                                                                      roblandon Level 1

                                                                      There was a previous post about inserting some registry keys using Adobe Customization Wizard.

                                                                       

                                                                      It's not just Adobe Reader. Acrobat Professional has the same quirks when attempting to install via GPO.

                                                                       

                                                                      Rob Landon, A, Net & MCP

                                                                      PC Support Specialist

                                                                      Clipper Magazine

                                                                      • 34. Re: Applying 9.1.2 to existing admin install point
                                                                        roblandon Level 1

                                                                        I'm not sure that’s a solution or not. It really explains well why it is happening.

                                                                         

                                                                        I'm going to try scripting this:

                                                                         

                                                                        Workaound for User installations, which were deployed from an AIP containing a Security update as the last update applied

                                                                        In order to successfully deploy a Quarterly update onto these User systems, the Msiexec.exe "v" option must be added to the commandline. An example syntax is as follows:

                                                                         

                                                                        msiexec /i REINSTALL=ALL REINSTALLMODE=vomus

                                                                         

                                                                        Using the above command line with the option "vomus" present will cause the MSI to run from the source AIP and re-cache the User's local MSI for future changes or repair. This is the most trustworthy method for deploying updates of this nature.

                                                                         

                                                                        And then patch to 9.1.2. Still a royal pain though.

                                                                         

                                                                        Rob Landon

                                                                        PC Support Specialist

                                                                        Clipper Magazine

                                                                        • 35. Re: Applying 9.1.2 to existing admin install point
                                                                          wbbigdave Level 1

                                                                          Am I the only person who reads a lot of Corporate BS coming off this adobe KB article.

                                                                           

                                                                          "The patch types are different"...yeh I get that

                                                                           

                                                                          "Different patch types can't be applied together"...ok, a little off but...

                                                                           

                                                                          "Note, Attempting to create an AIP using the last configuration shown above will fail. The failure, however, serves to prevent a usage of updates which is not recommended by Adobe"...WHAT! this just douns like an excuse to broken patching, be it 9.1.1 or 9.1.2

                                                                           

                                                                          Don't release the patch as an incremental unless it actually is. Unless they changed it *runs off to check* WHICH THEY HAVEN'T!

                                                                           

                                                                          "NOTE: This update can be applied either to Adobe Reader version 9.1 or to version 9.1.1"

                                                                           

                                                                          then this is a cop out.

                                                                           

                                                                          Either way, i got mine sorted out but no less angry with Adobe for this shoddy patching cycle.

                                                                          • 36. Re: Applying 9.1.2 to existing admin install point
                                                                            roblandon Level 1

                                                                            It does make you wonder why they would need to differentiate their patches, so you do have to wade through some BS.

                                                                             

                                                                            The script mentioned: msiexec /i REINSTALL=ALL REINSTALLMODE=vomus

                                                                             

                                                                            Only recaches the installation. I believe the user has to run the msp file.

                                                                             

                                                                            At this point I'm just going to rebuild my AIP to match what adobe says is the best practice.

                                                                             

                                                                            Rob Landon, A, Net & MCP

                                                                            PC Support Specialist

                                                                            Clipper Magazine

                                                                            • 37. Re: Applying 9.1.2 to existing admin install point
                                                                              TTEConline

                                                                              I don't even know why I continue to use adobe products. Adobe software development is a joke. So are their UIs.

                                                                               

                                                                              First, this forum crashed my FireFox 3.0.10 browser, twice. The second time, I figured out it was Adobe's fault. Why doesn't Adobe learn to script AJAX properly so it doesn't crash browsers? So here I am in IE8 typing a reply.

                                                                               

                                                                              All of you guys were beating around the bush in regards to the "solution" to this problem. I have found a way to apply the patch and use an MST generated by the Adobe Customization Wizard. Granted, it would be much better if Adobe would just generate their patches correctly to begin with.

                                                                              As you all have found out, you cannot create an MST using the ACW (Adobe Customization Wizard) and then use the following command

                                                                              msiexec /i AcroRead.msi /p AdbeRdrUpd912_all_incr.msp /t

                                                                               

                                                                              This will cause the aforementioned problem. Below is the proper sequence of events:

                                                                              1. Make a backup copy of the 9.1.0 AcroRead.msi (just in case).
                                                                              2. Run the following command: msiexec /a AcroRead.msi /p AdbeRdrUpd912_all_incr.msp This command will create an Administrative Install Point (AIP) in the directory you choose. I will place it in a directory called Patched The AcroRead.msi file will be rewritten and will be version 9.1.2 (check the Property table with ORCA and look at the value ProductVersion). In addition, the files that were in Data1.cab will be expanded and patched and are in the Patched folder I specified above. At this point, we no longer need the Data1.cab file. If you know how, you could compress all the files back into a cab and insert them back into the media table, but that is overly complicated and I forget how to do it successfully. In any event, the major benefit would be some space savings. If you had a lot of apps like this, it would be beneficial; but for one, not so much so.
                                                                              3. Open AcroRead.msi with ACW. Make any changes you want for your installation. However, the following changes must be made or browser integration will be broken (per an earlier post in this thread):
                                                                                1. Go to the Registry item in the left-hand menu.
                                                                                2. Under the Destination Computer section, navigate to the following key: HKEY_CLASSES_ROOT\acrobat\DefaultIcon.
                                                                                3. Modify the (Default) value to the following: [READER]AcroRd32.exe. NOTE: This only applies if you are installing Adobe Reader. If you are installing Acrobat, this may not apply, but I am not sure. YMMV.
                                                                              4. This step was updated 10 July 2009 11:30:00 EST (GMT-05:00). If your are performing application virtualization, you will want to make te following changes to the MSI (via ORCA or ACW). I'm making these changes from ACW. The installer will fail during application sequencing during the installation of the Adobe Updater Manager (AUM). For virtualized applications, this component is unnecessary and should not be installed. Other sites lead you through a lengthy, risky process to eliminate the installation of the AUM. This step will eliminate the installation of AUM with two simple changes to the MSI.
                                                                                1. In ACW, select the Direct Editor node from the left hand side.
                                                                                2. Select the Feature table.
                                                                                3. On the right side, locate the features named AUM and Updater. Note that the Level field for both features are 1. Change the Level field for both fields to be 200. Actually, any number greater than 100 will do, but 200 is a nice round number. Since the installer defaults to INSTALLLEVEL=100 (see the Property table), any feature with a Level value of 100 or less will be installed. Since we have now given these features an install level of 200, these features will not be installed. Generally, this tactic can be used on any component you wish not to have installed (for Adobe Reader and some other applcations with simple installers), such as AIR and Acrobat.com. Those are the only two changes that need to be made to not have AUM installed.
                                                                                4. To make sure your users don't encounter an error while running Adobe Reader, make sure, in ACW, to uncheck the box Disable all updates under the Online and Acrobat.com Features section.
                                                                                5. Save the package (in ACW, File->Save Package). This modifies the setup.ini file so that it will use the changes you just made (saved by default in AcroRead.mst).
                                                                                I left my original instructions below, but marked as deleted. Please see step 5 below these deleted instructions. This is a new step.
                                                                                If you are performing application virtualization, you want to make the following changes to the MSI (via ORCA or ACW). I'm making these changes via ACW. The installer will fail during application squencing due to not being able to create to two certain registry keys. This is the easiest way that I can think of to get this to work.
                                                                                1. Start your sequencing machine (in my case, a VM).
                                                                                2. Install Adobe Reader 9.1.x (do not sequence, simply install).
                                                                                3. Once installation completes, open the Registry Editor (assuming Windows Vista; if using WinXP or below, try RegEdt32.exe).
                                                                                4. Browse to HKEY_CLASSES_ROOT\Installer\Win32Assemblies\Global
                                                                                5. Double click the following entry (make sure you get the right one, there are two similar entries!): Microsoft.VC80.CRT,publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762", processorArchitecture="x86".
                                                                                6. Copy the value of the entry (on Vista, the value is already highlighted,simply right-click and choose Copy. Otherwise, right-click and choose Select All and then right-click again and choose Copy.).
                                                                                7. Paste this value into Notepad. Save the file, making sure to select the Unicode encoding type from the Encoding drop-down list. Save it with the name Microsoft.VC80.CRT.txt
                                                                                8. Back in the registry editor, double-click the following entry: policy.8.0.Microsoft.VC80.CRT,publicKeyToken="1fc8b3b9a1e18e3b",type="win32-policy",versio n="8.0.50727.762",processorArchitecture="x86".
                                                                                9. Copy the value of the entry (on Vista, the value is already highlighted,simply right-click and choose Copy. Otherwise, right-click and choose Select All and then right-click again and choose Copy.).
                                                                                10. Paste this value into Notepad. Save the file, making sure to select the Unicode encoding type from the Encoding drop-down list. Save it with the name policy.8.0.Microsoft.VC80.CRT.txt
                                                                                11. Close the registry editor.
                                                                                12. Reset your VM so it is clean for the sequencing (i.e. revert to a snapshot).
                                                                                13. Back in the ACW, at the Registry portion, navigate to HKEY_CLASSES_ROOT.
                                                                                14. Right-click HKEY_CLASSES_ROOT and selet New->Key. Name the new key Installer.
                                                                                15. Right-click the Installer key and select New->Key again. Name the key Win32Assemblies.
                                                                                16. Create a new key in Win32Assemblies called Global.
                                                                                17. Select the Global key you just created.
                                                                                18. On the right-side of the editor, right-click and choose New->Multi-String Value. Name the new value: Microsoft.VC80.CRT,publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762", processorArchitecture="x86".
                                                                                19. Right-click the new value and select Modify
                                                                                20. Open the text file Microsoft.VC80.CRT.txt you created aboe.
                                                                                21. Press CTRL+A or Edit->Select All (in Notepad) and then press CTRL+C (or Edit->Copy).
                                                                                22. Back in ACW, paste the value from the clipboard and click OK.
                                                                                23. Now right-click the editor and choose New->Multi-String Value again. Name it policy.8.0.Microsoft.VC80.CRT,publicKeyToken="1fc8b3b9a1e18e3b",type="win32-policy",versio n="8.0.50727.762",processorArchitecture="x86".
                                                                                24. Open the policy.8.0.Microsoft.VC80.CRT.txt file created above.
                                                                                25. Copy the file contents as the value of the new entry in the ACW.
                                                                                26. Save the package. You should now be ready to install Adobe Reader via Setup.exe for sequencing.
                                                                              5. Updated 10 July 2009 12:00:00 EST (GMT-05:00). We have one more step to perform just to clean things up bit. I'm going to create another AIP using the patched MSI and our newly created MST. However, this does not work quite as one would expect.
                                                                                1. Run the following command: msiexec /a AcroRead.msi /t <Your_transform.mst>. I created this AIP in a folder called PatchedTransformed.
                                                                                2. The above step created another AIP in the PatchedTransformed folder. What's different about this AIP compared to the one made at the beginning of this procedure is that the MSI file was copied to the PatchedTransformed folder as well. However, the MSI is not merged with the changes from the MST as I expected. There are two things you can do:
                                                                                  1. Modify the setup.ini file and add the following line to the [Product] section: CmdLine=TRANSFORMS="<Your_Transform.mst>", or
                                                                                  2. Use ORCA. Open your patched MSI in ORCA. Choose Transform->Apply Transform... and select the transform generated by the ACW. Then choose File->Save Transformed As... and give the transformed MSI a new name, e.g. Custom-AdobeReader-9.1.2.msi.
                                                                                  That's it. You now have a fully patched and modified Adobe Reader installer ready for installation or application virtualization.

                                                                              At this point, you should have an MSI and MST. If you want, you can use ORCA to merge the MST into the MSI. If you're using Setup.exe, you're going to have to change th Setup.ini file.


                                                                              To test that everything works, you can copy the files to a test directory and perform the following command: msiexec /a <AdobeReader.msi> [/t <Your_transform.mst>] Replace with the name of your MSI file and optionally, pass in your transform (definitely do this if you made a separate MST!). If all goes well, the installation should go well, too. During sequencing, you will still get an MSI installer error (actually, 2), number 1406, about not being able to write to two registry keys. These were the registry keys we added in the steps above. This does not happen on normal installatons.

                                                                               

                                                                               

                                                                              Please also note that I don't know whether the roaming user profile problem menioned in http://kb2.adobe.com/cps/404/kb404597.html is fixed in version 9.1.2. It was not fixed as of 9.1.0.163. This is all posted AS-IS. YMMV.

                                                                               

                                                                              UPDATE:

                                                                              In case you don't know, I will share a bit of enlightenment I had with my procedure above. This specifically relates to application virtualization and sequencing Adobe Reader for MS App-V.

                                                                               

                                                                              In step 4, I had you install Adobe Reader on a clean machine and obtain some registry information because otherwise, the installation may not be successful for virtualization. These steps are unneccessary. Here's why: you cannot "patch/upgrade" vitualized applications within the application itself. To patch/upgrade a virtual application, you have to use (in the case of MS App-V) the Application Virtualization Sequencing MMC to load the virtualized app, then run the upgrade/patch so that MS App-V can detect the changes and properly update the package. So what does this mean? Two things. First, whenever I use the ACW, under the Online and Acrobat.com Features section I always uncheck <b>Disable all updates</b>. However, checking this does not necessarily mean Adobe Reader does not install the Adobe Update Manager (AUM); in fact, it does install AUM, which is the feature that contains the component that attempts to write those registry entries and therefore, which is causing the error.

                                                                               

                                                                              Therefore, the solution (and what should be step 4) is to disable the installation of AUM. Now some have posted at various sites how to disable the installation of AUM by deleting a whole bunch of stuff in the MSI. This is not necessary. The steps are outlined in the new step 4 above. This should resolve sequencing issues.

                                                                               

                                                                              UPDATE 10 July 2009 12:00:00 EST (GMT-05:00) - Pertains to virtualizing Adobe Reader only.

                                                                               

                                                                              This doesn't work for virtualizing the application. When importing the application into MS App-V Server Management Console, the application version is still 9.1.0.163 even though the splash screen says 9.1.2. I think that my assessment is correct because of two reasons: 1) I still got the MS VC++ Runtime error when using a normal user with a roaming profile which Adobe said the latest 9.1.1 release fixed (and hence 9.1.2) (the AppData folder included) and for which Adobe's solution is a joke; 2) When I installed my "patched" Reader (as a normal install) with AUM and proceeded to go to Help->Check for Updates, the 9.1.2 update appeared in the list of updates (again, even though the splash screen said it was version 9.1.2). Adobe has got to get their patchng correct!!!

                                                                               

                                                                              For application virtualization, I'm going to recommend that you sequence the 9.1.0 version through to completion. Then, save the sequence and close it. Then re-open the sequence project for upgrade and applythe 9.1.2 patch. Whether you can use an ACW transform on the 9.1.0 installation and then patch, that's debatable. I sure hope so. If not, perhaps there's a way I can fudge it, namely, create an MST via ACW. Then, manually create an MST with the pertinent settings via ORCA and see if that works, instead.

                                                                               

                                                                              Having said all that, I seriously doubt this works at all even for GPSI deployment. Sorry all. Will post again when I finally get this application to sequence. Hopefully, the same principles will apply to GPSI deployment.

                                                                               

                                                                              Message was edited by: TTEConline on 10 July 2009 12:00:00 EST (GMT-05:00)

                                                                              • 38. Re: Applying 9.1.2 to existing admin install point
                                                                                Ubuntu17 Level 1

                                                                                Well I added this registry key in the customization wizard to fix the viewing in browser problem i was having and it worked

                                                                                [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\SOFTWARE\Adobe\Acrobat\Exe]

                                                                                @="\"C:\\Program Files\\Adobe\\Reader 9.0\\Reader\\AcroRd32.exe\""

                                                                                 

                                                                                Ran the transform again and re-ran the adminstrative install. I applied the 9.1.2 patch to the administrative install and I think it Finnaly is working so I can distributie it to the rest of the organization.

                                                                                 

                                                                                So when is the next security vulnerability going to be out so I can do this all over again..................................

                                                                                • 39. Re: Applying 9.1.2 to existing admin install point
                                                                                  mcbsys

                                                                                  TTECOnline - thanks for post #37 which got me going in the right direction. Blogged here:

                                                                                   

                                                                                  http://blogs.mcbsys.com/mark/post/Patching-Adobe-Reader.aspx

                                                                                   

                                                                                  Mark