SCOM 2012 SP1 availability report in MS Generic Report Libary shows inaccurate data

Hi,
in SCOM 2012 sp1, we have the generic availability report showing many of our web sites with no up time beyond a certain date. The web sites are ok, the web availability monitors are all healthy and the monitors test ok
None of these web availability tests are in Maintenance mode although what we are observing certainly makes us think that they are.
We also have a Web transaction login monitor for WEBSITE(A) that does not show this same outage for a login test.
However WEBSITE(A)'s availability monitor shows the same downtime as the other web availability tests.
Any thoughts on where to look for this problem? Im guessing its a problem placing the data in the Warehouse?
Thanks Lance

Hi,
Based on my understanding, the report shows there is downtime for the web site, but the web site did work well always.
It seems like that there is old data stored in data warehouse, would you please check the report for recent date, such as one day or two days.
Regards,
Yan Li
Regards, Yan Li

Similar Messages

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 Web Console High Availability Configuration

We are a large children's hospital, with many ancillary units that we are trying to get to help monitor their servers/devices/applications through the SCOM web console. Due to the number of connections we have two standalone web console servers. The
entire environment is running on Windows Server 2012 Standard Edition servers, and we are running SCOM 2012 SP1 UR3. When accessing the web console directly via the FQDN of the server, everything works great. We have an HLB virtual IP and DNS entry
(SCOM.domain.com), which works flawlessly when access the default IIS website. However, when accessing the web console URL (http://SCOM.domain.com/OperationManagerdown) Negotiate:Kerberos, NTLM, Negotiate. I believe the issue lies in the fact that
the Application Pools are running under the ApplicationPoolIdentity identity, and the HTTP SPN's are using the machine account. We have tried changing the identity of the application pools to a domain account (the SDK service account), and modified the
SPN's so the HTTP SPNs are assigned to the domain account. We also created SPNs for the HLB VIP DNS alias. But to no avail. While we realize that Microsoft does not support load balancing of the web console, there has to be a way to make
it work. We will have more than 50 connections, so using one web console server is not an option, and asking our users to use two different URLs is not very user friendly. If anyone has any suggestions or had any success, please let me know.
Any help is greatly appreciated!

Is switching to forms based authentication an option? The extra login might be considered a pain however, but forms plus SSL is the only successful LM configuration we have worked with. We use F5s.
Sign Up Now for the Infinity Connected™ Full Feature 30 Day Trial
Visit the Infinity Connected™ Support Center
Visit Our Website: http://www.infinityconnected.com
Visit Our Blog: http://blog.mobieus.com
Want to just talk shop? 1-800-691-6774 / [email protected]
Monitoring Information Center | Infinity On-Line | [email protected]

SCOM 2012 SP1 Upgrade - RMS fine but can't upgrade reporting or web console

Hi,
We've just upgraded our RMS to SCOM 2012 SP1 and everything went smoothly as per the documentation. However when I next try to upgrade the Reporting or Web Consoles (located on separate servers) to SP1 I am presented with a message saying:
"The management server to which this component reports has not been upgraded".
At that point we cannot proceed past the prerequisite checker.
I am totally confident that the SP1 upgrade went through on the RMS and all file versions are at SP1.
Can anyone help please?
Thanks,
Tim

Hi Retee,
I was not able to find a fix for this but I did find a workaround.
1. I copied the installation files from the SCOM 2012 SP1 DVD/ISO to a folder, SCOM_2012_INSTALL on the reporting server.
2. Browsed to the following folder ..\SCOM_2012_INSTALL\setup\AMD64\ and commented out the following section of the IntermilestoneUpgradePrereqs.xml file:

3. Ran ..\SCOM_2012_INSTALL\setup.exe and the upgrade was successful.
Our SCOM infrastructure has now been at 2012 R2 for a couple of months and I have not seen any issues caused by commenting out this section. But as always, use at your own risk.
Hope this helps.
Thanks,
Iain

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.

SCOM 2012 SP1 Update Rollups

Hi All,
I am planning to deploy patches on SCOM server. We are on SCOM 2012 SP1 as of now. As you know Microsoft has been released UR1, UR2, UR3, UR4, UR5 and UR6 for SCOM 2012 SP1.
Do I need to deploy each UR one by one on SCOM server or UR6 will have all fixes?
If I go for directly UR6 then does this patch contains all fixes which are available till UR5?

http://blogs.technet.com/b/server-cloud/archive/2014/04/23/system-center-2012-sp1-ur6-and-system-center-2012-r2-ur2-now-available.aspx
Customers can now download the latest update rollups for both System Center 2012 SP1 and System
Center 2012 R2. Update rollups provide a cumulative package of fixes for each System Center component and are available from Microsoft Update. Alternatively, they can be manually downloaded from the Microsoft Update Catalog.

SCOM 2012 SP1 UR4 management servers grey state

Hi,
My SCOM environment is made up of the below :-
SCOM 2012 SP1 UR4.
3 SCOM Management Servers all on Windows 2008 R2 SP1.
Shared SQL 2008 cluster with 2 Windows nodes also on same OS.
Just recently all our SCOM management servers have been flipping in and out from grey to green state. Gateways/agents all look ok as showing green. Alerting from agents appears normal as can see lots of them in console.
Have flushed the health state cache folder on all 3 SCOM MS's and still the same issue.
Appreciate any help on this one.

Event id: 7011 - Was your server recently patched (Installed by any automatic updates) ?
IS SCCM Configured in your MS? If Yes disable and check?
Is Windows update service running ? Stop if for one or two days and check if this issue still appears
Reference threads:
http://social.technet.microsoft.com/Forums/en-US/b86e5a3d-0c2e-4d5e-9d3d-905da91fc982/scom-2012-event-id-7011-service-control-manager-error-when-fep-definition-updates-apply?forum=configmanagersecurity
http://stefanroth.net/2012/09/26/scom-2012-event-id-7011-service-control-manager-error/
Solution also available in: http://technet.microsoft.com/en-us/library/cc756319(v=ws.10).aspx
===========================================
For Event id 20026 -
1. Does your Operationsmanager database have enough space ? Check that first.
What is you DB size ?
How much is the free space left ?
2. Was there any resent change in the SCOM Action accoutn password ? Or has the password expired. Try re entering the SCOM Action password by re directing your self to Administration tab --> Run as Config -- > Accounts --> SCOM Action account.
The description would be - This is the user account under which all rules run by default on the agent.
Right click and go to properties and re enter the account name and password there and check.
Refer the below screen shot
Check this article as well:
http://social.technet.microsoft.com/Forums/systemcenter/en-US/102d443c-db0e-4bf2-b0d6-31d7f9328537/all-agents-greyed-out-multiple-event-errors-with-ids-20026-20028?forum=operationsmanagergeneral
============================================
Event id : 11904 - As per my knowledge appears due to incorrect Alrting string display name selected in any Rule or monitor.
Also the description what you pasted in Event id : 11904 says Microsoft.SystemCenter.HealthService.ActionAccountConfigured.Error as highlighted below.
Suggest to re enter the action account password and tell the results.
Also is the Healthservice on the MS running using System account or Domain account ?
=================================================================
Description : The Microsoft Operations Manager Expression filter Module failed to query the delivered item, item was dropped.
Property Expression: Reachability/State
Error : 0XC00EE22
One or more workflows were affected by this. Workflow
name: Microsoft.SystemCenter.HealthService.ActionAccountConfigured.Error
Gautam.75801

SCOM 2012 SP1 : Update rollup installation failed

Hello,
I'm trying to update SCOM 2012 SP1 with UR7 but the installation rollback automatically.
Same error with others UR.
LOG MSP :
MSI (c) (08:1C) [14:49:24:772]: Product: System Center Operations Manager 2012 Server - Update 'System Center 2012 - Operations Manager SP1 UR7 Update Patch' could not be installed. Error code 1603. Additional information is available in the log file c:\logs3.log.
MSI (c) (08:1C) [14:49:24:772]: Windows Installer installed an update. Product Name: System Center Operations Manager 2012 Server. Product Version: 7.0.9538.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Update Name: System Center 2012 - Operations
Manager SP1 UR7 Update Patch. Installation success or error status: 1603.
MSI (c) (08:1C) [14:49:24:772]: Note: 1: 1729
MSI (c) (08:1C) [14:49:24:772]: Product: System Center Operations Manager 2012 Server -- Configuration failed.
MSI (c) (08:1C) [14:49:24:772]: Windows Installer reconfigured the product. Product Name: System Center Operations Manager 2012 Server. Product Version: 7.0.9538.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error
status: 1603.
MSI (c) (08:1C) [14:49:24:772]: Attempting to delete file C:\Users\ADMINJ~1\AppData\Local\Temp\10c36d.msp
MSI (c) (08:1C) [14:49:24:772]: Unable to delete the file. LastError = 32
MSI (c) (08:1C) [14:49:24:772]: Grabbed execution mutex.
MSI (c) (08:1C) [14:49:24:772]: Cleaning up uninstalled install packages, if any exist
MSI (c) (08:1C) [14:49:24:772]: Attempting to delete file C:\Users\ADMINJ~1\AppData\Local\Temp\10c36d.msp
MSI (c) (08:1C) [14:49:24:772]: MainEngineThread is returning 1603
=== Verbose logging stopped: 15/10/2014 14:49:24 ===
MOMPerfCtrsInstall.log
The uninstall is beginning.
See the contents of the log file for the D:\Program Files\System Center 2012\Operations Manager\Server\APMDOTNETAgent\Microsoft.EnterpriseManagement.OperationsManager.Apm.PerformanceCounters.dll assembly's progress.
The file is located at D:\Program Files\System Center 2012\Operations Manager\Server\APMDOTNETAgent\Microsoft.EnterpriseManagement.OperationsManager.Apm.PerformanceCounters.InstallLog.
The uninstall has completed.
The uninstall is beginning.
See the contents of the log file for the D:\Program Files\System Center 2012\Operations Manager\Server\Microsoft.EnterpriseManagement.HealthService.Modules.DataWarehouse.dll assembly's progress.
The file is located at D:\Program Files\System Center 2012\Operations Manager\Server\Microsoft.EnterpriseManagement.HealthService.Modules.DataWarehouse.InstallLog.
See the contents of the log file for the D:\Program Files\System Center 2012\Operations Manager\Server\Microsoft.Mom.DatabaseWriteModules.dll assembly's progress.
The file is located at D:\Program Files\System Center 2012\Operations Manager\Server\Microsoft.Mom.DatabaseWriteModules.InstallLog.
The uninstall has completed.
Running a transacted installation.
Beginning the Install phase of the installation.
See the contents of the log file for the D:\Program Files\System Center 2012\Operations Manager\Server\Microsoft.Mom.DatabaseWriteModules.dll assembly's progress.
The file is located at D:\Program Files\System Center 2012\Operations Manager\Server\Microsoft.Mom.DatabaseWriteModules.InstallLog.
An exception occurred during the Install phase.
System.FormatException: Input string was not in a correct format.
The Rollback phase of the installation is beginning.
See the contents of the log file for the D:\Program Files\System Center 2012\Operations Manager\Server\Microsoft.Mom.DatabaseWriteModules.dll assembly's progress.
The file is located at D:\Program Files\System Center 2012\Operations Manager\Server\Microsoft.Mom.DatabaseWriteModules.InstallLog.
The Rollback phase completed successfully.
The transacted install has completed.
Running a transacted installation.
Beginning the Install phase of the installation.
See the contents of the log file for the D:\Program Files\System Center 2012\Operations Manager\Server\APMDOTNETAgent\Microsoft.EnterpriseManagement.OperationsManager.Apm.PerformanceCounters.dll assembly's progress.
The file is located at D:\Program Files\System Center 2012\Operations Manager\Server\APMDOTNETAgent\Microsoft.EnterpriseManagement.OperationsManager.Apm.PerformanceCounters.InstallLog.
An exception occurred during the Install phase.
System.FormatException: Input string was not in a correct format.
The Rollback phase of the installation is beginning.
See the contents of the log file for the D:\Program Files\System Center 2012\Operations Manager\Server\APMDOTNETAgent\Microsoft.EnterpriseManagement.OperationsManager.Apm.PerformanceCounters.dll assembly's progress.
The file is located at D:\Program Files\System Center 2012\Operations Manager\Server\APMDOTNETAgent\Microsoft.EnterpriseManagement.OperationsManager.Apm.PerformanceCounters.InstallLog.
The Rollback phase completed successfully.
The transacted install has completed.
Maybe someone have a idea about that ?
Thank you !
Jérémy

Hi,
Have your tried to review the c:\logs3.log for any potential error or indication of cause?
For more information, please review the link below:
Update Rollup 7 for System Center 2012 Operations Manager Service Pack 1
http://support.microsoft.com/kb/2965420
Update rollup packages for System Center 2012 Operations Manager
http://support.microsoft.com/kb/2906925
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SCOM 2012 Sp1 Ur 9

Hello Team,
I am working on scom 2012 sp1 Ur5 and found there is an update available UR9.
can I upgrade SCOm 2012 sp1 Ur5 to UR9 directly or i need to upgrade to UR8 and then UR 9.
Regards

Hi,
We recommend that you install this update rollup package by following these steps:
Install the update rollup package on the following server infrastructure:
Management servers
Gateway servers
Web Console Server role computers
Operations Console role computers
Apply SQL scripts. (See the installation information for the update.)
Manually import the management packs.
Under "Pending Management", Select the a "Agent" and click "Approve" to update agent.
More details:
http://support.microsoft.com/kb/3023167
http://www.ms-opsmgr.eu/?p=1313
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]

STEPS to Make SCOM 2012 SP1 High Avaliability

Can anybody tell me the steps to make scom 2012 sp1 high avaliabilty with sql server 2008 r2 because i have akready deplyed scom 2012 single server with sql server 2008 r2 but now i have to make the replica of this on dr side so should i need one more
sql server 2008 r2 and one MS server on DR site

Hi,
Additional to dktoa’s reply, I would like to explian Resource pools are a new concept in Operations Manager 2012. When two or more management servers are added to a management group, the management servers automatically become part of a resource pool and
work is spread across all the members included in it. If one of the resource pool management servers fails, other management servers in the resource pool take over the workload, thus delivering an out-of-box highly available design.
Topology changes in System Center 2012 Operations Manager (Overview)http://blogs.technet.com/b/momteam/archive/2011/08/22/topology-changes-in-system-center-2012-operations-manager-overview.aspx
Niki Han
TechNet Community Support

Issue upgrading SCOM 2012 SP1 to SCOM 2012 R2

I have been having a really fun time trying to get my test SCOM 2012 SP1 environment upgraded to SCOM 2012 R2. I initially had an issue with the DB server not accepting connections to SMB which was causing the upgrade to fail stating database permission
issues (that was a fun one to troubleshoot). Once I figured out that problem I am now getting an error in the OpsMgrSetupWizard log that is stating the following:
[14:46:47]: Always:
:LaunchMsiSetup: Complete: 2 seconds
[14:46:47]: Error:
:LaunchMsiSetup: Failed, return code: 1612
[14:46:47]: Error:
:Error:Failed to uninstall previous MOM product on this machine, cannot proceed with upgrade
[14:46:47]: Error:
:Error:Failed to uninstall Operations Manager Agent on this machine. This is fatal error, we cannot proceed with upgrade
[14:46:50]: Error:
:LaunchMSI: MSI E:\Setup\AMD64\Server\OMServer.msi returned error 1603
[14:46:50]: Error:
:ProcessInstalls: Install Item Management Server failed to install. We did not launch the post process delegate.
In the application log I am getting the following error:
"Product: System Center Operations Manager 2012 Server -- The Operations Manager management server cannot be installed on a computer on which the Operations Manager agent, Operations Manager gateway, System Center Essentials, or System Center Service
Manager is already installed. These must be uninstalled to proceed."
I have verified that I don't have any of these installed and have even gone so far as to remove my Config man agent and System Center Endpoint Protection just in case it was getting confused with System Center Essentials.
I am at a loss as to what to try next. Any suggestions?

