Share
ReportWe have multiple AOS's and we are getting failed login attempts to SQL Server from each of them at 20 minute intervals. Because we have the LOCAL/SYSTEM account as the service account for the Microsoft Monitoring Agent, the authentication attempt is coming thru as the Computer Account..i.e. DOM/AOSSERVER1$, DOM/AOSSERVER2$, DOM/AOSSERVER3$, etc...
We set the value of this configuration correctly: "01@AOSSERVER1"
select [VALUE] from SysGlobalConfiguration where name = 'SCOMPERFORMANCEAOS'
We assigned the DOM/AOSSERVER1$ account as datawriter on the AX DB. We traced the connection and no SQL errors from that user.
we fixed a couple of powershell bugs in the Microsoft.Dynamics.AX.ManagementPackSupport.ps1 so no event log errors in the AOSSERVER1 SCOM event log.
We restarted all the AOS's.
But still we have login attempts being made from the other AOS's. I thought that if the Connection succeeded from the AOS designated in SCOMPERFORMANCEAOS config (AOSSERVER1)...that it would not try to run performance collection from the other AOSes....2,3,4,..
Would really like to know the specific trigger that makes the other AOS's not specified as the SCOMPERFORMANCEAOS, attempt to connect.
*This post is locked for comments
I have the same question (0)
All responses (
Answers (
16
