SCOM 2012: Agent Proxy not enabled.

I am seeing Critical Severity alerts on my SCOM 2012 Server stating:
"The agent was not able to submit data on behalf of another computer because agent proxy is not enabled. Details:Health service ( 0C43A2D6-628F-D150-9553-8EABFECA600C ) should not generate data about this managed object ( 716D31EF-F34C-A4E3-1A16-3B8B75E85C0D
I have about 8 servers with this error. All of which have had Proxy turned on in SCOM ( Administration -> Agent Managed -> <agents in question> -> Properties -> Security Tab -> Checked "Allow this agent to act as a proxy...".
All of these servers are on the same domain as the SCOM server (we only have 1 domain).
Thanks,

For what it's worth I'm experiencing this issue. I've closed out the alerts and watched them pop back up later.
The agent was not able to submit data on behalf of another
computer because agent proxy is not enabled. Details:Health service (
774FAEE6-003E-7CAC-FC02-676C0D9F675E ) should not generate data about this
managed object ( 13354EE4-F0F9-DF55-88F0-271F30A70AAB ).
PS C:\> Get-SCOMAgent |Where-Object -Property id -eq '13354EE4-F0F9-DF55-88F0-271F30A70AAB'
PS C:\> Get-SCOMAgent |Where-Object -Property id -eq '774FAEE6-003E-7CAC-FC02-676C0D9F675E'
PS C:\>
This alert was generated about an hour ago, I have 160 agents installed.
My guess is...well I don't have a good guess. any help about this would really be appreciated.
Jeffrey S. Patton Jeffrey S. Patton Systems Specialist, Enterprise Systems University of Kansas 1001 Sunnyside Ave. Lawrence, KS. 66045 (785) 864-0242 | http://patton-tech.com

Similar Messages

Agent proxy not enabled

The agent was not able to submit data on behalf of another computer because agent proxy is not enabled. Details:Health service ( OM.test.local ) should not generate data about this managed object ( Microsoft.SQLServer.2012.ReportingServices.DeploymentSeed

You can modify a hidden config setting via powershell and never have to worry about this again. Most agents need proxy enabled, so imho I would just config this to be auto enabled on all agents going forward with scom posh:
set-defaultsetting '-name HealthServiceProxyingEnabled ' -value True
Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/ If my response was helpful, please mark it as so, if it answered your question, then please also mark it accordingly. Thank you.

SCOM 2012 Agent - Best Practices with Base Images

I've read through the
SCOM 2012 agent installation methods technet article, as well as how to
install the SCOM 2012 agent via command line, but don't see any best practices in regards to how to include the SCOM 2012 agent in a base workstation image. My understanding is that the SCOM agent's unique identifier is created at the time of client installation,
is this correct? I need to ensure that this is a supported configuration before I can recommend it.
If it is supported, and it does work the way I think it does, I'm trying to find out a way to strip out the unique information so that a new client GUID will be created after the machine is sysprepped, similar to how the SCCM client should be stripped of
unique data when preparing a base image.
Has anyone successfully included a SCOM 2012 (or 2007 for that matter) agent in their base image?
Thanks,
Joe

Hi
It is fine to build the agent into a base image but you then need to have a way to assign the agent to a management group. SCOM does this via AD Integration:
http://technet.microsoft.com/en-us/library/cc950514.aspx
http://blogs.msdn.com/b/steverac/archive/2008/03/20/opsmgr-ad-integration-how-it-works.aspx
http://blogs.technet.com/b/jonathanalmquist/archive/2010/06/14/ad-integration-considerations.aspx
http://thoughtsonopsmgr.blogspot.co.uk/2010/07/active-directory-ad-integration-when-to.html
http://technet.microsoft.com/en-us/library/hh212922.aspx
http://blogs.technet.com/b/momteam/archive/2008/01/02/understanding-how-active-directory-integration-feature-works-in-opsmgr-2007.aspx
You have to be careful in environments with multiple forests if no trust exists.
http://blogs.technet.com/b/smsandmom/archive/2008/05/21/opsmgr-2007-how-to-enable-ad-integration-for-an-untrusted-domain.aspx
http://rburri.wordpress.com/2008/12/03/untrusted-ad-integration-suppress-misleading-runas-alerts/
You might also want to consider group policy or SCCM as methods for installing agents.
Cheers
Graham
Regards Graham New System Center 2012 Blog! -
http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/

Does the SCOM 2012 agent "look back" in the logs before the service was started?

Does the SCOM 2012 agent "look back" in the logs before the service was started?<o:p></o:p>
We raised this question to our Microsoft rep back when we migrated to SCOM 2007. We wanted to know if SCOM would alert on errors generated before the Heath Service started. For example, errors
logged before the service is started on reboot (which is when some critical errors are logged). We also wondered what happens when the service is restarted...would errors during the same window be missed?
If I remember correctly the MS response was that the agent looks back on startup/restart based on a timestamp of some kind. We did some testing that seemed to confirm this information. I've
recently encountered several instances of errors generated while the service was stopped (primarily during boot up) where SCOM failed to alert on the error.
Can anyone confirm how the SCOM 2012 agent deals with errors generated before the service starts on boot and during service restarts?

I would suspect it's with watermarks as it has been in the past. What you should look into is if these alerts you were expecting are event based, and if there are rules set to alert for these conditions. If so, and you don't get an alert,
then you can bring that up with your msft rep. However, they should be caught.
Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/ If my response was helpful, please mark it as so, if it answered your question, then please also mark it accordingly. Thank you.
There is a watermark. If the agent has been down for a significant period of time, the watermark may not apply, as the log would have rolled - but the entire log will still be processed regardless of what has already been discarded in the log. This may cause
some problems if a monitor picks up an unhealthy state, and the healthy state log entry has already been flushed. In this case, you need to reset health on that particular monitor, or just flush the cache on the agent to start anew.
Jonathan Almquist | SCOMskills, LLC (http://scomskills.com)

Scom 2007 and scom 2012 agent multi home

is there version limit for the agent multihom for scom 2007 and scom 2012?
In technet i found it for SCOM upgrade it mentioned need scom 2007 CU4 and above, how about for multihome approach for SCOM agent?
Besides that, instead of agent upgrade, could we perform agent uninstallation scom 2007 and reinstall scom 2012?
Thanks for your advice.

Hi Cylim,
You can upgrade your agents to SCOM 2012 only from SCOM 2007 R2 CU4. Please look at these helpful links:
http://blogs.technet.com/b/kevinholman/archive/2014/01/20/do-i-need-a-specific-cumulative-update-release-ur-in-order-to-upgrade-to-scom-2012-or-2012-sp1-or-2012-r2.aspx
http://blogs.catapultsystems.com/cfuller/archive/2012/05/31/quicktricks-multi-homing-an-agent-to-opsmgr-2012-scom-sysctr.aspx
http://blogs.catapultsystems.com/cfuller/archive/2014/04/02/multihomed-migrations-in-operations-manager-lessons-from-the-field.aspx
As Scott mentioned, you can uninstall SCOM 2007 agent and install SCOM 2012 agent on one or a few servers, and see if they report properly to both management groups SCOM 2007 and SCOM 2012:
http://dynamicdatacenter.wordpress.com/2012/10/15/om-2012-agent-report-to-scom-2007-not-r2-scom-2012/
Natalya

The debugger agent is not enabled on server....

We have to weblogic instances and IDM is deployed in both these instances.
When I am trying to start the debugger on server1 I do get this error:
+'The debugger agent is not enable on server2: To enable, please set the SystemConfiguration property serversettings.server2(or default).debugger.enabled=true and restart your application server.+
I have checked and modifed the sys.config object in both the instances and restarted the server instances on both but still the error persisted.
Am I missing anything here?
Thanks.

1) Launch BPE
2) Go to File | Open Repository Object
3) Double-click Generic Objects icon to expand it.
4) Double-click System Configuration
5) Expand serverSettings icon
Click on default
6) Highlight debugger
7) Click on checkbox to select it for the enabled attribute.
8) Save your change by going to File | Save in Repository.
9) Restart your web container.

