Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

MomADAdmin Not Run Error Message in SCOM 2007

Posted on 2012-03-29
14
Medium Priority
?
1,485 Views
Last Modified: 2012-05-18
I'm getting the following error message in SCOM 2007:  "OperationsManager container doesnt exist in domain SEDintl.net or the Run As Account associated with the AD based agent assignment rule does not have access to the container. Please run MomADAdmin before configuring agent assignment rules and make sure the associated Run As Account is the member of the Operations Manager Administrator role.".
0
Comment
Question by:edadmin
  • 6
  • 4
10 Comments
 
LVL 14

Expert Comment

by:alimu
ID: 37785706
sorry to start with the obvious but it's somewhere to begin..
did you run MomADAdmin as per the AD management pack installation instructions when
you installed it?
0
 

Author Comment

by:edadmin
ID: 37789667
Application has been installed on server for a couple of years now. Message just started appearing.
0
 
LVL 14

Expert Comment

by:alimu
ID: 37790712
ok, and I take it you've checked AD to make sure the OperationsManager container exists still and no over enthusiastic cleanup script or person has removed it on you?

Is the AD based agent assignment rule runas account setup with the account you expect to be there? Have you checked that it isn't locked out and still has permissions to the OperationsManager container?

(if in addition to the above you have done any other troubleshooting already please list so we can skip that)
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Author Comment

by:edadmin
ID: 37803027
There is an OpsMgrLatencyMonitors container in AD but no OperationsManager container. Also the two subscriptions I have setup keep reverting back to "False" as a result I'm not getting any email alerts.
0
 
LVL 14

Accepted Solution

by:
alimu earned 2000 total points
ID: 37804296
Hi edadmin, the OpsMgrLatencyMonitors container is used for monitoring replication, the other one is for agent based assignment.  
You will need to run the tool to get the container created.  You probably have it already but the full agent assignment install for scom 2007 sp1 or r2 can be found here to step you through: http://technet.microsoft.com/en-us/library/cc950514.aspx
There's also a SCOM team blog here that walks you through what happens when you run this tool: http://blogs.technet.com/b/momteam/archive/2008/01/02/understanding-how-active-directory-integration-feature-works-in-opsmgr-2007.aspx

I hope this helps!
0
 
LVL 14

Expert Comment

by:alimu
ID: 37835890
Hi edadmin, could you post an update? Have you tried running the tool and creating the container?
0
 

Author Comment

by:edadmin
ID: 37922833
I've requested that this question be deleted for the following reason:

None of the solutions resolved issue.
0
 
LVL 14

Expert Comment

by:alimu
ID: 37922834
these containers are created by running the MOMADAdmin.exe tool as indicated above.  The asker did not provide any feedback saying whether this tool had been run already or what errors were encountered when the tool was run.
0
 
LVL 14

Expert Comment

by:alimu
ID: 37927105
Recommendation: 4)
Without feedback from the asker indicating the outcome of following these instructions, running the momadadmin.exe tool using the instructions included in the articles referred to in comment #37804296 and with an account that has access to create AD containers should have resolved this issue by creating the missing containers.
0
 

Author Comment

by:edadmin
ID: 37958151
I've requested that this question be deleted for the following reason:

Resolved issue by reinstalling SCOM.
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
By default the complete memory dump option is disabled in windows . If we want to enable the complete memory dump for a diagnostic purpose, we have a solution for it. here we are using the registry method to enable this.
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …
This Micro Tutorial will give you basic overview of the control panel section on Windows 7. It will depth in Network and Internet, Hardware and Sound, etc. This will be demonstrated using Windows 7 operating system.

824 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question