SCOM 2012 client movement between Management servers

Hi all,
I know In SCOM 2012 sp1 all management servers are peers , if I have five management servers ( A, B, C, D,E ) and 2 gateway servers ( F, G ) . One client is assigned to A management server , in case if that management server down , to which management servers
or Gateway server that particular client will move any rule.
Thanks,
Sengottuvel M

By default, "the first available management server". There is a black-box algorithm that works behind the scenes in terms of agent failover selection. The only way to control this is to set agent failover lists, and this is only possible via the command
shell (powershell) - but it's relatively easy to do.
Here are a couple interesting articles about the topic:
http://blog.scomskills.com/agent-managementlist-primary-and-failover-configuration/
http://blogs.technet.com/b/jonathanalmquist/archive/2009/11/11/set-failover-management-server-for-gateway-role.aspx
...and there are probably 100 other blog posts talking about the same thing.
Jonathan Almquist | SCOMskills, LLC (http://scomskills.com)

Similar Messages

How to Restrict Oracle VIP address Movement between DB servers?

I installed the Oracle 11.2 RAC on 4 server setup.Its a 4 server Grid SETUP and out of 4 servers only servers are runnning the Database Instances.
The did this installation to use ACFS feature.
Now i need to map the Public IP with Oracle Database ip address. so from Internet limited user can connect through oracle tns and listener entry.
If i am mapping with database static ip, then will face service outage in case of that Oracle Instance server down.
If i am mapping with Oracle Virtual IP address, then this Virtual IP is shifting anyone of the three server. So sometimes it can shift to Grid server where Database is not running.
How Can I restrict the Database Virtual IP movement between Database servers only ?
-sumit

So you have a 4 node RAC, but with only 3 nodes running the database ?
I am confused about why the 4th node is part of the RAC then ?
Please post more info about how things are configured

SCOM 2012 Global Architecture, One management group or multiple?

Hi Folks,
I work for a global firm, we have multiple data caters in different regions. America, UK, Australia, China etc etc. We are looking to roll out SCOM 2012 for monitoring all systems. Our environment
1,000 Windows servers
All servers on the same Active Directory domain
10 Mbps links between data centers.
My question is around whether to use multiple management groups or one? I’ve seen recommendations for both. For example
In the Infrastructure Planning and Design guide for SCOM 2012 it is stated:
“A centralized management model with large remote locations works best with a management group in each region and a local management group (which provides a consolidated view of alerts and status) in the parent location. In this case, the centralized management
group connects through the software development kit (SDK) and functions as an additional console on each of the connected management groups.”
However moderators in this forum have stated
“Each management group has its own set of SQL Servers and Management Servers \ Gateways. It also adds considerably to administrative overhead. I'd try to avoid
multiple management groups where possible.”
” It will get expensive in terms of hardware and software with multiple management groups and you will duplicate a lot of work with regards to overrides”
“If you go with multiple Management Groups then you would need to add on a fair number of SQL licenses plus additional hardware. “
“Presumably if I have multiple management groups will that mean I will have to
create rules for each Management Group- correct. Same
with overrides. It could add a lot of administrative overhead. “
It would seem easier to just deploy one management group with the management servers in one datacenter but I’m concerned with performance. I’ve heard
stories about SCOM deployments architected in this way not performing well because of network latency. i.e admins from all regions besides the region local to the SCOM deployment not wanting to use SCOM because application performance is too slow.
What would the SCOM experts recommend for this scenario?
MH

1) My question is around whether to use multiple management groups or one?
Factors to consider in determine the number of Management group
• Scaling
• Agents separated from their management server by WAN-speed network links
• Political, administrative or security requirements within the organization requiring separate management groups.
• A view of AD DS topology required across multiple forests.
• A dedicated management group required for auditing purposes.
• Disaster recovery functionality required.
• Consolidated views of connected management groups required in Operations Manager.
• Operations Manager integration with the VMM console.
With refer to your situation
a) 1,000 Windows servers
b) All servers on the same Active Directory domain
c) 10 Mbps links between data centers.
It is suggest that one Management group is required.
2) It would seem easier to just deploy one management group with the management servers in one datacenter but I’m concerned with performance
It is recommend that you should deploy Gateway server in region office which has more than 10 agents.
• Gateway server reduce network bandwidth utilization. Agents located across WAN links consume network bandwidth, potentially affecting service delivery to and from the remote location. A gateway server can consolidate the traffic.
Roger

