VMWare Horizon requires its own server (much like vSphere), correct?
You are correct. Horizon View does require its own infrastructure like Connection Brokers (Connection Servers)
VMWare Horizon does not publish applications on its own. You still need Remote Desktop licenses for that, correct?
Horizon View is VDI, however does have now in version 6 the ability to publish RDSH Apps using their native protocol and present them in the same portal.
VMWare Horizon does not allow multiple users to simultaneously access a single resource at once, correct?
(So when user A is accessing Microsoft Word located on guest A, user B cannot access MS Word unless there is another copy of it on another guest, or unless we've got a volume license in a RDS scenario.)
Now Horizon View does allow RDS Sessions as well again using its PCoIP protocol. But using VDI each user gets there own desktop at a time.
VMWare Horizon does not provide access to an individual desktop across multiple guest operating systems, beyond what would be capable using a roaming profile, correct?
(So that user A's desktop is tied to guest A, unless there is a roaming profile scenario. Likewise, if user A is logged onto guest A, user B cannot use guest A until user A has logged off.)
This is true if you prevent a user from accessing more than 1 Pool at a time. Within 1 Desktop pool, a user can only have a single session.
I guess I don't see what Horizon gets my clients that isn't already being achieved with Remote Desktop Services, other than a convenient portal and better compatibility with non-MS brand tablets/phones.
I think you need to compare protocols, and what the use case is for remote desktops/VDI. Also, there are applications that do not support server OS or in a Remote Desktop Services scenario. You also have to consider that a down Remote Desktop Host takes down many more sessions than 1 Virtual Desktop in VDI. These are just a few differences.
Hope this helps.
Can someone please enlighten me?
.png "twrangham"){kind=avatar}
