I’m back with common issues faced by SCCM / ConfigMgr admins. In the Previous post “How to Overcome Daily Worries of a SCCM ConfigMgr Admin“, we’ve seen a number of daily issues faced by CM admins. Today, I’m going to cover two topics namely SCCM Client Data Upload and SCCM MP policy request bandwidth. I’ve seen several issues because of the data traffics which are initiated by Client Data Upload and Policy Request data. This can happen most of the enterprise world when your WAN connectivity to remote offices are SLOW. There is one other resource which talks about actual size of SCCM client data transferred between SCCM/ConfigMgr servers and client. More details here.
What is SCCM Client upload data? Client upload is a scheduled operation for each client. The size of upload depends upon inventory, the process executes a scan of installed software or files, then uploads the results to its MP. But when you’ve 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 call and then RCA documentations 🙂 Hopefully, you don’t want to write those SCCM traffic related Root Cause Analysis documents in 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 ? :- In a scenario, SCCM admins decided to put all the MPs in a central location as 1 MP can handle upto 25000 clients. So the clients in multiple remote offices with thousands of clients checking for client policy with MP which is connected via slow WAN. That mean 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. This connections via slow WAN could always cause network bandwidth issues. So
What is the Solution to control SCCM Client Policy Request Bandwidth ? :- Again Adaptiva OneSite can help to resolve this issue as well. Policy Bandwidth Management feature of OneSite (Policy Push) can help to control the policy bandwidth management. OneSite is deeply integrated with SCCM and hence it can immediately detect the client policy changes when they are made. Once the SCCM policy change is detected then 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 here.