Citrix Logon Times Not Being Reported in Director - Part 2

Firstly, let’s recap what we covered in part 1.  The symptoms of the issue initially came from Director, where a new 1909 Citrix environment was not logging user session logon times within Director. We also covered the fundamentals of the processes Citrix uses to capture the user logon times. Here, we will continue troubleshooting the issue and attempt to find the root cause.

Troubleshooting begins

Looking across the web, I found a large number of occurrences of the issue. I will start with the official guidance from Citrix. The article relates to the User Profile Management (UPM) WMI plugin either not being present or malfunctioning, as shown here  I confirmed the plugin was installed, and the UPM service was running. To test the WMI plugin is functioning correctly, you can execute a PowerShell command. To return the specific results relating to logon times, the class filter of logontimings  is used, the command is

get-wmiobject -namespace root\citrix\profiles\metrics -class logontimings

The expected result as indicated in the article is if this issue is occurring then the output of the test would produce either

  • A scripting error, meaning the plugin is not installed
  • No  

Instead, my testing   a valid output, but the logon timing metrics all show as zero’s. As shown in the screenshot below.

The metrics to pay attention to in the above screenshot are:

  • GroupPolicyStart, GroupPolicyComplete

This pair of metrics measure the amount of time it takes to read and process all group policy during the login process.

  • ProfileLoadStart, ProfileLoaded

This pair of metrics measure the time taken to load the user's profile, whether that is a local, roaming, UPM or Fslogix based profile.

  • DesktopReady

This metric is a marker for when all logon processes completed, and the user’s desktop was ready for use.

The time taken between ProfileLoadStart and DesktopReady are the metrics users to determine the profile load times. The below screenshot shows the expected results after running the test . All five metrics show values. If your environment utilises logon scripts, then the metrics LogonScriptStart and LogonScriptComplete, should also be populated. In this case, no login script was in use, so the expected metric is zero.

To test this further, I then uninstalled and reinstalled the UPM WMI plugin, following a restart and further testing, I am still presented with the same results.

Troubleshooting, testing the operating system

Moving  to the next Citrix article on the topic,  ,  which  goes into great detail for troubleshooting the logon duration at the Windows OS level. This test excludes Citrix from the equation. The instructions require you to download a Microsoft produced PowerShell script named AnalzerLogonDuration.zip.  You are required to modify the PowerShell script and add the following line to the end.

get-LogonDurationAnalysis -Username "YourUserName" -UserDomain "YourDomainName"

The output of the script was as follows.

The output from the test again shows that the script executed correctly but returned zeros for logon statistics.

After following these instructions successfully and it also not reporting the logon statistics, this leads me to believe that the issue was an operating system level issue, not a Citrix issue.

Reinstall the VDA

I continued to follow through with the next set of instructions from the article. This was to reinstall the VDA . I uninstalled and reinstalled the VDA agent, after several restarts, I again re-ran the test against the WMI object with the command line.

get-wmiobject -namespace root\citrix\profiles\metrics -class logontimings

The results remained the same, zero’s for all of the metrics.

In part 3 of the series of Citrix Logon Times not being reported in Director, I will continue with the troubleshooting as we get closer to the root cause and a resolution.

Join the Insentra Community with the Insentragram Newsletter

Hungry for more?

[Modern Workplace]

MapOne – Part 3 – Customer Case Study

By [Lee Foster]

Quick recap – What is #MapOne? – In its most basic form, #MapOne is a fixed price engagement targeting senior stakeholders in the business (often executives CIO, CTO, CISO, CDO) delivered through a series of workshops, meetings, interviews and interactive sessions.

[Modern Workplace]

MapOne Part 2 – The Roadmap

By [Lee Foster]

If you have read my Architect as a Service (#MapOne) Blog and are back here to understand more about the deliverable roadmap provided at the end of an #MapOne engagement, welcome to part 2.

[Modern Workplace]

MapOne Part 1 – Gain the clarity required to make inspired decisions

By [Lee Foster]