Welcome to Community Answers

Peter Commander

Stats

  • 5 reputation
  • 0 answers, 0 selected
  • 1 questions, 0 solved
  • Member for 1 years, 4 months, 7 days
  • 575 profile views
  • Last seen 12 Jul, 2018

Reputation

Total 5
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
+1
12 Jul, 2018 Commented Updates: Microsoft Premier has now been engaged. I worked with one of the DC's particularly that was not updating the AD object record. After removing dual-home, resetting the Agent, and even deleting the AD object under OpsMgrLatencyMonitors, problem still persisted. The object was never recreated by the agent, as described should be the case. As a (next-to) last resort, I removed the agent and all remnants in SCOM to this agent, and of SCOM on the DC. Rebooted the DC, waited 24 hours, and rediscovered the agent. After about 45 minutes, the AD object was recreated, and alerts stopped for this agent. Problem solved. As the last, last resort, I engaged MS to address this issue on the remaining DC's, and to figure out what happened / root cause, as well as to address some other issues with PS scripts failing. They (MS) also pointed me to the jimmy harper blog (above) about these scripts... and found a Holman blog entry that said that ANY override must be the same across ALL of the monitors for it to be effective: https://social.technet.microsoft.com/Forums/systemcenter/en-US/2a0e5a2b-a3d9-42d4-8474-9f690007caa0/opsmgrlatency-cn-gets-auto-created-in-domain-not-configuration?forum=operationsmanagermgmtpacks (This was written in 2010 - I haven't checked the guide to see if it has been fixed). These 14 monitors have now been uniformly altered with a max expected latency of 60 (minutes), and a frequency of 1800 (seconds); and three of the noisiest and duplicate PS scripts have been disabled. We now have significantly less noise, but the original symptom is still there. Now Giving it 24 hours to churn, and will re-address tomorrow. Trying to avoid total - nuke of the agents (as was done on DC #1), hoping to find and understand the actual issue behind the alerts. Will report how it goes, and what MS says may be the underlying issue.
+1
18 May, 2017 registration

Votes

0 votes received 0/100 0up 0down
0 votes casted 0/100 0up 0down

Top Answers

No answer posted yet!

New questions