v4.06-Errors while installing MSI

The Toolkit General Discussion
1

Hi,

I’m still pretty new to the App Deployment Toolkit. I’ve already packaged and deployed two apps using it through Intune, and those went smoothly. But of course, on the third try, I hit a wall.

Here’s the deal: I’m using version 4.06 and trying to deploy an MSI installer. The installer works fine when I run it locally through the command line with silent switches — so I figured this would be a breeze.

Nope.

First, I tried the zero-config method. Dropped the MSI into the Files folder and left Deploy-Application.ps1 basically empty. That gave me an ADT-Process error 1603 when I was using Intune. Locally ran the script and it installs the software.

Then I tried adding this to the install block:
Start-ADTProcess -FilePath "xx.msi" -Argument "S"
Realized I didn’t need the argument, so I removed it — still got an error saying it’s not a valid application for this OS platform.

Next, I tried Start-ADTMSIProcess -FilePath, but that threw a 60001 syntax error. Locally ran the script and it installs the software.

So I ditched the zero-config idea and filled in the $appName variable, then used:
Start-ADTMSIProcess -FilePath "xx.msi"
Still no luck — Intune threw the random XX has failed.

I know version 4.05 had a bug with zero-config MSI installs, which is why I upgraded to 4.06. But I feel like I’m missing something super small and obvious… I just can’t figure out what it is.

Help?

2

A full log might help? All we have here are smatterings of info.

2 Likes
3

Sure. Sorry, I should’ve included it in my post.

Found no application based on the supplied FilterScript.]LOG]!><time= component="Get-ADTApplication" context="NT AUTHORITY\SYSTEM" type="1" thread="23280" file="C:\WINDOWS\IMECache\69d4b1d7-9d33-4b50-a820-50d949baf7db_12\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Install] :: [C:\WINDOWS\system32\msiexec.exe] is a valid fully qualified path, continue.]LOG]!><time="" date="" component="Start-ADTProcess" context="NT AUTHORITY\SYSTEM" type="1" thread="23280" file="C:\WINDOWS\IMECache\69d4b1d7-9d33-4b50-a820-50d949baf7db_12\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Install] :: Checking to see if mutex [Global\_MSIExecute] is available. Wait up to [10 minute(s)] for the mutex to become available.]LOG]!><time="" date="" component="Test-ADTMutexAvailability" context="NT AUTHORITY\SYSTEM" type="1" thread="23280" file="C:\WINDOWS\IMECache\69d4b1d7-9d33-4b50-a820-50d949baf7db_12\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Install] :: Mutex [Global\_MSIExecute] is available for an exclusive lock.]LOG]!><time="" date="" component="Test-ADTMutexAvailability" context="NT AUTHORITY\SYSTEM" type="1" thread="23280" file="C:\WINDOWS\IMECache\69d4b1d7-9d33-4b50-a820-50d949baf7db_12\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Install] :: Working Directory is [C:\WINDOWS\IMECache\69d4b1d7-9d33-4b50-a820-50d949baf7db_12\Files].]LOG]!><time="" date="" component="Start-ADTProcess" context="NT AUTHORITY\SYSTEM" type="1" thread="23280" file="C:\WINDOWS\IMECache\69d4b1d7-9d33-4b50-a820-50d949baf7db_12\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Install] :: Executing [C:\WINDOWS\system32\msiexec.exe /i "C:\WINDOWS\IMECache\69d4b1d7-9d33-4b50-a820-50d949baf7db_12\Files\_2.3.6_Windows_64bit.msi" REBOOT=ReallySuppress /QB-! /L*V "C:\WINDOWS\Logs\Software\"]...]LOG]!><time= component="Start-ADTProcess" context="NT AUTHORITY\SYSTEM" type="1" thread="23280" file="C:\WINDOWS\IMECache\69d4b1d7-9d33-4b50-a820-50d949baf7db_12\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Install] :: Execution failed with exit code [1603].]LOG]!><time="" date="" component="Start-ADTProcess" context="NT AUTHORITY\SYSTEM" type="3" thread="23280" file="C:\WINDOWS\IMECache\69d4b1d7-9d33-4b50-a820-50d949baf7db_12\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Install] :: Execution failed with exit code [1603].
Error Record:
-------------
 
Message               : Execution failed with exit code [1603].
 
FullyQualifiedErrorId : ProcessExitCodeError,Start-ADTMsiProcess
ScriptStackTrace      : at Start-ADTProcess<Process>, C:\WINDOWS\IMECache\69d4b1d7-9d33-4b50-a820-50d949baf7db_12\PSAppDeployToolkit\PSAppDeployToolkit.psm1: line 20256
at Start-ADTMsiProcess<Process>, C:\WINDOWS\IMECache\69d4b1d7-9d33-4b50-a820-50d949baf7db_12\PSAppDeployToolkit\PSAppDeployToolkit.psm1: line 19546
at Install-ADTDeployment, C:\WINDOWS\IMECache\69d4b1d7-9d33-4b50-a820-50d949baf7db_12\Invoke-AppDeployToolkit.ps1: line 156
at <ScriptBlock>, C:\WINDOWS\IMECache\69d4b1d7-9d33-4b50-a820-50d949baf7db_12\Invoke-AppDeployToolkit.ps1: line 313
 
PositionMessage       : At C:\WINDOWS\IMECache\69d4b1d7-9d33-4b50-a820-50d949baf7db_12\Invoke-AppDeployToolkit.ps1:156 char:9
+         Start-ADTMsiProcess -FilePath 'Setup_Windows_64bi ...
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
]LOG]!><time="" date="" component="Start-ADTMsiProcess" context="NT AUTHORITY\SYSTEM" type="3" thread="23280" file="C:\WINDOWS\IMECache\69d4b1d7-9d33-4b50-a820-50d949baf7db_12\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Install] :: Error Record:
-------------
 
