We had been waiting anxiously for AppVolumes 2.10 sup portability so we cant implement our architecture into our own internal VDI (upgrading from view 5.3).
We would like to see the login times under 30 seconds.
Without any appstacks attached 18 seconds to login (not using any roaming profile or uia+profile), with 1-2 stacks attached we saw anywhere up to 5 minutes to login with a baseline out of the box appvolumes agent configuration on the VDI's.
After tweaking registry agent keys (additional Notes), I can get it to around 55-60 seconds with the same configuration but no writable volume.
I am experiencing very long login times up to 5 minutes for Windows 10 VDI's using the following configurations:
* Windows 10 (64bit, 6gb, nVidia vGPU)
* App-volumes 2.10
* Horizon View 6.2 Pooled Linked Clones
* ESXi 6u1
* UEM 8.7
I have also confirmed by installing the same applications into the direct image that login times around 18-25 seconds, so i firmly believe this is an issue with the App-Volumes agent. I can confirm via vCenter the AppStacks get attached to the VM's in under 3 seconds each.
I have attempted to tune the AppVolumes svservice (via registry keys attached here)
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\svservice\Parameters]
"Hypervisor"="vcenter"
"Manager1"="LEONVANWYK"
"RebootAfterDetach"=dword:00000000
"VolAttachMessageOn"=dword:00000000
"LogFileSizeInKB"=dword:00002048
"DomainNameWaitTimeOut"=dword:00000003
"WaitForFirstVolumeOnly"=dword:00000001
"HidePopups"=dword:00000001
"DisableRunKeys"=dword:00000001
"VolDelayLoadTime"=dword:00000000
"MaxDelayTimeoutS"=dword:00000002
"VolWaitTimeout"=dword:00000001
"ConnectTimeOutMs"=dword:00000100
"DisableAutoStartServices"=dword:00000001
"ResolveTimeOutMs"=dword:00000100
"WaitForFirstVolumeOnlyValue"=dword:00000001
Also looking through the svservice.log it appears there is 22-32 seconds of the agent doing nothing....