tyson3264

Once you give account limitations, they are unable to see any other node. You'd basically need to create a special account in Orion with the account limitations and the necessary admin permissions. If adding a node with that account and they forget to set a custom property value that gives them access to the node, they…

Bump... being able to define the custom property order is long overdue. While the custom HTML resource workaround works well for the node details page, it does not help when editing node details. I have over 30 custom properties and need the ability to order/group them by relevance, not alphabetically.

Bump... Account and view limitations is helpful in some situations, but is not sufficient for an enterprise IT environment with hundreds of IT employees across many departments with different responsibilities. I need the ability to give view access to everything and give special permissions to other objects. This needs to…

This is needed for both serial numbers, warranty dates, hardware type, and machine type. I could even find uses for CPU sockets, cores, memory, and disks. Due to either regulations or even support, not all devices are able to be polled via SNMP or WMI. We shouldn't need to the same type of data in multiple fields.

Thanks for the information. I did see that method is available, but it still requires multiple node entries for a single box. It also increases the amount of groups and dependencies that would need to be administered. I think having the ability to manually add an interface by IP or DNS name to an existing node would be…

Bump... being able to define the custom property order is long overdue. While the custom HTML resource workaround works well for the node details page, it does not help when editing node details. I have over 30 custom properties and need the ability to order/group them by relevance, not alphabetically.

Bump. This is long overdue. Display names are built into other products like Lansweeper.

Bump... being able to define the custom property order is long overdue. While the custom HTML resource workaround works well for the node details page, it does not help when editing node details. I have over 30 custom properties and need the ability to order/group them by relevance, not alphabetically.

Where is the Windows Server 2012 and later "DHCP Failover" support? IPAM needs to be able to support failover relationships and replicate scope changes when an action is performed within the IPAM interface. These types of DHCP deployments have been in production 4+ years.

Hi David, I believe you are using old variables. Try something like this... Escalation Level 1 APM\SolarWinds.APM.RealTimeProcessPoller.exe -n=${NodeID} -count=10 -timeout=90 -alertid=${N=Alerting;M=AlertID} Wait 5 minutes Escalation Level 2 Subject: Alert: ${Caption} - CPU load is currently ${CPULoad} Message:…