Setting up vmware horizon suite license#
You can even free-up a SQL Server license saving a lot more. One of the arguments for using the vCSA over a Windows-based vCenter server is that you free-up a Windows license, saving quite a bit. Parts of your VDI environment will depend on whether you decide to create a Windows-based vCenter Server or decide to use the vCenter Server Appliance (vCSA). Set up a pair of inside connection servers, load balanced. Go crazy? Set up a security server paired to a connection server. Set up a couple of connection servers, one paired with the security server and one not, for connections originating from inside. NAT incoming and outgoing connections to it.
Setting up vmware horizon suite full#
You're good with vSphere 6, and no teething pains with that.īest practice in a lab? Set up a connection server, a security server, a SQL Server, Composer, if you plan to use linked clones, and build a master desktop image, which you will keep safe and use to create masters for linked clones, full clones and instant clones.īest practice all-out? Set up a DMZ. 6.5 is about 24 hours old as I write this. Using VMware's interoperability matrix, verify that Horizon 7.x or Horizon View 6.x will run with a vSphere 6.5 back-end. Regarding vSAN, yes, Horizon desktops can and will use vSAN for back-end storage. No virtual servers running on these hosts. The only restraint is number of desktop VMs and, oh, desktops only. For desktops, ESXi is licensed in a Desktop Host model where you can run X number of desktop VMs on any number of hosts (with any number of cores, RAM, etc.). Licensing for ESXi is different for Horizon VDI than for the usual server-oriented virtualization. I hate to put this first, but licensing has a lot to do with your host and cluster configuration.
0 kommentar(er)
