SCOM 2012 design document

HI team,
can any one please share the design document.

Hi,
I would like to share this document with you. Hope it helps.
SC2012_OpsMgr_Design_and_Planning_Guide.docx
http://blogs.technet.com/cfs-filesystemfile.ashx/__key/telligent-evolution-components-attachments/01-4616-00-00-03-49-19-33/SC2012_5F00_OpsMgr_5F00_Design_5F00_and_5F00_Planning_5F00_Guide.docx
Niki Han
TechNet Community Support

Similar Messages

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)

SCOM 2012 design plan

Hi
Am designing SCOM2012 R2 for monitoring 300 servers and 50 network devices . Client asks me to install server monitoring, network monitoring,ACS in only two servers since the monitored devices are very less . I would to know that enabling all this 3
services in two servers will work smoothly. What would be the best design solution for this requirement ?
All monitored servers are 2012 R2 and there is a separate high end DB server is hosting SCOM DBs'.All servers are running from single cloud location.

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 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]

XML document could not be created because server memory is low( SCOM 2012 R2).

Hi
I am facing below issue in the scom 2012 r2.
please find the error below
On SCOM MS:
Alert name :Data Warehouse relationship synchronization process failed to write data
Alert description :Data Warehouse relationship synchronization process failed to write data to the Data Warehouse database. Failed to store data
in the Data Warehouse. The operation will be retried.
Exception 'SqlException': Sql execution failed. Error 6624, Level 16, State 1, Procedure sp_xml_preparedocument, Line 1, Message: XML document could not be created because server memory is low. Use sp_xml_removedocument to release XML documents.
Event id in Operation log:
Event id :33333
Data Access Layer rejected retry on SqlError:
Request: DataWarehouseSynchConfigChangeTypeGet -- (InstalledManagementPackXml=<ManagementPacks><ManagementPack>7b9f4239-7351-e72b-4ce4-d6c56ddb401d</ManagementPack><ManagementPack>848edb97-9da5-e2ae-24d4-56...),
(RETURN_VALUE=-6)
Class: 16
Number: 6624
Message: XML document could not be created because server memory is low. Use sp_xml_removedocument
to release XML documents.
ON SCOM DB server:
SQL version : SQL 2012 SP1 X64 bit Host all SCOm db (SCOM DB,SCOM DW,Reporting)
Ervent id : 28005 ,Application log,source: MSSQLSERVER
Please suggest me in this regard.
Thanks
sridhar v

For fix error 33333, you can refer below links
http://opsmgradmin.blogspot.com/2011/05/scom-event-id-33333-in-scom-from-source.html
http://systemcenterblog.blogspot.com/2009/11/error-id-33333-data-access-layer.html
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

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

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 Report Server component install to SQL 2012 Sp1 error?

