{"id":37803,"date":"2022-09-29T17:14:58","date_gmt":"2022-09-29T16:14:58","guid":{"rendered":"https:\/\/www.n-able.com\/?p=37803"},"modified":"2025-02-20T21:57:47","modified_gmt":"2025-02-20T21:57:47","slug":"n-central-getting-customers-active-issues-under-control","status":"publish","type":"post","link":"https:\/\/www.n-able.com\/it\/blog\/n-central-getting-customers-active-issues-under-control","title":{"rendered":"N‑central: Getting customers\u2019 Active Issues under control"},"content":{"rendered":"

For some N‑central<\/span><\/a> users, clicking on the Active Issues view<\/span><\/a> and seeing the total number of issues in the bottom right hand corner can be daunting and lead you to think \u2018How am I ever going to get this under control?\u2019 In this blog, we are going to look at a few steps you can take to address some of these issues and bring that number down, so that your Active Issues view returns to a useful dynamic dashboard, with key issues that you need to address.<\/span><\/p>\n

Before you take any actions, it\u2019s a good idea to make a note of the current state of your Active Issues screen. By default, the Active Issue screen will include services in a Disconnected state and since it\u2019s common for laptops and workstations to be powered down periodically, this can lead to the Active Issues numbers being inflated on first view.\u00a0<\/span><\/span><\/p>\n

To get a clear understanding of where you are, use the Show Filter pop out on the right hand side of the screen to filter on Failed, Warning, Misconfigured, and Stale status. Note that number down as your overall total, then reset the filter and find the number of Failed and Warning issues, then repeat the process to find the number of Misconfigured then Stale issues.\u00a0<\/span><\/span><\/p>\n

So where do you begin?<\/span><\/h2>\n

Once you have a general picture as to what your Active Issues are, you can start taking steps to address them. For a start, check on the state of your probes, failed probes can often cause a spike in your active issues, so resolving issues with probes can have an instant impact on your overall active issues. Common issues with probes, can include credentials used to start the probe having been changed but not updated on the Windows Software Probe service. This will result in service failing to start. Alternatively, the device where the probe was initially installed may have been replaced, but the tasks where never transferred, or no new probe installed.\u00a0<\/span><\/span><\/p>\n

Resolving issues with probes is a good place to start when looking to reduce misconfigured and stale active issues.<\/span><\/p>\n

Look for more quick wins?<\/span><\/h2>\n

Once you\u2019ve resolved any issues with probes, the next step is to look for quick wins with the Failed and Warning issues. Here are some common examples:<\/span><\/p>\n