SCOM 2012 R2 Design

Dear SCOM experts/engineers,
I am writing to this forum to kindly ask you about SCOM design that we want to implement to our environement. I would like to be sure sure about the initial design.
I am attaching picture made by VISIO program.
According to picture you can see we are considering about special management domain for SCOM OpsMGr with following trusts. No other trust ways are possible because of firm policy. We have internal and external forests with child domains.
Inside each forest we have +-100 servers and inside each domain we have +- 200 servers. I am interesting in communication between servers inside child domain and GW servers located in Forests(it should work because of two-way trusts). Is that possible
to have like in the picture below? I know that communication between OpsMgr and GW will be based on certificates.
If you could advise me if there you can see some future issues or if we can go ahead with this design and also get me advantages and disadvatages of it.
If any further question I will reply as soon as I can.
Thank you
Liibas

Hi, it's ok
and Don't forget
1. about priority assignment for agent and GW, and have dedicated MS/MSs for GWs with approximately equal number of agents.
https://social.technet.microsoft.com/Forums/systemcenter/en-US/6dae0b67-714a-4b89-8120-6981637a3707/scom-management-server-not-communicating-with-root-management-server
2. about failover if you need high availability.
http://blogs.catapultsystems.com/cfuller/archive/2012/06/05/how-does-the-failover-process-work-in-opsmgr-2012-scom-sysctr.aspx

Similar Messages

SCOM 2012 R2 HA design but using SQL 2014 Standard edition

Hi All,
I want to deploy SCOM 2012r2 with a HA design (but have constraints!)
Plan is two management servers with all roles to each (fresh deployment so 2012r2 RU5)
SQL servers need to be 2014 standard edition due to licensing and cost constraints.
Design is to be split between two datacentres that are fibre connected and sub 3ms latency
Plan was to have a Management Server and a SQL server at each location.
Each location has a dedicated SAN but SAN replication is not an option.
What are my SQL options for the DB??
AlwaysOn FCI is not preferable as it gives a single point of failure due to shared storage requirement.
I read Database mirroring is not a supported config but this isn't Microsoft direct info just blog post, is this correct.
Which leaves me with log shipping, is this supported and the best option??
Would be great to get advice on what works well in the field with a contraint of having to use SQL Standard edition!
Thanks
James

Hi,
No additional licenses are needed for management servers or SQL Server technology.
System Center 2012 R2 licensing
http://www.microsoft.com/en-us/Licensing/product-licensing/system-center-2012-r2.aspx#tab=2
Reference:
SCOM 2012 R2 HA options with Server 2012 and SQL 2012
https://gallery.technet.microsoft.com/SCOM-2012-R2-HA-options-540beb95
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

SCOM 2012 Design questions?

While design SCOM 2012 , what are important things to be noticed ? like Environment to be monitored , Budget , Network Bandwith , Application to be monitor ..etc
Like this any other important things to be noticed.

For SCOM Design, you can check below links
http://technet.microsoft.com/en-us/library/jj593271.aspx
http://blogs.technet.com/b/momteam/archive/2012/04/13/opsmgr-2012-design-guide.aspx
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

SCOM 2012 Design including DR

I have been spending quite a bit of time researching HA in SCOM 2012 and have seen other posters being pointed in the direction of best practice docs etc but none seem to talk about hyper-v replica. My initial implementation will consist of about 300
servers to be monitored, the sizing tool recommends 2 MS and a single SQL server hosting the OPS and DW SQL DB.
This seems a reasonable configuration but I need to incorporate a DR solution into this. We have a Hyper-V 2008 cluster in DC1 which is replicated to DC2 which is out DR site. I am proposing hosting all of the servers on the Hyper-V cluster,
in the event of DC1 going down my plan is to bring the replicated servers up in DC2.
Does this seem like a reasonable solution or am I missing something? Are there any limitations to this design that I am not seeing or any problems I am likely to run into?
Thanks

