There are probably safer ways to do this without periodically killing wfica32 processes. There are better ways to do what I've done. This script is not a clean, finished, completely working product. If it waits for longer than the timeout period, it'll assume failure and alert in Nagios. If it logs in successfully, a file is updated on a central share, and the monitoring script moves onto the next server in the queue. The script runs on one VM, contacts the controllers for my XenApp 6.5 and XenApp 7.6 farms, gathers a list of current XenApp nodes, then iterates through each one and attempts to log in. almost stable enough to add it to our after-hours alerting group (not while I'm on call - just the other engineers, of course!) The Overview It's taken months of working on this on and off, but I finally have something in a reasonably stable state. Since then, I've wanted to be able to have my monitoring system (in this case, Nagios) log into all of my XenApp servers, and report back whenever there was an issue getting into one. This has been an ambition of mine ever since I started playing with some of the ICA Client DLLs in PowerShell and watching Citrix sessions launch by magic (if you could get it to work, it was magic, plain and simple). ![]() ![]() Update: I'd recommend using one of the many free tools available to do this now, like ControlUp Scoutbees free edition, or just using the ControlUp Logon Simulator, or using Desktop/Application Probing in Citrix itself (if you're licensed for it!)
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |