So I’ve gone and optimised my image using the Server 2016 optimisation script. Add applications, larger profiles, Group Policies in to the mix and more seconds get added. That time has advantages such as being able to go and make coffee or produce a logon time report from Director to show your boss, which probably won’t go down all that well.
I built a brand new Windows Server 2016 VDA streaming from PVS. Non-optimised image vs optimised image – logon time results Logon times will also fluctuate based on factors such as load (busy periods), VDA performance and underlying hardware used. You don’t have to implement all of them, consider each one individually. Note: The following configurations can be applied to both Server and Desktop OS in persistent and non-persistent environments. The Target Device Write-Cache is configured as RAM w/overflow to HDD (which is on SSD storage). The VDA runs Windows Server 2016 with no optimisations to start however as you will see later it does become optimised and improves logon times. This produces innacurate results in Director for true logon times so let me show you how you can almost eliminate Interactive Session times, get overall logon times reduced and get Director logging much more accurate data.įor the following logon tests, I used XenDesktop 7.13, running PVS 7.13 and a 7.13 VDA configured with 2GB RAM and 2vCPU. So whilst Director records logon times, it is important to understand that this is the time taken from clicking to launch a resource until the machine is actually usable even though the actual logon may have completed some time before that. Event ID 1000 is logged by the Citrix Profile Management service. This event triggers the Interactive Session timer which ends once Event 1000 is logged to indicate that the session is ready for use. Įvent ID 2 is initially logged on the VDA shortly after the desktop/application icon is clicked within Receiver client or Receiver for Web.
It is the time taken to handoff keyboard and mouse control to the user after the profile of the user is loaded for a session. That metric is: Interactive Session Time.
Don’t map tonnes of drives, especially to users who do not need them.Keep close control of Group Policy incuding monitoring –.Keep GPOs at a minimum (don’t be GPO happy).Many of the logon friendly optimisations and best practices out there today are straight forward and common sense and help to get you started: Citrix unfortunately doesn’t magically make logons quicker than any other desktop. We can even produce logon reports and show them off to managers or other teams within the organisation to show them how good (or bad) the virtual workspace performs! Though without any effort you’ll likely be wowing everyone for the wrong reasons until you put in the background work to get logon times down to a low number. ♣ UPMEvent – logon time results – Saving the best to lastĬitrix Director is great at recording logon times per session and logon averages over periods of time. ♣ Autologon account/the second logon is quicker – logon time results ♣ Serialize/StartupDelayInMSec – logon time results ♣ Non-optimised image vs optimised image – logon time results
This post covers several recommendations that increased by logon times by more than 75%, even on non-persistent machines where the user profile is not permanently cached.