SCOM 2012 R2 Modify Subscriber Address
hello,
we want to Change the subscriber address.
We want to Change the current value with a powershell script.
can anyone help me?
i can add a ne subscriber with
Set-SCOMNotificationSubscriber -Name "TEST" -DeviceTable @{"RB"= 'sms:+49123456'; "Command" = $Channel.DisplayName}
but we want to change the current value 'sms:+49123456' in 'sms:+9874563'. We don't want to delete the subscriber
thx
Hi,
Please refer to the link below:
Add-SCOMNotificationSubscriber
http://technet.microsoft.com/en-us/library/hh920214(v=sc.20).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.
Similar Messages
-
SCOM 2012 Installation problem - SQL Instance name
Hi All
Strange problem here, I wonder if anyone else has had the same issue.
I have a two-node SQL Server 2014 (Enterprise) Database server configured with a "SQL AlwaysOn Availability Group & Listener". The listener DNS name is: sql-ag-listener
On a separate server VM I attempted to install SCOM 2012 R2 - but when it came to the setup prompt to enter the "Servername & Instance" for the SQL server / Databases it will not accept my SQL AG Listener DNS name. However if I enter any
of the two individual SQL node names (SQL1 or SQL2) then it does accept those values and proceeds with the setup wizard. I do have a DNS entry for the SQL AG name.
All VMs are hosted in Azure. The SQL Servers are in their own Cloud Service and the SCOM MS Servers are in their own Cloud service.
I tried moving one of the SCOM MS Servers to the same Cloud Service container as the SQL Servers - still the same result.
Interestingly (as a test) - I started the SCOM 2012 Installation wizard on one of the SQL Servers and it DID accept the SQL AG value as the "Servername & Instance".
No firewalls are on. The VM endpoints allow SQL port 1433. Also, I can Telnet to the SQL Servers using 'telnet > O sql-ag-listener 1433' - response = Connected....
Not sure why this wont accept my virtual SQL AG name....?
thanksHi,
As when you install SCOM on one of your SQL server, then the AG name can be resolved, so it seems like this issue related with network resolution.
On the server where you want to run SCON setup, please use NSLOOKUP command to make sure it can the AG name to an IP address.
In addition, when you run the setup, don't select reporting server, as reporting server role need to install on a SQL server holding SSRS.
We still can install SCOM on normal database, and then add them into availability group later:
Add SCOM Databases to Availability Groups
http://www.tech-coffee.net/alwayson-part-8-methods-to-add-database-scom/
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] -
Exchange 2013 CU2, Alert for OWA Health set unhealthy from SCOM 2012
I am facing issue in Exchange 2013 CU2, I got this alert from SCOM 2012 atleast 5-6 times a day, OWA health set is unhealthy, I have done all the steps mentioned in this web link. Authentication type for OWA Virtual directory is integrated windows and Basic.
I have 2 CAS servers, and this alert generated from both of them.
http://technet.microsoft.com/en-us/library/ms.exch.scom.OWA(EXCHG.150).aspx?v=15.0.712.24
Alert: Health Set unhealthy
Source: EX-CAS - OWA
Path: EX-CAS;EX-CAS
Last modified by: System
Last modified time: 1/5/2014 8:15:08 PM
Alert description: Outlook Web Access logon is failing on ClientAccess server EX-CAS.
Availability has dropped to 0%. You can find protocol level traces for the failures on C:\Program Files\Microsoft\Exchange Server\V15\Logging\Monitoring\OWA\ClientAccessProbe.
Incident start time: 1/6/2014 4:05:08 AM
Last failed result:
Failing Component - Owa
Failure Reason - CafeFailure
Exception:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.Exchange.Net.MonitoringWebClient.ScenarioException:
Microsoft.Exchange.Net.MonitoringWebClient.ScenarioException:
Failure source: Owa
Failure reason: CafeFailure
Failing component:Owa
Exception hint: CafeErrorPage: CafeFailure Unauthorized Inner exception: Microsoft.Exchange.Net.MonitoringWebClient.CafeErrorPageException
ErrorPageFailureReason: CafeFailure, RequestFailureContext: FailurePoint=FrontEnd, HttpStatusCode=401, Error=Unauthorized, Details=, HttpProxySubErrorCode=, WebExceptionStatus=
Microsoft.Exchange.Net.MonitoringWebClient.CafeErrorPageException: An error occurred on the Client Access server while processing the request
WebExceptionStatus: Success
GET https://localhost/owa/ HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; MSEXCHMON; ACTIVEMONITORING; OWACTP)
Accept: */*
Cache-Control: no-cache
X-OWA-ActionName: Monitoring
Cookie:
HTTP/1.1 401 Unauthorized
request-id: 211474d2-a43e-4fab-8038-3aab35353568
X-FailureContext: FrontEnd;401;VW5hdXRob3JpemVk;;;
Server: Microsoft-IIS/7.5
WWW-Authenticate: Negotiate,NTLM,Basic realm="localhost"
X-Powered-By: ASP.NET
X-FEServer: EX-CAS
Date: Mon, 06 Jan 2014 04:14:47 GMT
Content-Length: 0
Response time: 0s
---> Microsoft.Exchange.Net.MonitoringWebClient.CafeErrorPageException: Microsoft.Exchange.Net.MonitoringWebClient.CafeErrorPageException
ErrorPageFailureReason: CafeFailure, RequestFailureContext: FailurePoint=FrontEnd, HttpStatusCode=401, Error=Unauthorized, Details=, HttpProxySubErrorCode=, WebExceptionStatus=
Microsoft.Exchange.Net.MonitoringWebClient.CafeErrorPageException: An error occurred on the Client Access server while processing the request
WebExceptionStatus: Success
GET https://localhost/owa/ HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; MSEXCHMON; ACTIVEMONITORING; OWACTP)
Accept: */*
Cache-Control: no-cache
X-OWA-ActionName: Monitoring
Cookie:
HTTP/1.1 401 Unauthorized
request-id: 211474d2-a43e-4fab-8038-3aab35353568
X-FailureContext: FrontEnd;401;VW5hdXRob3JpemVk;;;
Server: Microsoft-IIS/7.5
WWW-Authenticate: Negotiate,NTLM,Basic realm="localhost"
X-Powered-By: ASP.NET
X-FEServer: EX-CAS
Date: Mon, 06 Jan 2014 04:14:47 GMT
Content-Length: 0
Response time: 0s
--- End of inner exception stack trace ---
at Microsoft.Exchange.Net.MonitoringWebClient.BaseExceptionAnalyzer.Analyze(TestId currentTestStep, HttpWebRequestWrapper request, HttpWebResponseWrapper response, Exception exception, Action`1 trackingDelegate)
at Microsoft.Exchange.Net.MonitoringWebClient.HttpSession.AnalyzeResponse[T](HttpWebRequestWrapper request, HttpWebResponseWrapper response, Exception exception, HttpStatusCode[] expectedStatusCodes, Func`2 processResponse)
at Microsoft.Exchange.Net.MonitoringWebClient.HttpSession.EndSend[T](IAsyncResult result, HttpStatusCode[] expectedStatusCodes, Func`2 processResponse, Boolean fireResponseReceivedEvent)
at Microsoft.Exchange.Net.MonitoringWebClient.HttpSession.EndGet[T](IAsyncResult result, HttpStatusCode[] expectedStatusCodes, Func`2 processResponse)
at Microsoft.Exchange.Net.MonitoringWebClient.Authenticate.AuthenticationResponseReceived(IAsyncResult result)
--- End of inner exception stack trace ---
at Microsoft.Exchange.Net.MonitoringWebClient.BaseTestStep.EndExecute(IAsyncResult result)
at Microsoft.Exchange.Net.MonitoringWebClient.Owa.OwaLogin.AuthenticationCompleted(IAsyncResult result)
--- End of inner exception stack trace ---
at Microsoft.Exchange.Net.MonitoringWebClient.BaseTestStep.EndExecute(IAsyncResult result)
at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Bool
States of all monitors within the health set:
Note: Data may be stale. To get current data, run: Get-ServerHealth -Identity 'EX-CAS' -HealthSet 'OWA'
State
Name
TargetResource HealthSet
AlertValue ServerComponent
NotApplicable OwaCtpMonitor
OWA
Unhealthy None
States of all health sets:
Note: Data may be stale. To get current data, run: Get-HealthReport -Identity 'EX-CAS'
State
HealthSet
AlertValue LastTransitionTime
MonitorCount
NotApplicable ActiveSync
Healthy 1/3/2014 5:21:13 AM
2
NotApplicable AD
Healthy 11/24/2013 6:54:18 AM
10
NotApplicable ECP
Healthy 1/5/2014 3:03:05 AM
1
Online
Autodiscover.Proxy
Healthy 11/20/2013 10:06:37 AM
1
NotApplicable Autodiscover
Healthy 1/3/2014 10:18:17 PM
2
Online
ActiveSync.Proxy
Healthy 11/20/2013 10:06:37 AM
1
Online
ECP.Proxy
Healthy
11/21/2013 6:16:08 PM 4
Online
EWS.Proxy
Healthy 11/20/2013 10:06:37 AM
1
Online
OutlookMapi.Proxy
Healthy 11/24/2013 6:54:28 AM
4
Online
OAB.Proxy
Healthy 11/19/2013 7:14:34 PM
1
Online
OWA.Proxy
Healthy 11/20/2013 10:06:37 AM
2
NotApplicable EDS
Healthy 1/3/2014 5:19:56 AM
10
Online
RPS.Proxy
Healthy 1/3/2014 5:21:27 AM
13
Online
RWS.Proxy Healthy
1/3/2014 5:20:09 AM 10
Online
Outlook.Proxy
Healthy 1/3/2014 5:21:12 AM
4
NotApplicable EWS
Healthy 1/3/2014 10:18:17 PM
2
Online
FrontendTransport
Healthy 1/5/2014 3:47:09 AM
11
Online
HubTransport
Healthy 1/5/2014 3:47:09 AM
29
NotApplicable Monitoring
Unhealthy 1/5/2014 4:05:57 AM
9
NotApplicable DataProtection
Healthy 1/3/2014 5:25:42 AM
1
NotApplicable Network Healthy
1/4/2014 1:51:16 PM 1
NotApplicable OWA
Unhealthy 1/5/2014 8:05:08 PM
1
NotApplicable FIPS
Healthy 1/3/2014 5:21:12 AM
3
Online
Transport
Healthy 1/5/2014 4:11:00 AM
9
NotApplicable RPS
Healthy 11/20/2013 10:07:12 AM
2
NotApplicable Compliance
Healthy 11/20/2013 10:08:10 AM
2
NotApplicable Outlook
Healthy 11/21/2013 6:12:54 PM
2
Online
UM.CallRouter
Healthy 1/5/2014 3:47:10 AM
7
NotApplicable UserThrottling
Healthy 1/5/2014 4:16:42 AM
7
NotApplicable Search
Healthy
11/24/2013 6:55:06 AM 9
NotApplicable AntiSpam
Healthy 1/3/2014 5:16:43 AM
3
NotApplicable Security
Healthy 1/3/2014 5:19:28 AM
3
NotApplicable IMAP.Protocol
Healthy 1/3/2014 5:21:14 AM
3
NotApplicable Datamining
Healthy 1/3/2014 5:18:34 AM
3
NotApplicable Provisioning
Healthy 1/3/2014 5:19:56 AM
3
NotApplicable POP.Protocol
Healthy 1/3/2014 5:20:44 AM
3
NotApplicable Outlook.Protocol
Healthy 1/3/2014 5:19:46 AM
3
NotApplicable ProcessIsolation
Healthy 1/3/2014 5:19:26 AM
9
NotApplicable Store
Healthy 1/3/2014 5:20:38 AM
6
NotApplicable TransportSync
Healthy 11/24/2013 6:53:09 AM
3
NotApplicable MailboxTransport
Healthy 1/3/2014 5:21:11 AM
6
NotApplicable EventAssistants
Healthy 11/21/2013 6:22:01 PM
2
NotApplicable MRS
Healthy 1/3/2014 5:20:29 AM
3
NotApplicable MessageTracing
Healthy 1/3/2014 5:18:15 AM
3
NotApplicable CentralAdmin
Healthy 1/3/2014 5:17:25 AM
3
NotApplicable UM.Protocol
Healthy 1/3/2014 5:17:08 AM
3
NotApplicable Autodiscover.Protocol
Healthy 1/3/2014 5:17:13 AM
3
NotApplicable OAB
Healthy 1/3/2014 5:20:51 AM
3
NotApplicable OWA.Protocol
Healthy 1/3/2014 5:20:52 AM
3
NotApplicable Calendaring
Healthy 11/24/2013 6:56:59 AM
3
NotApplicable PushNotifications.Protocol
Healthy 11/21/2013 6:16:05 PM
3
NotApplicable EWS.Protocol
Healthy 1/3/2014 5:19:07 AM
3
NotApplicable ActiveSync.Protocol
Healthy
1/3/2014 5:20:16 AM 3
NotApplicable RemoteMonitoring
Healthy 1/5/2014 3:47:09 AM
3
Any solution for this alert, how to rectify it, but OWA is running perfect for all users.Hi,
Sorry for the late reply.
Do we have Exchange 2010 coexistence?
If it is the case, I know the following known issue:
Release Notes for Exchange 2013
http://technet.microsoft.com/en-us/library/jj150489%28v=exchg.150%29.aspx
Please note the "Exchange 2010 coexistence" session.
If it is not related to our problem, please check the IIS log.
If there is any detailed error code, like 401.1, 401.2, please let me know.
Hope it is helpful
Thanks
Mavis
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support -
Hi everyone,
We are doing an exclusive webinar for MS SCOM experts and would like to invite you to join us on 24<sup>th</sup> of April.
Visit our webinar to learn how to implement self-service reporting in SCOM 2012.
Agenda:
• How to address Cloud reporting
• SCOM 2012 reporting
• DevOps and Cloud - self provisioning
• Self-service in SCOM
Join the meeting:
https://cms.join.me/axibase.com (for North and South America)
Join the meeting: https://cms.join.me/axibase.webinar (for
EMEA)
On a computer, use any browser with Flash. Nothing to download.
On a phone or tablet, launch the
join.me app and enter meeting code:
axibase.com
Join the audio conference:
Dial a phone number and enter access code, or connect via internet.
By phone:
Access Code 346-934-063# (for North and South America)
Access Code 516-347-987# (for EMEA)
United States +1.860.970.0010
+1.408.418.5040
+1.860.970.0010
+1.646.307.1990
+1.682.710.0032
+1.213.226.1066
Argentina +54.11.5352.8217
Australia +61.2.9191.6319
Brazil +55.11.3958.8707
Canada +1.647.977.2648
Chile +56.22.582.8713
Colombia +57.1.381.2853
Japan +81.3.4579.5983
Mexico +52.55.4631.9922
New Zealand +64.9.951.8390
Panama +507.836.5977
Peru +51.1.707.5722
Venezuela +58.212.335.7832
By computer via internet:
Join the meeting, click the phone icon and select 'Call via internet'. A small download might be required.
Best regards,
Alex Ganyukov
VP of Sales
[email protected]
Direct no. +1.408.915.5551
www.axibase.com
Axibase CorporationHi,
From my point of view, SCOM reporting is to use to get needed reports about service availability, performance and alerts and so on. With those report, we may do data analysis to get more details about the monitored environments.
With management pack imported, there may be many available reports that can be run to get proper information about what monitored by using this management pack.
If there is any misunderstanding, please feel free to let me know.
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] -
SCOM 2012 R2 deployment on Amazon Cloud VM
Hi,
I am planning to deploy SCOM 2012 R2 on VM hosted on Amazon Cloud, is this supported deployment??
Also is any impact after the MAC address of SCOM VM`s changed??
i have deploy all the System center 2012 R2 Components on Amazon Cloud only ..
Shailendra DevHi,
Please refer to the link below:
Hardware Requirements for System Center 2012 R2
https://technet.microsoft.com/en-us/library/dn726764.aspx
These computers can be physical servers or virtual servers.
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] -
SQL version could not be verified error while installing the SCOM 2012 R2 reporting component
I have the below SCOM server roles in my SCOM 2012 R2 set up
1) All servers with Windows Server 2008 R2 SP1, MS - SCOM1, DB & DW - DB1, Reporting Server - DB2
2) All the DB servers with SQL 2012 SP1
3) Windows firewall is turned off on all the servers.
4) Success fully installed all the components except SCOM reporting.
While installing the SCOM 2012 R2 reporting component on DB2 ( Iam running this set up on the server where I instllaed the SQL DB engine and reportin services in Native mode. Configured the SQL reporting database and reporting URLs successfully in SQL reporting
configuration manager) getting the below error in the Rporting server instance page. Kindly advise.
I ran mofcomp.exe and there is no firewall restrictions. My account also has DB owner & sysadmin permissions.
Also tried re installing the SQL on Reporting server.
"The installed version of SQL Server could not be verified or is not supported. Verify that the computer and the installed version of SQL Server meet the minimum requirements for installation, and that the firewall settings are correct. See the Supported
Configurations document for further information".Hi,
As far as I know, after installing SSRS, we don't need to configure the database and reporting URLs manully. When we install the reporting service for SCOM, it will configure those automatically.
If possible, you may re-install SSRS and then install SCOM reporting service.
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] -
SCOM 2012 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!
KeithHi,
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 HA design but using SQL 2014 Standard edition
Hi All,
I want to deploy SCOM 2012r2 with a HA design (but have constraints!)
Plan is two management servers with all roles to each (fresh deployment so 2012r2 RU5)
SQL servers need to be 2014 standard edition due to licensing and cost constraints.
Design is to be split between two datacentres that are fibre connected and sub 3ms latency
Plan was to have a Management Server and a SQL server at each location.
Each location has a dedicated SAN but SAN replication is not an option.
What are my SQL options for the DB??
AlwaysOn FCI is not preferable as it gives a single point of failure due to shared storage requirement.
I read Database mirroring is not a supported config but this isn't Microsoft direct info just blog post, is this correct.
Which leaves me with log shipping, is this supported and the best option??
Would be great to get advice on what works well in the field with a contraint of having to use SQL Standard edition!
Thanks
JamesHi,
No additional licenses are needed for management servers or SQL Server technology.
System Center 2012 R2 licensing
http://www.microsoft.com/en-us/Licensing/product-licensing/system-center-2012-r2.aspx#tab=2
Reference:
SCOM 2012 R2 HA options with Server 2012 and SQL 2012
https://gallery.technet.microsoft.com/SCOM-2012-R2-HA-options-540beb95
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] -
SCOM 2012 R2 installtion wizard not able to contact SQL server cluster
Hi,
This is about the error faced while installing SCOM 2012 R2.
My customer has SQL 2012 SP1 cluster installed. I am trying to install the SCOM 2012 R2 with this installed SQL cluster. The SQL cluster is installed with default instance and with AAG (Always on Availability Group).
The edition of SQL server is, SQL Server Enterprise edition with SP1
After check services on both the SQL nodes found that SQL Full text is not installed (as the related SQL Full text service not present in the services.msc) on any of the SQL cluster node & SQL Browser service is not running.
The running services for SQL are, SQL Server (MSSQLSERVER) & SQL Server Agent (MSSQLSERVER).
When I started to install the SCOM 2012 R2, Within a SCOM 2012 wizard, On the Configure the Operational Database screen, entered only the name of SQL cluster & no instance as it is with default instance MSSQLSERVER.
I faced error as, This SQL Server could not be found.
After installed SQL full text, the service is showing in services.msc as "SQL Full-text Filter Daemon Launcher (MSSQLSERVER)".
Now when I started to install the SCOM 2012 R2, Within a SCOM 2012 wizard, On the Configure the Operational Database screen, entered only the name of SQL cluster & no instance as it is with default instance MSSQLSERVER.
I faced error as, The installed version of SQL Server could not be verified or is not supported.
Followings test carried out for the connectivity between SCOM 2012 MS &SQL Cluster
Ping SQL Cluster successfully
Telnet SQL Cluster for port 1433 successfully
Tracert SQL Cluster – completed successfully with single hops.
The windows firewall is off on both sides
The SQL services running on the Active node 1 of the cluster are as follows:
SQL Full Text Filter Daemon Launcher (MSSQLSERVER) -- Running & Manual
SQL Server (MSSQLSERVER) -- Running & Automatic
SQL Server Agent (MSSQLSERVER) -- Running & Automatic
SQL serve Browser - Stopped & Manual
SQL Server VSS Writer -- Running & Automatic
The SQL services running on the Passive node 2 of the cluster are as follows:
SQL Full Text Filter Daemon Launcher (MSSQLSERVER) -- Running & Manual
SQL Server (MSSQLSERVER) -- Running & Automatic
SQL Server Agent (MSSQLSERVER) -- Stopped & Automatic
SQL serve Browser - Stopped & Manual
SQL Server VSS Writer -- Running & Automatic
The SQL Server Agent (MSSQLSERVER) service is not running on the second node. It is running only on first node which is active.
The account used to install SCOM has the local admin privilege on the SQL server
To ping the cluster use the cluster name & it solved the whole FQDN of cluster in ping result. When ping with IP address with -a it not resolve to name.
Is any one can provide their valuable inputs.
Regards,
SandeepKHi SandeepK,
Before Installing Operations Manager on an availability group, please
1. Make sure to use the Group listener Name and port when installing Operations Manager for the databases that are going to be added to the availability databases.
2. The first management server will use the Group listener to get the primary SQL instance, and will install the databases on that instance.
System Requirements: System Center 2012 R2 Operations Manager
http://technet.microsoft.com/en-us/library/dn249696.aspx#BKMK_ClusterConfig
Niki Han
TechNet Community Support -
SCOM 2012 Network Monitoring Does Not Show Servers
We are testing out the network monitoring piece in SCOM 2012 but for some reason it never does show the servers. We have a test switch with a monitored server connected directly to it but after the discovery completes it doesn't show the server as
being connected. The switch in question is a Juniper and if you look at the diagram view for the device it does show all of the ports under "not monitored" and the Processor and Memory under "Healthy." The following event sequence shows up in the
"Network Discovery Progress Events" view:
Full Discovery Started for 1 request(s)
Proceeding to discover all systems in repository
Probing <<IP Address 1>>
Probing <<IP Address 2>>
Probing completed for <<IP Address 2>>
PostProcessing started
Probing completed for <<IP Address 1>>
PostProcessing completed
Switch::<<IP Address 2>> discovered successfully
Switch::<<IP Address 1>> discovered successfully
Discovery Completed / Devices discovered: 2 / Windows computers filtered: 0 / Devices in pending list: 0 / Devices excluded: 0
No devices were found in filtered list after discovery
Start processing connections to computers
Finished processing connections to computers. Number of connections made: 0
I've been trying to find some documentation on any other settings that are required to get network monitoring to work as advertised but so far I have struck out. Help!Sorry Matt - you did say that very clearly in your previous post. I'll try and do better this time ;-)
From here:
http://technet.microsoft.com/en-us/library/hh212935.aspx
From here:
http://blogs.technet.com/b/momteam/archive/2011/09/20/what-gets-monitored-with-system-center-operations-manager-2012-network-monitoring.aspx
"An agent computer that is directly connected to a device will have the connecting interface added to this group. For this to work the management group must have the Windows Operating System management pack for the agent’s operating system, the Windows
Client Network Discovery management pack and the Windows Server Network Discovery management pack. The full discovery of the agent’s operating system has to be completed including the discovery of the agent’s network adapters. Then when network discovery
runs for the device it should stitch the port on the device to the network adapter on the computer and add the port to this group."
So possibly:
- check the management packs specified are imported
- check the the agents network adapters have been discovered
From here -
http://technet.microsoft.com/en-us/library/hh212935.aspx - it is also possible to do this for non-scom monitored servers.
"Ports that are connected to a computer are not monitored; only ports that connect to other network devices are monitored. You can monitor a port that is connected to a computer that is not agent-managed in the same management group by adding the port to
the Critical Network Adapters Group."
Cheers
Graham
Regards Graham New System Center 2012 Blog! -
http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/ -
SCOM 2012 R2 Reporting is down
Hi All,
Reporting is down in SCOM 2012 R2.
Environment and issue: I have a small management group which consists of two MS and a SQL DB which is clustered. The reporting binaries have been run on node1 of the DB server only and the node 1 only has the follwing registry key :
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\System Center Operations Manager\3.0\Reporting,\ DWDBInstance
Now , all the sql resources are on Node 2 and when i run the report it says :
Reporting Services Error
An internal error occurred on the report server. See the error log for more details. (rsInternalError) Get
Online Help
And when i dug into the log it says:
library!ReportServer_0-1!1940!01/18/2015-21:07:03:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: Incorrect security descriptor version, Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
An internal error occurred on the report server. See the error log for more details.;
Earlier the following link format use to work but it does not now:
http://clustername/ReportServer_instancename
I tried to change it to node 2 like below [which does not work]:
http://node2/ReportServer_instancename
Finally i just tried with node 1 which works just fine via web browser:
http://node1/ReportServer_instancename
I think switching the sql resources back to node1 will solve the situation, i have already created a ticket to the DB team to look into it.I know that SCOm reporting is not cluster aware and that is how i just ran the reporting server binaries on the first
node.
Could you help me with the change of reporting server entries in either registry or config files or DB tables which could tell SCOM to look and contact only the node1 for reporting and not the node2.
Any comments would be greatly appreciated as I need to fix this soon else I would not be able to send the monthly SLA reports to my stakeholders as the Service Level Report Library option is not visible via SCOM web portal reporting.
Regards,
Techie Seeker.Hi,
As SQL cluster is not supported for operaion manager reporting(more information, please check
Operations Manager Reporting – Supported SSRS Configurations ), it is suggest you to move your data warehouse to another SQL:
How to Move the Data Warehouse Database
https://technet.microsoft.com/en-us/library/hh268492.aspx?f=255&MSPPError=-2147217396
Moving the Data Warehouse Database and Reporting server to new hardware–my experiencehttp://blogs.technet.com/b/kevinholman/archive/2010/08/25/moving-the-data-warehouse-database-and-reporting-server-to-new-hardware-my-experience.aspx
In addition, although cluster is not supported, someone else really have this done, you may refer to
Moving Operations Manager Data Warehouse Database part in the below article,and you may find registry keys and databases that needed to verified.
SCOM DataBases Migration to SQL Cluster
Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] -
SCOM 2012 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) -
Poweshell script for adding the computer object in to SCOM 2012 group.
Hi Team,
Is there any way to add the computer object ( csv file) to SCOM 2012 manually created group.Hi,
In addition, hope the links below be helpful for you:
Creating and Updating Groups
http://blogs.msdn.com/b/jakuboleksy/archive/2006/11/15/creating-and-updating-groups.aspx
Programmatically Creating Groups
http://blogs.technet.com/b/brianwren/archive/2008/11/18/programmatically-creating-groups.aspx
Modifying Explicit Group Membership in SCOM 2012 with PowerShell
http://blogs.msdn.com/b/rslaten/archive/2013/06/27/modifying-explicit-group-membership-in-scom-2012-with-powershell.aspx
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help. -
Orchestrator/SCOM 2012 and UTC Time for Get Alert
We are currently moving to using Orchestrator to act as a connector between SCOM 2012 and Unicenter for ticket generation. Right now, the runbook that I have built out does the following.
Monitor Date/Time > Format Date/Time > Get Alert
The monitor Date/Time runs every 60 seconds.
Format Date/Time then pulls from a variable that grabs the current time using now(). I then have it adding 4 hours and 55 minutes to the time to set the UTC time to 5 minutes earlier.
Get Alert then looks for all alerts that meet a specific criteria. This includes the time and any alert that was generated within the last 5 minutes, which is why I have it currently set to 4 hours and 55 minutes.
In a few months, that's going to break and I'll have to manually update the format date/time to 5 hours and 55 minutes. What I'm trying to find is a way to do this automatically so the runbook doesn't have to be modified. I'm thinking of using
the 'Activity End Time in UTC' from the Monitor Date/Time but want to see if there's any other easier way of doing it.Hi again,
If the question is to have a an easy way to get only Alerts not already seen with "Get Alert" before:
Use "Update Alert" and update fields like TicketID or ResoultionState after "Get Alert" and exclude this criteria in the Filter tab of "Get Alert" ...
Regards,
Stefan
www.sc-orchestrator.eu ,
Blog sc-orchestrator.eu -
Hi, all
I have Exchange Server 2013 and SCOM 2012 installed. I have imported Exchange Server 2013 Management Pack to SCOM 2012. Now I have a question that when there is a service not healthy, I can find the red alert in my alert view with the Exchange 2013 server,
but after the service is healthy automatically, the red alert is still there. I can only make it become green healthy status after reseting the healthset status in the healthset explorer.
Does anyone know how to make the server become green healthy status automatically after the monitor is healthy?
Thank you.
NileHi,
How many Exchange Servers do you have? Does this issue only occur on one Exchange Server?
Please check the application log on the problematic Exchange server and see whether there are any related event error.
Regards,
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]
Simon Wu
TechNet Community Support
Maybe you are looking for
-
Help needed in inserting into column of XML type
i have requirement of inserting data into column of xml type eg cust product cost 1 a 3 1 b 7 1 c 5 now required result should <PROD-LIST> <a>3</a> <b>7</b> <c>5</c> </PROD-LIST> Please let me know how to achieve this , i was trying write function ,
-
BLOCK CORRUPTION (ORA-1578) 처리 (ORACLE 8I NEW FEATURE)
제품 : ORACLE SERVER 작성날짜 : 2002-05-31 BLOCK CORRUPTION (ORA-1578) 처리 (ORACLE 8I NEW FEATURE) ======================================================== PURPOSE Block Corruption의 처리 방안에 대해 알아본다. Problem Description block corruption 시 10210, 10211,10231 의
-
Web.show_document and Firefox
Hi, we are usin web.show_document in oracle forms 9 for showing scanned documents Call working fine in IE all versions, but in firefox ver.2.0.0.6 we are not able to see *.tif document. When we press the button nothing happens. Is there problem with
-
Audio from imported mini dv footage seems to work in iMovie, but not in Quicktime or Toast
I'm importing some old footage from mini dv tapes using iMovie 10. When I play back the footage using iMovie it plays back with audio. When I go into the library and look at the .mov files, they don't play back with audio in Quicktime. I'm running Ma
-
Your Iweb video on TV? ?
I have been looking over some of the I web sites out there and to say the least I was impressed, entertained, amused, and informed. Some excellent sites! I am just inquiring as to how many of you with short video blogs from around 30 seconds to 5 min