A good idea is to backup the operational database daily, and ship that backup using whatever tool or process you want. If you care about historical data, then I suggest setting up log shipping or similar for the data warehouse database.
In terms of DR for the MG, my preferred way to go about this is to have warm MS's in another DC, completely installed and ready to go. Depending on how "mission critical" monitoring is, this is about as good as it gets for DR. If monitoring is
number 1 priority mission critical to your business, then I suggest 2 MG's - one in each DC - and multi-homing your Windows agents and monitoring all other devices (network, UNIX/Linux) from both MG's at all times. When one fails, there is literally no outage
for those monitored instances in the DC that is still alive, and no additional DR procedures are really necessary in this case.
In my experience, monitoring is not mission critical. This is not my opinion, but the opinion of all the organizations I've worked with. There is a cost to DR, and having a completely HA scenario with absolutely no down time for those instances that are
still "alive", usually it simply isn't worth the cost and administrative overhead.
A simple backup and move job of the operational database, and a "seed" management server in another DC is typically the design I would suggest.
Jonathan Almquist | SCOMskills, LLC (http://scomskills.com)

SSRS for SCOM 2012 need separate instance of SQL

Hi All,
My customer has planned to install SCOM 2012 R2 in their environment. I designed for them as followings:
Planned 3 MS servers namely, MS1, MS2 & MS3
The rolls planned on those MS servers as follows:
MS1 – Management Server,
Operation console & Web console
MS2 – Management Server,
Operation console & Web console
MS3 – Management Server,
ACS, SQL Reporting services & SCOM Reporting server
Customer has their existing SQL cluster database configured. This existing SQL database is also utilized by other applications.
I am planning to keep all the SCOM databases (Operation Manager DB, Operation DW DB, Reporting DB & ACS DB) on the central location on SAN storage of the SQL cluster.
For this, I requested to customer for a new instance of SQL to install SCOM DBs & SQL Server Reporting services.
Customer raised a concern on Why would need to install the databases & SQL Server Reporting services on a separate instance.
I replied as, The new instance requested will host the databases along with the SQL Server reporting services (SSRS).
The installation of SQL server report server will integrate the security of selected SSRS instance with Operation Manager role based security. Any reports that were previously installed on this
SQL server instance might become inaccessible. No other applications that are using SQL Server Reporting Services can be installed on this instance of SQL Server.
On this, Customer says if SSRS is planning to install on the MS3 server then there would not need to create a separate instance on SQL cluster. We can go with the existing instance for installation
of SCOM databases on SQL cluster and SSRS on MS3 server.
I need your inputs on this, as can I still require the new instance of SQL on SQL cluster or can go with the existing instance for installation of SCOM databases on SQL cluster and SSRS on MS3 server.
Kindly provide your inputs.
Regards,
SandeepK

Although SCOM can share a single instance running SQL Server to store data, this is not a recommended configuration. The SSRS is the same, no document says that it can be shared with others.
Also, refer to
http://social.technet.microsoft.com/Forums/en-US/84e89021-6794-421e-b41c-5da1186aae2e/sccm-and-scom-reporting-on-the-same-sql-instance?forum=configmgrreporting
Juke Chou
TechNet Community Support

SCOM 2012 Linux Monitoring - RPCBIND, RPCIDMAP, RPCSTAT services not running

We are running SCOM 2012 SP1 and added a test Linux server running Red Hat Enterprise 6.3. SCOM is reporting that the server is in Critical health because the following three services are not running.
1) Process Rpcbind Service Health - Rpcbind Mapper Not Running
2) Process Rpcidmap Service Health - NFSv4 ID Name Mapper Not Running
3) Process Rpcstat Service Health - NSM Status Monitor Not Running
My question is that are these services required to be running in order for SCOM to monitor the Linux servers properly? If yes, can you please give brief explaination as to why so I can explain that to our Linux Administrator. The Linux Administrator
is saying that we do not run these services on any of the Linux servers because they are not needed. If infact these services are not needed, how can I have SCOM ignore the critical error messages? Thanks

Yup, generally running. I'm assuming you've done a basic install of RHEL 6. All processes listed above are enabled by default on a RHEL 6 install if you take the default settings. If someone is just getting started you can pretty much guarantee
they will do a basic install of RHEL 6 and this will not be an issue.
Could it be done better... sure but at what point do you stop? We could discover all services running on the system and start monitoring them out of the box but what are important and what are not to each customer? The idea is to give you some basic monitoring
on a default install based on what each OS provider starts on a "default" install. If this does not suite your needs SCOM is very configurable and adding a custom service monitor is very easy to configure along with disabling existing ones.
If you'd like to provide feedback on this feel free to open a support ticket with Microsoft and file what we call a 'Design Change Request' [DCR]. We go though these prior to starting each update to SCOM. No guarantee it will get fixed/changed as we do have
priorities but we are listening.
Regards,
-Steve

SCOM 2012 Global Architecture, One management group or multiple?

