![]() These are our findings, your mileage may vary. Sysprep and a new SID caused an almost exactly 60 second increase when logging in with AD user accounts. There is almost never a need to generate a new SID for these machines. Anything that you can turn off via group policy or configuration manager packages in Windows 10, use that method instead of registry hacks or OSOT. Believe it or not we have seen that surgically disabling the firewall causes start menu problems (HUH? I know right?). Leave unchecked at least "Device Setup", "Windows Search", "Windows Firewall", and "Windows Themes". Now run it, but leave some things 'un-optimized'. Some settings have been updated for 1607 and newer Windows releases. When using the OS optimization tool, go to Public Templates, find the win10 beta one.Seems to work flawlessly, unlike every single other method. Use Export-StartLayout to put the start menu somewhere locally, then use local group policy to reference that. Use the WindLTSB and Horizon 7.0.3 - the 1607 version has fundamentally different Start Menu workings than the older 2015 releases.You won't be leaving for 1:10 at least.") All the registry hacking in the world wont fix those things reliably, but group policy will. Use group policy (local or AD central store) to disable OneDrive, Windows Defender, etc, the "consumer experience" and other Windows 10 bloat (such as the initial sign on message "We're glad you're here.Here are a few things we've found that made a difference: We've been tinkering with it for a couple months now, and have non persistent Windows 10 logins down to about 16 seconds as a baseline, which grows to around 24-27 when using GPU (Tesla M10), UEM 9.1 clients, and AppVolumes 2.12 agent in the base image. When someone logs in it says "Preparing Windows" then you get the "We're Happy You're Here" followed by a few more messages and finally the desktop appearsĬouple things on this. Login times are 1:10 which is twice as long as Win7.Took a snapshot, and made a new pool with just 3 desktops. ![]() HKLM\Software\WOW6432Node\Microsoft\Active Setup\Installed Components.HKLM\Software\Microsoft\Active Setup\Installed Components.Deleted all stub paths in the registry under.We took all the defaults except we also checked most of the built-in apps to have them removed Our storage is a Nimble All Flash Array so IOPS and latency is not an issue Installed Windows 10, 64 bit, build 1607 which is the latest available for download.We are running View 7.0.2 under ESXi 6.0 Update 2. I am working on building a master image for Window 10. It takes about 35 seconds to login to a Win7 desktop. We have been running Window 7 using View for several years. I gave this another go since my original post was March 2016 and several things have changed including the version of View, ESXi, and Win10 we are running Would things improve under ESXi 6.0 Update 2? We are upgrading to the newest version of vSphere in about 2 weeks Is Windows 10 under View just not a good choice? We use non-persistent desktops so they are refreshed after each log off. Using a console session in the client to login twice does not refresh the desktop. ![]() Of course a desktop will only realize you have logged in before if it is a persistent desktop. In other words, logging in the second time cuts login time significantly. I then just went to the vSphere client, got a console session to one of the desktops, logged in (which took 1:50), logged off, and logged back in again, it took about 35 seconds. When someone logs in it says "Preparing Windows" then you get the "We're Happy You're Here" followed by a few more messages and finally the desktop appears Login times are 1:50, more than a minute longer than Win7.Took a snapshot, made a new pool with just 2 desktops.VMware OS Optimization Tool – VMware Labs Ran the optimization tool found here taking all the defaults.This is the same resources that we use under Win7 Ran Windows updates and installed all available.Installed Windows 10, 32 bit, build 1511 which is the latest available for download. ![]() We are running View 6.2.1 under ESXi 5.5 Update 2. ![]() I am working on building a master image for Window 10 but found logins to be very slow. It takes about 35 seconds to login to a Win7 desktop ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |