I no longer have it showing up multiple times now. I think it was doing it because I was using the wrong Product Code. It kept showing up in Windows Update because the Product Code would never be found so it would always show up. The install would still work because the MSP file was smart enough to know the update was already installed.
To build the initial Adobe Acrobat Reader base, I followed the instructions in the Adobe Reader XI Deployment with Custom Settings (skipping the custom settings section). In other words, I extracted the Adobe Reader EXE (7zip), and uploaded the SETUP.EXE file in the Update Creation Wizard. I added the 5 additional files minus the MSP update file. If you view the PDF I note above, you'll start with Page 9.
Once you've published that (don't forget to use the MSI tool to get the product code), create another Update for Adobe Reader and add just the MSP file (use my instructions in the previous post to get it published). You'll create multiple of these as Adobe releases.
Do not use supersede. I was confused on that. Supersede means it replaces a previous update. That would be correct except Adobe doesn't repackage the downloadable executable into one file--i.e. all of their downloadable executables (for this year) will come with the MSI for version 15.007.20033 and an MSP for the update. What we were doing was superseding the full blown Adobe Reader with just the Update (MSP file)--i.e. kinda like trying to install Windows 7 from scratch with just the Windows 7 SP1 disc.
Hope this helps. I've been testing this quite a bit and it works flawlessly. I'm now tackling Java.
To build the initial Adobe Acrobat Reader base, I followed the instructions in the Adobe Reader XI Deployment with Custom Settings (skipping the custom settings section). In other words, I extracted the Adobe Reader EXE (7zip), and uploaded the SETUP.EXE file in the Update Creation Wizard. I added the 5 additional files minus the MSP update file. If you view the PDF I note above, you'll start with Page 9.
Once you've published that (don't forget to use the MSI tool to get the product code), create another Update for Adobe Reader and add just the MSP file (use my instructions in the previous post to get it published). You'll create multiple of these as Adobe releases.
Do not use supersede. I was confused on that. Supersede means it replaces a previous update. That would be correct except Adobe doesn't repackage the downloadable executable into one file--i.e. all of their downloadable executables (for this year) will come with the MSI for version 15.007.20033 and an MSP for the update. What we were doing was superseding the full blown Adobe Reader with just the Update (MSP file)--i.e. kinda like trying to install Windows 7 from scratch with just the Windows 7 SP1 disc.
Hope this helps. I've been testing this quite a bit and it works flawlessly. I'm now tackling Java.