SCOM 2012 r2 - Add GW Sitename on a later stage

Hi,
Does anyone know how to add sitename to a spesific Gateway server without rerunning the Microsoft.EnterpriseManagement.GatewayApproval.exe tool?
regards,
lostcase

No, you can't do that without
run the gateway approval tool. Microsoft.EnterpriseManagement.gatewayApprovalTool.exe
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

Similar Messages

Agent Server not reflecting under "Add Group" or " Add Object in SCOM 2012

Hi,
Here the Windows Agent server are showing healthy under 'Windows Computer' in Monitoring tab. Also I can view the various objects like Memory, Logical Disks, System etc under Performance View. Once I moved to Reporing tab, I cannot find
this agent server under Add Group or Add Object.
I tried reconfigure the SCOM agent on this server and still no luck.
Could some one pls assist me to resolve this issue.
Here the Management server is SCOM 2012.
Thanks
Regards, Rajeev Parambil

Hi Yan Li,
Thanks for your reply.
Even I tried to do the same. No luck. Am attaching the same snif here for ref.
But at the same time I can see the different counter & its output details under "performance view".
refer the below snip.
Am able to pull the reports for other set of servers. My confusion here is why this particular server details are not showing under Reporting module. How can I isolatae this issue. Pls advise. Thanks
Regards, Rajeev Parambil

Unable to add a performance widget to a dashboard in SCOM 2012

When trying to select a group or object when attempting to configure a new performance widget within a SCOM 2012 dashboard, I get the following error. Anybody any ideas what is causing this issue in my instance of SCOM 2012?
This is part of a custom built Management Pack and a Distributed Application linking just three computers together.
Any help would be welcomed.
Please provide the following information to the support engineer if you have to contact Microsoft Help and Support :
Microsoft.EnterpriseManagement.Presentation.DataAccess.DataAccessDataNotFoundException: Exception reading objects ---> Microsoft.EnterpriseManagement.Common.UnknownDatabaseException: The query processor ran out of internal resources and could not produce
a query plan. This is a rare event and only expected for extremely complex queries or queries that reference a very large number of tables or partitions. Please simplify the query. If you believe you have received this message in error, contact Customer Support
Services for more information.
   at Microsoft.EnterpriseManagement.Common.Internal.ServiceProxy.HandleFault(String methodName, Message message)
   at Microsoft.EnterpriseManagement.Common.Internal.EntityObjectsServiceProxy.GetManagedEntitiesByManagedEntityTypesAndCriteriaWithInstanceQueryOptions(IList`1 managedEntityTypeIds, IList`1 managedEntityBaseTypeIds, IList`1 criterias, String languageCode,
InstanceQueryOptions instanceQueryOptions)
   at Microsoft.EnterpriseManagement.InstancesManagement.GetObjectsReaderInternal[T](ICollection`1 criteriaCollection, ObjectQueryOptions queryOptions)
   at Microsoft.EnterpriseManagement.Management.DataProviders.ManagedEntityProvider.GetManagedEntitiesByClass(ICollection`1 baseTypeNames, String criteriaString, List`1 valueDefinitions, List`1 sortValueDefinitions, Int32 maxEntities, String typePropertyName,
String typeWithIconPropertyName, Boolean propertyCollectionRequested)
   --- End of inner exception stack trace ---
   at Microsoft.EnterpriseManagement.Presentation.DataAccess.DataProviderCommandMethodInvoker.Invoke()
   at Microsoft.EnterpriseManagement.Monitoring.DataProviders.RetryCommandExecutionStrategy.Invoke(IDataProviderCommandMethodInvoker invoker)
   at Microsoft.EnterpriseManagement.Presentation.DataAccess.DataProviderCommandMethod.Invoke(CoreDataGateway gateWay, DataCommand command)
   at Microsoft.EnterpriseManagement.Presentation.DataAccess.CoreDataGateway.ExecuteInternal[TResult](DataCommand command)
   at Microsoft.EnterpriseManagement.Presentation.DataAccess.CoreDataGateway.<ExecuteAsync>b__0[TResult](<>f__AnonymousType0`1 data)

