edadmin
asked on
MomADAdmin Not Run Error Message in SCOM 2007
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.".
ASKER
Application has been installed on server for a couple of years now. Message just started appearing.
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)
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)
ASKER
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi edadmin, could you post an update? Have you tried running the tool and creating the container?
ASKER
I've requested that this question be deleted for the following reason:
None of the solutions resolved issue.
None of the solutions resolved issue.
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.
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.
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.
ASKER
I've requested that this question be deleted for the following reason:
Resolved issue by reinstalling SCOM.
Resolved issue by reinstalling SCOM.
did you run MomADAdmin as per the AD management pack installation instructions when
you installed it?