Wanted to add - a SQL standard license is included in System Center licensing, 
so there should not be much additional cost in scaling these out - except for 
additional hardware or VM costs.

Lastly, the sizing spreadsheet shows the web console collocated on the 
reporting server, which is a bad idea and I never recommend that.  I always 
recommend installing that role on management servers, otherwise you will 
struggle with NTLM auth sign on issues.


From: [email protected] [mailto:[email protected]] On 
Behalf Of Orlebeck, Geoffrey
Sent: Monday, January 26, 2015 2:19 PM
To: '[email protected]'
Subject: [msmom] OpsMgr 2012 R2 Architecture Question

Hello everyone.

I'm new to SCOM and we currently have a hybrid MOM 2005 and SCOM 2007 R2 
environment. I've gotten so far as to recreate all MOM alerts in SCOM so we can 
finally begin decommissioning our MOM servers. However, I am now turning my 
eyes towards OpsMgr 2012 R2 and have a couple questions.

I have reviewed Microsoft's TechNet articles (link 
here<https://technet.microsoft.com/en-us/library/hh298610.aspx>) on their 
Distributed Deployment and I am wondering if the Operational DB can be on the 
Management Servers? In the diagram from the link above, the Management servers 
only hold the management role while the operational DB looks to be clustered 
between two additional servers. I was thinking of the following for our design, 
but not sure if it's really possible:

Our site is ~600 servers and ~200 Network devices:
2 Management servers for agent-based monitoring (w/ operational DB on the 
management server[s])
2 Management servers in a resource pool for network device monitoring
1 Data warehouse server

Not sure if attachments are allowed, but I have attached the diagram I 
designed, but again, I'm just not sure if the operational DB can sit on the 
actual management servers or not. I saw Microsoft's "all-in-one" single server 
design for testing, which is why I figured the Operational DB *can* sit on the 
management server(s), but wasn't sure if I'm missing potential pitfalls of 
doing that. We aren't trying to cut corners, we merely want to avoid an 
increase in the number of VMs/SQL instances unnecessarily. Thank you for your 
time.

-Geoff
Confidentiality Notice: This is a transmission from Community Hospital of the 
Monterey Peninsula. This message and any attached documents may be confidential 
and contain information protected by state and federal medical privacy 
statutes. They are intended only for the use of the addressee. If you are not 
the intended recipient, any disclosure, copying, or distribution of this 
information is strictly prohibited. If you received this transmission in error, 
please accept our apologies and notify the sender. Thank you.




Reply via email to