What is your SCOM version and patch level?
For SCOM 2012 SP1, there is known issue that:
When you select objects on the dashboard, you receive the following error message:
Microsoft.EnterpriseManagement.Presentation.DataAccess.DataAccessDataNotFoundException: Exception reading objects ---> Microsoft.EnterpriseManagement.Common.UnknownDatabaseException: The query processor ran out of internal resources and could not produce
a query plan. This is a rare event and only expected for extremely complex queries or queries that reference a very large number of tables or partitions.
This can be resolved by apply UR4
https://support.microsoft.com/en-us/kb/2879276/
Roger

How can I add SCOM 2012 Alert Context within a SCOM Alert When using a cusom powershell script in a two state monitor?

Hello, we have a two state monitor and I would like to channel the Alert Context to Alert Description.
The powershell script being used to find the stopped services is pasted below:
$API = new-object -comObject "MOM.ScriptAPI"
$bag = $api.CreatePropertyBag()
$ServiceStatus = Get-WmiObject -class win32_service |where {$_.startmode -eq'Auto'-and $_.State -eq 'Stopped' -and
$_.name -ne 'wuauserv'}
if (!$ServiceStatus) #if there are no automatic services that are stopped, we are healthy.
write-host "good"
$bag.addvalue("State","good")
if ($servicestatus) #if there are any automatic services that are stopped, we are unhealthy.
write-host "bad"
$bag.addvalue("State","bad")
foreach ($service in $servicestatus) #enumerate the stopped services
$bag.addValue("$($Service.Name):","$($Service.state)")
$bag
$API.Return($BAG)
The results of the services that are stopped are being captured in the Alert Context”. How can I pipe the Alert Context to “Alert Description” to obtain a meaningful alert?
Alert Context data:
Property Name                              Property Value
State
bad
clr_optimization_v4.0.30319_32: Stopped
clr_optimization_v4.0.30319_64: Stopped
How can I pipe to Alert Description in SCOM 2012?
Thanks,
Kapil Dham
Kapil Dham

you don't need write-host
you should create
$bag.addvalue("ServiceName1","StateOK")
$bag.addvalue("ServiceName2","StateStopped")
and in alert description you will see
ServiceName1
StateOK
ServiceName2
StateStopped
So try $bag.addValue($Service.Name,$Service.state)
and $Data/Context/Property$

SharePoint 2010 SP2 hosted on Windows 2012 R2 NOT discovered by SCOM 2012 R2 + 2 SP MP's

What is the process to get SharePoint 2010 Management Packs loaded in System Center 2012 R2 to discover/monitor SharePoint 2010 SP2 (14.0.7121.5000) loaded on Windows 2012 R2?
View of installed system:
System Center 2012 R2 loaded on Windows 2012 R2 (supported separately by SQL 2012 SP1 loaded on Windows 2012 R2)
-Microsoft SharePoint 2010 Products Management Pack for System Center Operations Manager 2007
-System Center 2012 Monitoring Pack for SharePoint 2010
SharePoint 2010 SP2 (14.0.7121.5000) loaded on Windows 2012 R2 (supported separately by SQL 2012 SP1 loaded on Windows 2012 R2)
The SharePoint 2010 Management Shell works fine!
Result
Event 0, Operations Manager - Cannot identify which SharePoint farm server is associated with. Check the management pack guide for troubleshooting information.
Looked at these already:
KB2690744, Configuring the SharePoint 2010 Management Pack for System Center Operations Manager.
http://om2012.wordpress.com/2013/05/24/sharepoint-2010-mp-on-scom-2012/
Further, if the xml push does have the command get-farm instead of get-spfarm, that could be the issue. i.e.
http://www.scom2k7.com/advanced-troubleshooting-of-the-sharepoint-2010-mp/
Thanks,
+Tony
Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you.

Peter,
I recommend to remove the Windows 2012 R2 server out of the farm and redeploy on W2008 R2.
This issue does not have an easy fix.
Summarizing, this appears to be the issue:
1. Windows Management Framework 3.0 is integrated with Windows 2012 R2, which installs .NET 4 and Powershell 4.0. Not uninstallable.
2. The Add-PSSnapin Microsoft.SharePoint.PowerShell is not supported with Powershell 4.0.
3. The SCOM SP2010 MP puts a package on the defined farm server and when the agent launches the package, it calls Powershell (v4 in theis case) and errors out. The target W2012 server will have an Error 0 in the Operations Manager Event log. See below.
Options:
1. Work around maybe - Develop method for manual discovery (I'm working on that now).
2. Rebuild SP2010 farm on Windows 2008 R2
3. System Center Team - Write a new MP to down version Powershell (Powershell.exe -Version 2)
4. Powershell Team - Write a SharePoint Snapin for Powershell 4
Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you.

How to create a group in SCOM 2012 R2 based on SCCM Collection?

Is there a way to create a group in SCOM 2012 R2 based on sccm collection? I am planning to use that group for maintenance mode.
Thanks, Samer

Hi,
I think you could query all the collectin members from SCCM database then use powershell to add them to a specific OU.
How to Create Groups in Operations Manager
http://technet.microsoft.com/en-us/library/hh298605.aspx
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

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

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

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

Is it possible to deploy 2 SCOM 2012 R2 reporting in a SQL server which already has SCOM reporting of a different management group but with 2 different reporting instance.

Hi Experts,
I have a typical situation in the LAB environment. Hope some one helps. I have Installed a SCOM 2012 R2 with SQL 2012 SP1 in a single server (Management group 1). I have installed another management group on another server using this SQL server for its database
so i have everything going fine.
The first management group has its reporting installed in the SQL server. For the second i created a new named instance for that. But i cannot run the SCOM setup in the SQL server (Also holding the Management group 1 MS) as 1 st reporting is already there.
When i run the setup it is asking me to repair it. I don't get the install option so i can install the reporting for management group 2 in the named instance.
Default instance is being used by the 1st management group.
Can any one figure a possibility for installing 2 SCOM reporting services for different management groups in a same SQL 2012 server please.
Gautam.75801

Hi Yan Li,
Thank you for the reply. So as you are aware If i need to instal reporting, i need to run the SCOM 2012 R2 setup in the SQL server and select reporting and select the
instance and then mention the management server there right. I am not getting that option there it is asking me to remove or repair the existing installation as there is already a SCOM entire setup including reporting there. As it is a lab there is no problem
in testing. I have 2 reporting instances. Any suggestions for me on how to overcome this issue and deploy the second reporting in the new named instance ?
Below is the screenshot of the error what i am talking about when i run SCOM 2012 R2 setup to install reporting in the SQL server
When i click on add feature reporting is greyed out (As already 1st management groups reporting is installed)
When i click on remove or repair it
uninstalls the existing one. But i want both SCOM 2012 r2 reporting to be there(For both Management group). Is it possible ? If yes What is the trick to run the setup ?
Gautam.75801

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 # 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

Errors installing SCOM 2012 Reporting Services

I've run into an issue installing SCOM2012 Reporting Services, that I can't seem to figure out. I installed SQL Server 2008 R2 SP2 SSRS local to the SCOM server using an instance name of SCOM. I created the databases for this on another server (SQL server
2008 R2 SP2) during the SSRS configuration. All from SSRS looks fine, and shows the scale out join, all good. I can browse to the reports page, add folders, all that normal stuff. I added the domain\datareader and datawriter accounts as SSRS admins in the
site security, as well as ensured they are sysadmin in SQL, and local admins on the SQL and SCOM servers. So, all looks good. Until I go to add reporting services to SCOM 2012. It fails to complete, and the log shows:
[12:28:36]: Warn: :Message:SRSPolicySetter SoapException Exception: System.Web.Services.Protocols.SoapException: An error occurred when invoking the authorization extension. ---> Microsoft.ReportingServices.Diagnostics.Utilities.AuthorizationExtensionException:
An error occurred when invoking the authorization extension. ---> System.ServiceModel.FaultException`1[[Microsoft.EnterpriseManagement.Common.UnauthorizedAccessMonitoringException, Microsoft.EnterpriseManagement.OperationsManager.Common, Version=7.0.5000.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: The creator of this fault did not specify a Reason.
at Microsoft.ReportingServices.WebServer.ReportingService2005Impl.GetRoleProperties(String Name, Task[]& Tasks, String& Description)
at Microsoft.ReportingServices.WebServer.ReportingService2005.GetRoleProperties(String Name, Task[]& Tasks, String& Description). Will retry..
I then look in the SSRS logs, and see:
library!ReportServer_0-1!89c!08/12/2013-12:28:34:: Call to GetRolePropertiesAction(Browser).
library!ReportServer_0-1!89c!08/12/2013-12:28:36:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.AuthorizationExtensionException: , Microsoft.ReportingServices.Diagnostics.Utilities.AuthorizationExtensionException: An error occurred when
invoking the authorization extension. ---> System.ServiceModel.FaultException`1[Microsoft.EnterpriseManagement.Common.UnauthorizedAccessMonitoringException]: The creator of this fault did not specify a Reason. (Fault Detail is equal to Microsoft.EnterpriseManagement.Common.UnauthorizedAccessMonitoringException:
The user domain\DataReader does not have sufficient permission to perform the operation.).
So, I'm at a loss. That user is a sysadmin in SQL, has been added to the SSRS security for site and folder with full permissions, has been added to the SSRS databases specifically, and is a local administrator on both the SSRS/SCOM server and the SQL server.
What am I missing here folks? The SSRS is then completely hosed, and no longer works either. So, I have to uninstall and reinstall to even try again. This is getting frustrating.
Please help! :)
Thanks in advance,
mpleaf

