Automatic windows agent fail over in SCOM 2012 / 2012 R2

Hi All,
I have a question with respect to SCOM 2012 / 2012 R2 windows agent fail over.
For example i have only 400 windows agents and i have 2 MS in my environment. So 200 windows agents are managed by MS1 and the rest 200 are managed by the MS2.
What i want to know is if either of the MS (MS1 or MS2) Shutdown / restart or any thing happens to them, Do the agents automatically fail over to the other MS ? As i have not configured ant thing for this as i don't know.
So is there any configuration to be done for the above to happen after the deployment of both the management servers is done before discovering the agents or does it automatically understand take the rest 200 agents thinking that the other MS is down ?
Gautam.75801
This happens automagically for Windows agents within a domain that are assigned to a Management Server. For other scenarios, such as Gateways, the Gateways should be configured for failover between Management Servers, and the agents attached to those
Gateways should be configured to failover between the Gateways. Cross platform agents report to a resource pool, so that happens automagically as well.
To confirm your scenario, simply run the Get-SCOMAgent cmdlet.
To test you can do the following, assuming first agent in the array isn't a Management Server/Gateway :)
$SCOMAgents = get-scomagent
$SCOMAgents[0].PrimaryManagementServerName
$SCOMAgents[0].GetFailoverManagementServers()
Supporting article:
http://blogs.technet.com/b/jimmyharper/archive/2010/07/23/powershell-commands-to-configure-gateway-server-agent-failover.aspx

Similar Messages

Is there a matrix showing the difference with features of agent vs. agentless in SCOM 2012?

Is there a matrix showing the difference with features of agent vs. agentless in SCOM 2012?

Agent monitoring requires an agent installation on the target machine
Agentless monitoring
An agentless-managed computer is a Windows-based computer that is discovered by using the Operations console. You assign an management server or agent-managed computer to provide remote (proxy) agent functionality for the computers.
Agentless-managed computers are managed as if there is an agent installed on them. Not all management packs work in agentless mode.
Agentless versus Agent-based server monitoring
http://thwack.solarwinds.com/community/solarwinds-community/geek-speak_tht/blog/2013/02/11/agentless-versus-agent-based-server-monitoring
Roger

Which role do I need DFS or File server on fail over cluster server 2012 R2?

what I want to achieve is that I want to share all my user data files in a central location and to be highly available all the time whether it's a general share or folder redirection data. BUT I'm a bit confused; I have fail over cluster set-up
on server 2012, now I would like to add DFS as a role but than we have another role called File server and virtually it does the same thing as DFS? Means it creates a namespace share that can be access even one of the nodes goes down. Now I am thinking is
that DFS does the replication between two physical location but fail over cluster works slightly differently and with file server it pretty much does the same thing except for replicating data from one drive to another. Now what do you suggest I do or
did I get the concept wrong like a noob?

DFS and Failover Clustering for file shares provides a similar end result for file access, but they are significantly different implementations.
Clustering provides high availability to files by presenting shared access to set a files served from a cluster. With 2012 R2 Microsoft added the ability to create a Scale-out File Server that even allows all nodes of the cluster to server access to
the files for a higher level of performance and other great things. Bottom line with Failover Clusters for files is that there is a single copy of the file presented from the cluster.
DFS on the other hand provides high availability to files by presenting multiple copies of the file by making a copy in two or more locations and presenting a naming space that allows access to the file through any of the network paths. DFS works very
well for files that are primarily read-only. When you get into a situation where there is a lot of updating of the shared files, DFS is not a very good solution. There are ways to implement DFS for read/write files, but it generally requires a
good knowledge of how the files are used and how you want to manage them.
The key to answering your question comes in your first sentence "I want to share all my user data files in a central location and to be highly available all the time". My initial reaction to this is that central location means Failover Cluster
- there is only a single copy of the file. However, "all the time" can be compromised by network failures to the central site. Remote sites would not have access if they can't access the central site. DFS provides the ability to
have copies remotely, but then if you allow updating at multiple sites, you have to manage the merging of the changes, among other things.
. : | : . : | : . tim

