SCOM 2012 SP1 - Created a new group and unable to "find" newly created group to create custom report

Hello,
I just created a new custom dynamic group based on database instances using a wildcard. The group "DBgroup" populates just fine, I can see the members when choosing to view them via the group properties. My issue is that when I'm going
into the reporting pane, choosing the MS generic report library, and then choosing custom configuration...I am unable to "FIND" my group that i just created? My questions are is there a length of time in which this group will get populated
to the report server or do I have an issue? I see no errors in the logs on the report server or management server. I have not seen this before and I'm unsure where to go from here. Any help is appreciated, thanks.

Hello,
Does the group pop-up in the list now? It may take hours for the new Computer Group could be used in the reports.
Besides, did you define a Group Scope for your user role?
Thanks,
Yog Li
TechNet Community Support
It's been over 48 hours now and still do not see the new groups. I have no group scopes defined

Similar Messages

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

SCOM 2012 SP1 Datawarehouse event id 31553 and after 2 minutes successful id 31572

Hello guys,
I'm running SCOM 2012 SP1 and in one of my 3 Management groups i got the following events. I get them every few minutes and i cannot explain it. I have checked the aggregation of the DW and its fine. I Have extended the timeout from 5 to 15 minutes ... What
should i do next. Please help with this. I have checked all 2007 posts but they are not related to my problem. I have tried a number of queries but they don't return any result. Do I have a SQL server performance issue ?
Date and Time:
10/27/2014 11:05:10 AM
Log Name:
Operations Manager
Source:
Health Service Modules
Generating Rule:
Data Warehouse related event collection
Event Number:
31553
Level:
Error
Logging Computer:
User:
N/A
Description:
Data was written to the Data Warehouse staging area but processing failed on one of the subsequent operations. Exception 'SqlException': Transaction (Process ID 71) was deadlocked on lock resources with another process and has been chosen as the deadlock
victim. Rerun the transaction.
One or more workflows were affected by this.
Workflow name: Microsoft.SystemCenter.DataWarehouse.CollectPerformanceData
Instance name: server2.mymg.corp
Instance ID: {EBD49B2A-D314-07DF-9E2C-B79CF86B1A72}
Management group: MyMG
Date and Time:
10/27/2014 11:26:36 AM
Log Name:
Operations Manager
Source:
Health Service Modules
Generating Rule:
Data Warehouse related event collection
Event Number:
31553
Level:
Error
Logging Computer:
server10.mymg.corp
User:
N/A
Description:
Data was written to the Data Warehouse staging area but processing failed on one of the subsequent operations. Exception 'SqlException': Transaction (Process ID 68) was deadlocked on lock resources with another process and has been chosen as the deadlock
victim. Rerun the transaction.
One or more workflows were affected by this.
Workflow name: Microsoft.SystemCenter.DataWarehouse.CollectPerformanceData
Instance name: server10.mymg.corp
Instance ID: {DBDD19A5-98B3-F90A-641E-7C4693BFD6EB}
Management group: MyMG
Event Data:
View Event Data
< DataItem
type ="
System.XmlData "
time =" 2014-10-27T11:26:36.2773982-05:00
" sourceHealthServiceId
=" DBDD19A5-98B3-F90A-641E-7C4693BFD6EB
" >
< EventData
>
< Data > MyMG</
Data >
< Data >
Microsoft.SystemCenter.DataWarehouse.CollectPerformanceData
</ Data
>
< Data > server10.mymg.corp
</ Data
>
< Data >
{DBDD19A5-98B3-F90A-641E-7C4693BFD6EB}
</ Data >
< Data >
SqlException </
Data >
< Data >
Transaction (Process ID 68) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
</ Data
>
</ EventData
>
</ DataItem
>
User:
N/A
After 2 minutes i will have the 31572 which is
Data writer successfully performed data maintenance operations. What would be the reason for this ?

