Run sudo vim /etc/vmware/nf and uncomment the necessary line for your desktop environment. Now set the correct SSO Desktop Type for the View Agent (see page 18 and 107).
Now that your iso is ready to be mounted let´s create a new Virtual Machine. CentOS 8.0 (at this time only 8.0 is supported!):.In this post, I´ll concentrate just on Ubuntu 18.04 LTS and CentOS 8.0 but in case that this is not your pick, you´ll find all Linux distributions that are supported for Horizon Agent on page 14 of the official installation guide here: “Setting Up Horizon 7 for Linux Desktops”.
Install a Linux-VM 2.1 Select a Linux Distribution
Download and install the Connection Server v.7.11 installer (VMware-Horizon-Connection-Server-x86_64-7.11.0.exe / ~250 MB).The Connection Server cannot be installed on a Domain Controller (e.g.
Windows Server VM (W2k8R2 - W2k19) which is part of a MS Domain.If all PREREQUISITES are given ( Figure I: Mindnode Development Desktop), the installation itself is really quick and simple. Source: Digital Workspace Tech Zone - VMware Workspace ONE and VMware Horizon Reference Architecture Figure II: VMware Horizon Client authenticating to a Connection Server The VMware Horizon Connection Server is the broker for your client connections which authenticates users through Windows Active Directory and directs the request to the appropriate virtual machine ( Figure II). Setup VMware Horizon Connection Server (v.7.11) Video I: SSO and HTML5 feature in VMware Horizon My Mindnodeĭownload on Figure I: Mindnode Development Desktop 1. Please give 3 minutes of your precious time for the following recording to get an idea of what you can expect at the end of these three articles.
This will include the setup of a VMware Horizon Connection Server (broker for client connections), the installation, configuration and preperation of the Linux distributions Ubuntu and CentOS and how you can turn them into a universal workbench for development and operations.
With this series of posts, I´d like to demonstrate how you can build such an environment for the described use-cases on your own and what´s necessary to offer it as a VDI desktop to your team or external employers. SRE´s, PRE´s) and provide a environment to them, that is on the one hand organization compliant and on the other hand offers sufficient flexibility and appropriate tools to these developers and engineers. Organizations today will perhaps reach a point, where it will be necessary to employ external developers and engineers (e.g. Building the OVA takes time.Īnd another very important aspect of having a “Developer-friendly” environment quickly available comes into play! Let´s consider the rise of Kubernetes for example. I recently had to repeatedly create new versions of an OVA for testing purposes as changes were made to the code.Deploying an OVA (Open virtualization Appliance) which is located locally on your workstation into your remote Datacenter via VPN isn´t really a good idea.Having a suitable Jumphost, Remotehost, Development-workstation or however you like to call the system that you connect to, to have access to the appropriate tools and applications available, comes in very handy when you reach the limits or get stuck with your local machine. Big thanks to Gerrit Lehr, Hilko Lantinga and Alex Lopez for your valuable input and feedback.