I found this thread from last November, but it really doesn't answer my question. I was trying to deploy an application and a patch together using an application in SCCM 2012.
My first attempt was to create an application in SCCM 2012 with an MSI deployment type and the following command line:
msiexec.exe /i MyApp.msi PATCH="%CD%\MyAppPatch.msp" /q
This command line works when invoked manually in a command window, but fails in SCCM 2012 with an "Error 1635" indicated in the AppEnforce.log in CCM\logs.
So I tried separating the two parts into two deployment types with second dependent on the first as follows:
msiexec.exe /i MyApp.msi /q
msiexec.exe /update "%CD%\MyAppPatch.msp" /q
Now the initial App gets installed but the patch fails with an "Error 1636" indicated in the AppEnforce.log in CCM\logs. The windows application log only shows the transaction for the MSI completing, but there is no indication of the patch running or even starting. The only error I get is as stated in the CCM\logs. Both these command lines work correctly when I invoke them manually in a command window. I even tried opening a command window and navigating to the appropriate ccmcache folder and invoking the above-noted update command line; the patch installed manually.
Is there something in the Config Manager client that would impede this patch or have I missed something in creating the app in SCCM 2012?