There are a few things that can cause this. Your hint here is the deadlock message; processes are competing to write data in the DW, so you need to find out what that is. You also have a message stating that data is written to staging, but timing out moving
the data. If you happen to be running the Exchange MP, this creates an additional data set that can quietly clog up the works--but you would see that dataset in the event message as well.
Because you say aggregation is moving, try following these steps, they have served me well. I think you are seeing the results of data getting 'stuck' that causes the system to slowly choke itself. Note: You can focus on just the perf dataset, but always
a good idea to make sure everything is healthy while you're at it.
Steps:
Check to see if the staging area for data written to the DW is clear and data is moving:
select count(*) from Alert.AlertStage
select count (*) from Event.eventstage
select count (*) from Perf.PerformanceStage
select count (*) from state.statestage
These values normally rise and fall rapidly. If you open each table, they should also only contain recent data. If you find any data points older than a day, something is stuck. In one case I found state.statestage stuck around 14300. A look at the data
showed a few hundred rows of data that had information 4 months old.
See if data is moving (if you have old data, the answer is evident):
1. select * from StandardDataset
2. Plug the appropriate GUID into exec StandardDatasetMaintenance @DatasetId='<GUID from query>'
3. See if the count decreases
If it doesn't, if the data is expendable, just truncate the table (don't be afraid to do this--if OpsMgr is choking, stop the choking, and don't fret over missing data points)
truncate table state.statechange
Optional query:
Plug the DatasetId into the below query
USE [OperationsManagerDW]
DECLARE @DataSet uniqueidentifier
SET @DataSet = (SELECT DatasetId FROM StandardDataset WHERE DatasetId = '138B1324-BE31-42D7-A6CB-EA10139E309C')
EXEC StandardDatasetMaintenance @DataSet
Note: Valid current values are Event, Alert, CM, Perf, State
If these check out, it's time to
See if any SQL jobs are running that could be interfering
If you are not out of space, but close, and autogrow is killing your performance
Run the large table query to see if you have unchecked perf data growth that exceeds the performance capability of the SQL box
You may indeed have a SQL performance issue, but that's the last thing you troubleshoot--make sure OpsMgr is healthy first

SCOM 2012 SP1 Update Rollup 5 - DB and DW SQL script and the Management Packs

Hi,
I am applying SCOM 2012 SP1 update rollup 5 from KB article : 2904680.
Step# 4 and 5 from the "Installation Information" sections says to run the SQL queries(UR_Datawarehouse.sql and Update_rollup_mom_db.sql) located at "%SystemDrive%\Program Files\System Center 2012 SP1\Operations
Manager\Server \SQL Script for Update Rollups\."
But I do not have "System Center 2012 SP1\Operations Manager\Server \SQL Script for Update Rollups\." folder location on my SCOM Management Servers. Similarly I do not have the MPs given in Step #6.
Can someone please let me know from where else can I get these SQL scripts and the MPs. What if I don't run these SQL scripts. Is that OK?

You will find it on below path%SystemDrive%\Program Files\System Center 2012\Operations Manager\Server \SQL Script for Update Rollups\.
inside system center 2012 folder> search to Server folder and inside it you will find SQL Script
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).

Problem upgrading from SCOM 2012 SP1 to R2 (near impossible to uninstall SCOM agent from Management Server)

I'm trying to upgrade our SCOM 2012 SP1 environment to R2, but I have a heck of a problem getting there.
We currently have an test installation with SCOM 2012 SP1 with Management Server and Console on a single 2012 Standard server. The database are located on a remote server. The R2 setup stopped mid way through the setup, because the SCOM 2012 SP1 agent is
installed. And I could NOT remove it my any normal means. I've tried "misexec.exe /x productcode", the setup, powershell uninstall and so on. Nothing works, because the management server installation is blocking the uninstall. The uninstall says
I have to remove the management installation first. And that's not gonna happen.
I had to follow this guide to finally getting through the setup: http://www.opsman.co.za/forcibly-removing-a-scom-agent-that-cannot-be-uninstalled-by-normal-means/
In addition to searching for the agent msi install key in registry, and deleting everything. After I did this, the setup is working, and the SCOM management server, console and DB are up to date. However, the Microsoft Monitoring Agent are STILL there in
Control Panel. And this can NOT be the most healthy way of getting through the setup.
I'm about to upgrade to R2 in our production environment with 3 management servers, and I would hate to go through this sketchy process there as well. Just for the record, I have no idea why the agents are installed on our management servers.
Any of you have tips as to how I can get rid of the agents more gracefully?