SAML2 between Managed Servers in same Weblogic

Hi,
I need to configure SAML V2 between 2 or more applications deployed in WebLogic 10.3.6 server.
My problem occurs when I try to use application in same weblogic, different managed server.
* App1 call App2 within an iframe.
* When I access App1, logon page works.
* When I access App2 within iframe, credentials was transfered perfectly from App1 to App2.
* When I return to App1, session is ended.
Deploying apps on diferent weblogic all works fine and I can access App1 and App2 normally.
Deploying apps on same weblogic, same managed server, credentials are sharing automatically even SAML not configured.
I can't understand why App1's session was killed when I access App2 in same weblogic and different managed servers.
Does someone can help me?
Regards

I am setting a different cookie for each application. First app show login form and authenticate correctly but when I open second app, credentials was not recnognized.

SCOM 2012 System Center Operations Manager has stopped working when adding Web Console.

I am trying to ad the Web console to one of my Management Servers but at the point where it asks what website to use it fails with the "System Center Operations Manager Setup has Stopped working error.
This is the included information.
Problem Event Name: CLR20r3
Problem Signature 01: setupchainerui.exe
Problem Signature 02: 7.0.9538.0
Problem Signature 03: 509042f2
Problem Signature 04: System
Problem Signature 05: 4.0.30319.18022
Problem Signature 06: 506a7689
Problem Signature 07: 1cf5
Problem Signature 08: 72
Problem Signature 09: System.UriFormatException
OS Version: 6.2.9200.2.0.0.272.7
Locale ID: 1033
Additional Information 1: 79c6
Additional Information 2: 79c63d7b6daeea05a42903612b7137d2
Additional Information 3: 88ec
Additional Information 4: 88ec54f8fa758d8069cdb2ad5cd91e2b
The only error I get in the log file is this.
Error: :Error:IsReportingValidToInstall failed SRS instance not provided
I don't understand why I would be getting an SRS error, our reports run fine.
Thanks,
Gary

