SCOM 2012 R2 Hardware Requirements

Hi,
I am trying to work out what specification machines to use for a deployment of SCOM 2012 R2. I have searched on this forum, online generally and used the sizing guide but its all a bit vague. The sizing guide spat out the result below but as you can see
it makes no mention of CPU speeds or server HDD space apart from the DW server which says 300GB. The sizing wizard also spat out 14.43GB for the Ops DB and 427.45GB for the DW DB based on managing 600 servers, no network devices or applications.
Minimum Hardware Recommendation:
Role: (Total: 2) (1) management server managing up to 1000 agents, plus (1) management server for HA, managing up to 10 SDK users total
Hardware:
• 4 disk RAID 10
• 16 GB RAM
• 4 Cores
Role: Operations Database Server
Hardware:
• 6 disk RAID 10 (Data)
• 2 disk RAID 1 (Log)
• 16 GB RAM
• 4 Cores
Role: Operations Data Warehouse Server
Hardware:
• 12 disk RAID 10 (Data) (300 GB)
• 2 disk RAID 1 (Log)
• 16 GB RAM
• 4 Cores
Role: Web Console Server & SQL Server Reporting Services Server
Hardware:
• 2 disk RAID 1
• 8 GB RAM
• 4 Cores
I have also seen in the documentation that the management servers only require 1024MB of free space on the System Drive, that seems a bit overkill to have that spread across 4 disks at RAID 10. With regards to the DW disk requirements does it really need
300GB on 12 disk RAID 10 plus the 427.45GB for the Data Warehouse?
If someone could possibly clear this up I would be extremely grateful.
S

Your 4 cores CPU have met the requirement. SCOM does not use CPU resource much.
Juke Chou
TechNet Community Support

Similar Messages

SCOM 2012 Hardware Requirments

Can anyone point me in the direction of the hardware requirements for SCOM? I'm thinking about setting it up on a hyper v virtual server. Thanks.
Charles

you can use the sizing sheet provided by microsoft :
http://blogs.technet.com/b/momteam/archive/2012/04/02/operations-manager-2012-sizing-helper-tool.aspx

General hardware monitoring on SCOM 2012 R2

Hello everybody. Sorry for maybe common question, i'm absolutely newbie in SCOM. I'm standing at task of monitoring basic servers counters - Memory utilization, disk free space & CPU utilization. After reading some articles about SCOM architecture I
get a little frustrated - cannot get full understanding about monitoring mechanisms. What I want from my monitors:
- Monitor 2,3...N groups of servers with _different_ disk free space thresholds and sending alerts (email) to specific people.
I've already have imported management pack for Windows OS, configure channels & subscribers.
I get a lot of question trying to configure such monitoring, maybe you can help me (or send me to manuals)
1. I can use monitor's for specific OS (i.e. logical disk free space), then I need to override it(why? I can't use it?) and select servers.
2. How can I map a group of servers to monitor?
3. Do I need rules?
4. New monitor sets in installed agents automatically?
Cannot understand steps, in which I should resolve my task..

1. Windows OS management pack has default monitor for disk free space and CPU utilization. If you 2,3,...N groups of servers with different disk free space thresholds, you should create Groups which contains the required servers and using override with target
of the gorups.
For how to create an override, pls. refer
http://jimmoldenhauer.blogspot.hk/2012/11/scom-2012-creating-overides.html
2. The target of the monitor is set to the groups of server
3. It depend on situation
Rules do not affect the health state of the target object. They are used for one of three functions
a) Alerting Rules
Alerting rules create an alert when a particular event is detected. This can be any of the different kinds of events shown in Data Sources. Alerting rules do not affect health state.
b) Collection Rules
Collection rules collect events or performance data to the Operations Manager database and data warehouse. They do not create alerts or set health state.
Collection rules can use each of the data sources shown in Data Sources. The data will be converted to either an event or to performance data depending on the particular kind of collection rule you are creating. For some wizards, you will need to provide
the specific information from the data source that will be used for different properties of the data being collected.
c) Command Rules
Command rules will run a script or command on a schedule. They do not create alerts or collect any data.
4) All agents will automatic download updated its monitor and rule which applicable to the server.
Roger

Dell server hardware component monitoring with scom 2012 R2.

hello ..
We have some dell poweredge r710 SFF 2X SIX CORE X5 SAS Servers ,I need to monitor its hardware components with scom2012 R2.I have installed os:windows server hyper-v server on this and windows server core OS management packs on scom and monitoring
working fine .next I want to know their is Latest Management pack available for this dell model server and what are hardware components can be monitored with scom 2012 R 2. I want to monitor Hardware failure such as Power failure ,cpu failure,disk
failure and NIC failure etc
Thanks
Richa

