We have been running Window 7 using View for several years. It takes about 35 seconds to login to a Win7 desktop
I am working on building a master image for Window 10 but found logins to be very slow. We are running View 6.2.1 under ESXi 5.5 Update 2.
Here is what I have done
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. In other words, logging in the second time cuts login time significantly. Of course a desktop will only realize you have logged in before if it is a persistent desktop. Using a console session in the client to login twice does not refresh the desktop. We use non-persistent desktops so they are refreshed after each log off.
Any ideas how to speed up logins?
Is Windows 10 under View just not a good choice?
Would things improve under ESXi 6.0 Update 2? We are upgrading to the newest version of vSphere in about 2 weeks
Are you not using any kind of roaming profile? If you have a roaming profile, only the first log in is slow as Windows is preparing your profile. Another thing you can do to speed up first log in, is to completely remove some of the default Store apps (such as XboxApp, Zune.video etc).
Having Windows 10 running smooth in View is doable in my experience, but it requires a bit more work
These are all non-persistent desktops that get refreshed on logout. Will a roaming profile help in this case?
The optimization utility provided by VMWare does remove all the default store apps so that piece is already done.
The original Win10 desktop I was testing this on also had Office 2016 installed, a few settings tweaked, and sysprep was run. This is the one with a 1:50 login. Yesterday I made another master image with just Win10 and optimization utility run. The login time was 1:10. This is still double the Win7 login time of 35 seconds
Is anyone else running Win10 under View? If so, what is your login time?
The delay is most likelly due to Windows installing the "Metro Apps".
Have the same problem with physical Windows.
One way to overcome it somehow is to remove most of the shipped apps with dism.
I think the optimization utility found at the link below not only removes the pre-installed metro apps, I believe it prevents them from reinstalling themselves when another user logs in. I could be wrong about this
Are you able to reduce the login time.
We are also facing slow login time on Windows 10, takes 2 minutes to login.
OS: Windows 10.0 ( Build 10240) 64 bit
Profile management through UEM 8.7
VMware Tools: 10.0.9 installed
Horizon view : 6.2
Uninstalled all the Metro apps through - VMware OSOT tool (latest)
Appreciate any solution to reduce the login time
Have checked to make sure that you have your antivirus set correctly? We made changes to our antivirus and it decrease log in time significantly. VMware has a good document on what things to exclude to help performance.
We experienced similar times with Win10 1607. Always 1:00+, no matter what. Test machines had quick initial logons (15-20 secs), but a pool extended it to over the 1 minute mark. We switched to QuickPrep method of linked clone pools, and it brought the time down to around 20-30 seconds.
Make sure to follow this guide to create the mandatory profile for Windows 10, it's the only supported way:
My windows 10 as i'm working on as we speak use about 10-15 sec to log in, but still i have to figure out why it always "preparing windows", it shold be looging in a few seconds.
I beleive that my issue is that i used the standard user profile when i copied it, and therefor it always preparing windows.
I'll try to create a new mandatory profile, and give it a shot.
You also should consider to uninstall all unessesary Windows 10 apps using powershell(i have removed almost every app I found in my list):
And also blocking windows to automaticly install them again on your image:
The VMWare Optimization Toold does delete all the unwanted applications in such a fashion that they do not come back
We do use Quickprep
We did use sysprep with an answer file
The only thing we did not do is make the change in Active Directory to force a mandatory profile. We never did this with Win7 either
Still seeing 1:00+ login times
Try to force mandatory profile, i assume that you will get a lot quicker login time...
I use UEM, and with my policy(still testing before production) i have a first time logon at about 20-30 sec, and second one and so on, between 10-20 sec.
I find this acceptable.
But still, it may be longer, since i have to do some work to add more policy into my UEM and to my clients/users.
I may try mandatory profiles but they do have a downside
All of my desktops are non-persistent and used by 7-12 grade level students. I do use a group policy to do folder redirection so students do not lose work if they save it to the desktop or document folder. Also, under Win7 I have never used mandatory profiles and have 30 second login times. Windows 10 just seems to be a different beast. I have some additional testing and tweaking and will report back.
There is a good registry hack that I found but i have to relocate it. I had the same issue and it took my login down to 20 seconds when i was well over a minute. If anyone knows of it please post, otherwise i will look to find it.
This is one of them. Still looking for the other. http://www.sovsystems.com/vmware-horizon-view-and-long-login-times/
Here's a link to some information you may find helpful:
Have you considered using Persona Management to keep individual profiles in a common folder so they will be readily available for users when they log in?
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
We have been running Window 7 using View for several years. It takes about 35 seconds to login to a Win7 desktop. I am working on building a master image for Window 10. We are running View 7.0.2 under ESXi 6.0 Update 2.
Here is what I have done
I just stumble across this article
I enabled this key to get rid of the startup animation and it chopped nearly 25 seconds off the login time. Wow, never thought the login animation would have any affect on login time.
The only other problem I am having is once logged in the Win10 Start menu is sluggish. I have to click on it 2 or 3 times to get it to open. Might start another thread on this
Couple things on this. 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. Here are a few things we've found that made a difference:
These are our findings, your mileage may vary. Windows 10 is an incredibly frustrating experience with respect to VDI.
We are already running windows 10 LTSB with Horizon 7.0.3(upgraded from 7.0.2 today).
Also runnig UEM 9.1.
Running most of what you mention in your first section with GPO .
Running StartLayout from UEM-Config share, with policy in UEM.
I'll also upgrade vmware tools to 10.1 later today, on core and client.
But i'll follow your advice regarding optimizing tool.
Quickprep, I'll also have a closer look at this, just need to google a perfect recipe for this...
We are getting there, slowly...
Upgraded vmware tools to version 10.1
Upgrade Horizon from 7.0.2 to 7.0.3 (client and server)
Still the same logon time. And we also have a issue with a second delay when you click start menu, and with icons that are visible but not able to click them...