Deploying SCOM 2012 Agents to untrusted Forests/Domain

Can we deploy SCOM 2012 agents to untrusted forest/domain? I don't want to use SCCM 2012 for installing agents via package deployment. Pls suggest.
Regards,
Ravi

Yes, You can deploy SCOM Agent to untrusted domain manually and using Certificate.
For deployment scom Agent, you can refer below links
http://www.toolzz.com/?p=279
http://jimmoldenhauer.blogspot.com/2012/11/scom-2012-deploying-agents-to-untrusted.html
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

SCOM 2012 Agent Deployment query

Hello,
I have tried to deploy the agent remotely to a Windows Storage Server Standard - SP1 server but it failed,
I have checked the compatible OS list and it makes reference to Server 2008 SP2 but not Storage Server.
If I upgrade to SP2 will the agent install on the OS or will it fail anyway.
THanks
Nick

Hello,
I have tried to deploy the agent remotely to a Windows Storage Server Standard - SP1 server but it failed,
I have checked the compatible OS list and it makes reference to Server 2008 SP2 but not Storage Server.
If I upgrade to SP2 will the agent install on the OS or will it fail anyway.
THanks
Nick
I had raised a ticket with Microsoft as this was quite unclear no matter where we looked.
This was their response,
I can confirm SCOM 2012 SP1 agent can be installed on the server “Windows Storage Server Standard –
SP2” as per the below technet link.
http://technet.microsoft.com/en-us/library/jj656654.aspx#BKMK_RBF_WindowsAgents
Operating Systems: Windows Server 2003 SP2,
Windows Server 2008 SP2, Windows Server 2008 R2, Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server 2012 R2, Windows XP Professional x64 Edition SP2, Windows XP Professional SP3, Windows Vista SP2, Windows
7, POSReady, Windows XP Embedded Standard, Windows XP Embedded Enterprise, Windows XP Embedded POSReady, Windows 7 Professional for Embedded Systems, Windows 7 Ultimate for Embedded Systems, Windows 8 Pro, Windows 8 Enterprise, Windows 8.1 Pro, or Windows
Embedded 8.1 Industry.
Hope this answers your question. Kindly let me know if you have any queries regarding this case further if not I will proceed with the case closure.

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

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

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

Issues with SCOM 2012 Agent on Red Hat 5 Server

We are running SCOM 2012 server and have deployed the agent successfully to a number of Red Hat Linux servers. I am having an issue on about a quarter of the hosts, in that they appear as HEALTHY but are Grayed out and not green. When I look at the /var/opt/microsoft/scx/log/omiserver.log
file I see:
WARNING: wsman: authentication failed for user scom2012
I have verified that the system account is setup with the correct password and the runas account is setup with the correct password (i am able to deploy the agent from the SCOM server using it, so the passwords DO match).
Any ideas?

We are running SCOM 2012 server and have deployed the agent successfully to a number of Red Hat Linux servers. I am having an issue on about a quarter of the hosts, in that they appear as HEALTHY but are Grayed out and not green. When I look at the /var/opt/microsoft/scx/log/omiserver.log
file I see:
WARNING: wsman: authentication failed for user scom2012
I have verified that the system account is setup with the correct password and the runas account is setup with the correct password (i am able to deploy the agent from the SCOM server using it, so the passwords DO match).
Any ideas?
I've seen this on a few systems here when the agent has been upgraded but the old agent process does not die off. Just to rule it out, pick a node, make sure there are no instances of scxcimserver or scxcimprovagt and then start the agent and
see if the issue goes away. I've also seen wsman authentication failures related to the libssl issue that was fixed in yesterday's release.

SCOM 2012 Installation does not show the SQL Server Instance for reporting services

I have an issue when I try to install SCOM 2012 with the Reporting Server feature, so in the step that I have to select a SQL Server Instance I cannot do that, because as you can see in the picture no one option appears.
In my scenario I have a DCSERVER, SQLSERVER2008 R2, SCCMSERVER 2012 and in other server I are trying to install SCOM 2012. I are trying to use the same SQLSERVER to SCOM 2012.
Should I do other procedure on SQL Server before to continue? I will apreciate someone could say me what I need to do to resolve this issue.
Regards,
Paul Mendoza.

Hi Paul
Can you confirm that SQL Reporting Services is installed on the server that you are doing the install.
For a lab environment where you have SCOM Management Server, Web Server on one server and SQL Server on another you need to:
- run setup on the SCOM Server and choose NOT to install reporting. The install here will create the OperationsManager database and OperationsManagerDW (reporting) database.
- run setup on the SQL Server where SQL Reporting Services is installed. Then choose to install reporting. You should then see the SQL Reporting Services instance on the above window which is blank in your screenshot.
Take note of the warning in that window - SCOM uses its own role based security within SQL Reporting Services and this can break other reporting. E.g. you can't install SCOM and SCSM reporting (SQL RS component) together.
Cheers
Graham
New SCOM 2012 Blog! - http://www.systemcentersolutions.com/blog/
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/

SCOM 2012 R2 - Tasks not running and Discovery never finishes

Hi all,
I'm having some really weird issues with a new SCOM 2012R2 install. The issue I first noticed was none of the tasks on the right hand side of the SCOM console that run on a monitored server will complete. The window opens and will just have the spinning
green "I'm doing something" circle.
Example: If I run the task list processors on the management server it just sits there like it is running but never returning the result.
Frustrated, I rebuilt the management server and deleted the DB's. And same issue.
Since these tasks are added with the MP's I tired an older Windows Server Operating System MP just to see if the latest one had issues. Unfortunately I still have the same issue and its driving me crazy
Second issue is the Discovery Wizard is also just sitting there when using the advance option to specify the server I want to push the agent too.
I have tried specifying a domain admin account for both the task and the discovery
Checked the SPN's for the management server and SDK account have been registered.
I have checked the SQL broker is enabled and SQL services are using domain accounts
This is the setup:
SCOM 2012R2 running on VMware Virtual Machine with Server 2012R2
SQL Server 2012 SP1 with the Ops DB on one server and the DW on another
Accounts:
OM_MSAA - Domain Admin... Hopefully gets resolved in the future
OM_DAS - Local Admin on the MS
OM_DRA - Local Admin on the SQL Servers
OM_DWWA - Local Admin on MS and SQL Servers
This is an SOS as I have been given a very short deadline and these are the last issues I needed.
I did install a DEV environment running SCOM 2012R2 but on Server 2012 NON R2 and it works with any of the issues mentioned above.
Thanks Mike

