143 votesstarted · AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Changing status back to “Started” as there’s more work to do here. We plan to simplify adding requirements to DTs as well as complete the missing scenarios for detection methods in a future release. Stay tuned for more updates.
An error occurred while saving the commentTony Morrow commented
Enhanced Detection Rules and Requirements are two different things. For example, we use a requirement to ensure the ActiveX version of Adobe Flash player is not installed on computers running Windows 8.1+ because the install will fail. Currently I do not see an easy way to define a "requirement" for a deployment type. The "Add-CM***DeploymentType CMDlet has a parameter called "-AddRequirement", but it requires a "Microsoft.SystemManagementServer.DesiredConfigurationManagement.Rules.Rule" object and I don't see a cmdlet to create that type of object.
Raphael Perez from http://www.thedesktopteam.com created a powershell cmdlet in 2015 to define a requirement and add it to a deployment type, but it would be really helpful to define requirement objects and feed them to the deploymenttype cmdlets, similar to the cmdlets for creating detection rules and dependencies.
Updated by bobmn for sangeev/OSD