Hi Folks,
I work for a global firm, we have multiple data caters in different regions. America, UK, Australia, China etc etc. We are looking to roll out SCOM 2012 for monitoring all systems. Our environment
1,000 Windows servers
All servers on the same Active Directory domain
10 Mbps links between data centers.
My question is around whether to use multiple management groups or one? I’ve seen recommendations for both. For example
In the Infrastructure Planning and Design guide for SCOM 2012 it is stated:
“A centralized management model with large remote locations works best with a management group in each region and a local management group (which provides a consolidated view of alerts and status) in the parent location. In this case, the centralized management
group connects through the software development kit (SDK) and functions as an additional console on each of the connected management groups.”
However moderators in this forum have stated
“Each management group has its own set of SQL Servers and Management Servers \ Gateways. It also adds considerably to administrative overhead. I'd try to avoid
multiple management groups where possible.”
” It will get expensive in terms of hardware and software with multiple management groups and you will duplicate a lot of work with regards to overrides”
“If you go with multiple Management Groups then you would need to add on a fair number of SQL licenses plus additional hardware. “
“Presumably if I have multiple management groups will that mean I will have to
create rules for each Management Group- correct. Same
with overrides. It could add a lot of administrative overhead. “
It would seem easier to just deploy one management group with the management servers in one datacenter but I’m concerned with performance. I’ve heard
stories about SCOM deployments architected in this way not performing well because of network latency. i.e admins from all regions besides the region local to the SCOM deployment not wanting to use SCOM because application performance is too slow.
What would the SCOM experts recommend for this scenario?
MH

1) My question is around whether to use multiple management groups or one?
Factors to consider in determine the number of Management group
• Scaling
• Agents separated from their management server by WAN-speed network links
• Political, administrative or security requirements within the organization requiring separate management groups.
• A view of AD DS topology required across multiple forests.
• A dedicated management group required for auditing purposes.
• Disaster recovery functionality required.
• Consolidated views of connected management groups required in Operations Manager.
• Operations Manager integration with the VMM console.
With refer to your situation
a) 1,000 Windows servers
b) All servers on the same Active Directory domain
c) 10 Mbps links between data centers.
It is suggest that one Management group is required.
2) It would seem easier to just deploy one management group with the management servers in one datacenter but I’m concerned with performance
It is recommend that you should deploy Gateway server in region office which has more than 10 agents.
• Gateway server reduce network bandwidth utilization. Agents located across WAN links consume network bandwidth, potentially affecting service delivery to and from the remote location. A gateway server can consolidate the traffic.
Roger

MonitoringHost.exe RAM usage SCOM 2012 SP1 UR1

Hello,
From two days the MonitoringHost.exe use more than 6 go ram on two of my four management servers. After some research I found that these two servers are member of my UNIX/Linux Monitoring Resource Pool. And when I delete on these management server
of this resource pool the process return to the normal with 500 mo of ram usage.
I have 11 UNIX/Linux computers for the moment composed by 5 SunOS 5.10, 4 SLES 10 and 2 SLES 11. I have only imported MP for these versions. I think that the problem come of a rule in on of these management pack but I don't know how to investigate and find
the source of problem.
Any help would be welcome.

You should apply the latest Update Rollup 2 for System Center 2012 SP1 Operations Manager. It contains quite a few updates to SCOM itself, plus it contains new cross platform Management Packs. Cross platform monitoring works in proxy,meaning
the Management Server resource pool or Management Server that you appoint to monitor the workloads truly does a lot of work. I would recommend, and so does Microsoft, having a dedicated resource pool of Management Servers to perform the monitoring for
cross platform systems.
In addition to this the most important resource to a Management Server is RAM. I'm not sure the scale of your environment and your current configuration (physical vs virtual) but I would highly recommended scaling your Management Servers a little higher
in RAM to accommodate console sessions, dashboards creation and viewing etc. You can even scale out now with the nice architecture changes to SCOM 2012. If you start to use dashboards in your environment that will chew through a ton of
RAM which Microsoft design recommendations don't currently account for.
http://support.microsoft.com/kb/2802159?wa=wsignin1.0

O365 SCOM 2012 requirements

hi,
I have recently tried to install the O365 Management Pack on our SCOM 2012 Mgmt Server. I ran into the following requirements:
O365 MP needs:
System Center Core Library / Microsoft.SystemCenter.Library 7.0.8432.0, currently 7.0.8427.0
Health Library / System.Health.Library 7.0.8432.0, currently 7.0.8427.0
Microsoft.SystemCenter.Visualization.Library / Microsoft.SystemCenter.Visualization.Library 7.0.9538.0, currently 7.0.8560
Unfortunately, our current libraries are not at the level of the requirements. How/where can I get the required MPs ? I thought O365 supports SCOM 2012!
dave

