Using OMS for Patch Deployment

Not too long ago, the OMS team introduced the Update Management solution. This solution has definitely made the patch management process a lot easier, however at the same time, has raised some questions, such as:

  • What’s the future of SCCM (Configuration Manager) with OMS now deploying patches?
  • Can this be used concurrently/dual-homed with SCCM for on-premises environments?
  • Is OMS essentially System Center in the cloud?
  • Is OMS the future?

For the most part, SCCM will still be required for on-premises environments. When it comes to application deployments, computer/server images, granularity with patch/hotfix selection, etc. Microsoft has explicitly stated SCCM configured machines cannot be tagged to OMS with respect to patching, so at the current time, OMS and SCCM cannot/will not work together, whereas OMS and SCOM work hand-in-hand (for now?).

It also seems OMS is slowly becoming System Center in the cloud. It has absorbed the monitoring capabilities from SCOM, and now the patch management process from WSUS and SCCM.

So, is OMS the future, in my opinion, no, it is not the future, it is very much the present! I think OMS/Azure will soon welcome the demise of System Center.

Getting started with OMS Update Management is very easy. For starters, you will need the following:

  1. OMS Workspace
  2. Update Management Solution added to OMS
  3. Automation account (create in Azure first)
  4. Machines to manage

Once we have taken care of these steps, the rest is pretty easy.


Clicking on the Update Management title, here is an overview.


For the complete blog post, please visit,

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.