Adobe Acrobat Pro

[scopa]

MSI install using Transform and Patch but install fails with Exit Code 1603. MSI, MSP, MST all in toolkit files folder. Can someone tell me what I am doing wrong.

MST is configured to remove all versions of Adobe (currently installed is x86 version). Version being installed is x64.

What am I doing wrong?

Execute-MSI -Action Install -Path 'AcroPro.msi' -Transform 'AcroPro.mst' -Patch 'AcrobatDCx64Upd2400220991.msp

[Installation] :: Executing [C:\Windows\System32\msiexec.exe /i "C:\Users\user\OneDrive - \2020 - intune\2024 Intune Deployment\Adobe\Toolkit\Files\AcroPro.msi" 
TRANSFORMS="C:\Users\user\OneDrive - \2020 - intune\2024 Intune Deployment\Adobe\Toolkit\Files\AcroPro.mst" 
TRANSFORMSSECURE=1 REBOOT=ReallySuppress /QB-! /L*v "C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\AcroPro_Install.log"]...	Execute-Process	8/[Installation]
Getting message for exit code [1603].
Get-MsiExitCodeMessage	8/23/2024 3:30:22 PM
11140 (0x2B84)23/2024 3:30:21 PM	11140 (0x2B84)

Thanks
Scott

[That-Annoying-Guy]

Look in "C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\AcroPro_Install.log"
to see what is causing MSI Error 1603.

[scopa]

Nothing useful

<![LOG[[Installation] :: Executing [C:\Windows\System32\msiexec.exe /i “C:\Users\user\OneDrive - \2020 - intune\2024 Intune Deployment\Adobe\Toolkit\Files\AcroPro.msi” TRANSFORMS=“C:\Users\user\OneDrive -\2020 - intune\2024 Intune Deployment\Adobe\Toolkit\Files\AcroPro.mst” TRANSFORMSSECURE=1 REBOOT=ReallySuppress /QB-! /L*v “C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\AcroPro_Install.log”]…]LOG]!><time=“16:26:51.697-240” date=“08-23-2024” component=“Execute-Process” context=“me” type=“1” thread=“7996” file=“Deploy-Application.ps1”>
<![LOG[[Installation] :: Getting message for exit code [1603].]LOG]!><time=“16:26:53.572-240” date=“08-23-2024” component=“Get-MsiExitCodeMessage” context=“me” type=“1” thread=“7996” file=“Deploy-Application.ps1”>
<![LOG[[Installation] :: Execution failed with exit code [1603].]LOG]!><time=“16:26:53.593-240” date=“08-23-2024” component=“Execute-Process” context=“me” type=“3” thread=“7996” file=“Deploy-Application.ps1”>
<![LOG[[Installation] :: Closing the installation progress dialog.]LOG]!><time=“16:26:53.647-240” date=“08-23-2024” component=“Close-InstallationProgress” context=“me” type=“1” thread=“7996” file=“Deploy-Application.ps1”>
<![LOG[[Installation] :: Closing the installation progress dialog’s runspace.]LOG]!><time=“16:26:53.691-240” date=“08-23-2024” component=“Close-InstallationProgress” context=“me” type=“1” thread=“7996” file=“Deploy-Application.ps1”>

[scopa]

First tried relying on MST to remove previous installations. Currently ‘Adobe Acrobat DC’ is installed (x86 version).

When that did not work I tried adding a function in MAIN

function Remove-AdobeAcrobat {
    $adobeAcrobat = Get-InstalledApplication | Where-Object { $_.DisplayName -like 'Adobe Acrobat DC'}
}

if ($adobeAcrobat) {
    Remove-MSIApplications -Name 'Adobe Acrobat DC'
    }

And I call Remove-AdobeAcrobat in Deploy - Pre-Installation section. But that never even runs.

If I run AcroPro.msi on it’s own to see what happens. I get an message

Setup has detected that you already have a more functional product installed. Setup will not terminate.