Hi
Thanks for the replay guys!
None of those links touch my problem I'm afraid. I have followed the Upgrade guides you pointed to, step by step. But the setup does not Complete. There's problems during the actual software Upgrade of the management servers (3'rd step in the Upgrade page).
I've dived into the Application logs and installation logs, and as far as I can tell, it stops because it has trouble upgrading while the server has the 2012 SP1 Agent installed. I do not remember the actual error text right now, but I can get it in a few
days.
Anyhow, the setup DID move on once I removed most of the registry information of the agent installation. So. that leaves me to the conclusion that the agent IS in fact stopping the setup. Either the agent are malfunctioning, or the setup do not expect the
agent to be present on the management servers. I suspect the latter to be the the most plausible. At least until Yan Li told me this was normal.
So, I'm not sure what to think. I'm pretty much forced to remove this agents, as this is the only thing allowing me to continue the setup. At least untill I'm told otherwise. But I hate to do it this way. It's so dirty. The registry is pretty much cleaned,
but there's still Application files present, and the agent is still in the Control panel and can be started. It's not something I would like to do in our prodution environment.

Error 1723 when removing scom 2012 sp1 agent

Hi All,
I am trying to remove the scom 2012 SP1 agent from a machine and i get an error - 'Error 1723. There is a problem
with this Windows Installer package. A DLL required for this install to complete could not be run.
Any idea how can i remove the agent from the box. Let me now if any other info required to give a hint to the problem.
Durgesh Kumar

Hi,
Reinstall the agent, and the uninstall ? If possible, reboot the server and then uninstall?
Same issue here:
http://answers.microsoft.com/en-us/windows/forum/windows_8-windows_install/get-error-1723-there-is-a-problem-with-windows/3d68fc4b-c968-4796-a270-27027a52de3f?page=2
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

SCOM 2012 R2 Agent Deployment - Uninstall Old and Install New

By chance anyone come up with a scripted method for removing an existing SCOM 2012 SP1 agent and installing a new 2012 R2 agent? While I've come across a few scripts I'm trying to kill a few birds with one stone. This is a cross-domain attempt where the
SCOM servers sit in one domain and the member servers are scattered across multiple domains. Member servers range from Windows Server 2003, 2008, and 2012. In most cases the servers have the 2012 SP1 agent installed and in some cases there are multiple management
groups from previous SCOM standups. In addition there's a separate DEV SCOM 2012 R2 environment to manage DEV/QA servers. Active Directory Integration is configured and I have the necessary security groups created. There is a group policy created which is
filtered to just that security group. So the plan is to simply drop the servers into the correct group and have the agent installed via group policy start up script. ADI should have DEV servers appear in DEV SCOM and PROD in PROD SCOM.
Although there are ways to facilitate agent deployment via the console I need to perform a staged migration against a ton of server so as to not impact the existing production environment. So I'd rather do this remotely to pre-selected servers. This process
should involve removing the existing agent, installing the new one, and if possible removing any existing management groups. So far I've come up with the following:
Uninstall SCOM Agent:
%WinDir%\System32\msiexec.exe /x <path>\MOMAgent.msi /qb
Install SCOM Agent:
msiexec.exe /i \\path\Directory\MOMAgent.msi /qn /l*v \logs\MOMAgent_install.log USE_SETTINGS_FROM_AD=0 MANAGEMENT_GROUP=<MG_Name> MANAGEMENT_SERVER_DNS=<MSDNSName> ACTIONS_USE_COMPUTER_ACCOUNT=0 ACTIONSUSER=<AccountUser> ACTIONSDOMAIN=<AccountDomain>
ACTIONSPASSWORD=<AccountPassword>
Remove Management Group via Script
http://gallery.technet.microsoft.com/Remove-a-Management-group-336c849a/view/Discussions#content
I'm guessing this wheel has already been invented or maybe there's a better way. So I'm open to ideas or suggestions.
Any responses appreciated.

Wow! 4 days and no responses, not good Microsoft SCOM Community. So here's a status on this issue.
As stated I have Active Directory Integration configured which means:
I see the OperationsManager container in AD: dev_scom
I see the HealthService SCP and separate OU's for each of my management servers.
I have an ADI security group containing my management servers and scom action account.
I have an Agent security group which will contain servers the scom agent will be deployed via group policy.
I also have an AD LDAP query set to target the SCOM agent group.
(&(objectCategory=group)(name=DSCOM_ADI))
I finally get the script to install via the following steps:
Reference:
http://technet.microsoft.com/en-us/library/cc754995.aspx
http://technet.microsoft.com/en-us/library/cc770556.aspx
http://blog.coretech.dk/msk/install-a-scom-2012-agent-silent/
1. Launch Notepad ++ and enter the following:
msiexec /i
\\server.yourdomain.com\opsmgragent\%Processor_Architecture%\MOMAgent.msi USE_SETTINGS_FROM_AD=1 MANAGEMENT_GROUP=DEV_SCOM MANAGEMENT_SERVER_DNS=YourSCOMsrvr1.yourdomain.com ACTIONS_USE_COMPUTER_ACCOUNT=0 USE_MANUALLY_SPECIFIED_SETTINGS=0 ACTIONSUSER=svc_dscom
ACTIONSDOMAIN=yourdomain ACTIONSPASSWORD=YourPassword! AcceptEndUserLicenseAgreement=1 /qn /l*v c:\scom2012r2mmainstall.log
2. Save the script to a name of your choice. For me it's installdopsmgragent.cmd. Watch the extensions as you may end up saving it as installdopsmgragent.cmd.txt.
Note: Make note of this steps in the reference articles listed above:
"In the Add a Script dialog box, do the following:
In the Script Name box, type the path to the script, or click Browse to search for the script file in the Netlogon shared folder on the domain controller."
It's been a while since having to use a startup script so it took me a minute to figure this out. "getting too old 'fer this..."
3. Copy the script to the Netlogon folder which is located in the following directory on my Windows 2012 server: E:\SYSVOL\sysvol\yourdomain.com\scripts
4. Launch the group policy management console, create a new policy, edit it, and navigate to the following location:
Computer Configuration > Policies > Windows Settings > Scripts (Startup/Shutdown)
5. Double-click Startup to open the Startup Properties window.
6. Click Add and browse to the location of the script which you copied to the Netlogon share.
7. Click OK to close the Startup Properties window.
8. Close the Group Policy Management Editor.
9. Link the policy to an OU containing the servers.
10. Add the SCOM Agent group to the Security Filtering area of the group policy. I also remove Authenticated Users.
Note: make sure you have a few test servers in your Agent security group.
11. Drop to a command line and run gpupdate /force. You can also use gpupdate /force /sync but you will have to reboot the box you're running this from.
12. Log into one of the servers you have slated to deploy the agent to, drop to a command line, and run the same gpupdate command.
13. Follow this with a gpresult /r command to ensure that you see the policy applied in the Computer Settings area.
14. Reboot the server and you should see the startup script run.
15. Log into the server and launch the Control Panel.
16. If all went well you'll see the "Microsoft Monitoring Agent" icon.
17. Launch Event Viewer, navigate to the Operations Manager events node located under Applications and Services Logs and validate the logs.
17. If all didn't go well check the error log located, for me, on the C:\scom2012r2mmainstall.log
My issue: I don't see the management info in the Agent properties.
I installed this last night and waited until the next day still no changes. Event logs show the following:
Event ID: 2011 The Health Service did not find any policy in Active Directory
Event ID: 2003 No management groups were started. This may either be because no management groups are currently configured or a configured management group failed to start. The Health Service will wait for policy from Active Directory configuring
a management group to run.
I see the HealthService is Running in Task Manager on this server and of course I don't see anything listed in the Management Groups registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HealthService\Parameters\
I don't want to manually add the management group info. Checking as I may have missed something in one of the switches.
Any responses appreciated.

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

Rebuilding/Reseting the SCOM 2012 SP1 Data Warehouse. What is the easiest way and what steps i have to perform

Hello guys,
What are the best steps to rebuild the data warehouse ? In SCOM 2012 SP1 it is build during the initial installation and SCOM it is not giving you a tool to rebuild it. I have tried to create one DW database using the Data Warehouse Initial Setup.sql file
from the installation dvd and copied the permissions from my original DW. Although the sql script executed successfully i found some missing tables in the newly created database. So I'm not sure whether if i detach the old DW and rename the new test database
to OperatonsMangerDW it will work. Please advice on this issue. Please let me know if there is any easier approach of rebuilding/resetting the Data Warehouse database.

Hi,
I would like to suggest you refer to the below link to move the data warehouse database to a different system:
How to Move the Data Warehouse Database
http://technet.microsoft.com/en-us/library/hh268492.aspx
In addition, here is a similar thread, please refer to it:
https://social.technet.microsoft.com/Forums/systemcenter/en-US/c8e17cba-ad59-4474-9c90-787e4dec1307/create-operationsmanagerdw-manually?forum=operationsmanagergeneral
Regards,
Yan Li
Regards, Yan Li

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.

Difference between scom 2012 sp1 and SCOM 2012 R2

what is the difference between scom 2012 sp1 and SCOM 2012 R2 ?

What's New in System Center 2012 R2 Operations Manager:
https://technet.microsoft.com/en-us/library/dn249700.aspx

Create MP via Powershell in SCOM 2012 SP1

Is it possible to create MP via Powershell in SCOM 2012 SP1? If so, how?
(New-SCOMManagementPack is unrecognized cmdlet)

$name="NewMP"
$displayname="NewMP"
$mpStore = New-Object Microsoft.EnterpriseManagement.Configuration.IO.ManagementPackFileStore
$mp = New-Object Microsoft.EnterpriseManagement.Configuration.ManagementPack($name, $displayName, (New-Object Version(1, 0, 0,0)), $mpStore)
import-scommanagementpack $mp

Upgrading SCOM 2012 SP1 agent to SCOM 2012 R2

Hello All
We have created a new SCOM 2012 R2 environment and now planning to upgrade our agents which are in SCOM 2012 SP1 environment . We want to keep the agents dual homed for some time . I would like to know if there is any kind of automation/script that someone
has already made to upgrade SCOM agent from SP1 to R2 ,and at the same time have it dual homed (pointing to 2 MG)

You may try
1) upgrade the SCOM agent by
msiexec /i MOMAgent.msi /qn /l*v D:\logs\AgentUpgrade.log AcceptEndUserLicenseAgreement=1
2) Add additional management group y using following vb script
Option Explicit
Dim objMSConfig
Set objMSConfig = CreateObject("AgentConfigManager.MgmtSvcCfg")
‘Add a management group
Call objMSConfig.AddManagementGroup ("MyManagementGroupToAdd", "company.sm.net",5723)
For detail, pls. refer to
http://technet.microsoft.com/en-us/library/jj899848.aspx
http://msdn.microsoft.com/en-us/library/hh329017.aspx
Roger

