Closed AlBrough closed 2 years ago
Thanks @AlBrough for taking the time to share this with the Configuration Manager documentation team. I’m sorry that you’re having problems, and I want to make sure it gets to the right people that can help. There are a couple of options available to provide the best level of support for this:
I wasn't able to reproduce your issue, even creating the same registry type detection rule on an app deployment type. The Get-CMDeploymentTypeDetectionClause cmdlet returns the detection rules from the deployment type.
I'm closing this issue as there's nothing actionable for docs at this time.
I have the following script below as per the example on the page, it does however not return a result when running the Get-CMDeploymentTypeDetectionClause cmdlet. The inputObject variable, when queried, is populated correctly by the Get-CMDeploymentType cmdlet.
$inputObject = Get-CMDeploymentType -ApplicationName "Office 365 2102 SAC x64 Visio Std" -DeploymentTypeName "Office 365 Default Deployment Type"
Get-CMDeploymentTypeDetectionClause -InputObject $inputObject
Entries confirmed exist against the application detection.
Running MECM CB 2107
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.