Generates alert if time taken for the logon scripts to be executed exceeds a threshold value.
Helps to identify a user whose logon scripts phase was very slow. This logon phase covers the time taken for the logon scripts to be executed.
Overridable parameters:
IntervalSeconds | The recurring interval of time in seconds in which to run the rule (the default value is set to 300 seconds). |
InfoThreshold | Info alert threshold (the default value is set to 30 seconds). |
WarningThreshold | Warning alert threshold (the default value is set to 60 seconds). |
CriticalThreshold | Critical alert threshold (the default value is set to 120 seconds). |
Debug | Used for troubleshooting (the default value is set to false). |
Logon scripts can have a large impact on start time. Some of the most common ways that logon scripts increase logon times are:
Slow or resource-intensive startup scripts (for example, those that move large numbers of files).
Inefficient loops in scripts.
Nested calls to different scripts.
To identify if this is a general issue on a delivery group, compare the user's load scripts time to the average time for all users in this Delivery Group for the last seven days.
See Delivery Group Average Logon Performance
Check also the User - Logon Activity (Troubleshooting) report to get information about this user's logons in the past.
Some scripts may complete a lot of actions, including calls to other scripts, long loops, mapping network drives, and others.
Optimize and merge logon scripts where possible. Windows Server 2008 introduced Group Policy Preferences, which when used can reduce, or in some cases eliminate, the need for logon scripts. When not using Group Policy Preferences, assign logon scripts to users via GPOs, rather than the AD User Account property setting.
In addition to alert description, some information is also available in Alert Context tab:
CatalogName - The server/desktop OS machine catalog name.
MachineIP/MachineHostname - The IP address/host name of the machine hosting the session.
ClientIP/ClientHostname - The IP address/host name of the client connected to the desktop or application.
ClientVersion - The version of the Citrix Receiver running on the client connected to the session.
ConnectedViaIP/ConnectedViaHostname - The IP address/host name of the incoming connection. This is usually a gateway, router or client.
LaunchedViaIP/LaunchedViaHostname - The IP address/host name of the StoreFront server used to launch the session.
ControllerHostname - The host name of the controller that the session's hosting machine is registered with.
SessionType - Indicates if this is an Application or Desktop session.
IsReconnect - Indicates if the user has reconnected to an already existing session or launched a new one.
BrokeringUsername - The user name of the brokering user.
Click the following link to get more info about logon process:
XenApp/XenDesktop Connection Process and Communication Flow
Also, please see the following Citrix article on troubleshooting slow XenApp logons:
How to Troubleshoot Slow Logons
You may also want to check out the Citrix logon optimization guide:
Target | Citrix.XenDesktop.DataWatcher |
Category | Alert |
Enabled | False |
Alert Generate | True |
Remotable | True |
ID | Module Type | TypeId | RunAs |
---|---|---|---|
DS | DataSource | Citrix.XenDesktop.EndUser.DS.Logons.AlertProvider | Default |
filterProper | ConditionDetection | Citrix.XenDesktop.EndUser.CD.Logons.Alert.ConditionDetection | Default |
Alert | WriteAction | System.Health.GenerateAlert | Default |