The user is looking for input on triggers and scripts to monitor/remediate VMware Horizon VDI environments. They recommended using a logon script triggered when a slow logon threshold is reached. Tuning the timing parameters and enabling extra logging is suggested.
Read the entire ‘Monitoring/Remediating VMware Horizon VDI with Triggers and Scripts’ thread below:
Currently using the 3 builtin triggers (VMware horizon) to monitor Horizon view pools in 40 different CU installs. As we start to take the training wheels off, I’m seeing some gaps and room for improvement with them. As we work to tweak and create new triggers in our client’s environments, I am looking for input from other users who are actively monitoring\remediating their Horizon VDI environments. What’s your best set of triggers? Thanks!
The number 1 trigger/script combo I recommend to everyone with VDI is the logon script and the trigger to launch it when a slow logon threshold is reached.
You should tune the timing parameters to run it when a logon takes a bit longer than normal for your environment (I usually suggest about 10 seconds longer than typical if your logons are typically consistent) and make sure that you enable the extra logging for it, but it’s amazing how much it can help you out when someone catches you in the hallway and says "Oh, by the way, I had a slow logon last week, can you look into it?"
Continue reading and comment on the thread ‘Monitoring/Remediating VMware Horizon VDI with Triggers and Scripts’. Not a member? Join Here!
Categories: All Archives, ControlUp Scripts & Triggers