OpsMgrLatencyMonitors

[PN]

Hello!

In the documentation for the current release (6.0.7065.0) of the "Active
Directory Management Pack" on page 36-37 under "Container Creation" it is
mentioned that you should connect to the naming context "Configuration" and
here add the "OpsMgrLatencyMonitors"-container. It is also stated that a
script attempts to create the container if possible.

If the Healthservice of the domaincontrollers runs as the local system
account, this container is created automatically, presumably by the above
mentioned script, however it is NOT created in the mentioned naming context.
Instead it is created in the following THREE places:

DC=domain,DC=com,CN=OpsMgrLatencyMonitors
DC=DomainDnsZones,DC=domain,DC=com,CN=OpsMgrLatencyMonitors
DC=ForestDnsZones,DC=domain,DC=com,CN=OpsMgrLatencyMonitors

The first container is populated with all domaincontrollers, the second and
the third with dns-servers.

Even if the container does not exist in the "Configuration" naming context,
no events in the DC´s OpsMgr-eventlog have surfaced regarding this. In my
specific case I only got a couple of warnings as the exemplifed below:

------------------------------------------
Event ID 1000
AD Replication Monitoring : encountered a runtime error.
Failed to write the adminDescription attribute of
'CN=computer,CN=OpsMgrLatencyMonitors,DC=domain,DC=com' to Active Directory.
The error returned was: 'The object already exists.' (0x80071392)
Check the access permissions for this object.
----------------------------------------------------

This event was also forwarded as an alert to SCOM, but this indicate only,
as I see it, that everything is working as excpected, only that the script
trying to create the object was run more than one time.

Questions:

1. Should really the "OpsMgrLatencyMonitors"-container be created in naming
context "Configuration" considering the above observations?

2. How can one be sure that replication monitoring is working (not to be
confused with replication performance collection)?

Sincerely
Peter

[Suschi]

I have little different problems regarding to OpsMgrLatencyMonitors

########### LOG ############
Log Name: Operations Manager
Source: Health Service Script
Date: 08.04.2010 10:06:30
Event ID: 67
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: dc02.blabla.blubb.com
Description:
AD Replication Monitoring : encountered a permissions error.
The script failed to create the OpsMgrLatencyMonitors container in the
naming context 'DC=DomainDnsZones,DC=blabla,DC=blubb,DC=com' because access
was denied. Alter the permissions for this naming context so that the script
can add this container, or change the parameters for this script to stop
monitoring this naming context.

The error returned was: 'General access denied error
' (0x80070005)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Health Service Script" />
<EventID Qualifiers="0">67</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-04-08T08:06:30.000Z" />
<EventRecordID>400093</EventRecordID>
<Channel>Operations Manager</Channel>
<Computer>dc02.blabla.blubb.com</Computer>
<Security />
</System>
<EventData>
<Data>AD Replication Monitoring</Data>
<Data>encountered a permissions error.
The script failed to create the OpsMgrLatencyMonitors container in the
naming context 'DC=DomainDnsZones,DC=blabla,DC=blubb,DC=com' because access
was denied. Alter the permissions for this naming context so that the script
can add this container, or change the parameters for this script to stop
monitoring this naming context.

The error returned was: 'General access denied error
' (0x80070005)</Data>
</EventData>
</Event>

########### END LOG ##########

I found some information using an workaround
WORKAROUND
Open Active Directory Users & Computers (DSA.msc).
Click on view and select Advanced Features.
Click on MOMLatencyMonitors container and click on properties (you should
see your DC's in this container).
Click on security tab and add MOM ACTION account and give it Full Control.
Restart the MOM service

But i didnt have any Container named MOMLatencyMonitors !!!!!!

We are using SCOM 2007 R2 in a mixed 2003/2008 DC environment.
The agents are running under local system account

Any ideas?

Regards Suschi

[USBomSquad]

I was having a similar issue today. It turns out that I had not configured
the ADMP Run As account properly.

Check out http://technet.microsoft.com/en-us/library/dd262059.aspx for
information on how to properly configure the ADMP Run As account.

[PN]

Found an explanation here:

http://social.technet.microsoft.com/Forums/en-US/operationsmanagermgmtpacks/thread/2a0e5a2b-a3d9-42d4-8474-9f690007caa0

/Peter