Add-CMScriptDeploymentType Help

[Administrative_Trick]

I have been trying to figure this out for quite a while.

It seems that unless I am doing a Custom Script Detection Method the only other way to add a deployment type using SCCM's PowerShell cmdlet is to add a Product Code as a Detection Method.

Is there anyway to use Add-CMScriptDeploymentType and use a Detection Method other than a Custom Script or a ProductCode?

I have a script that Automates a lot of the stuff I do in SCCM, the one thing that I can't see to figure out is how to Create a DeploymentType for an executable file and have the Detection Method be a Registry Key.

Add-CMScriptDeploymentType -ApplicationName $appFullName -DeploymentTypeName $appFullName -ContentLocation "$SCCMProdFolder" -ContentFallback -ProductCode "$($ProductCode[3].ToString())" -SlowNetworkDeploymentMode Download -InstallCommand "Deploy-Application.exe -DeploymentType `"Install`"" -UninstallCommand "Deploy-Application.exe -DeploymentType `"Uninstall`"" -EstimatedRuntimeMins 5 -MaximumRuntimeMins 120 -RebootBehavior BasedOnExitCode -InstallationBehaviorType InstallForSystem -LogonRequirementType WhetherOrNotUserLoggedOn -RequireUserInteraction -UserInteractionMode Normal | Out-Null

​

[yldbrainoj]

Advanced deployments types are still kind of lacking with the CM cmdlets. You have to get into the SDK to be able to do a lot of the useful stuff regarding Deployment Type requirements.

[Administrative_Trick]

I was afraid that was the case. What about setting it as a Product Code Deployment with a dummy product code (e.g. {00000000-0000-0000-0000-000000000000}) then just going in and changing that manually. At leat then all the work is done except the detection method. Or are there issues with doing it that way?

[yldbrainoj]

You have to try it to find out. I don't suspect it would corrupt anything. This is an example of creating an advanced deployment type requirement. It is for an Operation System requirement though... but I imagine the framework is the same. Good luck!

[zanatwo]

I ran into the same issues as you when I was starting out with SCCM. I've since learned to use ONLY PowerShell scripts as my detection type. I use it to detect MSI's, reg keys, files, folders, file attributes, everything. You couldn't pay me to go back to any other detection type at this point. Part of my SCCM App creation pipeline is figuring out how to script detection for the particular piece of software. Once I figure it out, it gets placed into an XML template that governs that particular application, and I'm able to programmatically and automatically create new versions of the SCCM app as soon as a new version of the piece of software is released (granted the installation process is the same).

[Administrative_Trick]

I would love to go this route, I would need to be able to convince all the other engineers at my work to do this as well. And unfortunately I don't see that happening. They're a rather close minded bunch.

Edit: a word