How to Overcome Daily Worries of a SCCM ConfigMgr Admin


First of all I would like to share the most” common worries of a SCCM / ConfigMgr admin. As SCCM admin, You must have faced several issues like, distribution of a package didn’t go well on remote DPs, deployment of an application never reached SCCM client. Also, something like a package distribution caused network bandwidth outage. Another big headache is bandwidth throttling and it’s known fact that the SCCM bandwidth throttling mechanism doesn’t work very well. How to get rid of these issues in your SCCM infrastructure and how to improve the productivity of the service that you provide? 

Another post which talks about the SCCM admin challenges when we make design decision are explained in the post “How to Control SCCM Client Data Upload and MP Policy Bandwidth

SCCM Admin Common Worries

Most common worries of SCCM Admins !!

(Will try to keep this list updated whenever I recollect some other issues)

1) Troubleshooting on package distribution issues

Every day, we’ve to monitor DPs and troubleshoot any issues with the infrastructure.

2) Troubleshooting on boundary conflicts or Boundary assignment issue

When your environment has more than 3000 IP subnets (or zillion different IP ranges) then it would be a pain to define and manage boundary groups. Whenever network team changes network then SCCM team needs to update the same. If a client is not within a defined boundary, it won’t know where to get content, and the package distribution will fail.

3) Bandwidth throttling issues 

A lot of companies only SCCM send data at night because they are worried about flooding the WAN links. Sending data over WAN requires scheduling, calculating (how big package, how much bandwidth, how long…)

4) Disk space issues on remote DPs,  5) DP health issues and 6) IIS issues on DPs

When you distribute content to DPs, if you’ve got 400 DPs, you need to make sure that all 400 downloaded it. If you have 5 or 10 that didn’t, then you need to troubleshoot what’s going on there. In some OSD scenarios, when a single package (out of 30 packages which are associated with a TS) is not successfully distributed to a DP then the task sequence can’t start the OSD process. So DP package replication could become very critical. Another issue is all 400 DPs will have same package content without any redundancy between them. Hence the disk space use is not very excellent.

7) Deployment Failures

Troubleshooting on application deployment failures can take long time and efforts. The route case could be boundary assignment, package replication, wrong assignment etc…

8) Immediate need of application deployment

In case, your manager approached you to install/deploy an application ASAP (within an hour) on a number of machines. Would that be really easy and possible with native SCCM? From SCCM Admin perspective it would be a big headache. Because you need to think about client policy refresh, distribution of packages to remote DPs and so on ….

9) Coordination with external teams like network

The biggest headache of SCCM admins could be that “to get the work done” from external teams like Network, Storage, SQL etc.. To build and implement OSD solutions in enterprise environment, SCCM admins need to work with network team to get IP Helper and DHCP scope options configured correctly .

Now, it’s time to mention about the solution to overcome these common issues of SCCM admins. I’m not going to tell you that manage your boundaries using IP Ranges rather than using IP subnets, network team should perform bandwidth throttling via switches or routers from network layer. How do you manage the remote DP issues when there are no technical person on the remote office to help you with disk space issues, OS related issues etc.. and the remote DPs outage can cause impact (backlog) to your SCCM hierarchy.

In my SCCM career, I’ve noticed that the most of the issues and troubleshooting which SCCM admins do is on Deployment, Distribution and boundary conflict (or management) related issues. How to overcome these issues? Adaptiva Onesite is one stop solution for all of these common issues. Quick video will give you more details :-


Solutions to “most common” worries of SCCM Admins !!

1) Troubleshooting on package distribution issues

NO DP Management : – Adaptiva Onesite will eliminate the need of remote DPs so no overhead of troubleshooting on DP related issues. More details here.

2) Troubleshooting on boundary conflicts or Boundary assignment issue

No Boundary Management : – With Adaptiva OneSite, we can define one group, put all the boundaries in that group and OneSite allows less boundary groups !

If you have 5 offices you need boundaries for each one. But with OneSite, they can all be in the same boundary group.

3) Bandwidth throttling issues

No Scheduling of content delivery :- With Adaptiva OneSite, drop it on the WAN and forget it. Adaptiva will automatically monitor the network bandwidth and act accordingly so no worries and no special approvals from network managers 🙂

4) Disk space issues on remote DPs, 5)  DP health issues  and 6) IIS issues on DPs

No Baby-sitting on DPs :- With Adaptiva OneSite, be sure they received content and/or content updates and no single point failure at remote sites.

7) Deployment failures 

No failed deployments with OneSite :- Adaptiva OneSite will take care of most common root causes for package deployment failures on SCCM client machines.  

8) Immediate need of application deployment

No right-click tools :- No right-click tools required to get ASAP deployments out immediately, Adaptiva uses push rather than polling cycles (that may need to be manually initiated using the right-click tools). If Adaptiva OneSite push policy is enabled, it instructs the client when a policy change has occurred, which reduces traffic and speeds deployments.

9) Coordination with external teams like network

No reliance on networking :- No need to coordinate with network team for router changes (IP Helpers or DHCP scope options) for PXE. Adaptiva Onesite uses peer to peer PXE solution and this is very much resolves the issues like changing the router settings and DHCP scope settings.

Happy Administration !!!


  1. Hi Anoop – good article…do we have any ALTERNATEs for Adaptiva onesite…we recently deployed SC12 with all the infra DPs etc i am sure we cannot switch over to adaptiva now….but need suggestions to over a BIG PROBLEM we have….we have about 3000 workstaions which are not getting the SC12 client onto them due DNS/WMI/etc reasons…how can we temporarily manage them to be compliant …as we try improve the client installation compliance….

    • Hi Ravs ! – Thank you. First of all, we don’t need to perform anything like switch over to Adaptiva. Adaptiva Onesite, itself is an extension product to SCCM. Hence we just need to install adaptiva onesite application on the top most SCCM server in your hierarchy and that is it. We’re good to go.

      Talking about alternatives of adaptiva, hope, you’re looking for native SCCM ways to solve this. I don’t think there is a way to solve (100%) these common issues without using any add-on or exention then that would be equally or more complicated than using native solution.



  2. In addition, after the SC12 implementation we are still unable to reach the 90% and above patch installation compliance in the 1st 2 weeks…it is still taking 5+ weeks to go above the 90% …what finetuning we can do to fasttrack the deployment compliance…..

    • I know, these are common issues which we need to deal with in day to day wise. There is no easy way to solve these issues, rather than preventing these issues from happening. This could be done by SCCM extension products. With SCCM extension products like adaptiva, what we are going to do is eliminate the complexity of SCCM like remote DP, boundary issues, client health issues etc…



Please enter your comment!
Please enter your name here