09/19/2017 5415 views
I have created a new application and after deploying to a collection the clients fail to install with an exit code of 1636.

Here is a copy from AppEnforce.log:

+++ Starting Install enforcement for App DT "CYP - Adobe Acrobat Reader DC Updates" ApplicationDeliveryType - ScopeId_9EB2E062-0F62-4E1A-8CB0-FB0FE6DF2F18/DeploymentType_b2578833-0ec2-4347-b94f-fb00adb1f900, Revision - 5, ContentPath - C:\windows\ccmcache\n, Execution Context - System AppEnforce 19/09/2017 15:50:56 3128 (0x0C38)
    A user is logged on to the system. AppEnforce 19/09/2017 15:50:56 3128 (0x0C38)
    Performing detection of app deployment type CYP - Adobe Acrobat Reader DC Updates(ScopeId_9EB2E062-0F62-4E1A-8CB0-FB0FE6DF2F18/DeploymentType_b2578833-0ec2-4347-b94f-fb00adb1f900, revision 5) for system. AppEnforce 19/09/2017 15:50:56 3128 (0x0C38)
+++ Application not discovered. [AppDT Id: ScopeId_9EB2E062-0F62-4E1A-8CB0-FB0FE6DF2F18/DeploymentType_b2578833-0ec2-4347-b94f-fb00adb1f900, Revision: 5] AppEnforce 19/09/2017 15:50:56 3128 (0x0C38)
    App enforcement environment: 
Context: Machine
Command line: msiexec /p “AcroRdrDCUpd1701220093.msp” REINSTALLMODE=vomus REINSTALL=ALL
Allow user interaction: No
UI mode: 0
User token: null
Session Id: 1
Content path: C:\windows\ccmcache\n
Working directory: AppEnforce 19/09/2017 15:50:56 3128 (0x0C38)
    Prepared working directory: C:\windows\ccmcache\n AppEnforce 19/09/2017 15:50:57 3128 (0x0C38)
Found executable file msiexec with complete path C:\windows\system32\msiexec.exe AppEnforce 19/09/2017 15:50:57 3128 (0x0C38)
    Prepared command line: "C:\windows\system32\msiexec.exe" /p “AcroRdrDCUpd1701220093.msp” REINSTALLMODE=vomus REINSTALL=ALL /qn AppEnforce 19/09/2017 15:50:57 3128 (0x0C38)
    Executing Command line: "C:\windows\system32\msiexec.exe" /p “AcroRdrDCUpd1701220093.msp” REINSTALLMODE=vomus REINSTALL=ALL /qn with user context AppEnforce 19/09/2017 15:50:57 3128 (0x0C38)
    Working directory C:\windows\ccmcache\n AppEnforce 19/09/2017 15:50:57 3128 (0x0C38)
    Post install behavior is BasedOnExitCode AppEnforce 19/09/2017 15:50:57 3128 (0x0C38)
    Waiting for process 4972 to finish.  Timeout = 120 minutes. AppEnforce 19/09/2017 15:50:57 3128 (0x0C38)
    Process 4972 terminated with exitcode: 1636 AppEnforce 19/09/2017 15:50:57 3128 (0x0C38)
    Looking for exit code 1636 in exit codes table... AppEnforce 19/09/2017 15:50:57 3128 (0x0C38)
    Unmatched exit code (1636) is considered an execution failure. AppEnforce 19/09/2017 15:50:57 3128 (0x0C38)
++++++ App enforcement completed (0 seconds) for App DT "CYP - Adobe Acrobat Reader DC Updates" [ScopeId_9EB2E062-0F62-4E1A-8CB0-FB0FE6DF2F18/DeploymentType_b2578833-0ec2-4347-b94f-fb00adb1f900], Revision: 5, User SID: ] ++++++ AppEnforce 19/09/2017 15:50:57 3128 (0x0C38)

I know I can deploy the msp using a package but am interested in using the app method so I can control deploying the updates to machines that only have adobe reader already installed (I guess I could make a collection for this to deploy a package to).. but i am interested to why this method is failing.

Many thanks.
0 Comments   [ + ] Show comments


All Answers

1636 means that the WI engine couldn't load the MSP:

Command line: msiexec /p “AcroRdrDCUpd1701220093.msp” REINSTALLMODE=vomus REINSTALL=ALL

I always, always, ALWAYS use explicit paths when dealing with files and folders. How? By adding the old favourite dodge, %~DP0, as a prefix to file/folder names.
Answered 09/19/2017 by: VBScab
Red Belt