[THIN] Re: Windows 2008 R2 VDI Broker
- From: "Joe Shonk" <joe.shonk@xxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Fri, 26 Feb 2010 15:09:00 -0700
The MS VDI solution integrates with RDS Gateway (formerly TS Gateway).
Think of RDS Gateway as MS' version of Citrix Secure Gateway. Aside from
that, all VDI solution connect the clients directly to desktop.
If you attended BriForum 2009, there is a session and demo I did on Beta
release. If not, I can send you the slide deck that shows and describes
traffic flow, etc..
Joe
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Nick Smith
Sent: Friday, February 26, 2010 1:58 PM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Windows 2008 R2 VDI Broker
We currently use Quest vWorkspace for provisioning and providing access to
our VDI machines. However, this requires the Quest client to be downloaded
onto client machines, and our customers are finding this onerous (Previously
they just used vanilla RDP to connect to vanilla TS).
We are contemplating using Windows 2008 R2 and I have read Michael Roth's
useful article:
http://www.brianmadden.com/blogs/michelroth/archive/2009/08/26/taking-a-clos
er-look-at-the-vdi-functionality-in-windows-server-2008-r2.aspx
It suggests that "The client connects directly to the virtual desktop.". I'm
inferring from this that I'm going to have problems coming in on a
firewalled environment to VDI machines with have local rather than real IP
numbers.
Am I right that this is an issue or does the connection broker provide some
kind of SSL-ish VPN?
Ta,
Nick
_____
SUBJECT TO CONTRACT
Other related posts:
