I’m doing some manual installation of agents in un-trusted domains and this includes domain controllers. I just found that once I did this, I’d get inundated with errors from agents on domain controllers (first time I’ve installed on un-trusted DC’s):
- AD Replication Monitoring : encountered a runtime error. Failed to create the ‘McActiveDir.ActiveDirectory’ object. The error returned was: ‘ActiveX component can’t create object’ (0x1AD)
- AD Lost And Found Object Count : The script ‘AD Lost And Found Object Count’ failed to create object ‘McActiveDir.ActiveDirectory’. This is an unexpected error. The error returned was ‘ActiveX component can’t create object’ (0x1AD)
- AD Database and Log : The script ‘AD Database and Log’ failed to create object ‘McActiveDir.ActiveDirectory’. The error returned was: ‘ActiveX component can’t create object’ (0x1AD)
Very annoying, you’ll agree. I was beginning to wonder if I needed to run the agent with some sort of elevated rights. In this scenario, you should first run OOMADS.MSI from the support tools folder on the SCOM 2007 installation media. Only then should you install the agent. If you made the mistake I did, you can install the tool and then restart the OpsMgr Health Service. That’ll sort you out.
None of this is required for an agent deployed to a DC from the OpsMgr Console it’s done automatically for you. And it’s not required at all for non-DC’s.
OOMADS.MSI creates the objects that are required to monitor AD for you. This will save you a lot of mucking around with ADSI editing which I never recommend to anyone not familiar with AD.
EDIT:
I’ve recently found another issue where there is an event in the Operations Manager log saying that the helper object cannot be found. This happens soon after the agent starts. The operations manager agent is search for OOMADS.MSI in %ProgramFiles%System Center Operations Manager 2007HelperObjects and it’s not there. The solution is to copy the file into there. I noticed that you need to do this again if you upgrade the agent to SP1. Restart the agent and the error doesn’t reoccur.