Slow Profile Creation and Logon Time with App Volumes 2.10 and Windows 10

[arosasoto]

My environment is vSphere 6.0 update 1, Horizon View 6.2, App Volumes 2.10, UEM 8.7 and Windows 10 x64 VDI. I am experiencing really slow first time profile creation and slow logon times when app stacks are attached. If I remove all app stacks logon times are normal. By slow I mean 5 minutes for initial profile creation and over 60 seconds logon time after subsequent logons. By normal I mean less than 30 seconds logon times and initial profile creation when no app stacks are attached.

[Ray_handels]

Just for the record, because I have the gut feeling that people are mixing things up here.

There are 2 "issues" that delay logon times for Appvolumes.

The first one is the slow reconfigure of the VDI's. This issue has been fixed by a patch in version 6.0 vanilla, 6.0 U1 and as it seems (looking at soppamanoz post) that it is also fixed in U2. We did hear that this was build into this version so one has to assume it is indeed fixed. And this had nothing to do with Appvolumes itself but more with the way VSphere did reconfigures of adding disks when the machine was turned on. We tested it with 8 randomly created disk with a machine without Appvolumes and saw the exact same behaviour.

The second one is that Appvolumes needs to attach Appstacks and presumably a writable volume to the desktop.

Any or every way you look at it logon will always be slower than  a machine without Appstacks due to the simple fact that Appvolumes Agent needs to speak to the manager to ask which Appstacks needs to be attached and the manager needs to speak to either VSphere or ESX to reconfigure the machine (which will always take 3 seconds to do if Appstack is assigned to a user). So looking at it like that logon will always be delayed by 10 seconds just to get through that process..

If you have a writable volume your profile also needs to be loaded into the non persistent machine and Appvolumes Agent will wait for it to be merged before it will log in. Otherwise you will get profile corruption.

The fastest we are able to log in to a VDI machine without writable volume and with mandatory profile is about 30 seconds. We also do apply user policies during logon which also takes up time (and no, these are NOT saved into the writable volume).

[ch4mp10n]

@Ray_handels.

This is exactly what I was getting at, I am running ESXi 6.0 u1, and do see a 3 second attachment time per Stack/Writable.

Im running Writable Volumes UIA without Profile.... I have literally 5 second login times for mandatory Profiles on Windows 8.1, Window 10 about 15. As soon as attaching a writable ontop it can increase the minimum login time to add an additional 25-30 seconds, for each OS then and additional 15 sec+ for each AppStack, these are extremely optimized profiles.

To break that down

Win8.1:

5 Seconds login with Mandatory profile

30-35 Seconds login with Mandatory profile and Writable.

45-120 Seconds login with Mandatory profile, writable and 1-3 AppStacks.

Win10:

15 Seconds login with Mandatory profile

40-45 Seconds login with Mandatory profile and Writable.

55-130 Seconds login with Mandatory profile, writable and 1-3 AppStacks.

I don't know if this is acceptable behaviour, but @ the end of the day its about the user experience... Running the above in a non-persistent pool + refresh, with UEM id expect closer login times to that of the mandatory profiles where users login every morning and have to wait that long to login seems very excessive and time consuming.

I have gone with no AppStacks, just a Writable volume for user personalization that alone speeds up the login time for them by 40-50% then having them attached.

[Ray_handels]

Hey ch4mp10n,

The 3 second timeout per attach has been resolved so it seems to me that you can atleast enchance that logon time. When you have 3 appstacks and a writable reconfigure time will be 2 to 3 seconds instead of about 15 seconds.

Also, when using a writable volume the agent will wait for the writable volume to be merged with the operating system. My guess is that it does this because when you do have profile in your writable volume it must wait for the volume due to profile issues.

But that being said, your logon time seems way to long for me to be honest.

What happens if you take 3 appstacks without writable, will logon be quicker than? The logon process doesn't have to wait for the writable then. Also, is the writable created before you log in? You can also add a group to the Appvolumes Manager ans let creation happen during logon.

As said. Normally it should add about 10 seconds to the logon process with Appvlumes and than about 1 to 2 seconds per appstack, that's about it, policies not taken into account.

[Gagan201110141]

Hello

I am running into the same issues with the VERY VERY Slow log in time and it's %100 due to app Volumes 2.12 and Windows 10

We have our golden images without app Volumes 2.12 log in time is about 55 seconds

This is Windows 10, Office 2017 and Browsers very simple golden image setup on AD

We want to create all of our apps and give them to different security groups. Great

This is Windows 10, Office 2017 and Browsers very simple golden image with Volumes 2.12 agent setup on AD

5 minutes to Log in

6 app's setup to my security group

I have a Large Windows 10 image with Volumes 2.12

That takes 10 minutes to load up this Image already has most of the apps just using a few from App Vol it's by far the slowest

8 app's setup to my security group

Right now it's not a huge deal as it's being used in a open KISOK lab environment but we are moving away from that.  I have them load at 2 AM and they are up for the day and get rebooted

We want to have all user's log in and need to find a way to speed up the log in process.