I am working on some pretty lengthy interlinked posts at the moment covering how-tos and case studies of AppSense Management Suite usage. These hopefully should be very useful to those just starting out with the software or wanting to learn more about its capabilities, but while I toil away on those I thought I’d share a quick point I came across today.
I was verifying a customer’s EM configuration when I saw that one of their Process Started nodes had been configured without a Process Name as the first condition. Now, in version 8.1, it won’t let you do this, you get the message below:-
All well and good, but this was an 8.1 system I was looking at, so they must have put together this erroneously-configured node in version 8.0 and then done the 8.1 upgrade, which let it slip through.
I wondered how that would work, a Process Started node without a Process Name condition? After a bit of investigation, it transpires that the actions in this kooky node would execute for every single process that started. Hmmm. Not a good situation to be in if resources are tight on a busy XenApp server!
Needless to say I quickly put the Process Name condition in that was supposed to be there, and now that they are on 8.1 they can’t make the same mistake again. Just a little disappointing that the upgrade process doesn’t check for these misconfigured nodes and flag them up to the administrator at install time (anyone at AppSense listening?)
Now back to my case studies, hopefully get them done as soon as I can!
Share
