Windows Enterprise Client Boot and Logon Optimization – Part 22, Blog Post Series Wrap Up
This post concludes the series that started here.
Over the past few weeks I’ve presented a “lite” version of the Microsoft Services Premier Workshop – Windows Enterprise Client Boot and Logon Optimization. If you’ve stayed with me from the start, I hope the series has been a valuable read and that it’s provided some insight into your choices when building a Windows client image for the Enterprise.
The series followed three main themes –
Design the image for performance
- Part 1, Introduction
- Part 2, Tools and Instrumentation
- Part 3, Trace Capture and Benchmarking
- Part 4, An Aside on ReadyBoot
Troubleshoot performance issues that creep into production
- Part 5, Windows Performance Analyzer – A Tour
- Part 6, Boot and Logon Overview
- Part 7, ReadyBoot Analysis
- Part 8, Code Integrity Checking
- Part 9, CPU and Disk Utilization
- Part 10, Boot Phase – POST
- Part 11, Boot Phase – OS Loader and Kernel Initialization
- Part 12, Boot Phase – Session Initialization
- Part 13, Boot Phase – Winlogon
- Part 14, Boot Phase – Explorer Initialization
- Part 15, Boot Phase – Post Boot
- Part 16, Wait Analysis
- Part 17, Wait Analysis – More Challenging Example
The influence on client boot performance imposed by infrastructure and settings
- Part 18, Infrastructure and Settings – Group Policy
- Part 19, Infrastructure and Settings – User Profiles
- Part 20, Infrastructure and Settings – User Data
- Part 21, Infrastructure and Settings – Network
Conclusion
Windows Boot and Logon Performance has a direct link to user productivity. If the experience is fast, the user is engagement more quickly with less frustration. At scale, this idea is worth embracing for the sake of business efficiency, user satisfaction and IT department reputation.
If you embrace the ideas in Parts 1 to 4 and Parts 18 to 21, there should largely avoid the need to perform the detailed investigations I’ve outlined in Parts 5 to 17.
Next Up
I’m in the middle of a project for the subject of my next post. For this reason, it’ll take me some time to post again.