Thanks for the reply Stefan.
The issue was with all Tasks. It was running against the Server 2012R2 management server so i guess it was the Windows Server 2012R2 Monitoring MP.
I have found the issue. The OM_DAS "SDK Account" needed the SQL service account to have read permissions.
On the Opsman DB server i was getting these errors:
An exception occurred while enqueueing a message in the target queue. Error: 15404, State: 19. Could not obtain information about Windows NT group/user 'domain\OmSDK', error code 0x5.
This article explains the fix: http://blogs.technet.com/b/lukaszr/archive/2012/10/24/discovery-never-stops-but-tried-everything.aspx
Thanks again for replying
Mike

SCOM 2012 reports do not show object or server name

When running any performance reports (I have tested OS, SQL, and generic reports) the object is not listed in the report and the only why to tell which object the counter is from is to drill open the Instance. However, this does not work on scheduled and
delivered reports.
Has anyone noticed this or am I crazy? If so, how did you get around it? I was thinking if I can get the RDL for the report I can create my own with the object name.
Thanks,
John

CU4 for SP1 is out http://support.microsoft.com/kb/2879276
I haven't seen any reports from anyone who has actually installed it to see whether it introduces any problems or whether the fixes work in a real-world environment.
the notes include:
"Issue 5
By default, when a generic performance report is exported, the object information (such as server name, disk label, and so on) is collapsed, and the information is missing."
So it looks like the fix is in.

SCOM 2012 Powershell command to remove agent

Hello,
Has anyone had any luck removing agents via Powershell to mimic the delete agent from the console?
Blogs don't turn up anything useful for this task.
The 2012 Powershell covers how to approve agents, add proxy flag, and uninstall agent, but nothing to remove. Used the SQL stored procedure previously in 2007R2 (and same procedure exists in 2012 SP1.
Anyone aware of Powershell automate agent removal?
Thanks!
SCOM Power Shell to add SCOM 2012 agent
Get-SCOMPendingManagement | where {$_.AgentName -eq "ServernameFQDN"} | Approve-SCOMPendingManagement
Enable Proxy on newly added agent
Get-ScomAgent | where-object {$_.DisplayName -like "okcnmo*"} | where-object {$_.ProxyingEnabled.Value -eq $False} | Enable-SCOMAgentProxy
SQL Query to remove
http://social.technet.microsoft.com/Forums/en-US/operationsmanagergeneral/thread/e413c030-509b-45e4-bcd4-b4ae1a649c73
Uninstall Agent
http://technet.microsoft.com/library/hh545186.aspx
Remove Unix agents
http://social.technet.microsoft.com/Forums/en-US/operationsmanagerunixandlinux/thread/081f2801-7dfa-4db9-8c78-6adbc487a031/

We actually have used the stored procedure for 2007 and 2012
OperationsManager.dbo.p_TypedManagedEntityDelete
If you want to use Invoke-Sqlcmd to run the query.
Another way from SQL which can be put in PowerShell
--Grab GUID for that health service
select * from BaseManagedEntity
where FullName like '%<servername>%'
and IsDeleted = 1
Look for FullName with Microsoft.SystemCenter.HealthService:servername
-- Use this to test the entity delete for the healthservice GUID
DECLARE @EntityId uniqueidentifier;
DECLARE @TimeGenerated datetime;
-- change "GUID" to the ID of the invalid entity
SET @EntityId = '<GUID here>';
SET @TimeGenerated = getutcdate();
BEGIN TRANSACTION
EXEC dbo.p_TypedManagedEntityDelete @EntityId, @TimeGenerated;
COMMIT TRANSACTION
--Check what is in deleted
select * from BaseManagedEntity
where IsDeleted = 1

Some of the SQL Server 2012 are not getting monitored in SCOM 2012 SP1.( basics monitoring is happening, expect SQL role)

Found that all the SQL servers are getting monitored, expect few servers which are having SQL server 2012 role.
proxy is enabled for these servers, when I checked discovered inventory for SQL 2012 database unable to find these servers in that list.
and other servers having SQL Server 2012 monitoring properly issue is with only few servers.

Hi,
thanks for the all the input, we are using service account as windows account instead of action account !!
will that also affect discovery of SQL role?
and also found that there are many alerts in SCOM console, with alert description :
SQL Server cannot authenticate using Kerberos because the Service Principal Name
(SPN) is missing, misplaced, or duplicated.
please let me know how we can resolve this issue, will it affect SQL discovery as well ?

SCOM 2012: Agent Proxy not enabled.

Similar Messages

Maybe you are looking for