Non supported version of SQL with new install of SCOM 2012 SP1

I have SQL 2012 SP1 running on Server 2012. I have tried the SCOM installation with and without CU2 (to fix the 1618 installation error)
SC VMM installed cleanly and appears to work.
The install for SCOM produces an error that says, "The installed version of SQL Server is not supported". I have not been able to find any log from the install that has that error in it.
Also, I have not been able to determine the true requirements of the SQL server for SCOM. (I found dock SCOM 2012 RTM and SQL 2008 R2, but noting for 2012 SP1.
Can someone point me to the correct place for the install log with (hopefully more information) and/or the requrements for the SQL installation?
Roy

The log is not created yet because it has not started the install.
The firewall is the most common issue indeed. Temporarily Disable the firewall and see whether you can continue.
Are you using a developers edition? The only 2 editions supported are standard and Enterprise.
The true requirements for SCOM 2012 sp1:
We recommend that you check for updates and hotfixes for SQL Server. Note the following database considerations for Operations Manager:
SQL Server 2008 R2 and SQL Server 2012 are available in both Standard and Enterprise editions. Operations Manager will function with both editions.
Operations Manager does not support hosting its databases or SQL Server Reporting Services on a 32-bit edition of SQL Server.
Using a different version of SQL Server for different Operations Manager features is not supported. The same version should be used for all features.
SQL Server collation settings for all databases must be one of the following: SQL_Latin1_General_CP1_CI_AS, French_CI_AS, Cyrillic_General_CI_AS, Chinese_PRC_CI_AS, Japanese_CI_AS, Traditional_Spanish_CI_AS, or Latin1_General_CI_AS. No other collation
settings are supported.
The SQL Server Agent service must be started, and the startup type must be set to automatic.
Side-by-side installation of System Center Operations Manager 2007 R2 reporting and System Center 2012 Service Pack 1 (SP1), Operations Manager reporting on the same server is not supported.
The db_owner role for the operational database must be a domain account. If you set the SQL Server Authentication to Mixed mode, and then try to add a local SQL Server login on the operational database, the Data Access service will not be able to start.
For information about how to resolve the issue, see System Center Data Access Service Start Up Failure Due to SQL Configuration Change
If you plan to use the Network Monitoring features of System Center 2012 – Operations Manager, you should move the tempdb database to a separate disk that has multiple spindles. For more information, see
tempdb Database.
Found here:
http://technet.microsoft.com/en-us/library/jj656654.aspx#BKMK_RBF_OperationsDatabase
It's doing common things uncommonly well that brings succes.

Similar Messages

Turn off the SQL DB monitoring entirely in scom 2012 (SP1)

Is there a way to centrally target and turn down monitoring of all the servers running SQL DB in SCOM 2012. We actually created groups using the OU's to target the SQL servers but some of the servers which have SQL DB are not in that OU and they are still
triggering DB alerts.
Some of the alerts also include
Management Group: Ancestry Ops. Script: DiscoverSQL2012FileGroups.js : Cannot login to database [XXserver.domain.com][SQLD114B:model]
and these servers are in the OU but still trigerring this DB alert.
Any information about this ll be greatly useful.
Thanks
Hari V

Pretty much what Hopeless guy said. I have scom 2007 in prod, so I use remove-disabledmonitoringobject after I override a discovery. The issue is that these SQL dbs are still being discovered. So if you want to disable sql monitoring
in total for them, override the seed discovery which will have a target of windows server/computer. Then after the override is in palace execute the remove command from SCOM commandshell. You then should scope to the class you want to disappear
(discovered inventory pane), and refresh every 15 min or so to see if they are being removed. I have had to run the remove command a few times to clean some large discovered inventory up.
Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/ If my response was helpful, please mark it as so, if it answered your question, then please also mark it accordingly. Thank you.

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]

Apple application support version 1.4.1 is installed error

I keep getting this error when I attempt to open itunes after upgrading to the latest version. 10.1.1
Apple application support version 1.4.1 is installed, itunes requires apple application support version 1.3.2 or later
Does anyone know what to do about it?
I have already uninstall the entire program and all its components 3 times. Still, same error after re-installing.

Bang goes another theory. Okay, let's try putting your AAS 1.4.1 back. (Fingers crossed, iTunes will notice it properly this time.)
Download and save a copy of the iTunesSetup.exe (or iTunes64setup.exe) installer file to your hard drive:
http://www.apple.com/itunes/download/
Download and install the free trial version of WinRAR:
http://www.rarlab.com/
Right-click the iTunesSetup.exe (or iTunes64Setup.exe), and select "Extract to iTunesSetup" (or "Extract to iTunes64Setup"). WinRAR will expand the contents of the file into a folder called "iTunesSetup" (or "iTunes64Setup").
Go into the folder and doubleclick the AppleApplicationSupport.msi to do a standalone AAS install.
Does it install properly for you? If so, does iTunes launch properly now?
If instead you get an error message during the install, let us know what it says. (Precise text, please.)

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

Three agent UR versions gets installed from gateway - SCOM 2012 SP1 UR4

Hi,
We have a SCOM 2012 SP1 UR4 installation with several gateways that servers connect to and get installation from.
We noticed that when the agent get installed on a client server it gets first the agent itself, then UR1, UR2 and last UR4.
From the XML-section in the task that has installed the agent one can read the following:
SoftwareUpdateInstalled KB2784734-amd64-Agent.msp;KB2826664-amd64-Agent.msp;KB2880799-amd64-Agent.msp; SoftwareUpdateInstalled
Below is from the application log of a newly installed server that got the agent installed.
The question I have is if this is correct? Why are all three UR installed?
Shouldn't it be enough with the latest version of UR? Are they not cumulative?
Can I simply delete the older versions in the agent directory of the Gateway?
Regards S-E
Windows Installer installed the product. Product Name: System Center 2012 - Operations Manager Agent.
Product Version: 7.0.9538.0. Product Language: 0. Manufacturer: Microsoft Corporation.
Installation success or error status: 0.
Windows Installer installed an update. Product Name: System Center 2012 - Operations Manager Agent.
Product Version: 7.0.9538.0. Product Language: 0. Manufacturer: Microsoft Corporation.
Update Name: System Center 2012 - Operations Manager SP1 UR1 Update Patch.
Installation success or error status: 0.
Windows Installer installed an update. Product Name: System Center 2012 - Operations Manager Agent.
Product Version: 7.0.9538.0. Product Language: 0. Manufacturer: Microsoft Corporation.
Update Name: System Center 2012 - Operations Manager SP1 UR2 Update Patch.
Installation success or error status: 0.
Windows Installer installed an update. Product Name: System Center 2012 - Operations Manager Agent.
Product Version: 7.0.9538.0. Product Language: 0. Manufacturer: Microsoft Corporation.
Update Name: System Center 2012 - Operations Manager SP1 UR4 Update Patch.
Installation success or error status: 0.
Windows Installer installed the product. Product Name: Active Directory Management Pack Helper Object.
Product Version: 1.1.0. Product Language: 1033. Manufacturer: Microsoft Corporation.
Installation success or error status: 0.

Hi,
This should be normal, as we can see in the below two articles. When applying Update Rollup 2, UR1 is listed there, and when applying Update Rollup 3, UR1 and UR2 is listed there also.
http://blogs.technet.com/b/kevinholman/archive/2013/04/11/applying-update-rollup-2-ur2-to-opsmgr-2012-sp1.aspx
http://blogs.technet.com/b/kevinholman/archive/2013/09/27/applying-update-rollup-3-ur3-to-opsmgr-2012-sp1.aspx
For example, UR3 can be applied to System Center Operations Manager 2012 SP1 (as released) or a SCOM 2012 SP1 deployment that has had UR1 or UR2 already applied.
Regards,
Yan Li
Regards, Yan Li

The problem with forecast reports in SCOM 2012 after integration with VMM 2012

Hello.
I have problem with forecast reports in SCOM 2012 after integration with VMM 2012. All other reports (not forecasting) works fine. For example, report “Host Group Forecasting” don’t work. The report is generated, but I have error: “Subreport
could not be shown”. I find only errors in SQL Server Reporting logs like this:
library!ReportServer_0-13!1758!06/26/2012-18:26:23:: i INFO: RenderForNewSession('/Microsoft.SystemCenter.VirtualMachineManager.2012.Reports/Microsoft.SystemCenter.VirtualMachineManager.2012.Report.ForecastHostGroup')
processing!ReportServer_0-13!1758!06/26/2012-18:26:28:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: , Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Не удалось выполнить
запрос для набора данных "DiskSpaceUsageForecasting". ---> Microsoft.AnalysisServices.AdomdClient.AdomdErrorResponseException: Execution of the managed stored procedure GetTimeSeriesForecast failed with the following error: Exception has been thrown by
the target of an invocation..
Query (5, 58) Parser: The syntax for '6' is incorrect.
   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.IExecuteProvider.ExecuteTabular(CommandBehavior behavior, ICommandContentProvider contentProvider,
AdomdPropertyCollection commandProperties, IDataParameterCollection parameters)
   at Microsoft.AnalysisServices.AdomdClient.AdomdCommand.ExecuteReader(CommandBehavior behavior)
   at Microsoft.AnalysisServices.AdomdClient.AdomdCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
   at Microsoft.ReportingServices.DataExtensions.AdoMdCommand.ExecuteReader(CommandBehavior behavior)
   at Microsoft.ReportingServices.OnDemandProcessing.RuntimeDataSet.RunEmbeddedQuery(Boolean& readerExtensionsSupported, Boolean& readerFieldProperties, List`1 queryParams, Object[] paramValues)
   --- End of inner exception stack trace ---;
The Russian string “Не удалось
выполнить запрос для набора данных "DiskSpaceUsageForecasting"” is translated to “Could not execute query for data set "DiskSpaceUsageForecasting"”.
I have clean installation SCOM 2012 RU1, VMM 2012 RU1. Integration SCOM with VMM work fine.
SQL collation for all SQL DB instances (SCOM and VMM and SCOM reporting) – “SQL_Latin1_General_CP1_CI_AS”
SQL Analysis service: SQL collation – “Latin1_General” ; language for the server – English (United States)
I think the problem in regional settings. By my opinion there are two possible mistakes:
SQL collation for all SQL DB instances. May be need use “Latin1_General_CI_AS”
as provided by
http://blogs.technet.com/b/momteam/archive/2012/05/25/clarification-on-sql-server-collation-requirements-for-system-center-2012.aspx
Need change regional setting. Question is for what (OS regional setting, SQL Analysis service settings,…) ?

Error: Subreport could not be shown
Opening a report for Client Security might result in the following error being displayed in one or more areas of the report: "Error: Subreport could not be shown."
Background
There are two possible reasons for this error:
1. Wrong location   The reporting server is pointing to the wrong computer running SQL Server or a SQL Server instance.
2. Insufficient permissions   The account configured (in SQL Server Reporting Services) to connect to the reporting database does not have appropriate permissions for the database.
Solution
To determine which reason is causing the error, attempt to directly open the subreport reporting the error, by clicking the name of the subreport.
If the reporting server is pointing to a wrong location, the report displays an error similar to the following:
Error message
An error has occurred during report processing.
Cannot create a connection to data source 'SystemCenterReporting'. Cannot open database "SystemCenterReporting" requested by the login. The login failed. Login failed for user username.
To verify the correct SQL Server computer and instance path
In Report Manager, navigate to the report generating the error and click the Properties tab.
Click Data Sources and under a Shared data source, note the path.
Open the reporting Web site. If you chose the default virtual directory for reports, the URL is: http://hostname/Reports/
If you chose to secure the viewing of reports with HTTPS, the URL is: https://hostname/Reports/
Click SCDW.
In the Connection type list, ensure that Microsoft SQL Server is selected.
In the Connection string box, ensure that the correct SQL Server computer and instance name are entered.
Note:
A period (.) denotes the local computer.
If the account has insufficient permissions, the report displays an error similar to the following:
Error message
An error has occurred during report processing. (rsProcessingAborted) Query execution failed for data set 'DSDashboardComputersTrend'. (rsErrorExecutingCommand) EXECUTE permission denied on object 'prSAS_UX_DashboardComputersTrend', database 'SystemCenterReporting',
schema 'dbo'.
To determine if you are experiencing the SQL Server permissions issue
Open the reporting Web site. If you chose the default virtual directory for reports, the URL is:http://hostname/Reportserver/
If you chose to secure the viewing of reports with HTTPS, the URL is:https://hostname/Reportserver/
Click Microsoft Operations Manager Reporting, click Microsoft Forefront Client Security, and scroll to DashboardComputersTrend.
Click DashboardComputersTrend.
If you are experiencing a SQL Server permissions issue, an error similar to the preceding error appears.
To grant permissions to the SQL Server computer
1. In Report Manager, click SCDW and note the account in the Connect using section. This is the account under which the database is contacted.
2. On the server with the System Center Reporting database, start SQL Server Management Studio.
3. In the tree, expand Security, and then expand Logins. Do one of the following:
If the user account is listed, right-click the account, click Properties, and then go to step 5.
If the user account is not listed, right-click Logins and choose New Login.
4. In the Login name box, enter the user account (domain\username).
5. In the Login Properties dialog box, click User Mapping, and then under Users mapped to this login, select the System Center Reporting check box.
6. Under Database role membership for: System Center Reporting, select the db_owner check box, and then click OK.
Thanks,
Yog Li
TechNet Community Support

System center data access service crashes with event id 26339 ad 26380 in SCOM 2012 Sp1 RTM

hi all,
I have deployed scom 2012 sp1 rtm on Os 2012 std and database is on another VM Machine having SQL 2012 sp1 with OS 2008 R2 SP1 std, suddenly sql vm get stopped and unable to start , so I have delete it from hyper-v 2012 console and imported the VM again
in Hyper-0S 2012 cluster.
Now, System centre data access service get crashed again and again with mentioned events
event 26339, OpsMgr SDKService
event 26380, opsmgr SDkService
An exception was thrown while initializing the service container.
Exception message: Initialize
Full exception: HTTP could not register URL
http://+:51905/ConnectorFramework/ because TCP port 51905 is being used by another application.
The System Center Data Access service failed due to an unhandled exception.
The service will attempt to restart.
Exception:
System.ServiceModel.AddressAlreadyInUseException: HTTP could not register URL http://+:51905/ConnectorFramework/ because TCP port 51905 is being used by another application. ---> System.Net.HttpListenerException: The process cannot access the file
because it is being used by another process
   at System.Net.HttpListener.AddAllPrefixes()
   at System.Net.HttpListener.Start()
   at System.ServiceModel.Channels.SharedHttpTransportManager.OnOpen()
   --- End of inner exception stack trace ---
   at System.ServiceModel.Channels.SharedHttpTransportManager.OnOpen()
   at System.ServiceModel.Channels.TransportManager.Open(TransportChannelListener channelListener)
   at System.ServiceModel.Channels.TransportManagerContainer.Open(SelectTransportManagersCallback selectTransportManagerCallback)
   at System.ServiceModel.Channels.HttpChannelListener`1.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Dispatcher.ChannelDispatcher.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at Microsoft.EnterpriseManagement.ConnectorFramework.ServiceDataLayer.ConnectorFrameworkDataAccessChannel.Initialize()
   at Microsoft.EnterpriseManagement.ServiceDataLayer.DispatcherService.Initialize(InProcEnterpriseManagementConnectionSettings configuration)
   at Microsoft.EnterpriseManagement.ServiceDataLayer.DispatcherService.InitializeRunner(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
Kirpal Singh

Hi Kirpal
Can you try this it might help as its an known issue of getting event id 's 26361,26380 try out & lets see if it helps.
The manifest files are located on the RMS at the \Program Files\System Center Operations Manager 2007\ root directory. The manifest files will need to be edited for the config and sdk service on affected RMS. The file names are:
Microsoft.Mom.Sdk.ServiceHost.exe.config
Microsoft.Mom.ConfigServiceHost.exe.config
In between the EXISTING <runtime> and </runtime> lines – you need to ADD a NEW LINE with the following:
<generatePublisherEvidence enabled="false"/>
This solution disables CRL checking for the specified execute-ables, permanently.

SCOM 2012 SP1 SQL Server 2008 R2 Clustering Monitoring?

We have a new print management system that was setup using SQL server 2008 R2 clustering. Right now we have SQL MP (monitoring)(discover) 6.3.173.1. They had a failover occur a week ago and SCOM didnt throw any alerts. As a temporary
fix, I found some correlated events and setup a monitor for those events on the servers. However, the system owner wants to know if there is a MP that will monitor for a SQL cluster failover event. I have looked and looked and cant seem to find
anything that gives a whole lot of detail on this.
Thanks
EFD
Warm Fuzzies!

Yes, you can monitor SQL Cluster 2008 using SCOM 2012 SP1. but you need to install SQL MP and Windows Cluster MP and Enable proxy Agent on physical nodes.
You can refer below link {it's same for SCOM 2012}
http://blogs.technet.com/b/birojitn/archive/2010/04/14/sql-server-2008-cluster-monitoring.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

How SCOM Agent will get degraded which is installed on the monitored server while reverting Back from CU6 to CU3 of SCOM 2012 SP1?

Hi,
I have SCOM 2012 SP1 (CU3) inatalled on base server 2012 Standard which is a VM.
Now I am planning to Go for CU6 and thinking to take snapshot of complete SCOM server instead of taking Data Base Backup. Which should I prefer?
If i am going for the Snapshot for complete SCOM server and run the CU6 complete setup. And some thing went wrong and not able to fix the issue.
And I need to reverted back to CU3 using Snspshot.
Now, how can I revert the Agent Version to CU3 level which is already upgraded to CU6?
Thanks
Amit Raj

Hi,
all agents with CU6 will be work fine with SCOM CU6.
But if you decide back to the CU3 you need to backup your OPsDB and DWH (if CU6 contains sql scripts).
In regard agents you can use repair from OPsMGR console.

SCOM 2012 SP1 Can't get email alerts for Heartbeat Failure or Computer Unreachable when combined with Group.

Hello,
I have SCOM 2012 SP1 RTM POC lab. I have created a dynamic group that picks up my system center servers based on some simple criteria and this works fine.
I have set up a subscription for critical and high severity alerts originating from this dynamic group called SCOM Servers to send emails to a distribution. This also worked well for any critical alert that was NOT Heartbeat Failure or Computer Unreachable.
I see those in the console but no email.
So I set up a new subscription by right clicking on the alerts and here's the kicker. If add no other conditions to these subscriptions, they will send emails to the DL I provided, but if add the condition initiating from group, and specify my dynamic
group SCOM servers, no email alert. But the alert still appears in the console.
Any ideas on this? I would like the appropriate support groups to get these types of alerts for the servers that they support (i.e. SCOM will get SCOM servers, Exchange Admin will get Exchange and never the two roads shall meet.).
I even tried some internet posted custom management pack, but I couldn't import it after adding the code that he listed.
I mean, isn't this a basic requirement for any mid-sized company?
Any help is greatly appreciated.

Hi Donald,
Like Dan says you need to add the "Health Service Watcher" objects to the groups as wel. Unfortunately this cannot be done in the Dynamic group Editor but has to be done in the XML. Export the XML and add the following piece of code between the
lines </MembershipRule></MembershipRules>:
<MembershipRule>
<MonitoringClass>$MPElement[Name="SystemCenter!Microsoft.SystemCenter.HealthServiceWatcher"]$</MonitoringClass>
<RelationshipClass>$MPElement[Name="MicrosoftSystemCenterInstanceGroupLibrary7084300!Microsoft.SystemCenter.InstanceGroupContainsEntities"]$</RelationshipClass>
<Expression>
<Contains>
<MonitoringClass>$MPElement[Name="SystemCenter!Microsoft.SystemCenter.HealthService"]$</MonitoringClass>
      <Expression>
<Contained>
<MonitoringClass>$MPElement[Name="MicrosoftWindowsLibrary7084300!Microsoft.Windows.Computer"]$</MonitoringClass>
          <Expression>
            <Contained>
              <MonitoringClass>$Target/Id$</MonitoringClass>
            </Contained>
          </Expression>
        </Contained>
      </Expression>
    </Contains>
</Expression>
</MembershipRule>
Save the XML delete the old one in OpsMgr and import the edited.
For SP1 the SystemLibrary version is 7.0.8430.0. If this is not your version you need to edit this in the code above.
Hope this helps,
Regards Marthijn van Rheenen
Blog: Heading To The Clouds

Upgrading from SCOM 2012 SP1 to SCOM 2012 R2 what CU do i install? CU5?

Hi,
I just upgraded from SCOM 2012 SP1 to SCOM 2012 R2. What CU version should I install? CU5?
Thanks
K

The most current CU version os SCOM 2012R2 is CU4
You can download it from
https://support.microsoft.com/kb/2906925?wa=wsignin1.0
For detail description of SCOM 2012 R2 CU4, you may refer to
http://support.microsoft.com/kb/2992020
and
http://syscentercldman.blogspot.hk/2014/12/update-of-scom-2012-r2-ur4.html
Roger

SCOM 2012 SP1 Integration with Qlikview

Hi ,
can anyone help me with information on how to integrate SCOM 2012 Sp1 and Qlikview ?
Any pointers or documentation will be greatly appreciated.
Thank you,

Hi,
I recommend you go to Qlik Community to find if there have a solution.
Welcome to Qlik Community
http://community.qlik.com/welcome
Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party
contact information.
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.

How to Custom Report using sql server report builder for SCCM 2012 SP1

Hi ,
I am new to database, if i want to create a manual report using sql server report builder for SCCM 2012 SP1, what step should i take.
i want to create a report in which computer name, total disk space, physical disk serial no come together. i already added class (physical disk serial no.) in hardware inventory classes. refer snapshot

Hi,
Here is a guide on how to create custom reports in Configuration Manager 2012, it is a great place to start, change to the data you want to display instead.
http://sccmgeekdiary.wordpress.com/2012/10/29/sccm-2012-reporting-for-dummies-creating-your-own-ssrs-reports/
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

SCOM 2012 SP1 Test environment - "New View" is greyed out?

I'm new to SCOM....
I just created a SCOM 2012 SP1 test environment, but for some reason the "New View" button is greyed out. (I attached a screenshot)
I can't figure out why and it pretty frustrating. I'm assuming it is a permissions issue, but I can't figure out how to get this feature enabled.
any assitance is greatly appreciated.

Hi,
The "New View" is greyed out if you try to create a new View in a sealed Management Pack.
You can create a new View only in unsealed Management Pack's inside the console.
Cheers
Christoph Maresch | My blogs: blog.cmaresch.at | XING:
Christoph Maresch
| Linkedin:
Christoph Maresch

Non supported version of SQL with new install of SCOM 2012 SP1

Similar Messages

Maybe you are looking for