Need differences explained

Hello, I'm in the process of setting up System Center Configuration Manager 2012 R2. I plan to start out with the modules needed to push out WSUS updates (WSUS) and also add in the System Center Update Publisher (SCUP) to be able to package/distribute 3rd party updates. Later I need to add in SCOM to replace IP Monitor, which I'm using now to monitor my network/devices. One of my colleagues mentioned Microsoft Operations Manager, looks like it does the same thing as System Center Configuration Manager. Can you answer the following 3 questions please:

1) What are the major differences between Center Configuration Manager 2012 R2 & Microsoft Operations Manager?

2) Do companies typically have both in their enterprise?

3) Benefits/downsides of having both in the enterprise.

Thank you

July 15th, 2015 12:48pm

1) What are the major differences between Center Configuration Manager 2012 R2 & Microsoft Operations Manager?
SCOM 2012 R2 is a monitoring tool which monitoring of Windows servers, clients, hardware, software, and services
SCCM 2012 R2  uses to Patch management (Microsoft and third party), Software distribution, Hardware and software inventory, Branch office updates and software distribution, Operating system deployment and Desired configuration management
SCCM is focused on the client-side, tends to use store-and-forward for management data, the agent works in the background.  Its strongest feature tends to be Software Distribution and Software Updates.  The client can be installed on servers in datacenters and is supported (but not certified).  The SCCM agents are optomized for windows clients only.  Functionality is enabled in SCCM by enabling SCCM Agents.  The more SCCM agents that are enabled, the more the administrator can do to manage the clients.  However, the cost is additional workload.  SCCM is not considered a monitoring application.

SCOM is focused on the server-side, tends to operate in near real-time, is for monitoring enterpise infrastructure, services, and applications like Exchange and SQL.  SCOM also installs an agent on the server (but it can also monitor agentless devices with reduced functionality).  SCOM is optomized for monitoring servers and is not considered a management application.  Functionality is enabled in SCOM by importing Management Packs.  For example, Exchange 2007 can be monitored by SCOM by importing the SCOM Management Pack for Exchange 2007.

SCOM can also monitor SCCM like it was just another enterprise app like Exchange.  To monitor SCCM 2007, you would import the SCCM 2007 Management Pack, then install the SCOM agent on each site server that you want monitored by SCOM.

for deatil, pls. refer to
https://social.technet.microsoft.com/Forums/systemcenter/en-US/9776151f-a0be-4d15-8f03-25483bd5d379/difference-between-sccm-and-sccm-management-pack-for-mscom-2007?forum=configmgrgeneral
2) Do companies typically have both in their enterprise?
Yes. SCCM for software and hardware inventory, patch managment and SCOM for enterprise monitor

3) Benefits/downsides of having both in the enterprise.

SCCM and SCOM is mainly two different product to cater different enterprise. Also. there are working well in our corporate environment.

Roger

Free Windows Admin Tool Kit Click here and download it now
July 15th, 2015 11:56pm

1. The major difference is:

SCOM is used for monitoring the Servers, Client computers, Network devices etc.

SCCM: Mainly used in Inventory, Patch pushing via WSUS, OS Deployment, Software installation

2. Depends on companies requirement.
Mostly Yes as they have to purchase the suit its self so they will use.

3. As of i see there is no down sides.
Benefits: You can cut of lot of manual work done in patch pushing and monitoring and managing the environment.

Eg: In SCOM we can run recovery tasks for alerts if there is any issue. So if a script can fix the issue you can save time in manually logging and doing it, SCOM does it automatically.

SCCM You can run reports for patches, Run inventory to fetch file / hardware firmware versions etc for planning for upgrade.

Also if you need any custom software to be pushed on 1000's of cients the SCCM can do that.

Also with SCCM  You have MDM technology where you can manage mobile devices and stuff and Compliance regulation stuff such as fixing a specific value to a registry key and if some one changes it then SCCM will re change it as per you have mentioned.

July 16th, 2015 1:28am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics