Probably you have already deployed adobe reader with sccm using a custom installation, if not you can find the article here: Install Adobe Reader DC with SCCM.
Adobe Patch Er Update The ProductIf you have already the product the normal way is just to update the product.Adobe Patch Er Download Just TheIn order to do this you need to download just the patch file.msp format from adobe.
For such unwanted events, Adobe Application Manager was created and it will take care of the issue and fix it automatically. From the main window of the program, you will be able to choose to view all the apps or only the updates. The fact that it runs without having to adjust any settings in advance is a great benefit and, perhaps, the main strong point of this utility. Filed under AAM patch Application Manager Adobe manager AAM Adobe Manager Installation. Softpedia and the Softpedia logo are registered trademarks of SoftNews NET SRL Contact. Bootstrapper Deployment DC Windows Desktop Deployment You will need to modify the setup.ini file and add the PATCH with the appropriate name of the MSP file you are updating with in your package. If you put an uninstall rule for msi code AC76BA86-7AD7-1033-7B44-AB0000000001 in package boot, any existing versions of Reader 11 will be uninstalled and the up to date package will be installed with your customizations. Adobe Patch Er .Exe SAll DISABLEARMSERVICEINSTALL1Using the Adobe Reader 11.0.02.0 (AdbeRdr11002enUS.exe sAll DISABLEARMSERVICEINSTALL1) 3rd party package I can update my clients, but without MST transformation. Using a decompressed AdbeRdr11002enUS.exe (resulting in 6 files) I can use the MST, but all that gets installed is the v11.0.0. Creating an administrative install point I can integrate the 2 update MSP Files and use the MST, but this install source does complain if the v11.0.0 is already installed and does then nothing. Has anybody gotten around such problem I would rather not have to provide multiple packages for reaching one target. At the moment Ive got four packages to achive the target state: package one: a complete installer with the latest patches included (build as described in this thread); this updates any pre-v11 installation three packages to update an existing v11 installation to 11.0.3 (one for each MSP) The setting originally intended to include as a MST file are published with a group policy. That gets me a success quote of 98 of the companys computers reaching the target state. I have clients on 10.0.4 and Id like to get that uninstalled and 11.0.02 installed. So far, Ive been unable to get 10.0.4 uninstalled so on test machines Im ending up with both versions installed at the same time. Im not sure what Im doing wrong, but Id like to get it right. I think the only option, short of a solution here, is to find a way to uninstall 10.0.4 separately. I found a reference on the Adobe community site: Adobe Community: Adobe Reader Customization uninstall previous versions that is still unanswered which makes me wonder if there isnt something broken with the transform. It turns out that theres a bug in the customization wizard which requires you to wait until just before you save the msi to check the remove all previous versions of reader box. I also had a separate, but related at least in my case, issue with the adobeARMservice, that Ive found a way to deal with now. How did you solve the adobeARMservice issue, and what was your issue. Verify that you have sufficient privileges to remove system services. I put these two commands in a batch file (using the GUID WSUS works with), then invoked them with package boot prior to the install and its working like a charm. Add a CmdLine parameter to specify your transform file, like the example below. ![]() If Ive got the v10.0.0 already installed it gets updated to the correct version but without usage of the MST. I want to be clear that my instructions do not apply to an admin install. Please try the following steps: Run the command AdbeRdr11002enUS.exe -sfxoC:Reader -sfxne This will extract 7 files into C:Reader Add your AcroRead.mst transform to C:Reader Edit the setup.ini file. Under the Product section, add the following line (and nothing else) CmdLineTRANSFORMSAcroRead.mst Run setup.exe with no switches If this works, you can now add the following parameter to Startup for a silent install CmdLinesAll rs (Edit: Corrected the parameters to perform a minimal and silent install). The administration install (step 3) has now been abandoned as this way nothing can be achived if already an older version is installed. To make sure that my install did not get corrupted I followed your 6 steps on a clean environment. Same result by using this package: No existing v11: everythins works, v11.0.2 with transformation applied, therefor no EULA. Here my full setup.ini from the last (fresh) test. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |