SCOM 2012: A report to show a server's uptime?

I need to write a report showing the availability of a number of servers which form a "system" and wanted to ask, which properties of each computer do I use for this in the report?
If I add all available properties, I get the following:
Windows Computer: Uptime=0, Downtime=100
Health Service: Uptime=100, Downtime=0
Health Service Watcher: Uptime=100, Downtime=0
Microsoft.Systemcenter.ManagementService: Uptime=100, Downtime=0
I know that this server has been up 100% during the test period so I'm confused as to why "Windows Computer" is showing Uptime as "0"?

Hi,
Did you run the Availability report under Microsoft generic report library for those servers?
What conditions did you choose as downtime:
Here is my result when only choose unpalnned Maintenance as downtime:
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]

Similar Messages

Is it possible to deploy 2 SCOM 2012 R2 reporting in a SQL server which already has SCOM reporting of a different management group but with 2 different reporting instance.

Hi Experts,
I have a typical situation in the LAB environment. Hope some one helps. I have Installed a SCOM 2012 R2 with SQL 2012 SP1 in a single server (Management group 1). I have installed another management group on another server using this SQL server for its database
so i have everything going fine.
The first management group has its reporting installed in the SQL server. For the second i created a new named instance for that. But i cannot run the SCOM setup in the SQL server (Also holding the Management group 1 MS) as 1 st reporting is already there.
When i run the setup it is asking me to repair it. I don't get the install option so i can install the reporting for management group 2 in the named instance.
Default instance is being used by the 1st management group.
Can any one figure a possibility for installing 2 SCOM reporting services for different management groups in a same SQL 2012 server please.
Gautam.75801

Hi Yan Li,
Thank you for the reply. So as you are aware If i need to instal reporting, i need to run the SCOM 2012 R2 setup in the SQL server and select reporting and select the
instance and then mention the management server there right. I am not getting that option there it is asking me to remove or repair the existing installation as there is already a SCOM entire setup including reporting there. As it is a lab there is no problem
in testing. I have 2 reporting instances. Any suggestions for me on how to overcome this issue and deploy the second reporting in the new named instance ?
Below is the screenshot of the error what i am talking about when i run SCOM 2012 R2 setup to install reporting in the SQL server
When i click on add feature reporting is greyed out (As already 1st management groups reporting is installed)
When i click on remove or repair it
uninstalls the existing one. But i want both SCOM 2012 r2 reporting to be there(For both Management group). Is it possible ? If yes What is the trick to run the setup ?
Gautam.75801

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

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 SP1 Reporting Services empty

Hello,
When i open Reporting from management console, reporting work space empty, but when i turn off windows firewall (Windows 2008R2 SP1) on my SQL server 2008 R2 SP2 i can see all MP/Data in Reporting action panel.
I've opened these ports :
1433/TCP, 1434/UDP, 5723/TCP, 137/UDP, 138/UDP, 139/TCP, 445/TCP,135/TCP,
But it did not help.
What is the configuration of the firewall for Reporting Service?

Hello !
Could you check this post please :
http://social.technet.microsoft.com/Forums/en-US/c219058f-d10d-48ca-8a61-ca9f1340bfdb/scom-2012-empty-reporting-workspace?forum=operationsmanagergeneral
Hope this helps.
Note: This posting is provided 'AS IS' with no warranties or guarantees, and confers no rights. Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable. This helps the community, keeps the forums tidy, and
recognises useful contributions.

SCOM 2012 R2 Reporting Services High Availability Configuration Setting

Can u guys tell me how I can make a scom 2012 r2 report server high availability configuration kindly share the steps or screen of it.

SCOM reporting feature is depend on SQL reporting and as a result you may refer to SQL reporting service high availability.
For detail, pls. refer
http://technet.microsoft.com/en-us/library/bb522745.aspx
http://www.mssqltips.com/sqlservertip/2335/scale-out-sql-server-2008-r2-reporting-services-farm-using-nlb-part-1/
http://www.mssqltips.com/sqlservertip/2336/scale-out-ssrs-r2-farm-using-windows-network-load-balancing-part-2/
http://technet.microsoft.com/en-us/library/hh882437.aspx
Roger

SCOM 2012 Installation does not show the SQL Server Instance for reporting services

I have an issue when I try to install SCOM 2012 with the Reporting Server feature, so in the step that I have to select a SQL Server Instance I cannot do that, because as you can see in the picture no one option appears.
In my scenario I have a DCSERVER, SQLSERVER2008 R2, SCCMSERVER 2012 and in other server I are trying to install SCOM 2012. I are trying to use the same SQLSERVER to SCOM 2012.
Should I do other procedure on SQL Server before to continue? I will apreciate someone could say me what I need to do to resolve this issue.
Regards,
Paul Mendoza.

Hi Paul
Can you confirm that SQL Reporting Services is installed on the server that you are doing the install.
For a lab environment where you have SCOM Management Server, Web Server on one server and SQL Server on another you need to:
- run setup on the SCOM Server and choose NOT to install reporting. The install here will create the OperationsManager database and OperationsManagerDW (reporting) database.
- run setup on the SQL Server where SQL Reporting Services is installed. Then choose to install reporting. You should then see the SQL Reporting Services instance on the above window which is blank in your screenshot.
Take note of the warning in that window - SCOM uses its own role based security within SQL Reporting Services and this can break other reporting. E.g. you can't install SCOM and SCSM reporting (SQL RS component) together.
Cheers
Graham
New SCOM 2012 Blog! - http://www.systemcentersolutions.com/blog/
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/

SCOM 2012 R2 Reporting services installation error - data reader account

I have successfully installed SCOM 2012 R2 and SQL 2012 SP1 on the same server. I was trying to install the reporting server piece of SCOM.
When I get to the part that asks for a domain account, I get this error:
"Data Reader account provided is not same as that in the management server"
The account is not the same as the management server, and it does have read access to the data warehouse and reporting databases. Is there some other permission this account needs for reporting services?
Thanks.

Adding more info：
I usually create the following account for SQL:
AD accounts for the following to be used with SQL Services:
SQL Agent for SQL Server Agent
SQL Analysis Services for SQL Server Analysis
SQL Database Engine for SQL Server Database Engine
SQL Reporting Services for SQL Server Reporting Services
For SCOM I create the following accounts:
SCOM DR - Used to deploy reports
SCOM DWR - for writing data from the management server to the reporting DW
SCOM MSA - Performs default actions
SCOM SDK - Used for updating/reading information from the operations Manager Database - Needs to be local administrator on the SCOM server
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 use the SCOM 2012 Web Reporting page

Hello all-
   We are on SCOM 2012 SP1. I just have a general question about reporting. I know there is a "Reporting" tab in the real, locally installed, SCOM Operations Console software. That part I get. I see that there
are many pre-made reports the for me to run. For example under Microsoft Server 2008 Operating System (Monitoring) folder there is a
Performance History report. When I double click on it, it takes me to the report window where I can click
Add Object and add a server and then click
Run.
This is pretty simple in concept.   BUT very few people at my company have the full Operations Console installed on their machine. And as I'm sure you know, the SCOM Web Console does not have a Reporting Tab. So they have to use the
SCOM Reporting website to run such reports. I found that you can get to this page at the url:
http://<reporting server>/Reports
This does bring up the Reporting console. On the list I do see a Report.Windows.Server.2008.PerformanceHistory listed. So this surely seems to be the equivalent from my screenshot above.   However, it's not even close to user friendly like
the Reporting area in the SCOM operations console software. There's multiple fields at the top. All of which are required, and almost none of which have dropbox or other ways to help you fill them in. I have no idea what to put into these boxes or the format
to use.
What am I missing here? Is there a more user friendly interface anywhere? In an ideal world, I'd really love to have a user interface where I can post the links to a few popular reports, like CPU and Disk Space for example. Then ideally
all the user would have to do is select their servers and the time frame and that's all.   Which really is what you do in the Operations Console software.   So isn't is it that easy in the web reporting tool? Is there a guide or how-to
section somewhere I'm missing? Or just a more friendly looking way to get at this information?

Well, my first screen shot above is squished, so you really can't see it. But what I'm saying is that the same report in the SCOM software has the level of configuration I want on it.   It allows you to pick the date range and add objects
to it, then you can click on Run.     However when I access the same report on the reporting console, it has all these extra fields. None of which I know how to fill in properly.
I would ultimately like my customers to be able to do exactly that in the web version. Pick their server and their date range and run it.   There are not likely going to be too many reports like you're mentioning which I can completely configure
before hand, so they just click on the link to have it run. Most times I'd like my users to at least be able to select a server name.
Any idea how I would simplify the web version of the report? Or why they look so very different?

SCOM 2012 R2 Reporting is down

Hi All,
Reporting is down in SCOM 2012 R2.
Environment and issue: I have a small management group which consists of two MS and a SQL DB which is clustered. The reporting binaries have been run on node1 of the DB server only and the node 1 only has the follwing registry key :
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\System Center Operations Manager\3.0\Reporting,\ DWDBInstance
Now , all the sql resources are on Node 2 and when i run the report it says :
Reporting Services Error
An internal error occurred on the report server. See the error log for more details. (rsInternalError) Get
Online Help
And when i dug into the log it says:
library!ReportServer_0-1!1940!01/18/2015-21:07:03:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: Incorrect security descriptor version, Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
An internal error occurred on the report server. See the error log for more details.;
Earlier the following link format use to work but it does not now:
http://clustername/ReportServer_instancename
I tried to change it to node 2 like below [which does not work]:
http://node2/ReportServer_instancename
Finally i just tried with node 1 which works just fine via web browser:
http://node1/ReportServer_instancename
I think switching the sql resources back to node1 will solve the situation, i have already created a ticket to the DB team to look into it.I know that SCOm reporting is not cluster aware and that is how i just ran the reporting server binaries on the first
node.
Could you help me with the change of reporting server entries in either registry or config files or DB tables which could tell SCOM to look and contact only the node1 for reporting and not the node2.
Any comments would be greatly appreciated as I need to fix this soon else I would not be able to send the monthly SLA reports to my stakeholders as the Service Level Report Library option is not visible via SCOM web portal reporting.
Regards,
Techie Seeker.

Hi,
As SQL cluster is not supported for operaion manager reporting(more information, please check
Operations Manager Reporting – Supported SSRS Configurations ), it is suggest you to move your data warehouse to another SQL:
How to Move the Data Warehouse Database
https://technet.microsoft.com/en-us/library/hh268492.aspx?f=255&MSPPError=-2147217396
Moving the Data Warehouse Database and Reporting server to new hardware–my experiencehttp://blogs.technet.com/b/kevinholman/archive/2010/08/25/moving-the-data-warehouse-database-and-reporting-server-to-new-hardware-my-experience.aspx
In addition, although cluster is not supported, someone else really have this done, you may refer to
Moving Operations Manager Data Warehouse Database part in the below article,and you may find registry keys and databases that needed to verified.
SCOM DataBases Migration to SQL Cluster
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.
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 SP1 Report Timed out

Hi All,
My large reports are timing out after 30 minutes in SCOM 2012 SP1, with the error: The Operation has timed out
I'm trying to run the Performance Detail report from Microsoft Generic Report Library against Windows Server 2008 Operating System group (1400 servers) for last 1 year for Percent memory used. I can run the same report for Windows Server 2012 Operating System
group (200 servers) sucecssfully.
I've already verified and configured the reporting services for reports to not time out.
http://www.systemcentercentral.com/forums-archive/topic/scom-reports-large-reports-time-out/
http://anoopcnair.com/2011/07/20/configmgr-sccm-sql-server-reporting-service-timeout-expired/
Any suggestions?
Thanks,
Harry
Thanks, Harry :-)

Hi There,
Based on my knowledge, When ever a SQL query is ran against any database the query output is executed and stored in TempDB and then it is shown to your SSMS or reporting application.
So i would suggest you check the size of the temp SQLDB and see if auto growth is enabled for that and does your drive as well have enough space to hold that temp DB in its local drive if the DB grows its self.
As querying 1 years data for 1400 servers is a huge data and requires lot of time and space.
I had a similar issue here, Look here:
https://social.technet.microsoft.com/Forums/en-US/6420f4e1-fc21-49c9-8fed-eddbe6cecabf/my-sql-server-seems-to-be-creating-huge-tempdbmdf-file-post-database-migration?forum=sqlservermigration
Gautam.75801

SCOM 2012 - Use Powershell to put specific server and contained objects into Maintenance Mode

I am still trying to develop what I thought was going to be an easy script, to put a specific server and all it's contained objects into maintenance mode in SCOM 2012.   Not a group, but just one specific server and all it's stuff.
My script to START maintenance mode has two parameters:
1. The FQDN. So for example: server1.contoso.com
2. The amount of minutes to put into maintenance mode
Then it does the following to START maintenance mode:
Import-Module OperationsManager
$Instance = Get-SCOMClassInstance -Name $FQDN
If ($Instance)
$newEnd = ((Get-Date).AddMinutes($minutes))
Start-SCOMMaintenanceMode -Instance $Instance -end $newEnd -Reason "PlannedOther" -Comment "Comments here"
This seems to work from what I can tell. I know that when you schedule maintenance mode manually in SCOM, there is an option to apply to "Selected objects and all their contained objects". I do not know if that is occurring based on
my code above.   But I think that is what I want to happen.   I just want all monitoring and alerting for the specified server to stop.   So if you think I need to change the above code so that it gets all the "contained
objects" please let me know.
The second part, which I know for a fact isn't fully working, is intended to stop maintenance mode for a server.
My script to STOP maintenance mode has only one parameter:
1. The FQDN. So for example: server1.contoso.com
Then it does the following to STOP maintenance mode:
Import-Module OperationsManager
$Instance = Get-SCOMClassInstance -Name $FQDN
If ($Instance)
$MMEntry = Get-SCOMMaintenanceMode -Instance $Instance
If ($MMentry)
#basically sends an end time of 1 minute from when the script is run
$newEnd = ((Get-Date).AddMinutes(1))
Set-SCOMMaintenanceMode -MaintenanceModeEntry $MMEntry -EndTime $NewEnd -Comment "Removing from Maintenance Mode"
This part does seem to work partially.   It does remove the server from maintenance mode. However, I suspect that it's not removing all the "contained objects" from maintenance mode because when I run the script to stop maintenance
mode on a server, the little maintenance mode icon in SCOM does go away but the overall light for the server stays set to "Not Monitored".   It never turns back to the green checkbox and says "Healthy".   When I start
and stop maintenance mode manually I can see that the green Healthy checkbox comes back. But when I try to run my above code to do it via script, it stays at "Not Monitored" instead.
Can someone help me out here? Looking for answers to two questions:
1. Does my Start maintenance mode code look ok? Will that put a server and all it's contained objects into maintenance mode?
2. What do I need to hadd to my Stop maintenance mode code, so that it correctly stops maintenance mode on the server and all its objects and everything starts to be monitored again?
Thanks in advance! Please let me know if you need any more information in order to be able to help me!

Hello, thanks for your response. Unfortunately, it does not appear that the link you provided works.
As far as not including "selected objects and all their contained objects" I am wondering if there is a way for me to tell for sure. One thing I found was that if I run this script and put the server into maintenance mode, then I go into
SCOM and click on Edit Maintenance Mode for that server, it shows me the details.   It has some comment, and my selected reason, based on the code I posted above.   It also DOES have "selected objects and all their contained objects"
selected at top. So it seems to me like it is working correctly, and does contain all the objects.   If you think that 'Edit' screen would be inaccurate for some reason, please let me know. Or if you know of a way for me to check and
confirm, please let me know that as well.
As for REMOVING it from maintenance mode, I did eventually find a line of code that I think works. Here's what my code looks like now:
Import-Module OperationsManager
$Instance = Get-SCOMClassInstance -Name $FQDN
If ($Instance)
$MMEntry = Get-SCOMMaintenanceMode -Instance $Instance If ($MMentry)
$Instance.StopMaintenanceMode([DateTime]::Now.ToUniversalTime(),[Microsoft.EnterpriseManagement.Common.TraversalDepth]::Recursive);
When I use the above code to STOP maintenance mode, the green checkmark does reappear for the server, and everything seems to be being monitored again.   Unlike before, where the maintenance mode icon would go away, but it would never change back
to saying 'Monitored' again. So I think that changing that one line to stop maintenance mode seems to have done the trick.
So I guess my last concern now is just putting in maintenance mode initially, as I was talking about above. If you still think the 'Edit Maintenance Mode' screen is not a good indicator of what my code does, please let me know.

Scom 2012 r2 - report viewer controls are not installed

Hi
I'm stop on this error when installing the operation console and web console
report viewer controls are not installed
OS : Windows 2008 R2
SCOM Version : SCOM 2012 R2
I installed the install Report Viewer Redistribution 2008 SP1 and install
Report Viewer Redistribution 2010 ans I'm still getting that error
Please advise ...
Robert

Hi
The requirements are listed here http://technet.microsoft.com/en-us/library/dn249696.aspx#BKMK_RBF_OperationsConsole
Install Microsoft
Report Viewer 2012 Redistributable Package then it should work.
Cheers,
Stefan
Blog: http://blog.scomfaq.ch

SCOM 2012 Console not responding when the server to be connected is down.

SCOM 2012 Console hangs when the server to be connected is down or gone (e.g. lease replaced). How to change the 'connection server' to point to a valid server without re-installing SCOM Console? Thx

To enable high availability for your Operations Manager Data Access service, you can use Network Load Balancing (NLB)
PLz refer: http://blog.coretech.dk/kra/how-to-make-operations-manager-2012-rc-scom-2012-fault-tolerance/
Faizan

How to use SCOM 2012 R2 Monitoring the standalone Windows Server

Greetings,
I want to use SCOM 2012 R2 to monitoring the standalone Windows Server that does not joined the domain. would you please guide me how to configure it.
Thanks
Frank@Hiweb 冯立超@瀚博资讯

I found the answer, as following:
http://pkjayan.wordpress.com/2010/05/17/agent-managed-non-trusted-servers-without-gateway/
and
http://blogs.technet.com/b/stefan_stranger/archive/2012/04/17/monitoring-non-domain-members-with-om-2012.aspx
Frank@Hiweb 冯立超@瀚博资讯

SCOM 2012: A report to show a server's uptime?

Similar Messages

Maybe you are looking for