As we saw in previous blogs, Microsoft added new default apps, services and scheduled tasks into the base operating system of the Windows 10 Build 1703 (Creator Update). These updates will have an impact on the user experience, especially in a VDI implementation.
As we saw in previous blogs, Microsoft added new default apps and services into the base operating system of the Windows 10 Build 1703 (Creator Update). These updates will have an impact on the user experience, especially in a VDI implementation.
Many of the new capabilities within the latest builds of Windows 10 also implements new scheduled tasks. Although the tasks do not run continuously, they will impact density when executing and many are irrelevant in a non-persistent VDI environment.
Build 1507: 130 Tasks
Build 1607: 166 Tasks
Build 1703: 165 Tasks
Build 1709: 173 Tasks
History has shown that optimizing Windows scheduled tasks can improve logon time and server density. It is recommended to review the list of scheduled tasks and disable those that are not necessary for the users.
To see a list of Windows services, run the following PowerShell command: Get-ScheduledTask
So I thought it might be interesting to see the difference Workspace Environment Management has on the logon experience with VDI.
Note: Both of these examples mapped 5 drives, mapped 3 printers, used a 500MB roaming profile and executed a single logon script that queried a single AD Group.
Improving logon time is a fun topic because the experience is oftentimes so bad. I heard (and I’ve complained) about the horrible experience. On the opposite side, I’ve also heard many others bragging about how fast their logon times are. What’s your logon time? Excited to share or afraid to say?