Does Quest bidirectional audio continue to work when a session is disconnected from one local machine and the same session then reconnected from another machine?
I understand this to be caused by different operating systems having different client modules or DLL's for the virtual channel. When a remote connection is first set up, the settings and dll that were first initialised will be the settings / module that the connection will use permanently, although the server side module (on vdi) will remain the same, attempting to swap to another machine may break this depending on the client module on the new machine.
Only works when connecting from macines that share the same OS as the originating device regardless of the physical hardware onboard.
Win7 - Win 7 = OK
Win7 - XP = Doesn't work
I've tested this on two Windows 7 Enterprise Local machines with identical hardware.
I connected to a Windows 7 Enterprise desktop (VDI) using the Quest Bidirectional audio feature turned on.
I was able to keep a Skype call running after disconnecting a session from PC A to PC B.
I also saw that the Quest Remote Audio device stayed in the device list in Microsoft Lync.
I tried locking my VDI before I left work and logged on from home with a different laptop and sound card and I could still see the Quest Remote Audio device.
I haven't tested XP - Win 7