Hi,
Please refer to the User’s Guide of the DELL MP:
http://support.dell.com/support/edocs/software/smconect/msscom/40/en/ug/pdf/Dell_Server_Management_Pack_Suite_v4.0_UG.pdf
Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Meanwhile, considering this is related to DELL products, if you need more information or further investigation, please also contact DELL support
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.

SCOM 2012 R2 - How to create a Web Application Monitor for an URL requiring certificate authentication

Hi All,
It looks like in SCOM 2012 there are two ways to monitor a web application (URL monitoring):
Way no 1: (Using the Web Application Transaction Monitoring template)
Way no 2: (Using the Web
Application Availability Monitoring template)
We have created some monitors using
Web Application Availability Monitoring to check if URL is up without any authentication method.
However, we have few URLs for which we need Client Certificates to be used for accessing them but found no option in SCOM 2012 to configured the certificates.
I have searched a lot on the Tech Net library but no clue. Does anyone know how to successfully monitor an URL requiring certificate authentication on SCOM 2012 ? or, at least, using no matter which method?
Thanks.
Regards,
Raju.

Hi,
Based on my research, it is not possible by using the built-in monitoring templates. Both of them handles “normal”, server-side, SSL-certs, and the transaction monitor handles basic/digest/NTLM authentication, but client certificate based authentication
is not a configurable option.
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 Domain Functional Requirement

Hi
We are planning to deploy SCOM 2012 R2 in our environment. We are running Windows 2012 AD and have Domain and Forest functional levels of
Windows Server 2012 R2. The Environmental prerequisites stated on Technet article
http://technet.microsoft.com/en-us/library/hh487285.aspx under section "Domain Functional Level", following description is provided:
Windows Server Active Directory can operate at different functional levels. These levels are distinguished by the version of the Windows Server operating system that is permitted on the domain controllers present in the domain. System Center 2012 – Operations
Manager requires that the domain functional level be Windows 2000 native, Windows Server 2003 interim, Windows Server 2003, or Windows Server 2008. The domain functional level of Windows Server 2008 R2 is also supported (for the SP1 version of System Center
2012 – Operations Manager, Windows Server 2008 R2 SP1 and Windows Server 2012 are supported). For System Center 2012 – Operations Manager to function properly, you must check the domain functional level and raise it to the appropriate version.
This description does not includes Domain Functional Level of Windows Server 2012 R2.
Does SCOM 2012 R2 supports domain and forest functional levels of Windows Server 2012 R2?
Thanks
Taranjeet Singh
zamn

Yes.
I has a SCOM 2012 R2 deploy in domain with forest and domain functional levels of Windows Server 2012 R2 and it work fine. Moreover, SCOM monitoring is more depend on kerberos encrpytion of data transfer rather than functional level.
Roger

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

Hardware Requirements for a SCCM 2012 CAS with SQL Server Remote

The hardware requirements for a CAS server with SQL Server Enterprise locally installed are:
16 cores (Intel Xeon L5520 or comparable CPU)
64 GB of RAM
1.5 TB of disk space for the operating system, Configuration Manager, SQL Server, and all database files.
Does anyone know what the hardware requirements are if SQL Server Enterprise is remote from the CAS server? It's not listed. -Shane

Even though I am going to be strung up for even saying this, I do agree there is a use for a CAS outside of 100,000 users. If you do indeed have distinct admins managing their own images and apps in remote
locations then I see the benefit of a CAS. A remote ConfigMgr console connecting to a primary site would perform poorly. Admin A at the primary site would not experience any issues but Admin B would be in for a lot of work and waiting. Any
time Admin B needed to add an app or image it would have to be copied up to the remote primary site and then distributed back down. This is not the best scenario.
There are scenarios in company merger situations (and others I am sure) where the management of both locations has not been consolidated down to one location yet and is not going to be done as part of the deployment or upgrade. If you had a 2007 environment
it is going to be very hard to convince the admin at the remote location that this upgrade is going to be a good thing for him/her. There is an option for the remote admin to RDP into a server in the primary site but the image and apps still need
to be distributed down to the remote location. During testing this can be very time consuming.
I do agree that adding a CAS adds additional complexity but in some cases such as the one I described it is the right decision.
Thank you for the reply. And i totally agree that in some cases a design like that is a necessary evil (but not by our personal wants).
We had that design with 2007 (implemented before my time), and as you predicted EU admins complained about difficulty using the console RDP-ed into a box close to the primary site. The bandwidth to and from different regions is out of scope for me so I do what
I can with what I have. We too will be moving forward with a CAS hierarchy.
Administratively the other IT depts in other regions operate on their own. I dont handle any of the EU computers on a day to day basis whatsoever, etc. We're not merging but our IT shops operate with near independence.

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 UCS pack and C-series monitoring

