Service Account Not recognised During MP Instal

Just an uodate on this issue for those still interested.

 

 

The workaround that we used was to temporarily add the SCOM Administrator account into the Domain Admins group just long enough to allow me to install the F5 Management Pack.

 

 

I was able to install the MP to the RMS server without issue and could see all the F5 folder objects in the Monitoring view after the install completed.

 

 

I then repeated the install on the Managament Server that will be designated to monitor the F5 devices.

 

 

The first attempt to install to the Management Server failed as I had not added the F5 Management Pack service account to the Local Admins group on the Management Server.

 

 

After this was done setup Setup seemed to go OK but then just before finishing an error message popped-up similar to the one that Nick and Julian have been dealing with in a separate thread relating to:

 

 

"The DataSource and ConditionDetection modules required for the F5 Monitoring Service to run could not be loaded by Operations Manager monitoring host. Check the Operations Manager Event Log for errors and manually start the F5 Monitoring Service once any issues have been resolved."

 

 

I clicked OK to get past this message and then manually enabled the F5 Monitoring Services in the Services Applet.

 

 

Within a short while an alert in the SCOM Console relating to the stopped status of the F5 Monitoring Service on the Management Server auto-resolved itself when it detected that the F5 service was now running.

 

 

Eventually the Event Logs of the Management Server returned to a clean-state with just regular Informational events being logged. I also confirmed that the SCOM Console installed locally on the Management Server was also showing the F5 folders in the Monitoring view.

 

 

My question now is how do I know if the F5 Monitoring Service on the Management Server that is to be the actual point of contact for the F5 devices is healthy and OK to try and perform a device discovery on it given the error message above that indicates an issue with loading Datasource and ConditionDetection modules?

 

 

Was this a transient error that I can safely ignore now that the F5 monitoring service is running?

 

 

I hope to attempt a device discovery via this Management Server soon and I guess that will be the real-test but I would be more comfortable doing so if I could be sure that the error seen during installation is no longer an issue still that might lead t other problems.

 

 

Kind Regards,

 

 

Michael