VMworld
Up to Discussions in Desktop Virtualization

This Question is Possibly Answered

1 "correct" answer available (4 pts) 2 "helpful" answers available (2 pts)
4 Replies Last post: May 27, 2008 8:03 AM by Patrick Rouse  
Click to view Colin DeSouza's profile Candidate
Colin DeSouza
1 posts since
Mar 11, 2008

Mar 11, 2008 12:08 PM

Connection Borker Required ?

Is a connection broker required with a VDI infrastructure ?
Click to view Axis's profile Apprentice
Axis
7 posts since
Feb 14, 2008
1. Mar 18, 2008 4:25 PM in response to: Colin DeSouza
Re: Connection Borker Required ?
It is not necessary but ......

Connection Broker or VDM2 is used to link users of AD with the virtual machines differently this allowance is manual.

Another important thing VDM2 acquiring licenses are obtained VI3 Enteprise much more economical exclusively for the vistualization of dasktops.

sorry my english (powered by google) http://www.vmworld.com/vmworld/images/emoticons/happy.gif

check this link for more infromation of Connection Broker http://www.theaxis.com.ar/vmware/Technical%20Deep%20Dive.pdf


-Albert

Click to view Oliphant's profile Apprentice
Oliphant
14 posts since
Mar 7, 2008
2. May 8, 2008 1:48 AM in response to: Colin DeSouza
Re: Connection Borker Required ?
No it is not but you need to look at your entire infrastructure. We uses it because we have over 300 desktops(using wyse) and it would be dificult otherwise. We use leostream - which is good. So if you want hassle free management, I would suggest you get one.
Click to view HHtony's profile Apprentice
HHtony
3 posts since
Sep 10, 2007
3. May 20, 2008 9:58 AM in response to: Oliphant
Re: Connection Borker Required ?
I disagree, if you plan correctly, no broker is ever needed. We have over 1700 virtual desktops, without a broker. But our environment i.e. our apps, force us to use a 1 to 1 connection. If you don't need ever ysession connected all the time you can have fewer sessions and use the broker to create a connection to the first available desktop. This is known as pooling.
Click to view Patrick Rouse's profile Apprentice
Patrick Rouse
7 posts since
May 27, 2008
4. May 27, 2008 8:03 AM in response to: HHtony
Re: Connection Borker Required ?

A connection broker is not "required", just like Active Directory is not required... it just depends on how much time you have to manage an environment, and what your remote access requirements are. Things that our connection broker helps with are

1. Provisioning/cloning of VMs across multiple resource pools and datastores (simultaneously) & automaticatic provisioning of new VMs before they are needed.

2. Automatic creation/deletion of AD Computer Objects in any OU one specifies

3. Power Management, i.e. powering on a machine when it's requested by a client, suspending the machine when it's not in use, resuming the machine when requested....

4. End-to-end Universal Printer Driver, so no printer drivers need to be installed on the VMs

5. Dynamic management of the Remote Desktop Users Group

6. Hybrid User Profile Management, so Roaming Profiles do not need to be used and user state can be de-coupled from the VM

7. Providing a single point of access to clients via Web Portal, Thin Client.... users need not know the name or IP Address of their VM, and secure remote access over SSL w/o requiring a VPN connection.

8. Temporary VM assignment, so users can get a different VM each time they logon, thus reducing the total number of VMs required to support users in multiple shifts

9. Fully redundant connection brokers, so there is no single point of failure, or bottleneck

10. RDP Protocol Enhancements for True Multi-monitor support, latency masking, bi-directional audio, Multimedia Redirection, USB handheld Sync...

11. User Environment configuration & lockdown

So although a connection broker may not be required, they surely can make life for IT and end users easier.

A connection broker comparison can be found here:

http://blogs.inside.quest.com/provision/2008/05/24/virtual-desktop-infrastructure-vdi-connection-broker-comparison/


Patrick Rouse
Microsoft MVP - Terminal Server
Sr. Sales Engineer, Western USA & Canada
Quest Software, Provision Networks Division
Virtual Client Solutions
(619) 994-5507
http://www.provisionnetworks.com
http://blogs.inside.quest.com/provision

Actions

More Like This