Message               : Execution failed with exit code [1603].
 
FullyQualifiedErrorId : ProcessExitCodeError,Start-ADTMsiProcess
ScriptStackTrace      : at Start-ADTProcess<Process>, C:\WINDOWS\IMECache\69d4b1d7-9d33-4b50-a820-50d949baf7db_12\PSAppDeployToolkit\PSAppDeployToolkit.psm1: line 20256
at Start-ADTMsiProcess<Process>, C:\WINDOWS\IMECache\69d4b1d7-9d33-4b50-a820-50d949baf7db_12\PSAppDeployToolkit\PSAppDeployToolkit.psm1: line 19546
at Install-ADTDeployment, C:\WINDOWS\IMECache\69d4b1d7-9d33-4b50-a820-50d949baf7db_12\Invoke-AppDeployToolkit.ps1: line 156
at <ScriptBlock>, C:\WINDOWS\IMECache\69d4b1d7-9d33-4b50-a820-50d949baf7db_12\Invoke-AppDeployToolkit.ps1: line 313
 
PositionMessage       : At C:\WINDOWS\IMECache\69d4b1d7-9d33-4b50-a820-50d949baf7db_12\Invoke-AppDeployToolkit.ps1:156 char:9
+         Start-ADTMsiProcess -FilePath 'Windows_64bi ...
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
]LOG]!><time="component="Invoke-AppDeployToolkit.ps1" context="NT AUTHORITY\SYSTEM" type="3" thread="23280" file="C:\WINDOWS\IMECache\69d4b1d7-9d33-4b50-a820-50d949baf7db_12\Invoke-AppDeployToolkit.ps1">
<![LOG[[Finalization] :: Closing the installation progress dialog.]LOG]!><time=" date="" component="Close-ADTInstallationProgressFluent" context="NT AUTHORITY\SYSTEM" type="1" thread="23280" file="C:\WINDOWS\IMECache\69d4b1d7-9d33-4b50-a820-50d949baf7db_12\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Finalization] :: [Setup] install completed with exit code [60001].]LOG]!><time="" date="" component="Close-ADTSession" context="NT AUTHORITY\SYSTEM" type="3" thread="23280" file="C:\WINDOWS\IMECache\69d4b1d7-9d33-4b50-a820-50d949baf7db_12\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Finalization] :: *******************************************************************************]LOG]!><time="" date="" component="Close-ADTSession" context="NT AUTHORITY\SYSTEM" type="1" thread="23280" file="C:\WINDOWS\IMECache\69d4b1d7-9d33-4b50-a820-50d949baf7db_12\PSAppDeployToolkit\PSAppDeployToolkit.psm1">

Looks like an exit code 1603. If I’m reading the forums right, it seems to be the msiexec command with the parameters not being right? But why would the software install when I run it locally?

4

MSI error 1603 usually means your MSI is broken.

You’d need to create a log file for the MSI to find out why.

5

Would this would be the correct command:

Execute-MSI -Action Install -Path “YourPackage.msi” -Parameters “/qn” -LogName “YourPackage_Install.log”

6

Amazingly there are no examples in the docs with the ‘-LogFileName’ parameter so here’s one that works:

Start-ADTMsiProcess -FilePath "$($adtSession.dirFiles)\YourPackage.msi" -Action Install -LogFileName "YourPackage_MSI"

I add the _MSI because some apps have both an EXE and an MSI to install.

7

Amazing. Thank you!

I’ll try this out and report back on this thread.

1 Like
8

There’s no example because all MSI operations log to an automatically generated file in the same path as the toolkit’s log anyway.

9

I think I found out what was creating the problem.

The MSI seems to be trying to install the software in the user folder. However, when the software is getting pushed from Intune, it’s a system installation. I think that’s why its failing. The installation is trying to write to a user folder.

Now I’m thinking that maybe I could change the directory of where it would be installed.
If I wanted to install the program in Program files, could the above work?

Start-ADTMsiProcess -FilePath "$($adtSession.dirFiles)\YourPackage.msi" -Action Install -AdditionalArgumentList 'INSTALLDIR="C:\Program Files\NameofSoftware" '

1 Like
10

That will work.

FYI: if your MSI or Setup.exe is in the \Files\ folder, you can just omit the $($adtSession.dirFiles)\ like this:

Start-ADTMsiProcess -FilePath "YourPackage.msi" -Action Install -AdditionalArgumentList 'INSTALLDIR="C:\Program Files\NameofSoftware"'

11

You should be trying with -AdditionalArgumentList 'ALLUSERS=1' as that will likely address your issue in the correct manner.

1 Like
12

That’s true. I forgot because I have that as part of my default MSI parameters in my config.psd1.

In fact, we’ve been using the following for 15+ years:
ALLUSERS=1 TRANSFORMSSECURE=1 ROOTDRIVE=C:\ ARPNOREPAIR=1 REBOOT=ReallySuppress /QB-!

13

Thanks for the all the tips!!

Start-ADTMsiProcess -FilePath “YourPackage.msi” -Action Install -AdditionalArgumentList ‘INSTALLDIR=“C:\Program Files\NameofSoftware”’

-AdditionalArgumentList ‘ALLUSERS=1’"

The two above commands worked. I started to put on my thinking cap on when we looked at the MSI log.

Case closed!

Thanks again.

2 Likes
14

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.