SCCM Client Software Distribution: Get Device Collection is not able to pull the information, if the Number of Device Collections is more than 2500Issue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } While testing the Get Device Collections SCCM Activity of SCCM Client Software Distribution module, it times out after 12 to 20 minutes with a WSMan error. We ran the commands manually as below from the MID Server to check if we are able to retrieve the Device Collections successfully:$cred = Get-Credential$computer = <SCCMServerHostname>$session = New-PSSession -ComputerName $computer -credential $credInvoke-Command -Session $session -ScriptBlock ${ Import-Module -Name "D:\Program Files\Microsoft Configuration Manager\AdminConsole\bin\ConfigurationManager.psd1"; Set-Location -path "$(Get-PSDrive -PSProvider CMSite):\" ; Get-CMDeviceCollection} But it was the same concern. Below error was displayed: "Processing data for a remote command failed with the following error message: Error with error code 14 occurred while calling method WSManPluginReceiveResult"or "Processing data for a remote command failed with the following error message: The WSMan provider host process did not return a proper response. A provider in the host process may have behaved improperly" The error seems to be specific to Powershell Remoting:"Error with error code 14 occurred while calling method WSManPluginReceiveResult" We found out that even after increasing the WinRM property MaxMemoryPerShellMB on both the SCCM Server and MID Server we are getting one of the below errors while running the Get Device Collection powershell command from the MID Server:Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Any Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } We need to consider increasing the values for the related WSMan Plugins and not only the ones related the "Common" entries.Below are the updates that can be performed to the PowerShell Memory variable global quota:Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 2048The PowerShell Memory Plugin Quota values also need to be updated are as below:Set-Item WSMan:\localhost\Plugin\Microsoft.PowerShell\Quotas\MaxMemoryPerShellMB 2048 Set-Item WSMan:\localhost\Plugin\Microsoft.PowerShell32\Quotas\MaxMemoryPerShellMB 2048 (Essential for MID Server PowerShell as we are running 32 bit scripts)Set-Item WSMan:\localhost\Plugin\Microsoft.PowerShell.workflow\Quotas\MaxMemoryPerShellMB 2048 Set-Item WSMan:\localhost\Plugin\microsoft.windows.servermanagerworkflows\Quotas\MaxMemoryPerShellMB 2048 In addition, for scripts like Get Device Collection, which pull a lot of data from the SCCM remote server, below Plugin Quota values need to be updated:Set-Item WSMan:\localhost\Plugin\'Event Forwarding Plugin'\Quotas\MaxConcurrentOperationsPerUser 100 (default value is 15)Set-Item WSMan:\localhost\Plugin\'SEL Plugin'\Quotas\MaxConcurrentOperationsPerUser 100 (default value is 15)