Apologies for the long therad title.
Lets take things in reverse:
I have an application that i wish to deploy during OSD. The application needs one deployment type for OSD, and one deployment type for regular installations. I've created two deployment types, and placed the one for OSD as highest priority to be selected first.
On the OSD deployment type, as a requirement, i've set a custom Global Condition in order to evaluate if the TS manager is running on the computer (which would then indicate a OSD deployment).
The custom Global Condition is created as a script with boolean data type. The script is powershell, and consists of one line to return 'true' if TSManager process is running: [bool] (Get-Process TSmanager ea 0)
I've tested this by the command console during OSD, and the script works fine. The boolean value should then be returned to configmgr, and the requirement for my OSD deployment type to be selected for installation.
During the task sequence, i also make sure to enable the execution of unsigned PowerShell scripts using the command powershell.exe -Command "Set-ExecutionPolicy Unrestricted" This command also works, and i've verified this from the command prompt during OSD using the Get-ExecutionPolicy powershell command.
However, when my application is to be evaluated the task sequence fails with the generic error 0x80004005. I can't seemto find which logs that will help me troubleshoot the problem.
I've made sure to enable powershell support for my boot image.
Can someone help shed some light on what i'm doing wrong?
- Edited by David.Petersen Friday, January 17, 2014 12:51 PM