Hi,
Office 365 management pack:
Supported Operating System
Windows Server 2012 R2
The Office 365 Management Pack for Operations Manager is designed for the following versions of System Center Operations Manager: • System Center
Operations Manager 2012 • System Center Operations Manager 2012 SP1 • System Center Operations Manager 2012 R2
More details:
http://www.microsoft.com/en-us/download/details.aspx?id=43708
As we can see the management pack require Windows Server 2012 R2. Did your environment meet this requirement?
Regards,
Yan Li
Regards, Yan Li

STEPS to Make SCOM 2012 SP1 High Avaliability

Can anybody tell me the steps to make scom 2012 sp1 high avaliabilty with sql server 2008 r2 because i have akready deplyed scom 2012 single server with sql server 2008 r2 but now i have to make the replica of this on dr side so should i need one more
sql server 2008 r2 and one MS server on DR site

Hi,
Additional to dktoa’s reply, I would like to explian Resource pools are a new concept in Operations Manager 2012. When two or more management servers are added to a management group, the management servers automatically become part of a resource pool and
work is spread across all the members included in it. If one of the resource pool management servers fails, other management servers in the resource pool take over the workload, thus delivering an out-of-box highly available design.
Topology changes in System Center 2012 Operations Manager (Overview)http://blogs.technet.com/b/momteam/archive/2011/08/22/topology-changes-in-system-center-2012-operations-manager-overview.aspx
Niki Han
TechNet Community Support

SharePoint 2010 SP2 hosted on Windows 2012 R2 NOT discovered by SCOM 2012 R2 + 2 SP MP's

What is the process to get SharePoint 2010 Management Packs loaded in System Center 2012 R2 to discover/monitor SharePoint 2010 SP2 (14.0.7121.5000) loaded on Windows 2012 R2?
View of installed system:
System Center 2012 R2 loaded on Windows 2012 R2 (supported separately by SQL 2012 SP1 loaded on Windows 2012 R2)
-Microsoft SharePoint 2010 Products Management Pack for System Center Operations Manager 2007
-System Center 2012 Monitoring Pack for SharePoint 2010
SharePoint 2010 SP2 (14.0.7121.5000) loaded on Windows 2012 R2 (supported separately by SQL 2012 SP1 loaded on Windows 2012 R2)
The SharePoint 2010 Management Shell works fine!
Result
Event 0, Operations Manager - Cannot identify which SharePoint farm server is associated with. Check the management pack guide for troubleshooting information.
Looked at these already:
KB2690744, Configuring the SharePoint 2010 Management Pack for System Center Operations Manager.
http://om2012.wordpress.com/2013/05/24/sharepoint-2010-mp-on-scom-2012/
Further, if the xml push does have the command get-farm instead of get-spfarm, that could be the issue. i.e.
http://www.scom2k7.com/advanced-troubleshooting-of-the-sharepoint-2010-mp/
Thanks,
+Tony
Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you.

