All was set as it should but still the DCs raised this Alert in the Console: ‘Health Service Credentials Not Found.’ And: ‘An account specified in the Run As profile "Microsoft.Windows.Server.AD.ActionAccountProfile" cannot be resolved.’.
So time to check everything. An AD account with sufficient permissions was in place and operational. Not blocked, what so ever. The account was neatly added in SCOM as a Windows Run As Account. This account was added to the related Run As Profile.
Of course, for the Run As Account the ‘More Secure’ distribution type was selected. Also the correct DCs for this Run As Accounts were selected.
Hmm. All seemed to be well. But when the Alert was closed and on the related DC the Health Service was restarted, the Alert reappeared. So somehow it did not work as it should.
Since the account itself and the Run As Account in SCOM are OK, the cause had to be found in the Run As Profile. Perhaps in this case more granular targeting was needed?
So I removed the earlier Run As Account from that Profile and added it. However, this time it was targeted directly at the DCs, like this:
At the ‘This Run As Account will be used to manage the following objects:’ hit the Select button > choose Object.
Hit the button Save and be fine.
Close all Alerts from these DCs about ‘Health Service Credentials Not Found.’.
Now when the Health Services of the related DCs are restarted, the Alerts won’t return.