Automate build TCP port checks in SCOM 2012 using template?

Hi, I would like to leverage Orchestrator to build TCP port checks from customer requests.
ie, Customer requests Port X on server Y be checked. Orchestrator to kick off script to generate the require entries in SCOM2012 allow the TCP port check to be dynamically built.
Cannot see anything that would assist with this.
Can anyone help?
Thanks, Thomas

For Create custom TCP Port Monitoring, you can refer to below links
http://www.systemcentercentral.com/custom-tcp-port-monitoring-management-pack-for-scom-2012/
http://technet.microsoft.com/en-us/library/hh457544.aspx
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer".

SCOM 2012 R2 # Windows Server agents remain in pending management

Hi,
First I installed one SCOM 2012 R2 Ops Manager. On same SCOM ops manager I added 3 windows server agents to monitor as below..
one 2008 R2 AD server
one Lync 2013 FE server
one Exchange server 2013
Now due to some technical issues later I had to completely remove/uninstall SCOM 2012 R2 setup. But I forgot to uninstall/remove 3 agents first before uninstalling SCOM 2012 R2 ops manager :( However I did manual uninstall of Microsoft monitoring agent setup
from all 3 monitored agent servers.
Now I setup new SCOM 2012 R2 ops manager once again. FQDN of new SCOM has been changed now, though server is in same domain as old one. Problem I am facing here is " I cannot able to add those 3 agents back into new SCOM ops manager. When I install
agent back onto those 3 servers (by agent discovery or manual setup) , servers remains in pending management. I used power shell command to approve all 3 but even after approval servers are not being monitored. Health status always showing not monitored. A
blank green circle.
I think I didn't properly removed old agent setup, & somehow those 3 agents still bound to old SCOM ops manager.
Could you please help me how I can remove remaining components of old agent setup from windows agent servers and monitor them with new SCOM?
BR,
Ajit

Ensure that the following registry keys are deleted:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HealthService
Reboot the agent machine (if possible)
Delete the agent from Agent Managed in the OpsMgr console.
Then try to discovery and push agent from console if failed. Try to install it manual and then from pending management click approved.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

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

New Build of SCOM 2012

build condition:
SCOM SQL DB with clustered(nodesql1 & nodesql2).
2 management servers(example: node1 & node2).
if this build is possible where 1 of the management is down and does not impact the monitoring. only node1 management server connect to the DB?
SCOM 2012 does not work like the SCOM2007R2 RMS right?

In your present configuration, node1 is down.
1) all SCOM 2012 agent reports to node1 will automatic failover to node2
2) all SCOM 2012 agent reports to node2 remain unchanged
3) all performance data or alert which is received by node2 will be written into SCOM DB
Roger

Mssql collation conflict while update scom 2012 sp1 to r2

hi all
i have scom 2012 sp1 (windows server2008 r2), mssql 2012 sp1 (windows server2008 r2)
while updating scom 2012 sp1 to r2 error is appears:
"DB operations failed with SQL error 468: Cannot resolve the collation conflict between "Cyrillic_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation."
how can i change collation of db "OperationsManager" from "Cyrillic_General_CI_AS" to "SQL_Latin1_General_CP1_CI_AS"?
thanks in advance

For Failed to store data in the Data Warehouse. Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation, you can refer below link
http://thoughtsonopsmgr.blogspot.com/2010/04/failed-to-store-data-in-data-warehouse.html
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

Is there a VSAE 2012 version that includes "PowershellGridWidget" from the latest SCOM 2012 update

