How to Control SCCM Client Data Upload MP Policy Bandwidth Configuration Manager | ConfigMgr? I’m back with common issues faced by SCCM / ConfigMgr admins. In the previous post, “How to Overcome Daily Worries of an SCCM ConfigMgr Admin,” we’ve seen many daily issues faced by CM admins.
Today, I will cover two topics, namely SCCM Client Data Upload and SCCM MP policy request bandwidth. I’ve seen several issues because of the data traffic initiated by Client Data Upload and Policy Request data.
Control SCCM Client Data Upload
This can happen most of the enterprise world when your WAN connectivity to remote offices is SLOW. One other resource talks about the actual size of SCCM client data transferred between SCCM/ConfigMgr servers and the client. More details here.
What is SCCM Client upload data?
Client upload is a scheduled operation for each client. The size of the upload depends upon inventory. The process executes a scan of installed software or files, then uploads the results to its MP.
But when you have a remote office with lots of clients, and they are sending inventory to a remote MP on a slow WAN, then you can be pulled into priority 1 issues and conference calls and then RCA documentation 🙂
Hopefully, you don’t want to write those SCCM traffic-related Root Cause Analysis documents in the future. We can’t control or throttle “this” data via SCCM.
What is the Solution to control SCCM Client Upload Data?
Adaptiva OneSite can help SCCM admins to get out of this bandwidth issue. With Adaptiva OneSite, SCCM admins can enable Client Data Upload Bandwidth Management for each major inventory action, including file collection. This feature gives SCCM admins the ability to define how many clients can concurrently upload inventory data to the MP at a given time, and it is configurable per each inventory action.
What is SCCM Client Policy Request Bandwidth? :-
SCCM admins decided to put all the MPs in a central location as 1 MP can handle up to 25000 clients in a scenario. So the clients are in multiple remote offices with thousands of clients checking for client policy with MP, which is connected via slow WAN.
That means each client will initiate an HTTP connection to its MP, and the MP will query the SCCM database to see if there are any new policies for the client, then return the results. These connections via slow WAN could always cause network bandwidth issues.
What is the Solution to control SCCM Client Policy Request Bandwidth? :-
Again Adaptiva OneSite can help to resolve this issue as well. The Policy Bandwidth Management feature of OneSite (Policy Push) can help to control the policy bandwidth management. OneSite is deeply integrated with SCCM, and it can immediately detect the client policy changes when they are made.
Once the SCCM policy change is detected, it instructs only the targeted clients to check for policy in real-time. This feature really allows SCCM admin to increase their policy polling interval to the maximum value, which is 24 hours; if there are no applicable policy changes for a given SCCM client within the 24 hours interval, then the client won’t check.
More Information about these features of Adaptiva OneSite is here.
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…