As we all know, the largest cost component of virtualization is typically shared storage. Be it Fibre Channel, NAS or iSCSI, it’s all expensive! Let alone a flash based array like Tinri or Whiptail.
One of the use cases of our OCP (Open Compute Platform) Container (above) gear is to test VMware’s new vSAN product. With vSAN, VMware not only removes the expensive disk cost out of the picture, but they also lock you in to using their Hypervisor exclusively. Continue reading “VMware vSAN on Open Compute”
Continuing with the basic foundation setup, it is time to setup the Web Access interface. At this point the vWorkspace Connectors can be used to connect to the environment but for most implementations, the Web Access interface is the preferred option.
The Web Access configuration settings are located in the vWorkspace Console.The user interface is not consistent in this section. Click the Website name in the right panel and then click Properties. The Web Access Properties window is presented. Continue reading “Configure vWorkspace Web Access”
In my previous post, we walked through configuring the farm settings. The next level of granular control for vWorkspace is Locations. A Location represents a group of one or more data centers and the desktops within those data centers. Each location can contain Connection Brokers, Session Hosts, Virtualization Hosts, and desktops. Locations can also be used to configure administrator delegation.
The top-level Locations Properties are settings that apply to all locations.
In general, I leave the defaults. To allow for remote administration control, go to the RDP Connection Restrictions tab then check Enable RDP remote administration control
The other item I configure is to establish a process ID for vWorkspace in order to remove computers from Active Directory.
Now that the global Location properties are set, we can make changes to the initially created Location.
There are just a few available options at the Location level. Let’s change the Location Name from the default Location1 to a more meaningful name.
If required, a Location specific administrative account can be created. In order to set granular Location permissions, the Permissions tab is used.
In my test environment, there is a single Location that has the server BROKER that is configured as a connection broker and as a session host.
In the next post, I will walk through setting up web access.