Hi Gary,
Did you end up finding a solution to this issue? The GUI and silent/command line installer are failing for me in the same spot.
App Log Errors:
Application: SetupChainerUI.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: Microsoft.EnterpriseManagement.Common.ServiceNotRunningException
Stack:
   at Microsoft.EnterpriseManagement.Common.Internal.ExceptionHandlers.HandleChannelExceptions(System.Exception)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.CreateEndpoint[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](Microsoft.EnterpriseManagement.EnterpriseManagementConnectionSettings,
Microsoft.EnterpriseManagement.Common.Internal.SdkChannelObject`1<Microsoft.EnterpriseManagement.Common.Internal.IDispatcherService>)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.ConstructEnterpriseManagementGroupInternal[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0,
Culture=neutral, PublicKeyToken=b77a5c561934e089]](Microsoft.EnterpriseManagement.EnterpriseManagementConnectionSettings, Microsoft.EnterpriseManagement.DataAbstractionLayer.ClientDataAccessCore)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.RetrieveEnterpriseManagementGroupInternal[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0,
Culture=neutral, PublicKeyToken=b77a5c561934e089]](Microsoft.EnterpriseManagement.EnterpriseManagementConnectionSettings, Microsoft.EnterpriseManagement.DataAbstractionLayer.ClientDataAccessCore)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.Connect[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](Microsoft.EnterpriseManagement.EnterpriseManagementConnectionSettings,
Microsoft.EnterpriseManagement.DataAbstractionLayer.ClientDataAccessCore)
   at Microsoft.EnterpriseManagement.ManagementGroup.InternalInitialize(Microsoft.EnterpriseManagement.EnterpriseManagementConnectionSettings, Microsoft.EnterpriseManagement.ManagementGroupInternal)
   at Microsoft.EnterpriseManagement.ManagementGroup.Connect(System.String)
   at Microsoft.SystemCenter.Essentials.SetupFramework.WebConsoleSite.GetValidationProperties(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
Faulting application name: SetupChainerUI.exe, version: 7.0.9538.0, time stamp: 0x509042f2
Faulting module name: KERNELBASE.dll, version: 6.3.9600.16656, time stamp: 0x5318237f
Exception code: 0xe0434352
Fault offset: 0x00000000000043c8
Faulting process id: 0x638
Faulting application start time: 0x01cf9a697847d9c8
Faulting application path: C:\Users\szb\AppData\Local\SCOM\SetupChainerUI.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: c52d5d75-065c-11e4-80c2-00155dcb0b37
Faulting package full name:
Faulting package-relative application ID:

What should be the client url for managed servers in a cluster

Hi guys,
I have created a cluster(cluster_1) having 4 managed servers. 2 managed servers on my machine(IP1) and 2 managed servers on other machine(IP2).
I am able to deploy a xxx.war file on my admin server
also
I am able to deploy the same war file on my cluster
When I try to hit the client url, it gives me back the correct data, but it creates the session on the admin server and not the cluster.
If I remove the xxx.war file from the deployment(deployed on admin server) and redeploy the xxx,war file on the cluster, it gets deployed successfully , but the client url gives me a 404 error.
What should I do, so that after hitting the client url, it creates the session on the managed servers in the cluster ?
My admin server is not the part of this cluster.
cluster ip:127.0.0.1
ip1: 10.25.63.130
ip2: 10.25.63.131
please help
Salil

Hi Salil
This is exactly what I mentioned in my earlier post. You CANNOT and should NOT expose the managed server url (host, port) to the end users. Because as you already figured out, you can specify only one. Or they cannot try one at a time like that.
This is where, the Load Balancer will come into picture like Apache Web Server. After installing Apache web server, usually it runs at default port 80. So you just expose the apache host to outside world. Also most companies will have Firewalls and Apache is outside of Firewall and all weblogic servers are inside the Firewall. In apache, you configure the weblogic cluster details like the host names and ports of each managed server etc in httpd.conf file etc.
Ex: For outside users, they may try like http://apachehost/myWeb/myHello.jsp -> apachehost is the host name where Apache web server is running at port 80. NOW Apache is smart enough to do Load Balancing and Failover. If 100 users access the site with 4 managed servers, ideally each managed server will get 25 requests (load balancing). Also if 2 servers are killed, automatically, request will NOT go to them, but to other 2 live servers etc etc. Apache takes care of this.
Bottom line, please see my earlier post, and you need to have some sort of Web Server like Apache for your cluster setup.
Thanks
Ravi Jegga

Security Context Propagation between Managed Servers

          I'm using WLS 8.1 SP2. I have one domain, two managed servers, each on a separate
          hardware server. Each managed server hosts a different web application. I want
          to authenticate to Web App "A" and be able to invoke Web App "B" (from "A") without
          having to re-authenticate. Is this possible via configuration and, if so, how?
          Thanks.


Frank,
You do not have to do anything to propagate identity between the two
containers. As long as the user is authenticating first..
There have been a number of issues with the propagation, so be sure to stay up
on the service packs.
HTH.
Frank wrote:
How do you propagate security context information from Servlet to
EJBs? I have an web app that uses the container's FORM based authentication.
The servlet resource then calls a session EJB (w/ security contraints
setup). The webapp and the ejbs are bundled into one EAR.
Thanks!--
Tom Mitchell
[email protected]
Very Current Stoneham, MA Weather
http://www.tom.org

Propagating Security Context between Managed Servers

I'm using WLS 8.1 SP2. I have one domain, two managed servers, each on a separate
hardware server. Each managed server hosts a different web application. I want
to authenticate to Web App "A" and be able to invoke Web App "B" (from "A") without
having to re-authenticate. Is this possible via configuration and, if so, how?
Thanks.

"K Northey" <[email protected]> wrote in message
news:[email protected]...
>
I'm using WLS 8.1 SP2. I have one domain, two managed servers, each on aseparate
hardware server. Each managed server hosts a different web application.I want
to authenticate to Web App "A" and be able to invoke Web App "B" (from"A") without
having to re-authenticate. Is this possible via configuration and, if so,how?
>
Does the following do what you want?
http://e-docs.bea.com/wls/docs81/security/thin_client.html#1039551
Multiple Web Applications, Cookies, and Authentication
By default, WebLogic Server assigns the same cookie name (JSESSIONID) to all
Web applications. When you use any type of authentication, all Web
applications that use the same cookie name use a single sign-on for
authentication. Once a user is authenticated, that authentication is valid
for requests to any Web Application that uses the same cookie name. The user
is not prompted again for authentication.
If you want to require separate authentication for a Web application, you
can specify a unique cookie name or cookie path for the Web application.
Specify the cookie name using the CookieName parameter and the cookie path
with the CookiePath parameter, defined in the WebLogic-specific deployment
descriptor weblogic.xml <session-descriptor> element. For more information,
see session-descriptor in Assembling and Configuring Web Applications.
If you want to retain the cookie name and still require independent
authentication for each Web application, you can set the cookie path
parameter (CookiePath) differently for each Web application.
As of Service Pack 1, BEA Systems added a new capability to WebLogic Server
that allows a user to securely access HTTPS resources in a session that was
initiated using HTTP, without loss of session data. To enable this new
feature, add AuthCookieEnabled="true" to the WebServer element in
config.xml:
<WebServer Name="myserver" AuthCookieEnabled="true"/> Setting
AuthCookieEnabled to true causes the WebLogic Server instance to send a new
secure cookie to the browser when authenticating via an HTTPS connection.
Once the secure cookie is set, the session is allowed to access other
security-constrained HTTPS resources only if the cookie is sent from the
browser.

Communicating between Managed Servers

Hi,
I have multiple Managed servers running on the same host, each hosting one web
app on a particular port.
The Admin server runs on port 7001.
Example :
The Managed Server hosting the Session Manager is running on 7100, and the
Managed server hosting the DSLTools is running on port 7200.
The following link works -
http://localhost:7100/sessionmgr/servlet/sessionmgr
Now when I click on DSLTools button on the page displayed by the above link,
it takes me to
http://localhost:7100/dsltools/servlet/dsltools
whereas, I want it to take me to
http://localhost:7200/dsltools/servlet/dsltools
If I type the http://localhost:7200/dsltools/servlet/dsltools
in the web browser, it works.
So, ques is how can I go from Session Manager running on port 7100 to
DSL Tools running on port 7200 ?
I am trying Proxy by path using ProxyServlet, but it doesn't seem to work.
I don't want to hard code the port numbers in the Session Manager servlet
for obvious reasons.
A quick response will be appreciated.
Thank you very much
-Anil Varma

Hi Chris,
Thanks for your suggestion. I am going to try you suggestion
and hope somebody responds to it.
Thanks
-Anil
"Chris Chiodo" <[email protected]> wrote:
Hi Anil,
You might consider asking this same question on the
"weblogic.developer.interest.servlet" newsgroup. The people monitoring
that
group would be likely to know the answer to this question.
Thanks
Chris Chiodo
BEA Systems
"Anil Varma" <[email protected]> wrote in message
news:3f1c020e$[email protected]..
Hi,
I have multiple Managed servers running on the same host, each hostingone
web
app on a particular port.
The Admin server runs on port 7001.
Example :
The Managed Server hosting the Session Manager is running on 7100,and the
Managed server hosting the DSLTools is running on port 7200.
The following link works -
http://localhost:7100/sessionmgr/servlet/sessionmgr
Now when I click on DSLTools button on the page displayed by the abovelink,
it takes me to
http://localhost:7100/dsltools/servlet/dsltools
whereas, I want it to take me to
http://localhost:7200/dsltools/servlet/dsltools
If I type the http://localhost:7200/dsltools/servlet/dsltools
in the web browser, it works.
So, ques is how can I go from Session Manager running on port 7100to
DSL Tools running on port 7200 ?
I am trying Proxy by path using ProxyServlet, but it doesn't seem towork.
I don't want to hard code the port numbers in the Session Manager servlet
for obvious reasons.
A quick response will be appreciated.
Thank you very much
-Anil Varma

Deploy SCOM 2012 R2 Agents to Domain Servers on Perimeter Network using SCOM Gateway on different Domain

Hi, I have a bit odd situation on a SCOM 2012R2 deployment.
I have a MS on the internal network, and a Gateway Server on the perimeter network. Each server is connected to different Active Directory Forests and there are no trust relationships between them. I configured the communication between the two using certificates.
I have already connected some servers through the Gateway using certificates because there are on Workgroups, they are already approved on the MS and reporting their status.
However, I have some servers that are member servers of the internal AD domain but are located on the perimeter network.
So I've tried to configure one of them for testing to connect to the Gateway Server using a certificate using manual agent installation. Initially it didn't report on the SCOM, but then I ran the get-scompendingmanagement and saw that it showed there,
so I ended up approving the agent using Powershell and then it was reported on the Console as "Not Monitored"
First the agent was running as local system and then tried using a local admin account on the server, neither options have worked.
I get the following errors:
The OpsMgr Connector connected to scomgateway.externaldomain.com, but the connection was closed immediately after authentication occurred. The most likely cause of this error is that the agent is not authorized to communicate with the server, or the
server has not received configuration. Check the event log on the server for the presence of 20000 events, indicating that agents which are not approved are attempting to connect.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
OpsMgr was unable to set up a communications channel to scomgateway.externaldomain.com and there are no failover hosts. Communication will resume when scomgateway.externaldomain.com is available and communication from this computer is allowed.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Is this configuration possible? Or do I need to open communication ports from the agents to the MS inside the corporate network and not use the Gateway?
Any ideas if someone else has done this are appreciated.
Thank you.
Regards.
Eduardo Rojas

I'm sorry, maybe I didn't explained myself correctly, I already have the gateway up and running with some Workgroup machines connected to it using certificates, so the Gateway is indeed working. These Workgroup machines are in fact reporting back to the
Management Server on the internal network through the Gateway.
My problem is with Domain Member machines that are on the perimeter network. This machines are joined to the Active Directory inside the corporate firewall, not the Active directory from the perimeter network (where the Gateway is joined). So my question
is, can I connect these machines through the Gateway (even if the Gateway is on a different domain) or do I need to open ports and connect them directly to the management server (which is on the same active directory domain)?
Let me know if I made myself clear.
Thank you.
Regards.
Eduardo Rojas

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

SCOM Management Servers not working after DW upgraded to SQL 2014

Hey guys,
Our setup is that we have 2 Management Servers running SCOM 2012 R2 UR3 on Server 2008. I want to say exactly what our problem is, and what my guesses are at it. Any additional information you need please just ask.
Problem = In the SCOM console we have the management servers and Gateway servers going grey. If i go to these servers and restart the Monitoring service, it acts like it was locked up or something and has to force stop it and restart it. Once back up, everything
works fine. Then it goes grey again at a random interval between 5-120 minutes. Recycle Repeat. I reviewed the Event Log during this and afterwards and ALOT of stuff points toward the DataWarehouse and not being able to write stuff to it. I have two suspicions.
Idea 1 = Another Engineer recently updated SQL on the Datawarehouse server to 2014. I recently found this had caused a problem with SCSM reporting and had to do some stuff to fix that.... so I was thinking that maybe this had something to do with it.
Idea 2 = Also around the same time... UR3 came out. This was auto pushed out to all the server and agents through WSUS, I also went through and manually did all the steps for this. Its still possible i suppose that I missed something.
Basically Im just looking to see if anyone has any advice as to what to check next, and/or see if anyone else has had this problem. Thanks guys!

I unfortunately do not have a solution for you, but can still try to provide some info :
1. SQL 2014 is NOT supported with system center 2012 R2! See http://technet.microsoft.com/library/dn281933.aspx
2. You might want to try the procedure for moving the databases : http://technet.microsoft.com/en-us/library/hh278848.aspx

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

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

SCOM 2012 Probe for Omnibus (Netcool)

Hi Team,
One of my client is using SCOM 2012
I have asked customer if they use a load balancing solution and they answered that
no:
if the RMS fails the system will switch to the next MS “in line” (let’s call it MS2) and when the RMS will finish rebooting (all 3 MSs, RMS and the other two MSs in the solution, work on virtual
machines and rebooting them will take one minute, or something like that) then it will become the active MS/RMS (a failback configuration).
If MS2 will fail (while the RMS is still down) then the third MS (MS3) will become the active one; if MS2 (or RMS) will recover then the active MS will be MS2 (or RMS).
Q1: That means Customer Configured Cluster Failover ? any specific ?
If yes. Do we have any Cluster IP which connect to Active MS (Actually SCOM Probe needs to be connected to MS)
Q2 : When Primary MS 1 goes down.. how Operator will see events from Which MS ? (Is Operational console will be installed on MS* also) ?
Q 3: So if there one connector to MS1 and a second connector on MS2, both MS on the same management group, and configured to get the same group of alarms (for example ResolutionState = 0
(New) ) then the two connectors will be in a race condition: each connector will receive different alarms because the alarms are stored in the same database (and not on the MS itself).
Is my understanding correct?
Thanks
Sekhar

Please check this:
http://social.technet.microsoft.com/Forums/systemcenter/en-US/ab30c52f-7b61-40fd-9845-6cb0caa7a396/how-does-an-scom-agent-know-what-failover-management-servers-are-available
http://vmajmudar.blogspot.in/2013/07/scom-2012-rms-emulator-fail-over.html
Hope it helps !!

Only showing APP monitoring Reports in SCOM 2012 Reporting

Hi all,
Recently i upgrade the SCOM 2012 from 2007 R2 Managament Server only because in previous environment we have only one MS server and SQL server 2008 SP2.
Now i have 4 servers for SCOM 2012.
1) SCOM Managament server (which was upgraded)
2) SQL server 2008 SP2 (running 3 instances)
3) SCOM ACS server (New installation)
4) SCOM Reporting server (New installation)
I have using two accounts
1) SCOM.action 2) SCOM.sdk
When i install reporting, reporting Tab are showing in the SCOM
2012 console but only Application monitoring reports are showing in Reporting. I was deleted some MP’s and then import it but the report are not imported in reporting tab. I also check SSRS, it works fine. Both SSRS url’s works fine.
I don’t know whats the problem.. Please clarify me what’s the problem.????
Regards,
Kamran

Hi Muhammad,
I am also facing the exact issue as expalined above.
Even the application monitroing reports are not working. When i try to launch application monitoring reports from reportmanger , I get dataset error and see that apm.* views are missing.
Also tried deleting and importing the managementpacks, without any success. This issue is happening only in production environment.
It will be very helpful if you can let us know what Account permisisons need to be checked for. Thanks in advance.
Thanks

SCOM 2012 client movement between Management servers

Similar Messages

Maybe you are looking for