Performance of Network Monitoring in SCOM 2012 SP1

Hi all!
I´ve problems with performance of the network monitoring feature in SCOM 2012 SP1.
According to the
guide the following should be adeqate:
•1000 network devices (approximately 12,500 monitored ports) managed by a resource pool that has three or more management servers
•500 network devices (approximately 6,250 monitored ports) managed by a resource pool that has two or more gateway servers
We have 800 network devices with a total of 24000 ports,
BUT only 1500 of them are monitored. This is basically what happens automatically after discovery, since only ports between monitored devices are monitored by default.
For this setup I first used only one management server dedicated to the Network Pool,
based on my assumption that if two servers could monitor 6250 ports, one server would be more than enough for 1500. I found this configuration working very poorly so I added another server. I now have two servers
dedicated for the Network Resource Pool. (They are NOT members of the “All management servers resource pool”)
Still, I get constant alerts regarding Health Services Private Bytes on these servers. They vary between 1-2Gbytes. Furthermore, if one of the servers goes offline, the network devices that was monitored by that server becomes grey for
several hours. Even if the server only is rebooted it takes forever to get everything online and green again.
I don´t really know what I should do now. I had a plan to replace our current network monitoring system (SNMPc) which easily handles this load on only one server. They are of course completely different beasts, but still. SCOM seems to
require a massive back-end to produce equivalent real life results.
Any suggestions or reflections from the field are highly appreciated!
Regards
Peter

Hi,
Try to overide the monitor Health Services Private Bytes by the following steps.
◾Go Authoring space – Management Pack Objects – Monitors
◾Go to change scope – select clear all – look for Health Service – tick it and press OK.
◾Expand Health Service – expand Entity Health – expand Performance – expand Health Service Performance
◾Select the Health Health Service Private Bytes Threshold.
◾Right click the mouse and choose to overide the monitor for a group
◾Select the group called Management Server Computer Group and press OK
◾Select the Agent Performance Monitor Type – Threshold and change the value 104857600 to ex. 2610612736.
◾Select to store the overide in a management pack you have created and press OK
Juke Chou
TechNet Community Support

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 SP1 - Created a new group and unable to "find" newly created group to create custom report

Similar Messages

Maybe you are looking for