4.1.5 - Application packaged and deployed in SCCM fails immediately

Hi All!

I'm fairly new when it comes to packaging and deploying applications through PSADT but have been able to deploy a lot of applications successfully in the old 3.x.x frameworks. Since 4.1.0 and above were released, I've tried to take one of my previous deployments and convert it to run on this newer framework. When I test the application manually on my machine by running the command "Powershell.exe -ExecutionPolicy Bypass .\Invoke-AppDeployToolkit.exe -DeploymentType Install -DeployMode Interactive" through Powershell, it runs as expected and works without any problems.

The issue occurs when I package my application in SCCM and try to deploy it to systems as Available to test the install and uninstall methods as when I try to hit Install, Software Center immediately throws the error 0x87D00324 stating that the application was not detected after the installation completed. My PSADT windows still appear prompting that the installation is about to commence and the installation still runs and if I hit Retry, it then appears as installed.

I am not sure why it is failing instantly as my appenforce logs look to show the processes running for the installation and at the same time immediately says the process has been terminated with an exit code 0, so it is instantly thinking that it has been installed before my PSADT windows appear for the user.

I've tested this on PSADT 4.1.3 and 4.1.5 and have the same issue. I don't remember doing anything specific in older versions of PSADT such as waiting for processes. I am not sure if it's to do with how the new framework works and now running steps for invocation and initializing the deployment.

You're using PowerShell to try and start an executable. Just call the exe, or change the extension to .ps1 and it should be fine.

2 Likes