Trigger Packs

This trigger activates if the free space on a machine's system (C) drive is less than 5GB. You can add a follow-up action to the trigger to automatically clean the system drive and delete data from directories that are rarely used by running the script Clean Windows system drive.

You can download the script action Clean Windows system drive from the community script library in the Real-Time Console.

This trigger activates if read or write latency from a datastore is greater than 10ms. 

This trigger activates when a host is no longer connected.

This trigger activates when a session is idle or disconnected for 24 hours. You can add a follow-up action to the trigger to automatically log off the session by running the script Log off session via script. Note that you can change the scope of the trigger if you want to automatically log off sessions in only a certain folder in your organization tree.

You can download the script action Log off session via script from the community script library in the Real-Time Console.

This trigger activates if there is a connection problem between StoreFront and the Delivery Controller.

To use this trigger, you must first add Citrix Delivery Services to the Events pane in the Real-Time Console. For details, visit Events Pane.

This trigger activates if any of your Citrix licenses are above 90% utilization. The trigger uses the Top Citrix License Utilization column on your Citrix license server, which shows the Citrix license with the highest utilization percentage.

This trigger activates if a CVAD Broker has connection problems or its services are not running. The trigger uses the CVAD Broker Health column, which shows an overall health percentage determined from several broker services and database connections. If any of these are not working properly, then the broker health is less than 100%.

This trigger activates if a CVAD server load index is greater than or equal to 10000, indicating that the server is fully loaded. The trigger uses the column CVAD Server Load.

This trigger activates if a Citrix VDA is not registered to the connection broker. The trigger uses the CVAD Registration column, and will activate only if the VM is powered on and not in maintenance mode. You can add a follow-up action to the trigger to automatically restart the machine by running the script action Restart computer with CU Agent.

You can download the script action Restart computer with CU Agent from the community script library in the Real-Time Console.

This trigger activates if your NetScaler license is 15 days away from expiration. The trigger uses the Days Until Next Certificate Expiration column.

This trigger activates if your NetScaler license is 15 days away from expiration. The trigger uses the Days Until Next License Expiration column.

This trigger activates if there is an unsaved change to the NetScaler applicance configuration for more than 14 days. The trigger uses the Days with Unsaved config column.

This trigger activates if the free space on your Citrix Provision (PVS) server is less than 10%.

This trigger activates if any of the key Horizon connection server Windows services aren't running. The trigger monitors the following services:

• VMware Horizon Log Collector
• VMware Horizon View Blast Secure Gateway
• VMware Horizon View Connection Server
• VMware Horizon View Framework Component
• VMware Horizon View Message Bus Component
• VMware Horizon View PCoIP Secure Gateway
• VMware Horizon View Security Gateway Component
• VMware Horizon View Web Component
• VMwareVDMDSG (only when using cloud pod)

To use this trigger, you must add these services to your list of monitored services in the Real-Time Console (Settings > Service Monitoring). For more details, visit Using Windows Services to Activate Triggers.

This trigger activates if there is a problem with the Horizon Agent on a machine for more than 1 minute. The trigger might indicate that there is a connection problem, or the Horizon Agent is not running. You can add a follow-up action to the trigger to automatically restart the machine by running the script action Restart computer with CU Agent.

You can download the script action Restart computer with CU Agent from the community script library in the Real-Time Console.

This trigger activates if a Horizon Desktop Pool or RDS Farm has no available machines available.

This trigger activates if a Horizon Desktop Pool or RDS Farm has less than 10% machines available.

This trigger activates if provisioning is disabled on a Horizon Desktop Pool or RDS Farm.

This trigger activates if an RDS server is in an unhealthy state. It does not activate if the server is disabled or in maintenance mode. The trigger uses the HZ RDS Server Health column.

This trigger activates if an RDS Farm is in an unhealthy state. The trigger uses the HZ Farm Health column.

This trigger activates if a Horizon Desktop Pool or RDS Farm has more than 5 machines that have a problem. The trigger uses the HZ Problematic Machines column.

This trigger activates if a connection server is in an unhealthy state. The trigger uses the HZ Connection Server Health Status column.

This trigger activates if FSLogix Disk Compaction can't operate because the Optimize Drives service has been set to disabled. When activated, the trigger runs a script action that enables the Optimize Drives service to ensure that FSLogix Disk Compaction can execute.

You can download the script action Configure Optimize Drives service for FSLogix Disk Compaction from the community script library in the Real-Time Console.

This trigger activates if the percentage of empty blocks on a disk is greater than 20%. Empty blocks are blocks in a disk that no longer contain data, but consume space.

The trigger uses the FSLogix Disk % Empty Blocks column. You can view the column under Storage > FSLogix Disks.

This trigger activates if the percentage of free space on a disk volume is less than 10%.

The trigger uses the % Free Space column. You can view the column under Storage > FSLogix Disks.

This trigger activates if the percentage of FSLogix profile containers in a healthy state is less than 100%.

The trigger uses the FSLogix % Healthy Office Containers column. You can view the column by selecting the FSLogix column preset under the Machines view.

This trigger activates if a FSLogix disk is not in a healthy state.

The trigger uses the Health column. You can view the column under Storage > FSLogix Disks. For more information about this column, click here.

This trigger activates if FSLogix is not healthy.

The trigger uses the FSLogix Health column. You can view the column by selecting the FSLogix column preset under the Machines view. 

This trigger activates if the column AZ OS Disk Caching is set to none. Learn more about Azure disk caching.