**Edit 2014/10/31 : I’m still struggling to make this cmdlet work with a Required schedule even if Microsoft says it’s fixed. If you have been able to make it work, leave a comment in this post. Start-cmpackagedeployment error **
**Edit 2014/06/27 : This issue is supposedly fix with R2 CU2 **
The Start-CMPackageDeployment cmdlet is failing with the following error when creating a “Required” deployment with a schedule.
This CMDLet starts the deployment of a software package to a Configuration Manager collection.
Run SCCM cmdlets and scripts by using the SCCM console or by using a Windows PowerShell session. When you run SCCM cmdlets by using the SCCM console, your session runs in the context of the site.
Example : Start-CMPackageDeployment -CollectionName “$Name” -PackageId $PkgId -StandardProgramName “Install” -DeployPurpose Available -DeploymentAvailableDay “2014/06/13” -DeploymentAvailableTime “12:12” -DeploymentStartDay “2014/06/19” -DeploymentStartTime “2:45”-RerunBehavior RerunIfFailedPreviousAttempt -SoftwareInstallation $True -SystemRestart $False
Error : Start-CMPackageDeployment : Parameter set cannot be resolved using the specified named parameters.
I’ve filed a Microsoft Connect case concerning the issues :
The Microsoft Team confirmed the bug and post this :
Thanks for the feedback. This issue should be resolved in the upcoming R2 CU2 release.
I’ll update this post when CU2 gets available and confirmed that it’s resolved.
Let us know if this tip was helpful for you by using the comments section.
Founder of System Center Dudes. Based in Montreal, Canada, Senior Microsoft SCCM Consultant, 5 times Enterprise Mobility MVP. Working in the industry since 1999. His specialization is designing, deploying and configuring SCCM, mass deployment of Windows operating systems, Office 365 and Intunes deployments.