BSOD when trying to kick off a disconnected user session

[cyberfed2727]

We are running AV 2.10 in a lab. We are using Horizon View 6.2.2 to deploy VDIs.

I have noticed a problem now, if we have an end user who connects to a VDI and gets his App Stack and Writable Volume deployed and then lets his session disconnect. If I then try to kick him off (by logging into the Win7 VDI machine expecting it to prompt me saying "hey another is connected would like to kick him off?") the machine blue screens.

I do not see any way of detaching an Appstack or writable volume for a disconnected user session. On the BSOD machine I see a ton of the following event logs:

EVENT ID 15 - Disk

The device \Device\Harddisk2\DR2, is not ready for access yet

EVENT ID 57 - NTFS

The system failed to flush data to the transaction log. Corruption may occur.

EVENT ID 26 - APPLICATION POPUP

Windows Delayed write failed : Exception processing message 0xc000a082

Thoughts?

My concern is often we have to recompose our VDI pools, sometimes with users disconnected and we give them the boot. However now with AV we can't have the VDI blue screening every time we have to kick someone off. As I understand all writable volumes need to be detached prior to a recompose operation. I'm trying to find a way of detaching those volumes for disconnected end user sessions without the machine taking a BSOD.

[Ray_handels]

Hey Cyberfed,

There is no need to log off the users. You can simply recompose a machine, even if an appstack or writable volume is attached. When the machine comes back up again and the disks are still attached the Appvolumes manager will see this and detach the stacks during startup.

The only thing you should NOT be doing is to remove the VDI machine while the writable volume is attached, this could cause a deletion of the writable.

Regarding the bluescreen, I have never experienced that issue when logging into a machine when another user is already logged in. It could be that Appvolumes is trying to attach your writable volume as well (it needs to do this prior to login) and that it fails in doing so.

What happens if you try to login with a locally created admin account?

[cyberfed2727]

Interesting I was just going by the official documentation. It states that WVs should always be detached prior to a recompose/refresh operation.

I was logging on to a VDI with an admin account that is not configured in AV's to push any app stack or WV to my account when the BSOD occurred.

Weird.