App Volumes 3.0 - Slow Logon Times

[jsinclair]

I'm testing out App Volumes 3.0 with Horizon 7, ESXi/vSphere 6 up2, and have noticed terrible performance logging in with just 2 app stacks attached. On average, it takes over 4 minutes just to login and the App Volumes Service is taking a majority of the time. Once the desktop logs in, it still is unusable for a couple of minutes. Has anyone else noticed this? I love the new concept, but I feel like this has gone backwards.

[lvanek]

i had a deployment just have this issue.

in the end it was not horizon, app vol or UEM. one DC out of their 8 had a outdated SYSVOL directory. this caused other DC's to respond with shitty login responses, login times would range from 30seconds to 3/4mins. upon rebooting all the DC's and addressing the sysvol issues the login time dropped to 16-22 seconds consistently.

[jsinclair]

I'll have to give that a shot. The 2.10 environment is working just fine, and I have verbose messages turned on and it gets stuck on the App Volumes Service message. Did yours do the same thing?

[jsinclair]

Just tried it with no App Stacks assigned and the logon time was less than 10 seconds, so I'm not sure the DC's have anything to do with it.

[Jason_Marshall]

Win7 or Win10? There is a known issue with Win10 and first logins at this time.

[dalexiev]

How did you determine the Sysvol is outdated? What if I have 80 DCs

[dalexiev]

Win 7 x86 desktops; AppVol3, ESXi6u2, View 6.2, auto, floating, linked-clone pool

on first logon - av3 server not reachable

reboot vm

logon fast, make some changes, reboot

stuck on "welcome"

Once reset this VM from "welcome-stuck" this user will be logging fast any time in the future (so far)

Add a new user in the AppStack assignment AD group and the same steps above have to be repeated, obviously manually

Not good.

Anyone having this issue?

[lvanek]

i was on the phone with support yesterday, their own tech support said DO NOT USE 3.0 in production environment. It was not released as a polished ready to use product. They said it was released to get beta and users doing testing with it to figure out some bugs, and how they want to approach some issues.

[cbSean]

I am seeing the exact same issues.  Logging in with no applications attached takes a few seconds, however if I attach any number of App Stacks it jumps up to minutes.  Windows 7 x64 with Instant Clones.

So Delving a bit deeper according the log it takes 3 minutes from start to finish with the Appvol stuff from initial login.  But going through the log there is a 2 minute gap from where it fails to execute a bat file.

[2016-05-05 15:11:16.072 UTC] [svservice:P892:T1072] RunScript: user script (event allvolattached) on "\SnapVolumesTemp\MountPoints\{25e8c1db-1217-11e6-9122-005056a728b7}\" go processing.

[2016-05-05 15:11:16.072 UTC] [svservice:P892:T1072] RunExecutableAsUser: Path "\SnapVolumesTemp\MountPoints\{25e8c1db-1217-11e6-9122-005056a728b7}\allvolattached.bat"

[2016-05-05 15:11:16.119 UTC] [svservice:1072] RunExecutableAsUser failed: no session available

[2016-05-05 15:11:16.119 UTC] [svservice:P892:T1072] Sending reply to Command 163 (Message 6, Status 0x00000000)

[2016-05-05 15:13:12.637 UTC] [svservice:P892:T3832] OnStartShell called (Session ID 1, Handle 0000000000416FB0, Params 0000000006F9E9F8, Context 0000000000000000)

[jsinclair]

I gave up on 3.0 and went back to 2.10. Like others have said, it's definitely not a polished product and still needs a lot of work.