Hi All,
I use MDT 2012 and SCCM Task Sequences. I have finally created a PowerShell script which relies on Parameters that match a PARAM statement within the script. when the MDT Run PowerShell script executes I look to see if the variables I am expecting to be instantiated when the parameters are supplied are, in fact created and available.
The issue I have is that the supplied parameters in the Run Powershell task sequence step are not being read/used. I have attached and image of the PowerShell script step.
If I run the script manually it is all good to go. It is something to do with ZTIPowershell.wsf but I am hesitant to edit that file.
I have looked in the BDD.LOG and it confirms that the parameters that I am supplying are not being created. If the parameters are not supplied, the variables that I rely on do not created. My script looks to see if they exist and, if not I throw an error which is recorded in the BDD.LOG log file.
I am going to try a "Run Command Line" task sequence step instead.
Any thoughts?
Image may be NSFW.
Clik here to view.
NSutton