<div>
<div class="content wysiwyg-content">
We are going to begin installation of SCOM 2007 R2 and have some configuration questions. Our goal is use existing hardware and want to make sure we have the server roles in the right places.<br />
<br />
Here is what we are planning. We have 100 Servers (60 physical / 40 virtual) that we are going to be monitoring. The applications include Sharepoint, Exchange, and SQL Server as well as .NET applications.<br />
<br />
We will have a dedicated system running the SQL backend. Our expectation is that the system will be used as both the DataStore and the Audit Database. The server will be running Windows 2008 x64 Enterprise SP2 and SQL 2008 fully patched. This will be using the SCOM 2007 R2 product. <br />
<br />
We intend to use virtual systems for our Management Server and Operations Console. We would like to install both roles onto the same virtual system if at all possible. This server will also be running Windows 2008 x64 Enterprise SP2<br />
<br />
Reporting Services will be it's own separate VM. Again running the same OS.<br />
<br />
Is this scenario one that is acceptable? Any other things we should be concerned about?
</div>
</div>


We are going to begin installation of SCOM 2007 R2 and have some configuration questions. Our goal is use existing hardware and want to make sure we have the server roles in the right places.

Here is what we are planning. We have 100 Servers (60 physical / 40 virtual) that we are going to be monitoring. The applications include Sharepoint, Exchange, and SQL Server as well as .NET applications.

We will have a dedicated system running the SQL backend. Our expectation is that the system will be used as both the DataStore and the Audit Database. The server will be running Windows 2008 x64 Enterprise SP2 and SQL 2008 fully patched. This will be using the SCOM 2007 R2 product. 

We intend to use virtual systems for our Management Server and Operations Console. We would like to install both roles onto the same virtual system if at all possible. This server will also be running Windows 2008 x64 Enterprise SP2

Reporting Services will be it's own separate VM. Again running the same OS.

Is this scenario one that is acceptable? Any other things we should be concerned about?

SCOM setup scenario

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.

Microsoft Server OS

Microsoft server applications are those applications developed specifically, but not necessarily exclusively, on the Windows Server platform. In addition to well-known products like SQL Server, Exchange, Internet Information Services (IIS), Microsoft Dynamics, Forefront, Lync and Sharepoint, they include applications like Skype, BizTalk, Hyper-V, Groove and Commerce Server. Server applications are managed with the Microsoft System Center.

Microsoft Server Apps

Network Management involves issues that are independent of specific hardware or software, including email policies, upgrade planning, backup scheduling and working with managed service providers for Desktop-As-A-Service (DaaS), Software-As-A-Service (SaaS) and the like through the use of tools, coupled with manufacturer standards, best practice guidelines, policies and procedures plus all other relevant documentation. Network management also includes monitoring, alerting and reporting, management reporting, planning for device or service updates, the backup of configurations, the setting of key performance indicators and measures (KPIs/KPMs), associated service level agreements and problem records as part of the IT Service Management (ITSM) framework.