Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

View devices that credentials are assigned to

In all cases where Orion stores credentials I would like a column that indicates the number of devices that the credential is currently assigned to. When I click on that number I would like to see a pop-up that shows which devices (much like SAM does with templates and where those are assigned). I am putting this feature request here for NPM because today I needed this functionality for the Virtualization Credentials; however, I would like to see it anywhere credentials are used.

I often find that my list of credentials get very long and I am always afraid to delete the old credentials just in case something is still using them; if I had this feature I could be much more effective at managing those and keeping the list short with only the most current credentials.

Find more posts tagged with

Status: None

Comments

rschroeder

I'd like this feature, too. And I'd like the option to take it a step further, and be able to sort devices by user name or community string used. AND show that user name or community string.

I realize that last item isn't a FIPS happiness, and various government or other groups would have it disabled. However, if access to seeing it were protected by AD Group permissions, and if viewing it could be administratively enabled or disabled, anyone who doesn't want it could shut it off.

It'd be nice to quickly and easily see which nodes are being polled by RO String X versus String Y, or by user X instead of user y or by community string Z. Then select all the ones that need to get on board with the big picture, push out a script via NCM that adds the credentials other nodes use, change the polling method for these nodes to use the new credentials, verify it works, and then use NCM to delete the old credentials.

That's a nice way to get everything back to the baseline or cookie cutter image for consistency.

kinstray

Here is the SQL to look this up manually until the feature gets implemented:

declare @Name nvarchar(256) = ''

select 
	n.[SysName],
	n.IP_Address,
	n.MachineType
from
	Nodes n
	left join NodeSettings ns on ns.NodeID = n.NodeID
	left join Credential c on ns.SettingValue = cast(c.ID as nvarchar)
where
	ns.SettingName LIKE '%Credential%' and
	c.[Name] = @Name