We have an odd scenario. Running a fresh install of AV 2.11
Win7 VDI Linked clones w/Horizon View 6.2.2
Everything appears to work fine when a user logs off, however we discovered if a user disconnects and leaves a stale session things go sideways.
We configured Horizon View to logoff users (thus triggering a dismount of AS and WV) stale sessions after 5 minutes.
Horizon View appears to do its job, logging off the user and making the VDI available. However that logoff process triggered by View is not causing AV to dismount. A review of the AV agent log on the VDI at the time of dismount reveals what I believe is the issue:
User logout URL: /user-logout?name=svservice&uuid=423321d7-aae0-1cf1-650c-0c679f715bf8&status=0&osver=6.1.7601&sp=1.0&suite=256&product=1&arch=9&proc=1&agentver=2.11.0.83U&username=XXXX&domain=XXX&userdomain=XXX&workstation=XXXX&machinesid=S-1-5-21-457945878-1175663176-964313020
[2016-06-24 17:31:05.261 UTC] [svservice:P916:T4408] [0] Connecting to FQDN OF OUR AV MANAGERt:443 using HTTPS (attempt 1)
[2016-06-24 17:31:05.308 UTC] [svservice:4408] HttpInitializeRequest: WinHttpSendRequest failed (error 2148074273)
[2016-06-24 17:31:05.308 UTC] [svservice:P916:T4408] Message: "Connection Error (Manager "FQDN OF OUR AV MANAGER"):
Unable to contact App Volumes Manager." (hToken FFFFFFFFFFFFFFFF)
[2016-06-24 17:31:05.308 UTC] [svservice:P916:T4408] RunExecutableAsUser: Path "C:\Program Files (x86)\CloudVolumes\Agent\svservice.exe"
[2016-06-24 17:31:05.308 UTC] [svservice:P916:T4408] RunExecutableAsUser: CommandLine svservice.exe message "Connection Error (Manager "FQDN OF OUR AV MANAGER"):
Unable to contact App Volumes Manager."
[2016-06-24 17:31:05.323 UTC] [svservice:4408] RunExecutableAsUser failed: no session available
[2016-06-24 17:31:05.323 UTC] [svservice:4408] User logout over HTTP failed
[2016-06-24 17:31:05.323 UTC] [svservice:P916:T4408] HttpLogoutWorker: failed (user logout)
Before you ask yes ports 443 and 80 have been verified as open. After Horizon View shows the VDI as available after logging the user off AV manager still shows the stack and writable volume attached.
Thoughts?? Suggestions?