Troubleshoot application installation
-
Thursday, October 18, 2012 1:19 PM
I'm quite new to MDT so bear with me if I missed something basic or obvious.
I have a few applications in an inherited MDT setup that are installed with powershell scripts. They are installed through install single application steps located in the state restore->install applications phase in a task sequence.
The ZTIApplication log shows the installation as successful and I don't see any obvious errors in the windows event log either.
Excerpt from the ZTIApplication log:
Validating connection to \\shareserver\DeploymentShare$\Applications\Microsoft Forefront Endpoint Protection
Already connected to server shareserver as that is where this script is running from.
Change directory: \\shareserver\DeploymentShare$\Applications\Microsoft Forefront Endpoint Protection
Run Command: \\shareserver\DeploymentShare$\Tools\X64\bddrun.exe powershell.exe -NoProfile -ExecutionPolicy Bypass -File "Install-FEP.ps1"
ZTI installing application
About to run command: \\shareserver\DeploymentShare$\Tools\X64\bddrun.exe powershell.exe -NoProfile -ExecutionPolicy Bypass -File "Install-FEP.ps1"
Return code from command = 0
Application Microsoft Forefront Endpoint Protection installed successfullyBut FEP is not installed on the computer.
What would the next step be for troubleshooting this?
All Replies
-
Thursday, October 18, 2012 9:29 PM
Hi,
The next step would be for you to run your code on a machine and see what's happening with it.
What's happening here is that MDT runs the run command line and it ends without an issue. Hence the success code. MDT is oblivious to the fact that the code did not run as expected. Post your code and I'll take a look at it.
Also, if you run your code in a Run PowerShell script task sequence step then MDT will report back any errors the script returns.
Blog: http://scriptimus.wordpress.com
- Marked As Answer by Molotch Friday, October 19, 2012 8:37 AM
-
Friday, October 19, 2012 8:37 AM
Hi,
Thank you for your help. I ran the scripts locally and the problem was that we had enabled ExexutionPolicy Allsigned through group policy, since the computer is joined to the domain before the state restore phase and none of the scripts is signed they weren't allowed to be run. I tried signing one and it installed just fine.
- Marked As Answer by Molotch Friday, October 19, 2012 8:37 AM

