steverunner

Thanks Zak....I'll remove the "Node Status is not equal to Down" entry and add the rest of the servers. I appreciate your help! - S

Thank you very much for your help Zak!

Thanks Mike.

Zak…I forgot to include a conditional test for node status….does this look right?

Zak: Thanks for your help. Looking at the attached image; does this look correct to you? If either nyctx01 or nyctx02 have any of the listed applications change state = down, will this generate an alert?

Thank you Mharvy...I appreciate the good advice!

Thanks for this link Rob, very much appreciated!

Steven: Not a silly question at all! That might be true; I'll look into it now. The bigger question is to see if there is a better way than sending "sh tech" to the Orion TFTP server...it would be better if it could be sent to the SW database (although, I understand the size of the output is problematic). For now, I'm…

Was there ever any resolution to this? We're having a similar problem using a WMI process monitor, to check on the state of executables running on a server. When I set up a test node and click "Test", the component monitor screen indicates "Testing against <server>" and just "sits there" spinning forever.

- I believe that the type of property to monitor needs to be APM: Application and that the following attributes must be true: Trigger Alert when all of the following apply: 1. 1. Group name is equal to Citrix Servers (this is a group of nodes that I have created) 2. 2. Application Name is equal to Citrix XenApp5.0 Core WMI…