Peter,
I recommend to remove the Windows 2012 R2 server out of the farm and redeploy on W2008 R2.
This issue does not have an easy fix.
Summarizing, this appears to be the issue:
1. Windows Management Framework 3.0 is integrated with Windows 2012 R2, which installs .NET 4 and Powershell 4.0. Not uninstallable.
2. The Add-PSSnapin Microsoft.SharePoint.PowerShell is not supported with Powershell 4.0.
3. The SCOM SP2010 MP puts a package on the defined farm server and when the agent launches the package, it calls Powershell (v4 in theis case) and errors out. The target W2012 server will have an Error 0 in the Operations Manager Event log. See below.
Options:
1. Work around maybe - Develop method for manual discovery (I'm working on that now).
2. Rebuild SP2010 farm on Windows 2008 R2
3. System Center Team - Write a new MP to down version Powershell (Powershell.exe -Version 2)
4. Powershell Team - Write a SharePoint Snapin for Powershell 4
Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you.

SCOM 2012 SP1 availability report in MS Generic Report Libary shows inaccurate data

Hi,
in SCOM 2012 sp1, we have the generic availability report showing many of our web sites with no up time beyond a certain date. The web sites are ok, the web availability monitors are all healthy and the monitors test ok
None of these web availability tests are in Maintenance mode although what we are observing certainly makes us think that they are.
We also have a Web transaction login monitor for WEBSITE(A) that does not show this same outage for a login test.
However WEBSITE(A)'s availability monitor shows the same downtime as the other web availability tests.
Any thoughts on where to look for this problem? Im guessing its a problem placing the data in the Warehouse?
Thanks Lance

Hi,
Based on my understanding, the report shows there is downtime for the web site, but the web site did work well always.
It seems like that there is old data stored in data warehouse, would you please check the report for recent date, such as one day or two days.
Regards,
Yan Li
Regards, Yan Li

How to create a group in SCOM 2012 R2 based on SCCM Collection?

Is there a way to create a group in SCOM 2012 R2 based on sccm collection? I am planning to use that group for maintenance mode.
Thanks, Samer

Hi,
I think you could query all the collectin members from SCCM database then use powershell to add them to a specific OU.
How to Create Groups in Operations Manager
http://technet.microsoft.com/en-us/library/hh298605.aspx
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Can overrides from SCOM 2007 R2 be used in a new SCOM 2012 R2 installation?

Hi All,
I'm wondering if we can "easily" use our overrides/configuration from our current SCOM 2007 R2 implementation and use them in a new SCOM
2012 R2 environment that we plan on standing up. We are using SCOM to monitor approx. 400 servers (physical and virtual).
We have been using 2007 R2 for a few years and we'd like to start using 2012 R2. Instead of using the update path (2007 R2 to 2012
to 2012 SP1 to 2012 R2), we are planning on setting up a new 2012 R2 environment and configuring our servers to start reporting to 2012 R2 (after it has been configured in such a way as to "mimic" our 2007 R2 environment).
Ideally, we'd like to avoid going through the upgrade path. (We'll leave our 2007 R2 environment running so that we can still access "historical
data" until the new 2012 R2 environment has had a chance to build up its own "historical data".)
So ... I was thinking we could export our overrides from 2007 R2 and import them into 2012 R2, but I'd like to verify that this approach makes
sense. We haven't done extensive customizations to 2007 R2 in terms of Distributed Applications or Management Pack Objects (although we have made some changes - which I guess we could manually configure in 2012 R2 to offer the same "experience").
The following are some of the Management Packs that we are using in 2007 R2:
Microsoft Windows Active Directory
Active Directory Certificate Services
EMC Storage Monitoring
IBM Hardware
Microsoft Exchange Server 2010
McAfee
Microsoft Forefront Server Protection 2010
Microsoft Office SharePoint Server 2007
Microsoft SQL Server
Microsoft Windows DNS Server
Microsoft Windows WINS
Microsoft Windows Hyper-V
Microsoft Windows Internet Information Services
Microsoft Windows Server
Microsoft Windows DHCP
NetBackup Operations Manager
Office Communications Server
OpsLogix (BlackBerry)
Service Level Dashboard for OpsMgr 2007 R2
SolarWinds Orion
Schedule Maintenance Mode
Team Foundation Server 2010
Virtual Machine Manager
Microsoft Windows Cluster
Operations Manager 2007 R2
I appreciate all feedback and the sharing of you expertise.
Thanks, Joe.

As long as the base pack works and you wish to retain the customisation then you should be ok, there’s a good article
here which explains how to perform the migration and some of implication/things to check.
There will be complications if you’ve stored anything in the default mp but this is explained in the above article.

SQL version could not be verified error while installing the SCOM 2012 R2 reporting component

I have the below SCOM server roles in my SCOM 2012 R2 set up
1) All servers with Windows Server 2008 R2 SP1, MS - SCOM1, DB & DW - DB1, Reporting Server - DB2
2) All the DB servers with SQL 2012 SP1
3) Windows firewall is turned off on all the servers.
4) Success fully installed all the components except SCOM reporting.
While installing the SCOM 2012 R2 reporting component on DB2 ( Iam running this set up on the server where I instllaed the SQL DB engine and reportin services in Native mode. Configured the SQL reporting database and reporting URLs successfully in SQL reporting
configuration manager) getting the below error in the Rporting server instance page. Kindly advise.
I ran mofcomp.exe and there is no firewall restrictions. My account also has DB owner & sysadmin permissions.
Also tried re installing the SQL on Reporting server.
"The installed version of SQL Server could not be verified or is not supported. Verify that the computer and the installed version of SQL Server meet the minimum requirements for installation, and that the firewall settings are correct. See the Supported
Configurations document for further information".

Hi,
As far as I know, after installing SSRS, we don't need to configure the database and reporting URLs manully. When we install the reporting service for SCOM, it will configure those automatically.
If possible, you may re-install SSRS and then install SCOM reporting service.
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

SCOM 2012 R2 Design

Similar Messages

Maybe you are looking for