Leostream Tames VDI Connection

Leostream Tames VDI Connection

By Cameron Sturdevant

Leostream Connection Broker

The Connection Broker is the heart of the Leostream offering and is seen here running as a virtual machine in my VMware vSphere 4 infrastructure.

More granular administration

Administration is more fine grained in this version of the Connection Broker. Here you see the creation of a sub-administrator. In the fields along the lower left you see the choices available for a variety of Connection Broker actions. The inset (lower right) shows that the role is available for assignment.

Administrators in action

Here you see that I’ve assigned the more restriced “eweek division admin” role to adminstrator accounts overseeint three areas of my test environment; accounting, development, and sales.

User policies

Here you see the beginning of a policy that describes how development users are assigned and allowed to use virtual desktop systems. The policy is itself made up of other rules, such as which desktop systems are assigned to the development resource pool.

User overview

Here you see current user, desktop and other usage information along with basic policy information.

System log

Here you see recent activity on handled by the Connection Broker, including a lot of activity by test user “camjhawks.”

Status report

The Leostream Connection Broker provides good overview reports on policies and virtual desktop usage.

Resource pools

I’ve clicked on the number 4 in the “total” column to reveal the virtual desktop systems currently assigned to the “accounting” group.

Resource destkops

Here’s a list of all the virtual machines in my VMware vSphere 4 infrastructure. Since this is a test environment, there are a number of systems that I would normally not mix with my VDI deployment, many of those are shown here as “stopped.”

Clients

The Connection Broker tracks connection method and other information about virtual desktop access. Here you see that I’ve connected from a variety of thin client and web-based connections as well as the Leostream Connect client.

Client locations

Here you see greater detail about the connection made via the HP t5440 thin client.

User authentication

I used our Microsoft Active Directory infrastructure to authenticate users. Leostream Connection Broker can use a variety of LDAP-based authentication systems.

System Log

The Connection Broker tracks administrative and usage data for detailed reports.

General Configuration

Connection Broker general configuration sets the stage for all subsequent use of the product. Here you se that I’ve “enabled virtual provisioning from templates” for use in my VMware environment.

dev-342

: Here you see my imaginary test user accessing a virtual desktop from the developers pool.

Switch User

Here you see me logging in via the Leostream Connect software installed on a Windows fat client.

HP Control Center

Here you see the connections offerings from the HP t5540 thin client. The Leostream client, along with many other connection choices, is built-in to this thin client.

Connected

It’s nearly impossible to tell, but my imaginary test user is accessing a virtual machine from the developer pool via a connection brokered by Leostream to the HP thin client.