Hello,
Does anyone know if the SCOM 2012 UCS pack can be used to monitor Cisco C-series server at the hardware level?
If so, can it do this directly without going through UCSM (FICs)?
If not, is there any sort of pack setup for monitoring of C-series servers?
If this requires the 2248TP units connected up to our FICs, I'm open to that, but need to justify the costs.

Hi Justin,
Currently we do not have a MP to support the C series in standalone mode. This is on the roadmap and we should have it in some future releases.
However C series integrated with UCSM can be monitored using the SCOM MP.
Please note: For the integration, you need the 2232 FEX. UCSM version 2.0.2 onwards, we only support 2232 for the C series integration.
Thanks!
./abhinav

SCOM 2012 - Deciding what to monitor

I'm new to SCOM and I'm having trouble determing what is being monitored and what is not.
I have been following the Technet Library, but it gets a little fuzzy after the install is completed. I have:
Added computers using the discovery wizard
Imported appropriate Management Packs (SQL, AD)
Now I want to know what is being monitored and what is not, and how can I customise what is being monitored.
Wayne Hoggett (MCITP, MCSE, MCSA, MCTS, MCP)

Personally I prefer a live test environment where I can really play with it to the structured virtual labs which are mostly just walkthroughs but that is personal choice. And the virtual labs will give a grounding in the functionality. There are also some
good guides available:
http://blogs.technet.com/b/kevinholman/archive/2010/09/02/operations-manager-101-download.aspx
http://technet.microsoft.com/library/hh769766.aspx
For overrides, never save them to the default management pack:
http://blogs.technet.com/b/kevinholman/archive/2008/11/11/cleaning-up-the-default-mp.aspx
Just be careful with deploying too many management packs and agents too quickly. It is easy to deploy a few hundred agents and a dozen management packs in a couple of days and then spend months managing operations manager alerts rather than having operations
manager manage your environment. Here is what I generally recommend for about 100 - 150 servers. It is personal but it works for me! And the basis of this is do one thing at a time and get it right before moving on to the next.
1) Have an alert management process in place before you start. You'll have to fine tune it as the deployment progresses. But if
you install Windows, AD, SQL, Exhange, IIS, Cluster, Hardware MPs
then the next thing is you'll have a console full of alerts and no process for managing them. A sure recipe for disaster.
2) Deploy slowly - get core components, agents and windows management pack deployed. This means that you are not fire fighting on multiple fronts (e.g. with AD, Exchange etc alerts). Just get the agents in and sorted. Get the windows MP in and sorted. The
Windows Management Pack is ideal for this as the alerts it generates are usually actionable, relevant and relatively straight forward to resolve so administrators can get familiar with OpsMgr in a fairly controlled environment that is still providing real
benefit to the organisation
3) Proitise other MPs - I like to get SQL in next as it is a relatively stable MP with less noise than AD, Exchange .. but still gives good business benefit. But deploy the MP and spend time fine tuning it. Make sure you are happy that the alerts you get
are actionable. Then move on.
4) Repeat slowly .. MP by MP ... the AD alerts you get might be relevant, they might not be. Even the relevant ones might take time to resolve. Same with Exchange.
Expect it to take a few weeks to a couple months to deploy fully rather than days depending on the size of your environment and how much fine tuning of management packs is required (plus how long it takes to fix any problems identified).
Cheers
Graham
New SCOM 2012 Blog! - http://www.systemcentersolutions.com/blog/
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/

SCOM 2012 R2 deployment on Amazon Cloud VM

Hi,
I am planning to deploy SCOM 2012 R2 on VM hosted on Amazon Cloud, is this supported deployment??
Also is any impact after the MAC address of SCOM VM`s changed??
i have deploy all the System center 2012 R2 Components on Amazon Cloud only ..
Shailendra Dev

Hi,
Please refer to the link below:
Hardware Requirements for System Center 2012 R2
https://technet.microsoft.com/en-us/library/dn726764.aspx
These computers can be physical servers or virtual servers.
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]

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 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 R2 Hardware Requirements

Similar Messages

Maybe you are looking for