This document discusses optimizing and troubleshooting virtual desktop infrastructure (VDI) images. It recommends building VDI like Frankenstein by using good parts without any abnormal parts, measuring carefully, and maintaining supportability. Key aspects for a good VDI include a solid network, reliable storage not like a black box, and upgradable server infrastructure. Images should be specifically made for VDI. The document also analyzes Windows 7, 8.1 and 10 for VDI, noting pros and cons of each, and emphasizes optimizing for performance and user experience across all versions.

1. TMH02: VDI Image Optimization
and Troubleshooting
Jeff Stokes
Sr Content Creator
Microsoft
Level:
Intermediate-ish

2. Jeff Stokes

3. VDI projects: walkthrough
• We need VDI to save money
• We need VDI for security
• We need VDI for app compat/BYOD
• We need VDI for remote workers
• We need VDI for …

4. Ok let’s do it!

5. Results

6. VDI Philosophy
• Build it like you’re building Frankenstein
– Good parts
– No Abby Normal parts!
– Measure twice, cut once
– Maintain supportability

7. VDI: Good Parts
• Solid network infrastructure (dedicated?)
• Storage that isn’t a black box
• Server farm(s) that are upgradable,
expandable, supportable
• Windows Image made for VDI

8. Why an image made for VDI?

9. VDI Performance at Scale

10. Windows 7
+ Well tested and supported (known)
+ Familiar UI
+ ‘Decent’ performance profile
- EOL soon
- ‘Decent performance profile

11. Windows 8.1
+ Tested/Supported OS
+ ‘Good’ performance profile
+ Pseudo VDI aware
- UI adaptation
- Servicing size

12. Windows 10
+ Excellent performance
+ UI ramp improved
+ Long lifespan
- Servicing familiarity

13. Optimization for all

14. What do these do?
• Exactly?

15. UX considerations

16. Q/A