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. More »
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.
Start the vWorkspace Management Console and you will be presented with the Quick Start Wizard.
I generally do not use the Wizard so I will check the “Don’t show this wizard automatically” and then click close. Let’s start with the File Menu option in the top line menu.
There are four options: Current user sessions…
and Database Configuration…
The Actions file menu is created dynamically when an abject is selected in the left-hand pane. Let’s configure the vWorkspace Farm. Click the top node of the left-hand pane then Actions and Farm Properties.
The first tab of the Farm Properties allow the farm name to be renamed. I named my farm Beta 8.
The second tab is Reporting Database which allows an administrator to setup data expiration and data purging. The report database has not been configured so there are no options active.
The next tab allows for configuring management domains. For my installation, the local machine (BROKER) and my domain (VTSCOTT) have been configured.
vWorkspace can be configured for two-factor authentication using the next tab. I do not have this function in my lab environment.
The next configuration option is Anonymous Login. I do not recommend leveraging this function but it is available.
The final Farm Properties option is called Other Settings. On this tab, pop-up messages can be reset and the recent lists can be cleared.
At this point, we have licensed the environment and have configured the Farm Properties.
In the first post of this series, we installed vWorkspace. After successful installation, there will be two shortcuts available on server’s desktop.
Double click the vWorkspace Management Console shortcut in order to start the console.
Licenses need to be added to the environment. Click OK to acknowledge the window.
Click the Add License… button.
Browse to the location on the license file. Highlight it then click Open.
You should be presented with a confirmation that the license has been added. Click OK to return to the Licensing window.
The beta license includes 200 licenses of the Enterprise edition of vWorkspace. Please note the beta licenses expire April 30, 2013. Click Close to get to the Management Console.