Hi All
Im having issues installing SCOM 2012 R2 Report Server component to a SQL 2012 Sp1 Server (which is a Windows 2012 R2 Standard server). Im trying to install to the SQL Default server instance, note that the server also has a named instance
which hosts the SCOM databases. SQL Reporting Services is up and running fine (can access the web urls etc). Im also using the SCOM install account wich has full SQL and SCOM Server admin rights for the install. Ive checked that the Firewall
is off locally on the SQL Server, Ive also checked that the existing SCOM components are all in a Healthy state in the SCOM console.
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.
Ive attempted the install on a standalone SQL Server away from the SQL Server hosting the SCOM databases, but encounter the same error. The full SCOM MSI Installer log details are below, line that appears most relevant is below but unsure why
this would be the case (same account that I used for SQL install etc). Any help much appreciated! : )
Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:51:46]: Debug: :CheckPrerequisites: IsComputerNameValidTitle: Passed
[11:51:46]: Debug: :
[11:51:46]: Debug: :**************************************************
[11:51:46]: Debug: :**************************************************
[11:51:46]: Debug: :<![CDATA[CheckPrerequisites:   Logic Type:and AvicodeAgentInstalled-x86: 0CheckPrerequisites:   Logic Type:and AvicodeAgentInstalled-x64: 0]]>
[11:51:46]: Debug: :
[11:51:46]: Debug: :CheckPrerequisites: AVIcodeAgentCheck: Passed
[11:51:46]: Debug: :
[11:51:46]: Debug: :**************************************************
[11:51:46]: Always: :CheckPrerequisites: Return Value 0
[11:51:46]: Always: :Entering Page: AdditionalPrerequisitesPage
[11:51:48]: Always: :Entering Page: ShortEulaPage
[11:51:48]: Always: :Displaying localized EULA for localization: en
[11:51:48]: Always: :Displaying Eula: C:\Users\opsmgr\AppData\Local\SCOM\Setup\en\eula_en_notice.rtf
[11:51:49]: Info: :Info:User has agreed to EULA.
[11:51:50]: Always: :Entering Page: SelectManagementServerForReporting
[11:52:08]: Info: :Info:Management Server matches the current version of setup.
[11:52:08]: Always: :Entering Page: SelectReportingInstance
[11:52:08]: Always: :SQL Server SRS Instance (escaped name) RS_MSSQLSERVER
[11:52:08]: Info: :Attempting to get the SSRS version from:
\\WDC-SYSSQL01\Root\Microsoft\SqlServer\ReportServer\RS_MSSQLSERVER:__NAMESPACE
[11:52:08]: Debug: :Path is
\\WDC-SYSSQL01\Root\Microsoft\SqlServer\ReportServer\RS_MSSQLSERVER\V11:MSReportServer_Instance
[11:52:08]: Always: :SRS instance on WDC-SYSSQL01. Version 11.0.3000.0.
[11:52:08]: Always: :No SRS instances on WDC-SYSSQL01.
[11:52:08]: Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:52:08]: Info: :Info: WDC-SYSSQL01 SRS version =
[11:52:08]: Error: :Couldn't check SRS version: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
[11:52:08]: Error: :StackTrace:   at System.Version.TryParseVersion(String version, VersionResult& result)
   at System.Version.Parse(String input)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportingComponent.CheckSRSVersion(String srsInstance, String requiredSRSVersion)
[11:52:11]: Info: :Attempting to check SRS version
[11:52:11]: Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:52:11]: Info: :Info: WDC-SYSSQL01 SRS version =
[11:52:11]: Error: :Couldn't check SRS version: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
[11:52:11]: Error: :StackTrace:   at System.Version.TryParseVersion(String version, VersionResult& result)
   at System.Version.Parse(String input)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportingComponent.CheckSRSVersion(String srsInstance, String requiredSRSVersion)
