We recently upgraded from ConfigMgr 1706 to 1806. I'm finding that when running the Add-CMScriptDeploymentType cmdlet, it fails with an AmbiguousParameterSet when both ProductCode and AddDetectionClause are specified (the application I'm adding needs both an MSI product code and a registry key detection). This wasn't happening before and appears to be a bug, as the parameter set I'm trying to use specifies the ProductCode as mandatory with the AddDetectionClause as optional (the parameter set I'm trying to use has ProductCode, DeploymentTypeName, InstallCommand and InputObject as the only mandatory parameters, according to the help).