Using built-in accounts like Network Service or Local System as application pool or as service identities is not supported in a farm configuration. The following services are currently running as built-in identities on one or more servers: OSearch15(Windows Service)
All the search service accounts are set to the domain/sharepointsearch account and all four servers are showing the same account being used for the running windows service.
What would cause this error to continue to pop up with the correct account being used everywhere?
Is there a script I can run that would double check or force SharePoint to recognize that the correct account is in fact being used?