Reviving this thread after recently discovering the now-bundled fling 'Logon Monitor' - and thought the detail, and the accurately timed results it generates could facilitate some decent discussion.
I guess I'm wishfully thinking that one of you will post a sub 15 second result for a windows 10 non-persistent desktop pool, and you could share how you got there.
Here's mine:
2017-08-07T17:31:19.500 INFO (0a74-0310) [LogonMonitor::LogSummary] ****************** Session Summary (User: <username>, Session: 1) *****************
2017-08-07T17:31:19.500 INFO (0a74-0310) [LogonMonitor::LogSummary] Logon Time: 43.88 seconds
2017-08-07T17:31:19.500 INFO (0a74-0310) [LogonMonitor::LogSummary] Logon Start To Hive Loaded Time: 15.07 seconds
2017-08-07T17:31:19.500 INFO (0a74-0310) [LogonMonitor::LogSummary] Logon Start To Classes Hive Loaded Time: 15.30 seconds
2017-08-07T17:31:19.500 INFO (0a74-0310) [LogonMonitor::LogSummary] Profile Sync Time: 0.00 seconds
2017-08-07T17:31:19.500 INFO (0a74-0310) [LogonMonitor::LogSummary] Windows Folder Redirection Apply Time: 0.00 seconds
2017-08-07T17:31:19.500 INFO (0a74-0310) [LogonMonitor::LogSummary] Shell Load Time: 18.77 seconds
2017-08-07T17:31:19.500 INFO (0a74-0310) [LogonMonitor::LogSummary] Total Logon Script Time: 0.00 seconds
2017-08-07T17:31:19.500 INFO (0a74-0310) [LogonMonitor::LogSummary] User Policy Apply Time: 5 seconds
2017-08-07T17:31:19.500 INFO (0a74-0310) [LogonMonitor::LogSummary] Machine Policy Apply Time: 0 seconds
2017-08-07T17:31:19.500 INFO (0a74-0310) [LogonMonitor::LogSummary] Group Policy Software Install Time: 0.08 seconds
2017-08-07T17:31:19.500 INFO (0a74-0310) [LogonMonitor::LogSummary] Free Disk Space Available To User: 21 GB
2017-08-07T17:31:19.500 INFO (0a74-0310) [LogonMonitor::LogSummary] **************************************************************************************
I've worked through various blogs to try and get logon time down - James Rankin has numerous posts relating to referencing a sanitised, 'pre-built' profile (as opposed to making the machine generate a new profile, which would occur during every logon in a non-persistent instant clone pool) - but personally I've not been able to achieve anything below 30 seconds following these guides, and in most cases it's caused issues like breaking the start menu / tile arrangement. This isn't to discredit the great work he's done, it's just I've not had great success with it.
It also seems that MS understandably don't support the use of profiles that have been hacked around having stuff removed from the user registry and file system...
I should also point out this environment is backed by a brand new, dedicated UCS environment and all-flash Pure Storage array - (40Gbe chassis connectivity + 16Gb FC). So I don't think hardware is the bottleneck here.
I think I'm either approaching this the wrong way, or it's simply not possible to achieve quick, 10-15 second logon times with WIndows 10 1607 in non-persistent VDI environments.
Hoping that one of you will prove me wrong, and we can all learn from it.
