VDI on the Horizons
Rating: 8 out of 10
IncentivizedUse Cases and Deployment Scope
We utilize Horizons currently as an RDP solution for our work-from-home associates. This allows them to access internal resources, such as applications, intranet, etc, easier as if they were remoting into a physical machine in the office. This allows us to purchase lighter physical machines with less resources since most of the computing will be done on the virtual machine.
Pros
- Ability to utilize voice when remoting into the virtual machine.
- Ability to utilize physical peripherals of a machine.
- Easier options for end users to configure in order for them to utilize.
Cons
- Disconnection from Horizons Agent randomly which forces the VM to need to be restarted before Horizons can administer it again and end users can login.
- Speed when being utilized by end users compared to Microsoft RDP. Horizons is noticeably slower compared to Microsoft RDP.
- Failover functionality when VMs disconnect from agent.
Likelihood to Recommend
Horizons is great when you need to utilize voice on the VM. Horizons is also great when you need to utilize peripherals like a physical machine. Overall, Horizons is a pretty good solution when it functions properly. The constant disconnections from the agent get extremely annoying. It seems like the best way to resolve the issue is to restart the VM in vCenter. This wouldn't be an issue for a small team, but if you're running 100+ VMs and this is happening every day to so many machines, it gets irritating that you can't be more productive elsewhere because you have to resolve the agent issue by restarting the VM before you can work on more important tasks or projects.