This project has moved and is read-only. For the latest updates, please go here.

[Publishing Issue] Adobe Acrobat Reader DC - MUI 15.006.30033

Topics: Configuration Issue, Publishing Issue
Jul 1, 2015 at 12:44 PM

after Import This Catalog:
pushing the update Fails.

the .cab file are available in the wsuscontent folder but in the wsus Publisher gui the update are not available!

Need some help!
Jul 9, 2015 at 1:52 PM
Edited Jul 9, 2015 at 2:39 PM
First- Thank you for tell me the Catalog Adress for the new Reader, because....
I cant found the .cab in the Adobe FTP Server for Adobe Reader.
I cant found the .cab in the Adobe Download Section: , the traditional typical place....

I'm downloaded the .exe manual, extract it to .msi and diffeent files more, change different install options with Adobe Customization Wizard, and then I create a new update in WPP, include the different files, and deploy it for a W7 Testclient. Works well.
I use Client-Group-permission with WPP, and not with WSUS, because it was a source of troubble in my installation to import and update the Database to make it visible in WSUS.

Make a deinstallation and reinstall Adobe XI, start the next test:

Now using catalog.....
open Katalog, download and Import. - works. ( Take al little bit time )..
On WPP main screen, Update is aviable under Updates / Adobe Systems, Inc / Adobe Reader - Adobe Acrobar ReaderDC - MUI15.06.30033 - ok.
Give it free for installation ( on the same a W7 Testclient ) -but ... Status returned : not applicable - HMMMM!

Set the catalog based deployment to "Not approved" , and the self created deployment to " approved for Installation".
Status returned " not installed ", and client installation start again.

Ok, based on this I will recommend to go the first way for deployment and dont use the catalog at the moment. Its the same like the old java deployment, and you can customize the Adobe Reader DC 2015 Installation ( e.g. without EULA )
Unfortunatly there is no .msi for the business Version AR DC 2015, .msi is only for the consumer version availible.

Catalog imported update used "requirements" ( on the first site of configuration ) , self created not, maybe it works if you deactivate the requirements ..... ( not tested)

kind regards,