Taking these points in order, for existing View 5 and below releases:
- No HTML access for terminalservers
- No PCoIP for terminalservers
Both the View HTML access and PCoIP remoting are based on remoting the VM console session, you can't use PCoIP with terminal server sessions today no matter how much you hack at the installer - new technology is required to run as terminal server sessions in a pure way as you can only ever have one "physical" console per windows machine. I don't see this being a feature small enough to be in a minor release.
- No Windows Server 2012
For existing features this is really a qualification exercise, so I can't really comment on that.
- Printing on terminlservers managed by View is not usable without having additional ThinPrint engines and licenses
As I commented on another thread, VMware have a licensing agreement to provide ThinPrint functionality for VDI sessions but this does not extend to terminal services. Since terminal servers are supported with RDP only, you can either use the built-in RDP printer redirection (if that provides sufficient functionality for you) or get a thirdparty license.
- only single servers can be published, it seems to not be possible to have multiple servers published by assigning them to single or multiple user-groups.
You definitely can have multiple terminal servers in a View pool, new connections will be load balanced amongst servers based on the number of free session slots on each server.
- by accessing single systems through Horizon Workspace there is no printing and audio support
This I can't comment on in too much detail as it's not View functionality, but if the connection is RDP then printing and audio are natively supported in the protocol. Or are you talking about using HTML access (which isn't supported)?