Memberships [ 1 ] [+]
Activity Stream [+]
Ideas Contributed [ 69 ] [+]
So the SO Level reporting (and the descriptions) is broken by design. It's a UX Disaster. They were never actually meant to be run at the so level which is why they don't include the details that the customer level reports do, and were never updated to include the customers/sites that an so level report would need to be fit for purpose. Yet the descriptions are the same as the customer level reports which is completely ...more »
ConnectWise introduced the ability to merge tickets back in July 2016. After trying to verify compatibility with N-Central at the time, we learnt that merged tickets were not supported through N-Central as the associated ticket numbers wouldn't track back correctly after the merge takes place. I assumed that this would mean N-central would talk to ConnectWise about it, but it looks like that never happened or talks halted ...more »
After introducing partial support for sites into n-central quite some time ago, support for customers/sites was removed or never actually added in filter previews and reports.
I am told that for a report or filter to include the customer/site instead of just a device name, a feature request needs to be created because Solarwinds consider this to be by design.
I feel really stupid having to request this, but SolarWinds won't do anything without it. Whilst patching our PSA recently and facing outages, we have found that depending on the type of PSA issue you are facing (eg connectivity, backend sql problem), the failure notice you receive from a ticket not being created/updated will always include details of the customer and notification recipient, but for some inexplicable ...more »
I'd like the ability to block customer level users from being able to access filter/dashboard/repositoy items that were created at a higher level. I don't want to completely remove access to the filters/dashboards/repo as they should be able to manage items at their level and below, but don't want them being able to look into the items that were created at a higher level, since they're not a higher level user that should ...more »
here we are almost a decade later and it's still not possible to set "unschedueld downtime" or "update monitored ip" via rule.
Support have now banned the abilit yot do so via a NAC advanced script and doing it via a manual bulk edit is what we've been trying to avoid.
So let's make rules great again and allow the setting of any device property you can do manually!
right now, the only option to transfer filter/item ownership is to kill the user, at which point n-central asks for you to grant ownsership to someone else.
I vote that this ability should be possible without the death penalty for the unsuspecting user that had the nerve to try to create a filter themselves.
they can do so for repository items, so why remove the ability to do so for filters?
it makes for a pretty powerless "product admin"...
right now the options are to have the user make the change, change th euser passowr dand make the change yourself, or kill the user which then transfers ownership of all their filters, items etc to another user. Either option seems too complicated to me.
I discovered today that productadmin is no longer able to edit a filter owned by another user. I propose that we fix this by tying it in with the user roles, and offer the ability for shared ownership to the members of the user role on a filter/repo item marked as shared so anyone can easily update. Changes would be auditable. If the item is marked as private then it belongs to the user, but we should allow for the ...more »
Solarwinds Backup seems to only support upto macOS 10.11.
Does anyone have any recommendations for a macOS backup product?
It would be useful to be able to patch 3rd party products only to a specific version.
Unfortunately, some LOB Applications still require specific version of Java, Adobe Reader etc.
At present we can either not patch them, or patch them to the latest version; Nothing between.
It would be handy if the N-Central agent supported an offline agent install for those cases when internet access to check for the connection back to the n-central server has not been provisioned yet, is temperamental, or is just plain down.