[Solved] Deploy Adobe Reader XI 11.0.07 with customized settings

Topics: Publishing Issue
Jun 20, 2014 at 11:47 AM
Edited Jun 20, 2014 at 11:48 AM
Hello,

i have problems with deploying Adobe Reader XI 11.0.07 with customized setting.

My method is similar to this thread Republishing Adobe Reader with customized settings from Jan, 2014.
  1. I create a custom update
    Image
  2. Adding all available files
    Image
  3. Publish the Update with a useful ruleset (not final yet but this is not the problem i think)
    is installed
<lar:Or>
<bar:FileVersion Path="C:\Program Files (x86)\Adobe\Adobe Reader XI\Reader\AcroRd32.exe" Comparison="EqualTo" Version="11.0.7.79"/>
<bar:FileVersion Path="C:\Program Files\Adobe\Adobe Reader XI\Reader\AcroRd32.exe" Comparison="EqualTo" Version="11.0.7.79"/>
</lar:Or>
is installable
<lar:Or>
<lar:Not><msiar:MsiProductInstalled ProductCode="{ac76ba86-7ad7-1031-7b44-ab0000000001}"/></lar:Not>
    <lar:And>
    <msiar:MsiProductInstalled ProductCode="{ac76ba86-7ad7-1031-7b44-ab0000000001}"/>
        <lar:Or>
        <lar:Not><bar:FileVersion Path="C:\Program Files (x86)\Adobe\Adobe Reader XI\Reader\AcroRd32.exe" Comparison="EqualTo" Version="11.0.7.79"/></lar:Not>
        <lar:Not><bar:FileVersion Path="C:\Program Files\Adobe\Adobe Reader XI\Reader\AcroRd32.exe" Comparison="EqualTo" Version="11.0.7.79"/></lar:Not>
        </lar:Or>
    </lar:And>
</lar:Or>
  1. Creating the Update takes a while with this result
    Image
  2. After Approving for my two test clients the ones which need it are getting them provided.
    The uninstallation works fine, but the second task for installing issues a failure after about ten minutes
{2D20FD5A-76C4-4D5C-9AE6-B17DCA5791E6}  2014-06-20 13:28:08:598+0200    1   147 101 {00000000-0000-0000-0000-000000000000}  0   0   AutomaticUpdates    Success Software Synchronization    Windows Update Client successfully detected 1 updates.
{C54F5E46-367B-45FA-82AB-3CB90D50FC50}  2014-06-20 13:28:08:598+0200    1   156 101 {00000000-0000-0000-0000-000000000000}  0   0   AutomaticUpdates    Success Pre-Deployment Check    Reporting client status.
{F6B4A13E-E0F3-46A2-B1BB-A6A3341D86F0}  2014-06-20 13:28:21:229+0200    1   147 101 {00000000-0000-0000-0000-000000000000}  0   0   AutomaticUpdates    Success Software Synchronization    Windows Update Client successfully detected 1 updates.
{211568CA-334C-46D2-8EAC-DF0CA3307CD7}  2014-06-20 13:28:21:229+0200    1   156 101 {00000000-0000-0000-0000-000000000000}  0   0   AutomaticUpdates    Success Pre-Deployment Check    Reporting client status.
{B8498456-8BDF-48DB-9CF5-F9944F398C17}  2014-06-20 13:28:50:343+0200    1   147 101 {00000000-0000-0000-0000-000000000000}  0   0   AutomaticUpdates    Success Software Synchronization    Windows Update Client successfully detected 1 updates.
{CE6872DC-ED50-4523-AA21-C33292D9EB55}  2014-06-20 13:28:50:344+0200    1   156 101 {00000000-0000-0000-0000-000000000000}  0   0   AutomaticUpdates    Success Pre-Deployment Check    Reporting client status.
{2B392999-4411-4FB1-91BE-7224B2BFDCEA}  2014-06-20 13:40:38:396+0200    1   182 101 {9C7482D5-707E-49E7-8731-E58ADD05037A}  2   80070643    AutomaticUpdates    Failure Content Install Installation Failure: Windows failed to install the following update with error 0x80070643: Adobe Reader XI 11.0.07 - Deutsch.
{3E15515C-42DC-49F8-B46E-AC95414FB953}  2014-06-20 13:40:46:650+0200    1   189 102 {00000000-0000-0000-0000-000000000000}  0   0   AutomaticUpdates    Success Content Install Installation Ready: The following updates are downloaded and ready for installation. To install the updates, an administrator should log on to this computer and Windows will prompt with further instructions:  - Adobe Reader XI 11.0.07 - Deutsch
The WSUS Update Files are all downloaded to the client look like correct
Image

Do you see my mistake?
Editor
Jun 20, 2014 at 2:00 PM
You don't need to create a custom update. Pls look at this small howto:
http://www.mysysadmintips.com/windows/active-directory/24-deploy-adobe-reader-using-group-policy

Download the EXE, extract the EXE, pick up every file incl. MSI in a download folder. After this create a 'nomal' update in WPP like this: https://www.codeplex.com/Download?ProjectName=WsusPackagePublisher&DownloadId=663365 You don't need to create a custom update, Registry settings you can deploy with Group Policy Preferences.
Jun 20, 2014 at 2:46 PM
Hello Winfried,

yes i need to because of my starting situation.

I have appropriated Adobe Reader XI 11.0.06 per GPO to all clients in our company. Therefor i made patched Package of Adobe Reader XI 11.0.00 with the command
o msiexec /a “C:\AdobeReader\AdbeRdr11000_AIP\AcroRead.msi“ /p “C:\AdobeReader\AdbeRdr11006_de_DE\ AdbeRdrUpd11006.msp”

This worked fine till to the clients in our stores which are connected through a slow VPN to our company.
An other disadvantage is that there is no report which clients have installed the software and which have not.

