Monitors average user logon GPOs time (in seconds) for a delivery group. During this phase the desktop/server machine applies user settings defined on the Domain Controller.
Monitors the average user logon GPOs time (in seconds) for a delivery group. During this phase the desktop/server machine applies user settings defined on the Domain Controller.
When an application or desktop is launched through Citrix, it kicks off a huge stream of events. Profiles are engaged, printers are mapped, and policies are applied.
Overridable parameters:
IntervalSeconds | The recurring interval of time in seconds in which the monitor is started (the default value is set to 300 seconds). |
WarningThreshold | Warning alert threshold (the default value is set to 40 seconds). |
Debug | Used for troubleshooting (the default value is set to false). |
Applying GPOs can have a large impact on start time. Some of the most common ways that GPOs increase logon times are:
Numerous GPOs, rather than a few large ones.
Large numbers of access control rewrites on folders and files.
Large numbers of mapped drives.
Large numbers of network printers.
Unused GPO sections (Computer/User) are not disabled.
Numerous XenApp/XenDesktop policies.
To view the logon phase trend on a delivery group in the past days, open the following link:
Delivery group average logon performance
Also, please see the Delivery Group - Logons per Week (Plan & Manage) report to view how the average logon phase time changed for the past weeks.
Resolutions to some common issues are as follows:
Issue Description | Mitigation |
Having GPOs that heavily rewrite access to files and folders on boot can have a significant impact on logon times. | Optimize access control to reduce number of required changes. Use AD groups and build permissions into base image. |
Merging GPOs takes additional time and adds load to the AD server. | Merge GPOs where possible, so that only several larger GPOs exist, instead of hundreds of small ones. |
Having many printer and driver mappings can increase logon time. | Reduce the number of required printer and drive mappings where possible, and ensure that client printer mapping is allowed to occur after logon in XenApp/XenDesktop. |
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 | ComTrade.Citrix.XenDesktop.DeliveryGroup | ||
| Parent Monitor | System.Health.PerformanceState | ||
| Category | PerformanceHealth | ||
| Enabled | False | ||
| Alert Generate | True | ||
| Alert Severity | MatchMonitorHealth | ||
| Alert Priority | Normal | ||
| Alert Auto Resolve | True | ||
| Monitor Type | Citrix.XenDesktop.EndUser.DeliveryGroup.Logons.UnitMonitorType | ||
| Remotable | True | ||
| Accessibility | Public | ||
| Alert Message |
| ||
| RunAs | Default |
Home
ENU