Do these look like issues to you? I'm wondering if this sorta thing is normal on everyone's SW....
In my experience this page generate a lot of red herrings and rabbit holes, but it can also sometimes highlight real problems. I basically just take it all with a grain of salt.
Thanks for good the answer... I appreciate this forum... You all really help!
Many of these health checks have good explanations if you click on them, and some include remediation information.
The "ping all plugins on agents" and "ping all registered agents" alerts usually indicate that one or more of your agent-managed nodes are having an issue. The agents may need to be restarted, have a pending update, or could be blocked by a firewall.
"Check if Database Maintenance works properly" is one of those big grey areas, but should lead to some potential DB related improvements if you dig through the recommendations. You might find that you need to widen your maintenance window or reduce the data retention period for some of your statistics.
The parallelism value checks are new to Orion as far as I can tell--they never popped up until our last update. Check with your DBAs and your VMware team (if that's not you) and you'll probably find a way to improve performance with those settings. Again, read the description on those alerts and bring in the right people for your infrastructure.
"Check subscriptions with too old last delivery" isn't a major issue, but again, the description does provide a link with steps to remediate the condition.
You can ignore the "pending Windows updates" message if you know that your server is up to date.
The DEP alert also provides instructions from the description, if you are not familiar with DEP.
Finally...if your Orion server is running SQL Server on the same machine, I feel sorry for you! You should definitely try to split SQL onto its own server unless you have a very small environment.
Good luck!
Thanks so much- very helpful- will check it out.sturdyerde
I think I can give an example for the Deployment Health, it's more of an environmental case, and we know that some tests might not apply to everyone. For example, we’ll warn you that if your SQL Server is on a VM, that might not be the best setup. Sometimes resource-intensive applications like SQL don’t play well with shared resources. But if you know that your VM is a beast and can handle whatever we can throw at it, you can just silence or ignore it. Another example is about the database maintenance where we can check the logs to see if it's completing successfully but sometimes it reports that we need to check it if it's successfully completing or not but if we look at the logs, we can see that it has completed and on that case we can just ignore it that alert. I hope this helps.
