As Microsoft announced, SCOM 2016 will be launched in September during Microsoft Ignite in Atlanta. This gives you about four weeks’ time to look at how to prepare your environment, design an installation or upgrade, if you are already running a previews version of Operations Manager.
When designing your SCOM 2016 environment, there are 12 key components you should care about.
Component 1 – Operational Database
First and foremost, there is going to be a central operational database, holding all the database information regarding your environment.
Component 2 – Management Server
The Management Server is a central part of your environment. It houses your configuration, it talks to agents and provides access to the consoles. You can have one Management Server or multiple. These multiple Management Servers together are called a Resource Pool.
Component 3 – RMS Role
The RMS also known as Root Management Server, since SCOM 2012 R2 is a role that has been dynamically placed in the Management Servers and Resource pools. The RMS used to be a separate server in previous versions of SCOM.
Component 4 – Console
Your operators will be working with the console within SCOM 2016.
Components 5 & 6 – Data Warehouse Database & Reporting Server
Ever since 2012 it’s a mandatory installation part. Here you get the reporting side of Operations Manager by installing both the database side and the Reporting Server!
Component 7 – Web Console Server
The Web Console Server allows you to access your information through the web.
Component 8 – Agent
You will be running different sorts of agents, such as Windows agents, Linux agents and all kinds of machines providing you with information regarding your environment.
Component 9 – Gateway Server
Depending on your configuration, network or other challenges you might be facing, it’s possible that you might need to add a Gateway Server. A Gateway Server allows you to deal with untrustworthy domains and helps you with latency.
Components 10, 11 & 12 – Audit Collector, Audit Database & Audit Forwarder
This is probably the least known part of Operations Manager. The Audit collector receives the information, the Audit Database is where the information is written into and there is also the Audit Forwarder, that is a part of Operations Manager’s agents. This infrastructure part is used for collecting security events.
So if you want to maintain the security of your Windows or Linux environment and you have your Operations Manager agents running there, simultaneously you can actually collect the security event and do reporting.