F5 Monitoring Agent Issues

Hi Joe,

 

 

I would probably first look into the "Default Action Account" profile: SCOM Management Console >> Administration >> Run As Configuration >> Profiles >> Default Action Account >> Properties >> Run As Accounts and make sure the action account specified there has enough privileges. The "Local System Action Account" should probably be appropriate. If it's a different action account, you'll have to check the privileges in the Run As Configuration >> Accounts section.

 

 

Another relevant Run As Profile involved in reading / writing to data sources would probably be the "Operational Database Account". Make sure the underlying action account has enough privileges on the OperationsManager SQL database. By default, if no action account is specified for this profile, the SCOM SDK service account is used.

 

 

Julian

 

(F5 Management Pack Team)