dprocopio

Ask the guard if he is the liar. If he is telling the truth, then his door is not safe. If he is not telling the truth, then he is the liar and his door is still not safe.

ugh nevermind.

Careful with that CPE! Mine's broke right now. Imported an excel sheet that NPM validated successfully, then it stopped showing me more than 10 values for a specific custom property. Subsequently, another team member edited a property across several nodes at once via "Manage Nodes," now we can't see values beyond the…

tried both "node" and "nodes." Neither work.

Thanks Again! My issue seems to be around application and component monitors associated with nodes not rolling their status up to the parent group object. I've seen that adding the application monitor itself to the group might alleviate this issue...but come on SW....that's messy and not at all why an admin would want to…

I haven't come across any issues yet and am confident using it in production. It does have some benefits compared to the old CPE.

Excellent. A very helpful response!

Thanks. I'm really trying to stay "out-of-the-box" in the event I get hit by a bus. Crafty stuff though!

I have inherited the database from hell ;-) Many trials and tribulations lie ahead. Thank you for your help!

I ran your test and everything went fine. I rewrote the body of the message, tried again, and everything worked. What is "node.caption?" For some reason that field returned the name of a node that I wasn't testing against! Any idea why that would be? Thanks! Dennis

That query will not return any nodes that have that field populated, and I'm not much of a SQL guy. I'm copying and pasting the ${Node.emailAddress} field directly from the Node variable category as I create the alert. The content is my email address, which is valid as this alert successfully tests against the same node…

yes I did see that in another thread, but it yields the same results....

Thanks. Yes, I've tried changing the roll up method to worst status but it never changes in the display. The release notes for NPM 10.3.1 state "Group member status now displays correctly on reports in the web console." However, does this mean I'm only displaying improperly or status is getting recorded improperly? I've…

I took the approach of classifying within 4 volume size ranges, and alerting on that criteria. 1.) I created a generic advanced alert to trigger when a fixed disk Windows volume reached 10% available. 2.) I created three True/False custom volume properties: Volume_Small: Mark "True" for volumes between 100GB and 512GB.…

These issues should be resolved for you in NPM 10.4.1. I experienced the same issue on 10.4 and it is now resolved. I recommend upgrading immediately to avoid data corruption. "The issue is caused by a defect that occurs when adding to many restricted values. A refresh restricted the values in our Information Service…

I took the plunge, and it works. No data loss. Woo hoo!

Sure I have a pointer for you. There is an MS hotfix that blocks Orion -> vCenter communications that should be removed on pollers and the vCenter: http://support.microsoft.com/kb/2661254 We have the virtualization piece of NPM implemented but I never use it (I prefer vCenter.) I've demo'd Virtualization Manager along with…

Is this known to have been resolved yet? I'm having the same issue on: Orion Core 2012.1.0, SAM 5.0.1, IPAM 3.0, NPM 10.3, NTA 3.9.0, IVIM 1.3.0 The value works fine on nodes, not on volumes, and prefixing the property with node. doesn't work either....

I have been advised that this feature will likely not be mature until 10.4.1, if that...