Installed version - Adobe Acrobat Pro DC Version 21.005.20058 (32bit)
New Version - Adobe Acrobat Pro 24.1 (64x)

[That-Annoying-Guy]

This log file is from PSADT.
The one you need is the one msiexec.exe creates as per the log file snippet your top post.

Maybe add the -LogName for Execute-MSI if you want change the name.

FYI: Error 1603 is an MSI error. Usually it means something is wrong in the MSI, MST and/or MSP file(s). Sometimes the error occurs way before MSIexec.exe reports it as 1603 in the MSI log file and that other error is the true cause of the 1603 error.

[KushPat]

I hate Adobe and I deal with it monthly now but I made it into JSON format so I just don’t touch main package anymore.
However, to remove older version, I will say just use one command line, if it’s installed - it will remove, if not, it won’t remove it.

Remove-MSIApplications -Name "Adobe Acrobat DC"

Also, regarding installation, I will say to just run msi and mst together and then MSP seperately.

Execute-MSI -Action Install -Path "$dirFiles\AcroPro.msi" -Transform "$dirFiles\AcroPro.mst"
Execute-MSP -Path "$dirFiles\AcrobatDCx64Upd2400220991.msp" -AddParameters '/QN'

My environment has bunch of different versions of Adobe so I check in Pre-Installation to see if those are installed, then I exit, if not, I continue with installation.
I just did upgrade from x32 to x64.
Also, always a good place to start is from MSI Log file. Once you get the msi log file, start from bottom and above where it usually says “Installer installed the product successfully” (or something like that), keep scrolling up and you will read the reason why it failed. If you have msi log file, feel free to post that, we can review and assist further

[Adrian_Scott]

@KushPat

I hate Adobe and I deal with it monthly now

I’m with you on that one @KushPat
Why Adobe have to make their installers so damn picky and unlike any other installer I just don’t understand their logic? Add to that the size of the installs makes pushing out new versions to fix security updates just tedious repetition.
We’ve gone to doing an annual full version upgrade (new install) and relying on Adobe’s RUM to keep versions up to date in the mean time (and thanks to the power of Intune Remediations, we can force our devices to run RUM on a daily basis).

[scopa]

thanks - you were correct. Issue was with the MSI itself.

Can I ask you - what is the best way to run a Pre-Installation check that if program name is Adobe Acrobat (regardless of Version) uninstall it. Then proceed. I tried adding a Function in MAIN - and I call Remove-AdobeAcrobat in Pre-Installation section but it never runs. If I replace the function and just hardcode msiexec x{GUID} it will uninstall Adobe Acrobat DC

function Remove-AdobeAcrobat {
    $adobeAcrobat = Get-InstalledApplication | Where-Object { $_.DisplayName -like 'Adobe Acrobat DC'}

    if ($adobeAcrobat) {
    Remove-MSIApplications -Name 'Adobe Acrobat DC'
        }
    }

[scopa]

@KushPat

Remove-MSIApplications -Name "Adobe Acrobat DC"

Thanks -

Will try - looks like my fail 1603 is that the MSI I am getting from Adobe admin portal is an old package. Older version that currently installed x86 - will reach out to Adobe as to why I can’t get an up to date version from the pacakage portal

[Gordy_B]

Just an FYI, Adobe Acrobat Reader is now a MS Store App via Intune. You wont need to package again.

[That-Annoying-Guy]

sure if you don’t need to tweak it to remove ads, desktop shortcut. Add trusted paths and host, etc.

[KushPat]

When I recently upgraded x86 to x64, I had to do hardening standard given by CISO and I found out that you actually install AcroPro.msi, and then it applies the free Patch, making PAID version of Adobe - free.
Yeah, weird, I know, we have to thank Adobe for it.
Also, I had users with SAME DisplayName who was using the software and paying for it so for free version of Adobe Acrobat Reader x64, I renamed the DisplayName and use that as DM.

[Gordy_B]

The desktop shortcut can be removed with either a remediation or platform script in Intune. Not had any reports of ads (as of yet).