Always trying to get better.
In 2012, I started my pursuit of astrophotography. Let’s just say the results of M42 – The Orion Nebula were not very impressive.
Over the course of 5 years, I continued to try out new techniques and learned a lot about signal-to-noise ratios, imaging histograms, Bahtinov masks and more. I continued striving for better results and am glad to say, the my work is finally showing positive results.
All of the effort is starting to show some very good results.
I find that astrophotography gives people a “Wow” feeling; so, let’s change topics to something that creates the opposite feeling: Logon Time.
When Windows 10 was initially released, I developed a set of optimizations and showed how OS changes can improve the overall logon time.
In addition, I also observed that enabling the Provisioning Services RAM Cache with Disk Overflow for write-based IO Activity also decreased user logon time.
And recently, I observed that XenServer’s new PVS Accelerator decreased logon time even more.
The one thing that is missing from all of these tests is a production environment experience, which often includes profiles, policies and logon scripts.
Workspace Environment Management is supposed to help improve user logon time in a XenApp & XenDesktop environment.
In order to validate if the statement is true, I decided to run the following tests.
- Baseline: Capture logon time for the baseline Windows 10 virtual desktop
- Optimize: Run through the Windows 10 optimizations
- Add PVS Accelerator: Use the new XenServer PVS Accelerator technology
- Add PVS RAM Cache with Overflow: Use write IO optimizations by adding PVS RAM Cache
- Add Drive Mapping: Use Group Policy Preferences to map 5 drives
- Add Printer Mapping: Use Group Policy Preferences to map 3 printers
- Add Logon Script: Use Group Policies to run a logon script that maps 3 drives based on Active Directory Group Membership
- Add Roaming Profile: Assign a 120MB roaming to the user
These are not complex operations, but I expect adding each one to the environment should gradually increase the user’s logon time.
Once I captured the results, I reran the tests using Workspace Environment Management to validate if it has any impact to what the user experiences.
As expected, in a native implementation, adding each item started increasing my logon time. But in an environment that included Workspace Environment Management, we were able to maintain are fast logon time.
Remember, the policies, scripts and profiles i used where very simple. This minimized the overall impact. Imagine what happens in a real production environment with larger profiles and more complex policies and logon scripts.