Hi everyone,
Is there a version of VSAE 2012 which includes a man pack with "Visualization!Microsoft.SystemCenter.Visualization.Component.Library.PowershellGridWidget" included so I can take advantage of the $globalselecteditems in my powershell scripts
to easily drive my other widgets.
When I try manually by doing "add references from management pack" Microsoft.SystemCenter.Visualization.Component.Library.mpb and build I get Visual Studio 2012 crashes first off - subsequent builds produce -
Cannot find ManagementPackElement [Type=ManagementPackElement, ID=Microsoft.SystemCenter.Visualization.Component.Library.PowershellGridWidget] in management pack ManagementPack:[Name=Microsoft.SystemCenter.Visualization.Library, KeyToken=31bf3856ad364e35,
Version=7.1.10226.0]. (Path = Pauls.MP)
ManagementPack.mpx 15
10 Pauls.MP
Error
2
Detected malicious verification code when verifying element of type Microsoft.EnterpriseManagement.Configuration.ManagementPackComponentImplementation with inner exception: : The requested ManagementPackElement
[Type=Microsoft.EnterpriseManagement.Configuration.ManagementPackElementReference`1[[Microsoft.EnterpriseManagement.Configuration.ManagementPackElement, Microsoft.EnterpriseManagement.Core, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]],
ID=Microsoft.SystemCenter.Visualization.Component.Library.PowershellGridWidget] in management pack [Pauls.MP, 28788124c9f39fcd, 1.0.0.442] is not accessible outside of this management pack.
Anyone had this problem or have a solution - my Visual Studio en/v is not on my SCOM box.
Cheers,
Paul

Thanks very much Yan Li,
I copied over the SCOM 2012 R2 U2 man packs from our SCOM server and removed the references from VSAE before re-adding them for the new versions esp. the Visualization man packs - it worked without a problem.
One further thing though and I believe this has been mentioned elsewhere, when I turn on "PackagetoBundle" to True for the mpbs I'm referencing, I always get this error-
Error
322
The "PackageToBundle" task failed unexpectedly.
: The provided file name (C:\Users\ppower\MPs\Pauls.MP\ManagementPacks\Microsoft.SystemCenter.Visualization.Library.mpb) does not end with any known management pack file extension.
Is this a bug with VSAE or something I'm doing - if not, is there a workaround?
Cheers,
Paul

Issues with Monitoring Azure services with SCOM 2012 R2

Hi,
I'm trying to setup monitoring of our Azure subscriptions in a new installation of Operations Manager 2012 R2 which is running in-house as it is also monitoring our internal services. I've used the guide below:
http://blogs.msdn.com/b/walterm/archive/2013/04/13/first-impressions-on-system-center-management-pack-for-windows-azure-fabric-preview-for-scom-2012-sp1.aspx
This has all worked OK and I've been able to add the subscription into OP Manager and it's found the cloud service, storage and VM's. However when I try to add the monitoring and I go to create this When I select the Add option in the Add Monitoring
Wizard and click the Search button to list the components (Cloud Service, Storage and VM's) nothing is found despite me having already selected the subscription.
Has anyone else experienced this or can offer any advice?
Many Thanks
Colin

Hi,
Which version of RDP client you are using for your client?
Does more user login at same period of time?
As you have commented that after sticking the user can’t able to login in RDCB server, here I can suggest you to check the setting of connection broker. Also you can check that you have place the proper location path of UPD while configuring in collection configuration
wizard. You can take a look at below article foe virtual desktop configuration.
Deploying Virtual Desktops with Windows Server 2012
Are you trying to use same UPD for different collection then also it might happens to occur your issue. The fact of UPD is User profile disks are for a single collection only. A user connecting to two different collections will have two separate profiles. If
you want to synchronize settings, refer to Microsoft User Experience Virtualization. Go through this article for more understanding related to UPD.
Working with User Profile Disks on Session-Based Desktop Deployments
Hope it helps!
Thanks.

SCOM 2012 R2 agent upgrade fails crippling agents

Running into a large amount of SCOM agents that are failing the upgrade from 2012 SP1 to R2 and would appreciate any feedback from my SCOM community colleagues. Warning this issue is not for the faint of heart.
Plan:
I am in the process of upgrading 1900 manually installed SCOM 2012 SP1 agents to R2. I am using SCCM to deliver the upgrade using the standard sanctioned upgrade parameters.
Momagent.msi /qn /l*v %SystemDrive%\SCOM2012AgentUpgrade.log AcceptEndUserLicenseAgreement=1
Problem:
I have run into a problem where on a larger group of systems, 165 servers, where the upgrade fails and leaves the agent in a crippled state. At this point the agent cannot be removed cleanly via add remove, nor can a straight install of the agent
be done. What is required is a manual removal of registry keys and then a clean install of the agent can be performed to remediate. This is no problem and I am able to do this. (Note: all other methods of agent removal did not work ie:
Cleanmom.exe utility or add remove)
Task:
Seeing that we need to do agent upgrades in the future it would be great to know why this happened so we can plan for this in the future.
Notes:
Seems like a random sample of servers (2003/2008) with different applications running on them so that doesn't help in narrowing things down.
Looking at the MSI log, I see a common issue among systems that had this problem.
******* Product: {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
           ******* Action:
           ******* CommandLine: **********
MSI (s) (7C:7C) [08:08:43:668]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (7C:7C) [08:08:43:668]: User policy value 'DisableMedia' is 0
MSI (s) (7C:7C) [08:08:43:668]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Looking for sourcelist for product {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Adding {387306D9-78CE-4E0E-B952-28A50CC8B3EE}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Now checking product {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Media is enabled for product.
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Trying source C:\WINDOWS\SysWOW64\CCM\Cache\LFG00446.1.System\i386\.
MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 2203 2: C:\WINDOWS\SysWOW64\CCM\Cache\LFG00446.1.System\i386\MOMAgent.msi 3: -2147287037
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Processing net source list.
MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Processing media source list.
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 2203 2: 3: -2147287037
MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Processing URL source list.
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1402 2: UNKNOWN\URL 3: 2
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2: 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Failed to resolve source
MSI (s) (7C:8C) [08:08:44:744]: Note: 1: 1714 2: Microsoft Monitoring Agent 3: 1612
CustomAction returned actual error code 1612 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (7C:8C) [08:08:44:744]: Product: Microsoft Monitoring Agent -- Error 1714.The older version of Microsoft Monitoring Agent cannot be removed. Contact your technical support group. System Error 1612.
Error 1714.The older version of Microsoft Monitoring Agent cannot be removed. Contact your technical support group. System Error 1612.
Action ended 8:08:44: RemoveExistingProducts. Return value 3.
Action ended 8:08:44: INSTALL. Return value 3.
Ok so the obvious is that the installer is looking for original source installation files and not able to find them. What is surprising to me however is that the product references a 32 bit scom agent guid
387306D9-78CE-4E0E-B952-28A50CC8B3EE, however this is a 64 bit machine. Our build process dictates that a 64 bit machine only receive a 64 bit SCOM agent.
Doing a search on this product guid I realized I skipped some other references at the top of the MSI log that might offer some more explanation...
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding OM_OM12_SP1_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330}'.
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Modifying OM_OM12_SP1_AGENT_FOUND property. Its current value is '{8B21425D-02F3-4B80-88CE-8F79B320D330}'. Its new value: '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
MSI (s) (7C:8C) [08:08:11:896]: Skipping action: _StopCoreServices.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)
MSI (s) (7C:8C) [08:08:11:896]: Skipping action: _KillOMProcesses.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)
MSI (s) (7C:8C) [08:08:11:896]: Doing action: _Set_OM_AGENT_FOUND
Action ended 8:08:11: FindRelatedProducts. Return value 1.
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding OM_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
Action start 8:08:11: _Set_OM_AGENT_FOUND.
MSI (s) (7C:8C) [08:08:11:896]: Doing action: _Set_MOMV3_AGENT_FOUND
Action ended 8:08:11: _Set_OM_AGENT_FOUND. Return value 1.
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding MOMV3_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
Action start 8:08:11: _Set_MOMV3_AGENT_FOUND.
Well that is interesting, seems to me that in the first line the MSI installer reads the OM_OM12_SP1_AGENT_FOUND property and identifies this with a 64 bit agent guid (8B21425D-02F3-4B80-88CE-8F79B320D330), but then appends
the 32 bit guid at the end (387306D9-78CE-4E0E-B952-28A50CC8B3EE). This is the point of my confusion and my suspicion as the cause of the problem I am having.
Concluding thoughts:
Why does the installer seems to first recognizes a 64 bit agent, but then later changes it's property to include a 32 bit agent guid.  Could a 32 bit agent have got on this 64 bit server based on the details of this log? Would this
cause my agents to fail the upgrade? I think so, but looking to bounce this over to another fellow SCOM colleague who may have wrestled with this before.
Thanks in advance if you took the time to read this and think about it. Extra points if you have any extra thoughts!
Keith

Hi,
Have you used Requirement to limit the platform when you deploy application with SCCM.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SCOM 2012 R2 Agent Issue: Error 25211.Failed to install performance counters.. Error Code: -2147024809

Hi All,
I'm trying to deploy SCOM 2012 R2 agent onto a domain controller and I get the following error "Product: Microsoft Monitoring Agent -- Error 25211.Failed to install performance counters.. Error Code: -2147024809 (The parameter is incorrect.)."
I've installed the agent successfully onto 4 other domain controllers with out any issues.</p><p>The domain controllers are all VM's running on VMWare and are Windows Server 2012 R2.
I've rebuilt the Perfmon Counters based on this article: https://support.microsoft.com/en-us/kb/2554336?a=wsignin1.0
I've also enabled verbose logging on the msi installation:
InstallHSPerfCounters: Custom Action Data. C:\Program Files\Microsoft Monitoring Agent\Agent\
InstallHSPerfCounters: Installing agent perf counters.
InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft Monitoring Agent\Agent\HealthServiceCounters.ini"
InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. HealthService
InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
InstallPerfCountersLib: Retry Count : .
InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft Monitoring Agent\Agent\MOMConnectorCounters.ini"
InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. MOMConnector
InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
Any help on this would be great.

Hi Stefan,
I've successfully installed the agent. The server needed a reboot after fixing the corrupt perfmon counters.
I know have a issue with the agent on the domain controller. It kkeeps on greying out and have used hslockdown to allow the local system access by using the following command.
HSLockdown.exe "ManagementGroupName" /A "NT AUTHORITY\Authenticated Users"
Further digging into the issue I see in the SCOM Management Server the following error "The entity servername is not heartbeating"
Written a SQL query to gather more information. SQL query I used is:
SELECT
ME.FullName,
HSO.StartDateTime AS OutageStartDateTime,
DATEDIFF (DD, hso.StartDateTime, GETDATE()) AS OutageDays,
HSO.ReasonCode,
DS.Name AS ReasonString
FROM vManagedEntity AS ME
INNER JOIN vHealthServiceOutage AS HSO ON HSO.ManagedEntityRowId = ME.ManagedEntityRowId
INNER JOIN vStringResource AS SR ON HSO.ReasonCode =
REPLACE(LEFT(SR.StringResourceSystemName, LEN(SR.StringResourceSystemName)
– CHARINDEX(‘.’, REVERSE(SR.StringResourceSystemName))), ‘System.Availability.StateData.Reasons.’, ”)
INNER JOIN vDisplayString AS DS ON DS.ElementGuid = SR.StringResourceGuid
WHERE (SR.StringResourceSystemName LIKE ‘System.Availability.StateData.Reasons.[0-9]%’)
AND DS.LanguageCode = ‘ENU’
AND ME.FullName like ‘%SERVER NAME%’ –Change name here or leave %% for ALL SERVERS
ORDER BY OutageStartDateTime
This gives me the following reason behind the failure : "The heartbeat from System Center Management Service is missing."
Have I missed anything? The agent is running fine, however SCOM is reporting that the heartbeat is missing.
Any help on this would be great.

SCOM 2012 ACS agent Failed connecting to collector

Hi,
We are using SCOM 2012 on Windows 2012, when installing the SCOM agent with Audit Collection Services the ACS forwarder will report in as healthy until reboot, after reboot the forwarder state changes to failed to connect to collector. (XXX's are redacted
system information).
Forwarder unsuccessfully tried to connect to the following collector(s): XXXXXXXX:51909, status: 0x80090322 (TCP connect), source: registry addresses tried: XXX.XXX.XXX.XXX:51909 If the list of collectors is blank, then AdtAgent was unable to locate a collector.
Common reasons for this message are: The machine(s) listed is not online AdtServer is not running on the machine(s) listed AdtServer on the machine(s) listed is not listening on the specified port TCP connectivity to the AdtServer machine is blocked by firewall,
IPSec, or other filtering mechanism AdtServer on the machine(s) listed actively refused the connection (due to policy or current activity load) For detailed failure information, enable trace logging using the TraceFlags registry key and examine the AdtAgent.log
in the \temp subdirectory of the Windows directory.
Enabling trace logging repeats the same error, unable to connect to server. We have verified, the IP is correct, the FQDN is correct and has a forward and reverse lookup record. We have also verified via telnet that port 51909 is open in both directions.
Any help would be appreciated.

If you are 100% sure port 51909 is open at Collector's side (you don't need to open it on ACS forwarder) and there's no additional firewall somewhere at the middle use wireshark and capture what's going on.
--- Jeff (Netwrix)

How to configure windows services alerts in SCOM 2012 for all agent servers. For eg, Terminal Services, Netlogon, RPC etc..

Hi,
I need to configure different windows services alerts in SCOM 2012. Below are some of the windows services I need to monitor through SCOM.
Serivce: Windows Management Instrumentation
Service: Netlogon
Service: Remote Procedure Call (RPC)
Service: Server Service
Service: Terminal Services
Service: Windows Time
Service: Workstation
Service : WWW Publishing Service
Could some one please assist or share me the details, how to configure these services for windows agent servers.
Thanks..
Regards, Rajeev Parambil

Hi,
A certain set of services are monitored by default on all agents:
DNS Client
DHCP Client
RPC
Workstation
Server
For all the other services you could create a service monitor.
A nice blog series outlining this process can be found here: http://www.bictt.com/blogs/bictt.php/2011/03/16/scom-monitoring-a-service-part1
It's doing common things uncommonly well that brings succes. Check out my SCOM link blog:
SCOM link blog

Upgrade to SCOM 2012 Agent - 25211.Failed to install performance counters.. Error Code: -2147024809 (The parameters is incorrect)

I have seen this behavior on multiple servers. I receive this error when upgrading from a 2007 Agent to SCOM 2012.
Event ID: 10005
Product: System Center 2012 - Operations Manager Agent -- Error 25211.Failed to install performance counters.. Error Code: -2147024809 (The parameter is incorrect.).
Event ID: 1008
The Open Procedure for service "HealthService" in DLL "C:\Program Files\System Center Operations Manager 2007\HealthServicePerformance.dll" failed. Performance data for this service will not be available. The Status code returned is the
first DWORD in the attached data.
Any idea why I receive this error?
Thanks
Mike

Hi,
Please refer to this article:
SCOM 2012 – Unable to upgrade agent after upgrade from SCOM 2007
http://www.phits.nl/wordpress/2013/02/01/scom-2012-unable-to-update-agent-after-upgrade-from-scom-2007/
Alex Zhao
TechNet Community Support

Automatic windows agent fail over in SCOM 2012 / 2012 R2

Similar Messages

Maybe you are looking for