Hi Steve,
From what I'm reading it sounds like 2 problems
1. Redirecting all the phones functions (including keypad+ and audio). In this case audio goes via the VM.
2. Redirecting just the keypad+ and terminating audio locally.
If I'm correct, I'd suggest getting 1. working first.
- Un-install PCoIP audio redirection on the VM (brute force approach to removing other audio devices)
- Put in an IncludeVidPid rule to allow the phone
- Connect to a desktop
- Close Lync and exit the systray app too
- Redirect the device
- Check that the device looks good in Device Manager. Check Device Manager->View->Devices by connection. Open the VMware View Virtual USB Host Controller->...->... and check that the composite child devices for the audio and keypad+ look correct.
- As a further check (I have not tried this with a phone, but it might work); select the phone as the default audio in and out device and try to record and play some sounds
- Open Lync
- Check that Lync has found the phone and recognised it as such
- Make a call etc.
If this works then, do the same but do not close Lync. We have seen a problem where by Lync sometimes does not detect the device as a "handset" phone if Lync is running when the device is plugged in.
If after 'Check that the device looks good in Device Manager' you think the device hasn't redirected correctly; can you send a registry export from a 'real' machine that has had the phone plugged into and working, and from the VM please. Export HKLM\System\CurrentControlSet\Enum\USB.
Thanks Pete