introduction
it’s very important to system administrator to understand the history of the product that will be applied to monitor the ALL his company aspects
this article we will try to discuss the history System Center Operation Manager until to get the current release
the start
SCOM’s roots came from a network management system named SeNTry ELM from a company named Serverware Group plc.
Company Mission Critical Software acquired the rights to SeNTry ELM in 1998, adapted it and changed the name to OnePoint Operations Manager.
Later : Mission Critical Software merged with NetIQ and sold the rights to OnePoint Operations Manager in 2000.
MOM2001
Microsoft renamed the product to Microsoft Operations Manager (MOM) and released it in 2001.
MOM worked in concert with two other Microsoft programs:
- Systems Management Server (SMS) 2.0
- and Application Center 2000.
MOM simplified the management of servers and applications.
It contained the same basic features as SCOM 2019, but with less scope due to the limited number of management packs.
MOM 2005 SP1
Microsoft released MOM 2005 Service Pack 1 in 2005 with several enhancements, including
- mutual authentication,
- agent proxy capabilities,
- secure communications channel
- secure credential storage.
- action account,
- tasks and a reporting
SCOM 2007
In 2007, Microsoft renamed MOM to System Center Operations Manager (SCOM).
The company added the command shell to this update that connected to Windows PowerShell.
and added about 80 cmdlets related to SCOM
which allowed administrators to develop scripts for task automation.
SCOM 2012:
In 2012, Microsoft released System Center 2012 and introduced
- high availability,
- application performance monitoring,
- dashboards,
- network device monitoring
- Java application monitoring to SCOM
Microsoft improved the installation process with a prerequisite checker in the installation wizard.
Microsoft added integration packs to enable SCOM to interact with System Center Orchestrator 2012.
SCOM 2012 R2
Microsoft released System Center 2012 R2 in 2013, which included
- improved fabric monitoring for private clouds
- integration with development tools for application troubleshooting
- improved monitoring agent
- support for IPv6, integration with the System Center Advisor service
- upgraded Unix and Linux monitoring.
SCOM 2016
Microsoft released System Center 2016 in October 2016 with
- more advanced cross-platform infrastructure
- Workload monitoring.
- Microsoft integrated SCOM with the rest of System Center and extended its toolset to provide a more consistent monitoring system.
SCOM 2019:
SCOM 2019 was released in March of 2019 and focused on areas of monitoring such as
- adding tools for monitoring
- managing data centers,
- adding support and management capabilities to newer versions of Windows server
- enabling hybrid management and monitoring with Azure.
System Center release strategy
Microsoft has two options for software release strategy:
- Semi-Annual Channel (SAC) release
- Long-Term Servicing Channel (LTSC) release
LTSC provides five years of mainstream support and five more years of extended support. This channel is appropriate for systems requiring a longer servicing option and functional stability.
Microsoft announced stopping the semiannual channel (SAC) update model with the System Center 2019 product. >> (i.e. they will not release 19XX)
SO ,,, the ONLY available choice is LTSC
conclusion
this was just brief for SCOM history
next article we will discuss what is the new feature of SCOM 2019 , and how it’s different of other releases
