Mike,
Sounds like we're in similar situations -- Unidesk, View, and the Teradici audio driver. I attempted to deploy version 1.2.0 of the Teradici Audio drivers with the View Agent (versions 5.1.1, 5.1.2, or 5.2.0), with any of those versions of the agent, the driver wouldn't be loaded on my virtual desktops and there would be an error in the device manager. The detailed status message on that was "Windows cannot verfiy the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)".
I went back to version 1.1.0 of the Teradici audio driver and was able to use it with out problems on my 5.1.1, 5.1.3, and 5.2.0 agent layers. Obviously the downside of this, I can tell you I had the issue, but never figured out where it was coming from.
To your other question about deploying or not deploying the View Agent audio drivers, I've done installs of the Teradici audio driver both within and without the View audio driver installed. Currently I'm doing all of my installs of the View agent without the View agent audio driver, and just installing the Teradici driver. This was for two reasons: 1) I was seeing cases where the default audio device wasn't always the Teradici driver (of course this surfaced in the locations where I NEEDED it to be the default and 2) there's some combintions of the View agent and the Teradici audio driver where installing the Teradici audio results in the View audio device no longer working and thus your end-users end up with no sound at all. -- Teradici or VMware had a kb article about this, I don't off-hand remember the exact version(s) involved. So far with just the Teradici audio drivers installed, I haven't had any sound related issues reported to me.
Jeremy Ey