Sc2012 Licensing Overview

1
This presentation discusses Microsoft® System Center 2012 - Operations Manager, the new features being delivered, and how they will be used to monitor and manage your infrastructure and applications. Operations Manager is a component of the full System Center 2012 product. The focus for Operations Manager is infrastructure management and tying applications to the supporting infrastructure.2
The goal is to reduce the mean time to resolution for problems that you are seeing within your environments and with the applications that rely on those environments. Microsoft is expanding the focus the IT pro has on the infrastructure they are managing so that they are able to dig deeper into their environments and pull out more information, more quickly. That helps to get the applicationteams as well as the networking teams and the infrastructure teams working together to solve problems. The shift from Microsoft Operations Manager in 2005 to System Center Operations Manager 2007 moved from server management to application management. Operations Manager 2007 introduced templates to work with applications and other objects, and had more of a modeling approach to working with theenvironment. Operations Manager 2007 R2 introduced cross-platform support, bringing in UNIX and Linux servers, and extended the scope of what you can do with Operations Manager. System Center 2012 – Operations Manager added several major improvements, including the networking layer, and more support for Microsoft .NET applications and Java applications.
3
This discussion covers the mainareas of the 2012 version of Operations Manager, including network device monitoring, .NET application monitoring, Java application monitoring, UNIX and Linux support, and the new visualizations that you can do through dashboards as well as Microsoft SharePoint® integration. It is now easier to roll out Operations Manager, extend the scale of the Operations Manager infrastructure, and scale out theoverall capacity of the system.
4
Customer feedback indicated that the Root Management Server (RMS) was the main bottleneck. It was handling a lot of load and it was the single point of failure. If the RMS went down, the entire management group could go down. That made the management group very difficult to manage, and introduced problems in planning and deploying Operations Manager properly.For the 2012 version of Operations Manager, Microsoft removed the RMS role and confederated the configuration services, spreading the load that the RMS used to handle across multiple management servers, which simplifies deployment. When considering scale, it always came down to a case of how many management servers were needed now, and how to add more later. Resource pools let you add newmanagement servers easily without having to manually balance the roles and agentless workflows.
5
Now with network monitoring, agent-less monitoring in general, and UNIX and Linux support, Microsoft has introduced the concept of resource pools. Resource pools take over what the RMS used to do, as well as auto-distributing the traffic coming from any agent-less style of monitoring. Another keyarea of focus is retaining backwards compatibility for System Center Management Packs between Operations Manager 2007 and the 2012 version. All of the existing management packs that you have for Operations Manager 2007 will continue to work in System Center 2012 – Operations Manager. In addition, the RMS emulator role is there to ensure that anything you used to have targeted and working with theRMS will continue to work against a single management server
6
Looking at the topology in a small environment, you could have several agents that are all talking to each other through a single management server. You could have some UNIX and Linux servers talking to Operations Manager as well as to network devices. With this small pool, you want to be able to scale it out, and you want to be...