[11:52:28]: Info: :The user canceled setup
[11:52:28]: Always: :Begin: Property bag dump.
[11:52:28]: Always: :SetupStartTime = 26/03/2014 11:51:38
[11:52:28]: Always: :Collection ProtectedProperties (System.Collections.ArrayList):
[11:52:28]: Always: : [0] = ActionAccountPassword
[11:52:28]: Always: : [1] = DASAccountPassword
[11:52:28]: Always: :DefaultLogName = C:\Users\opsmgr\AppData\Local\SCOM\Logs\OpsMgrSetupWizard.log
[11:52:28]: Always: :DefaultLogPath = C:\Users\opsmgr\AppData\Local\SCOM\Logs
[11:52:28]: Always: :path = F:\Setup\AMD64\
[11:52:28]: Always: :setupexepath = C:\Users\opsmgr\AppData\Local\SCOM\Setup
[11:52:28]: Always: :ArchitectureIs64Check = True
[11:52:28]: Always: :OperationManagerAgentInstalled = 1
[11:52:28]: Always: :Collection ListOfSupportedComponents (System.Collections.ArrayList):
[11:52:28]: Always: : [0] = OMCONSOLE
[11:52:28]: Always: : [1] = OMSERVER
[11:52:28]: Always: : [2] = OMWEBCONSOLE
[11:52:28]: Always: : [3] = OMREPORTING
[11:52:28]: Always: :install = 1
[11:52:28]: Always: :installpath = C:\Program Files\Microsoft System Center 2012 R2\Operations Manager
[11:52:28]: Always: :EulaFilesPath = C:\Users\opsmgr\AppData\Local\SCOM\Setup
[11:52:28]: Always: :HealthServiceTypeId = AB4C891F-3359-3FB6-0704-075FBFE36710
[11:52:28]: Always: :hsPort = C51B7833-DA54-1653-D8FD-1A738EF8DED5
[11:52:28]: Always: :ServerBlockReason = A Operations Manager agent was found on this computer. Please remove the agent and then run Setup again.
[11:52:28]: Always: :ScreensLoaded = 1
[11:52:28]: Always: :Collection ListOfSelectedComponents (System.Collections.ArrayList):
[11:52:28]: Always: : [0] = OMREPORTING
[11:52:28]: Always: :OMREPORTING = 1
[11:52:28]: Always: :SelectDatabaseInstanceReloadScreenInformation = 1
[11:52:28]: Always: :ReloadPrerequisitesPageChoice = PrerequisitesProgressPage
[11:52:28]: Always: :LoadedPrerequisiteXmlFile = True
[11:52:28]: Always: :PrerequisitesCheckXMLLoaded = True
[11:52:28]: Always: :CountFilteredPrerequisites_Failed = 0
[11:52:28]: Always: :CountFilteredPrerequisites_Warning = 0
[11:52:28]: Always: :CountFilteredPrerequisites_PassedWithChoices = 0
[11:52:28]: Always: :CountFilteredPrerequisites_Passed = 10
[11:52:28]: Always: :PrerequisiteState = Passed
[11:52:28]: Always: :XmlFilteredPrerequisites_Passed : Begin XML property
[11:52:28]: Always: :<?xml version="1.0" encoding="utf-8"?><Root><Title TitleText="OMREPORTING"><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="memoryCheckTitle" descriptionBody="" descriptionTitle="ReportingMemCheckPassed" resolution="ReportingMemCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="ntfsCheckTitle" descriptionBody="" descriptionTitle="ntfsCheckPassed" resolution="ntfsCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="DriveSpaceCheckTitle" descriptionBody="" descriptionTitle="ServerDriveSpaceCheckPassed" resolution="ServerDriveSpaceCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="OSVersionCheckTitle" descriptionBody="" descriptionTitle="OSVersionCheckPassed" resolution="OSVersionCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="WindowsInstallerCheckTitle" descriptionBody="" descriptionTitle="WindowsInstallerCheckPassed" resolution="WindowsInstallerCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="RemoteRegistryCheckTitle" descriptionBody="" descriptionTitle="RemoteRegistryCheckPassed" resolution="RemoteRegistryCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="PendingRebootCheckTitle" descriptionBody="" descriptionTitle="PendingRebootCheckPassed" resolution="PendingRebootCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="ActiveDirectoryCheckTitle" descriptionBody="" descriptionTitle="ActiveDirectoryCheckPassed" resolution="ActiveDirectoryCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="IsComputerNameValidTitle" descriptionBody="" descriptionTitle="IsComputerNameValidPassed" resolution="IsComputerNameValidResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="AVIcodeAgentCheck" descriptionBody="" descriptionTitle="AVICodeAgentCheckPassed" resolution="AVICodeAgentCheckResolution" /></Title></Root>
[11:52:28]: Always: :End XML property
[11:52:28]: Always: :ManagementServer = WDC-SYSOPS01.landmarc.local
[11:52:28]: Always: :DefaultSDKMachine = WDC-SYSOPS01.landmarc.local
[11:52:28]: Always: :UserCanceledInstall = 1
[11:52:28]: Always: :InstallSuccess = 1
[11:52:28]: Always: :End: Property bag dump.
[11:52:28]: Debug: :CEIP disabled. CEIP data will NOT be sent.
[11:52:28]: Always: :Application Ended: Successful
[11:52:28]: Always: :
[2014-03-26T11:52:28.4724357+00:00]: Always: Trace Session Ended