Now i cannot install the AdbeRdrUpd11007.msp without uninstalling the Adobe Reader XI 11.0.06. I tried it manually und it failed.

The only one that works is to uninstall it first (like my first cue in the custom update) and then install it again with the patch. I try to connect this steps in one update. And it works till the installation on my test clients.
Editor
Jun 20, 2014 at 3:06 PM
The following updates are downloaded and ready for installation. To install the updates, an administrator should log on to this computer and Windows will prompt >with further instructions: - Adobe Reader XI 11.0.07 - Deutsch
Maybe you need to reboot after uninstall. Try 2 updates, one for uninstall and the second one for install only.
Coordinator
Jun 20, 2014 at 8:11 PM
This is because you have write twice 'msiexec'. Once in the 'Path to the file' and second in the 'parameters' field !!!
Jun 24, 2014 at 10:36 AM
Edited Jun 24, 2014 at 10:56 AM
Thx, now i have fine working updates.

My solution:
  • Create a custom update with uninstalling Adobe Reader XI with
msiexec /x {AC76BA86-7AD7-1031-7B44-AB0000000001} /qn
and at next install Adobe Reader XI 11.0.00 with customized settings
msiexec -i AcroRead.msi TRANSFORMS=AcroRead.mst /qn
  • Using following Ruleset for this Update
  • installed
<lar:And>
    <msiar:MsiProductInstalled ProductCode="{ac76ba86-7ad7-1031-7b44-ab0000000001}"/>
        <lar:Or>
            <lar:And>
                <bar:Processor Architecture="0"/>
                <bar:FileExists Path="Adobe\Adobe Reader 11\Reader\AcroRd32.exe" Csidl="38"/>
            </lar:And>
            <lar:And>
                <bar:Processor Architecture="9"/>
                <bar:FileExists Path="Adobe\Adobe Reader 11\Reader\AcroRd32.exe" Csidl="42"/>
            </lar:And>
        </lar:Or>
</lar:And>
  • installable
<lar:Or>
    <lar:Not><msiar:MsiProductInstalled ProductCode="{ac76ba86-7ad7-1031-7b44-ab0000000001}"/></lar:Not>
        <lar:And>
            <msiar:MsiProductInstalled ProductCode="{ac76ba86-7ad7-1031-7b44-ab0000000001}"/>
                <lar:Or>
                    <lar:And>
                        <bar:Processor Architecture="0"/>
                        <lar:Not><bar:FileExists Path="Adobe\Adobe Reader 11\Reader\AcroRd32.exe" Csidl="38"/></lar:Not>
                    </lar:And>
                    <lar:And>
                        <bar:Processor Architecture="9"/>
                        <lar:Not><bar:FileExists Path="Adobe\Adobe Reader 11\Reader\AcroRd32.exe" Csidl="42"/></lar:Not>
                    </lar:And>
                </lar:Or>
        </lar:And>
</lar:Or>
  • Create an update for Adobe Reader XI 11.0.07 AdbeRdrUpd11007.msp which requires the Adobe Reader XI 11.0.00 Update without any rules
  • Deployment works on my Windows 7 32/64Bit fine and the Report in WPP shows the installed packages and instalable packages correctly
But there is another problem.
If i install Adobe Reader with the script with the same files in the published Package,
WPP shows me that the published Update is not applicable instead of is installed
msiexec -i "\\[SHARE]\AcroRead.msi" PATCH="\\[SHARE]\AdbeRdrUpd11007.msp" TRANSFORMS="[SHARE]\AcroRead.mst" /qn
Has someone else a similar problem?
Marked as answer by HermannKrebs on 6/26/2014 at 12:26 AM
Coordinator
Jun 24, 2014 at 5:35 PM
Please, check the path for the installation of Adobe Reader. For me it is : C:\Program Files (x86)\Adobe\Reader 11.0 \Reader
Jun 25, 2014 at 8:04 AM
DCourtel wrote:
Please, check the path for the installation of Adobe Reader. For me it is : C:\Program Files (x86)\Adobe\Reader 11.0 \Reader
I have changed the install path to C:\Program Files\Adobe\Adobe Reader 11\ and saved it in the AcroRead.mst so that the result of the prove after updating with the published package works right.

I really do not understand why WPP shows me that the update is not applicable if i install these package manually with script.

Next phenomenon located:
After installing published package correctly the WPP shows that the published package is installed;
after uninstalling it with script on the local client
msiexec /x {AC76BA86-7AD7-1031-7B44-AB0000000001} /qn
and installing it again manually with the script below the WPP shows again that the update is installed
msiexec -i "\\[SHARE]\AcroRead.msi" PATCH="\\[SHARE]\AdbeRdrUpd11007.msp" TRANSFORMS="[SHARE]\AcroRead.mst" /qn
Can i check the parts of my rules manually to differ the results?
Coordinator
Jun 25, 2014 at 7:25 PM
I really do not understand why WPP shows me that the update is not applicable if i install these package manually with script.
WPP shows you what it see in the Wsus server. Clients computers evaluate the 'Isinstalled' rule and the 'IsInstallable' rule and report their state to the Wsus server. Wpp query the Wsus server and show the result.
Can i check the parts of my rules manually to differ the results?
I never found a way to do that.
Jun 26, 2014 at 7:26 AM
OK

thx a lot for your help.

I think i can handle it.
Editor
Jun 26, 2014 at 11:07 AM
DCourtel wrote:
Please, check the path for the installation of Adobe Reader. For me it is : C:\Program Files (x86)\Adobe\Reader 11.0 \Reader
This is only the correct path on 64-Bit Windows. In a 32-Bit Windows it is C:\Program Files = %PROGRAMFILES%. ;)