After many google searches, and a lot of security changes, I think I found the right now that finally cured the issue. I had to add my datareader account to the Operations Manager Administrators in SCOM User Roles, and then it seemed to go through just fine.
mpleaf

SCOM 2012 RC - SCVMM 2012 RC - Virtual machine manager management group is not getting monitored

Hi All,
I have integrated SCOM 2012 with SCVMM 2012 environment. I could see two strange behaviors. All these instance are running on Windows 2008 R2 + Sp1 OS along with SQL 2008 R2 for database.
1) I could see two instance of VirtualmanagerDB
in the Database State view under the Microsoft SQL Server, out of that
one is showing as monitored and another one is
showing as not monitored. Why it is showing two instance of the same database? How can I remove the not monitored one?
2) In the distributed apps- Virtual machine manager management group is not showing as a monitored item. However the SCVMM server is getting monitored.
I'd appreciate if someone could help me out in understanding and resolving this.
Regards,
Ren.

Hi
I opened up a connect ticket on this on 17th Jan so sorry for not noticing your post earlier. The response was:
Health State dashboard view is targeted to two state views. "Agent Watcher State" and "Agent State". "Agent State" view (view with duplicate entry) is targeted to an abstract class "VMM Agent" which has below child classes.
    VMM Library Agent
    VMM Host Agent
    Guest Agent
For the Dashboard view, we need to taget the view to "Host Agent" not "VMM Agent". When we install VMM, it adds itself as a Library server and that is the reason for duplicate entry (VMM Library Agent).
Cheers
Graham
Regards Graham New System Center 2012 Blog! -
http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/

Which type of SQL DB do I need for SCOM 2012?

Hello everyone,
We would like to install a SCOM 2012 Server for reporting and alerting of our Exchange and Lync Server.
Our guys from database management asks me, what type of SQL DB do I need. "An SQL DB with 100GB" shouldn't be enough :-( I'm not very familiar with SQL.
So, which informations could be missing?
Thanks in advance and best regards
Daniel
Beste Grüße

Daniel,
usually Standard Edition is enough and included in the SCOM (agent) license.
Here you find more about requirements:
https://technet.microsoft.com/en-us/library/dn249696.aspx
SQL specific:
Check for updates and hotfixes for Microsoft SQL Server. See
SQL Server in System Center 2012 R2.
Operations Manager does not support hosting its databases or SQL Server Reporting Services on a 32-bit edition of SQL Server.
Using a different version of SQL Server for different Operations Manager features is not supported. The same version should be used for all features.
For SQL Server collation settings, see
SQL Server in System Center 2012 R2
The SQL Server Agent service must be started, and the startup type must be set to automatic.
The db_owner role for the operational database must be a domain account. If you set the SQL Server Authentication to Mixed mode, and then try to add a local SQL Server login on the operational database, the Data Access service will not be able to start.
For information about how to resolve the issue, see
System Center Data Access Service Start Up Failure Due to SQL Configuration Change
If you plan to use the Network Monitoring features of System Center 2012 R2 Operations Manager, you should move the tempdb database to a separate disk that has multiple spindles. For more information, see
tempdb Database.
You should have a look at the sizing calculator:
http://download.microsoft.com/download/C/A/6/CA60425C-950B-456E-986C-C5F2FCD5668D/System%20Center%202012%20Operations%20Manager%20Sizing%20Helper%20Tool%20v1.xls
Good luck,
Patrick
Please remember to click “Mark as Answer” on the post that helped you.
Patrick Seidl (System Center and Private Cloud)
Website: http://www.syliance.com
Blog: http://www.systemcenterrocks.com

