How to Identify Poor Drive Mapping to GPOs is Root Cause of Slow Logons
To analyze the 33+ stages of the user’s logon process, you can click on any user session to drill into the session metrics. Once you’ve drilled down, navigate to the logon duration tab (Figure 2). This tab is divided into two sections. The top sections break down the details of what is happening in the brokering stages and the bottom sections detail the high-level metrics of the launch on the App Server or VDI.
The brokering stages enable you to identify slowness due to Citrix Delivery Controller brokering issues such as Authentication, Logon Script, Profile Load time, and/or delays in Windows session creation on the session host. On the client side, you can identify delays in establishing the micro-VPN connection, receiver launch, ICA file download, and more.
At the bottom of the dialog (Figure 2.A), each stage of the logon process at the session host process is displayed, including authentication at the domain controller, determining how long it took to copy over the policy files to the session host, logon script execution, drive mapping, printer mapping, and folder redirection. Each policy and script which is executed is included in this stage.
Figure 2 – Session dialog – Logon Duration Tab
When you have many users in the environment complaining about the same issues (in this case logon duration), finding patterns can be key to isolating root cause and identifying a permanent solution.
Using the Logon Duration details, a system admin can determine that the widespread delays in logon duration stemmed from drive mapping (logon) scripts. This was discovered by tracking high GPO times in the top level (Figure 3) of the logon duration breakdown, then down to the brokering stage of PLSD (the time spent on the server loading the user’s profile), and then down to the bottom section of the page, specifically Group Policy Drive Maps Extension (Figure 3.A).
Figure 3 – Logon Duration Tab
Figure 3.A – Logon Duration Tab Drill Down
In the example scenario described above, reviewing the logon duration metric trends resulted in identifying high group policy drive mapping. By identifying the exact policies that were associated with the drive mapping extensions, further investigation of those policies could take place. Ultimately, the system admin discovered that the scripts were mapping 30+ errant drives to the user’s profile. The IT Pro was able to reduce the number of logon scripts down to a single script and removed the problematic, incorrectly linked GPOs. By determining the root cause and applying the aforementioned actions in their environment, the system engineers were able to reduce logon times and solve the end-user performance issues.