Forum Discussion
(WVD) Windows Virtual Desktop USB Redirection Full
ahewitt BigHand themselves said that they have reported to Microsoft an issue with the BigHand audio channel not reconnecting.
They stated that
"Although the BigHand audio channel will work as expected during the first logon of the day, if the Azure Remote Desktop session is later terminated or disconnected, the audio channel will fail to automatically initialise when a subsequent connection is established"
It is 100% possible this has already been fixed in the recent Remote Desktop Client updates so you may not see it anymore.
They gave a workaround to basically kill all the msrdc.exe processes on the local machine, then restart the BigHand client if it is still running to start a new virtual channel for your local recording and playback.
I am not actually sure if this error occurs for many people. I would imagine one of your users would have seen this by now. . .
James
Jamesatighe Hi James, having done some significant testing i believe this error relates to these event ids 227,228, 101 in RemoteDesktopServices-RdpCoreTS On the host
Event ID 227 Failed GetConnectionProperty' in CUMRDPConnection::QueryProperty at 3008 err=[0x80004001]
Event ID 227 'Failed CreateVirtualChannel call on this Connections Stack' in CUMRDPConnection::CreateVirtualChannel at 2622 err=[0xd0000001]
Event ID 228 Disconnect trace:CUMRDPConnection Disconnect trace:'calling spGfxPlugin->PreDisconnect()' in CUMRDPConnection::PreDisconnect at 5073 err=[0x0], Error code:0x0
I have a ticket logged with Microsoft relating to this and will post the output here.
Jamesatighe Hi James. The other thing i noticed yesterday. I was having inconsistent results trying to reproduce the problem. What i found was if i closed the remote app (which is running BigHand). I'm monitoring msrdc.exe using https://www.nirsoft.net/utils/cports.html current ports. I can see after about 15 seconds that there are some additional connections that are made and dropped. Then if i try and open the published app again after that, i'm prompted for credentials. I enter them, then it fails and BigHand audio does not work. If you reopen before that 15 second window the problem doesn't occur and i'm also NOT prompted for credentials. If you stay persistently connected. It doesn't seem to occur. You can probably replicate the behaviour yourself, assuming its not some setting we have that's causing it. Its like the remote host is somehow closing the connection and the client is not handling that correctly.
I think the reason we are seeing more of the problem at the moment is many users working from home with poor broadband connections.
- This is interesting to read. So it is clearly an issue with the MSDRC process somehow not releasing the audio channel.
Be interesting to see what MS come back with as seems to be an issue with anything using audio connections in this way.