How to Get Ability to Patch Systems Instantly using SCCM

Patch management through SCCM has sharpened very well during last few years. I started working on patching since ‘SMS 2003 + ITMU’ days. Previously, we need to perform loads of complex steps to deploy patches during that time period. With SCCM 2012, we can use ADR (Automatic Deployment Rules) Download and Deploy patches. There are some challenges in SCCM Patch management and one of them is installation of patches to system instantly using existing SCCM infrastructure.  
PatchDo you think, it’s really possible to deploy patches all the systems of a global organization instantly? It would be very challenging to deploy patch packages to remote office DPs without impacting network bandwidth. Also, it would be challenging to keep aggressive frequency for client policy pulling schedule because this may also make bandwidth issues, when you’ve thousands of clients from a remote office trying to pull the policies via Management Point at the end WAN connection at another office. How to patch systems instantly without those challenges ? The answer is Adaptiva Onesite – with super cool features like Policy Push, Predictive Bandwidth Harvesting and Client Data Upload Management. More details below.

Policy Push-2

Adaptiva OneSite Policy Push feature helps to serve requests immediately, without waiting for policy polling. Also, it (policy Push) gives greatly reduced impact on MP performance. In normal scenario, when you deploy software or patch to a machine (or end user requests install), you need to wait up to an hour (SCCM default setting) for the activity to begin. With combination of Predictive Bandwidth Harvesting and policy push technologies the systems will receive patches significantly faster. Client Data Upload Management and Policy Push, we can avoid SCCM client communications impacting other traffic and applications on the WAN, negatively impact the business, and cause repercussions (clamping down) from the networking team. SCCM client communications with OneSite never impacts the WAN because they are load-leveled.

More in depth details of all these innovative technologies explained here.

About Author 

Anoop is Microsoft MVP and Veeam Vanguard ! He is a Solution Architect on enterprise client management with more than 13 years of experience (calculation done on the year 2014) in IT. He is Blogger, Speaker and Local User Group Community leader. His main focus is on Device Management technologies like SCCM 2012,Current Branch, Intune. He writes about the technologies like SCCM, SCOM, Windows 10, Azure AD, Microsoft Intune, RMS, Hyper-V etc...

    Find more about me on:
  • googleplus
  • twitter
  • facebook
  • linkedin
  • youtube
Posted in: Adaptiva, ConfigMgr (SCCM), Patch Management, Patching, Sponsors

One Comment

  1. Sudarsan says:

    Hi Anoop,
    Need your help to understand the following scenario, In our environment planning to deploy updates using sccm 2012. my query is that I am planning to configure maintenance window(without configuring max runtime), we never patched the servers for years, so many updates needs to be installed and the maintenance windows will be 5-6 hours, take a scenario that I pushed 50 applicable updates to client and it is installing, mean time maintenance window completed during 43rd update, what will happen to rest of the updates and the update with already started to install. this info is really required to have the patching planned accordingly. Please help.

Leave a Comment and Contact Anoop