9 Known Issues with SCCM ConfigMgr PowerShell

9 Known Issues with SCCM ConfigMgr PowerShell. Microsoft has released SCCM 2012 R2 CU1. Along with ConfigMgr 2012 R2 CU1 release, Microsoft released kb/2932274. 

The KB article describes the Windows PowerShell issues fixed in Cumulative Update 1 (CU1) for SCCM 2012 R2.

9 Known Issues with SCCM ConfigMgr PowerShell

KB2932274 also contains very useful information about the know issues with PowerShell (even after installing SCCM 2012 R2 CU1). There are 9 documented known issues with Powershell.

I hope we don’t have to maintain another list of known and unknown issues.

1. Install-CMClient will not target all computers in a collection when the -collection ID parameter is used. To work around this issue, retrieve a set of devices by using Get-CMDevice -CollectionID, and pass each instance into Install -CMDevice -Device. For example, run the following command: Get-CMDevice -CollectionName MyCollection | foreach { Install-CMClient -Device $_ -IncludeDomainController $false -AlwaysInstallClient $false -ForceReinstall $false -SiteCode PSS } 
2. Start-CMDistributionPointUpgrade does not work with secondary sites. To work around this issue, perform the task by using the Administrator Console.
3. Save-CMSoftwareUpdate cmdlet does not work in a 64-bit Windows PowerShell environment. To work around this issue, use a 32-bit version of Windows PowerShell or ISE.
4.  New-CMVirtualEnvironmentGroup result does not show in the Administrator Console.  To work around this issue, perform the task by using the Administrator Console.
5.  Set-CMSite -Comment parameter causes cmdlets to fail.  To work around this issue, perform the task by using the Administrator Console.
6.  Remove-CMDeploymentType will not fail when you try to remove a deployment type that does not exist.  To work around this issue, use Get-CMDeploymentType to validate if the deployment type exists before you try to remove it.
7.  New-CMSecondarySite creates a distribution point that cannot be configured through the Administrator Console when you use a self-signed certificate.  To work around this issue, use any of the following procedures instead of the New-CMSecondarySite cmdlet: Configure the secondary site by using a certification authority issued certificate. Use Set-CMDistributionPoint to configure the distribution point after the secondary site is installed. Remove the secondary site’s distribution point, and add a new one after the secondary site is installed.
8. Some cmdlets may stop working after you use the New-CMTaskSequence cmdlet.  To work around this issue, restart Windows PowerShell.
9. Start-CMApplicationDeployment fails when it is used with Windows Store applications because the expectation is that the content exists on a distribution point. To work around this issue, perform the task by using the Administrator Console.

Resources

SCCM Related Posts Real World Experiences Of SCCM Admins (anoopcnair.com)

Author

Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is a blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. E writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…