I think the answer is, write them yourself, at the moment... The requirements and other settings can be accessed and modified using variations on this posted script (deserialize, edit and reserialize the XML content). In the comments, Derek says he has posted a request to Connect for a Requirements cmdlet. http://andrewdcraig.wordpress.com/2013/01/31/configmgr-2012-change-application-source-path/
Here is also one to get the dependencies. http://andrewdcraig.wordpress.com/2013/05/03/create-a-tree-view-of-applications-and-dependencies/ For Dependencies you need to access the relationships class. Hth Von: [email protected] [mailto:[email protected]] Im Auftrag von Ryan Gesendet: Dienstag, 14. Mai 2013 17:11 An: [email protected] Betreff: [mssms] Set-CMDeploymentType Let's pretend the 2012 cmdlets are working perfectly, is there any way to set: Requirements Enhanced Detection Methods (you can set script detection methods, what about the others?) Return Codes Dependencies with the Powershell cmdlets, or any command line option? I don't see anything that looks like it would work in the Powershell cmdlets. I want to write a template deployment type since so many fields are always going to be the same thing for us. I'll probably look into writing a C# program to do this if I can't do it with Powershell, it'd just be much faster if I could stick with what I know best and do it in Powershell. If the option is available in the cmdlets and it's just broken, I'll probably just wait for Microsoft to fix it rather than coding something myself.