Hi,
According to the error message:
[11:52:11]: Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:52:11]: Info: :Info: WDC-SYSSQL01 SRS version =
[11:52:11]: Error: :Couldn't check SRS version: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
The issue is SQL report server database related, I would like to suggest you create a new report database for SCOM and then check the reuslt. Please refer to the below links and follow it to set up SCOM 2012 R2:
http://blogs.technet.com/b/kevinholman/archive/2013/01/16/opsmgr-2012-sp1-quickstart-deployment-guide.aspx
In addition, here is thread for your reference also:
http://social.technet.microsoft.com/Forums/en-US/3f883b7f-5a33-49f0-a40d-f3311e68609d/unable-to-connect-to-the-data-access-service-installing-report-server?forum=operationsmanagerreporting
Regards,
Yan Li
Regards, Yan Li

SCOM 2012 SP1 is failing to install - SQL not compatible

I'm getting an error when installing SCOM 2012 SP1 stating the SQL is not supported. I have seen a few posts on the forum about this error message but so far none of the resolutions resolved my issue.
Using named instance on port 2433. Entering SQL\instance and port 2433 yields same message as seen in another post:
"The installed version of SQL server is not supported. Verify that the computer and installed version of SQL Server meet the minimum requirements for installation. Please see the Supported Configurations document for further information."
I noticed I get this in my OpsMgrSetupWizard.log
[15:03:28]: Error: :StackTrace:   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at System.Management.ManagementScope.InitializeGuts(Object o)
   at System.Management.ManagementScope.Initialize()
   at System.Management.ManagementObjectSearcher.Initialize()
   at System.Management.ManagementObjectSearcher.Get()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupValidationHelpers.GetRemoteOSVersion(String remoteComputer)
[15:03:28]: Debug: :IsSQLOnAValidComputer: remote OS version string was null or empty.
Notice the last line - IsSQLOnAValidComputer is null/empty. The solutions I found are to open the ports between these servers but the SQL server and SCOM server are on the same network - no firewall between them. The registry key for domain firewall
policy to 'EnableFirewall' is 0. The firewall service is disabled on both machines.
I am running the installation as a domain service account - for the DAA. It has local admin on the SQL and SCOM server. It has sysadmin DB access to the instance.
SCOM Server:
Server 2008 R2 Standard SP1
SQL Server:
Server 2008 R2 Enterprise SP1 | SQL 2012 RM 64-bit version 11.0.2100.60
Any help is greatly appreciated.

Glad to hear the issue has been resolved. Thanks for the update.
Niki Han
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

SCOM 2012 Reporting - Feature List

Is there a simple documentation listing out what SCOM 2012 R2 Reporting is capable of.
People at my company wants to know what this "Reporting" does.
Instead of giving them a 1,000 page documentation on SCOM, if there was a simple document listing out its feature set, that would be great.

Hi,
From my point of view, SCOM reporting is to use to get needed reports about service availability, performance and alerts and so on. With those report, we may do data analysis to get more details about the monitored environments.
With management pack imported, there may be many available reports that can be run to get proper information about what monitored by using this management pack.
If there is any misunderstanding, please feel free to let me know.
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]

How can install Reporting on SCOM 2012 R2

Recently we have install sql 2012 r2 with new feature of HA ie High Availability and we have 2 management server of SCOM 2012 R2 but we cannot install the reporting. so is there any document or can anybody tell me how we can install the reporting is it
possible to share the screenshots to install the reporting of scom 2012 r2.

Hi,
Please refer to:
How to Install the Operations Manager Reporting Server
https://technet.microsoft.com/en-us/library/hh298611.aspx?f=255&MSPPError=-2147217396
How To: Install System Center 2012 Operations Manager Reporting Server
http://1staff.com/Blog/post/2012/11/05/How-to-Install-Operations-Manager-Reporting-Server.aspx
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

SCOM 2012 UCS Management Pack Configuration/Administrator Guide

Hi,
We are planning to use SCOm 2012 for UCS Monitoring and Reporting purpose. Is there any detail configuration/Administrator Guide available?
Is there any best practice document availble to monitor critical ports( Network uplink/Storagre Uplink) ports and and setting up threshold limit?
Thanks in adavance for your help..

Hi Hetal,
Please take a look at this guide for starters:
http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/msft_tools/scom/scom_2.6/scom_2.6_user_guide/scom_2_6_monitoring.html
Thanks,
-Bruce

SCOM 2012 design document

Similar Messages

Maybe you are looking for