Monitor Dell Powerconnect Switches/Routers using SCOM 2012

Hello,
We are trying to find a way to monitor approximately 20-25 Dell Powerconnect switches/routers (models 5324,5424,5448,5548,6224,6024) through SCOM 2012.
Using SCOM network discovery we are able to get all Dell Powerconnect switches listed, but we are unable to get a network node dashboard, nor vicinity view 1 or 2 hops further. We are able to only see connected network printers and some serial/ethernet devices
we have.
In addition, SCOM 2012 seems to be able to recognize the model of only Dell Powerconnect 5224 switches. We have found that on the SCOM management server the "C:\Program Files\System Center 2012\Operations Manager\Server\NetworkMonitoring\conf\discovery\oid2type_Dell.conf"
only lists Dell Powerconnect 5224 switches as well as several models from the 3000 series.
We have contacted Dell PRO support, but their reply was that there is no management pack for SCOM available for their networking devices.
Would it be recommended to use http://xsnmp.codeplex.com/ on SCOM 2012 to monitor those switches and get a network digram view or are there any plans to include those MIBs in a future CU or SP of SCOM 2012?

Hi Alex
Network monitoring has changed from SCOM 2007 R2 to SCOM 2012 so this statement
"but if this works for SCOM 2007, it should apply to SCOM 2012"
is not accurate when it comes to network monitoring:
http://blogs.technet.com/b/momteam/archive/2011/10/24/migrating-operations-manager-2007-network-monitoring.aspx
Would it be recommended to use http://xsnmp.codeplex.com/ on SCOM 2012?
The codeplex solutions for SCOM 2007 R2 will not work on a new \ clean install of SCOM 2012 (if you upgrade from SCOM 2007 R2 they continue to work as legacy devices but you can't add more monitoring).
SCOM 2012 seems to be able to recognize the model of only Dell Powerconnect 5224 switches
What do you mean by recoginse? SCOM can discover network devices but there is an "approved" list that allows for extended monitoring:
http://www.microsoft.com/en-us/download/details.aspx?id=26831
You should still be able to discover and monitor other devices though:
http://blogs.technet.com/b/momteam/archive/2011/09/20/what-gets-monitored-with-system-center-operations-manager-2012-network-monitoring.aspx
Cheers
Graham
Regards Graham New System Center 2012 Blog! -
http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/

SNMP traps from EMC SRM to SCOM 2012 R2

Hi,
I'm trying to configure SCOM 2012 R2 as an SNMP trap listner. I've seen many articles on setting this up but all are based around SNMP traps from network devices which must first be discovered and identified in the network device list.
However in my scenario I am trying to monitor/listen for traps send by a Linux box hosting EMC SRM - this management software can be configured to send SNMP traps out so it is these that I need to try and listen for/capture.
So can anyone explain how I can configure SCOM 2012 R2 to do this. I have tried to just used the IP of the Linux box and discover it as a network device but it fails - in Network Devices Pending Mgmt it says No response Ping, even though I can
ping the box from the Server OK - so I am guessing you cant cheat scom in discovering the Linux box as a network device in ths way?
Can anyone offer any advice for setting this up. Just to add I've ensured the RunAs Community String (public) and SNMP version is correct on both side...
Cheers...

Once the Network Device (Linux server in this case) is discovered you will still need a rule that targets that class and accepts incoming SNMP Traps for that OID, or All OIDs if you prefer. I found 2 links that may be of help, the first is just a basic
overview of the SNMP listener in SCOM 2012 as it has changed from the OS Listener in 2007 to a dedicated one.
http://systemcentertech.com/2012/05/17/scom-2012-built-in-snmp-trap-listener/
The second link covers SNMP setup, but starting at Step 7 there is a great how-to on creating your own SNMP rule which will be needed to collect your traps.
http://scom-2012.blogspot.com/2012/07/setting-up-snmp-monitoring-in-scom-2012.html
www.Practice2Perfect.com

SCOM 2012 r2 - Add GW Sitename on a later stage

Similar Messages

Maybe you are looking for