Hi,
Check if you have the following registry. If so, please back it up first, then delete for a test.
HKEY_CLASSES_ROOT\Installer\UpgradeCodes\C96403E8AD6025B4F9E1FE9C574E34AE
Also, please uninstall MOM product and Operations Manager Agent manually to check the result.
Upgrading System Center 2012 SP1 - Operations Manager to System Center 2012 R2
http://technet.microsoft.com/en-us/library/dn249707.aspx
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.

Manage DPM servers, running DPM jobs, etc from SCOM 2012 SP1

Hi,
Little background about our systems.
We have a dedicated SCOM 2012.
We have 22 DPM servers, DPM 2010 and DPM 2012 (we are upgrading to 2012 SP1, we have customers that still using Windows 2003 servers) to be managed by SCOM
We have a few DPM servers that are not located on the same domain as the SCOM server (untrusted domain).
Some problem we have
1. When we try to manage the DPM servers from the SCOM server.
From SCOM 2012 server I can “Manage DPM server” that are located in our domain but I cannot manage DPM servers located on untrusted domains (customer’s domains). I receive the below error message
"Unable to connect to <untrusted domain DPM SERVER> ID: 948
Verify that the DPM service is running on this computer"
I guess it’s because the account that I’m using to run SCOM server located in our domain and does not have the permission to open the DPM console on the untrusted domain. So I wonder if it is possible to use “RUN AS profiles/accounts”
to solve this issue, and how?
2. I have installed SCOM 2012 Operations Manager Console on my computer and then installed DPM Central Console.
When I select one dpm server (from my computer), that is on our domain, and then click “Manage DPM server” I got this error message
"Unable to connect to <our domain DPM SERVER> ID: 33333
1. Verify that the DPM service is running on this computer (YES)
2. Verify that the current user has been added to at least one of the roles in Operations Manager. (YES)
3. Open Operations Manage console and then try launching the DPM Console (THAT IS WHAT I AM TRYING TO DO)
4. If you have re-imported the management pack recently, the role configuration may be corrupt. Open the DPM-specific roles and check if the roles have task assigned to them. If not, delete the roles and recreate the...."
When I click on “Get more information” I get this error message.
"You don´t have access permission to connect to the System Center Data Access service on <SCOM SERVER>. Please check if it is a permission issue".....
Do you know why I cannot connect to any DPM server on our own domain?
Why do I get access permission error on my computer but not on the SCOM server (using the same account)?
What should we do to be able to connect to DPM servers that are on untrusted domain?
3. Is it possible to see Last Recovery Point date/time in SCOM alerts?
For me it is the first thing I look at. If it has failed 10 min ago it is not critical.
But if it is a date and time more than 1 day old, then it is critical.
I hope someone can help us with this
Br
SvBoho

Hi,
To manager DPM, I think we may need to add the account to local admin group of the DPM server.
In addition, to connect to DPM the user needs permissions to DPM/SQL Server DPMDB.
For your DCs, have your enabled agent proxy option? If not, please enable that option for all DCs.
To monitor DPM with SCOM, please also go through the below links:
http://kevingreeneitblog.blogspot.com/2011/10/managing-and-monitoring-system-center.html
http://damatisystemcenter.com/2013/10/14/monitor-data-protection-manager-2012-using-scom-2012-sp1/
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Regards,
Yan Li
Regards, Yan Li

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.

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

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 availability report in MS Generic Report Libary shows inaccurate data

Similar Messages

Maybe you are looking for