WEBVTT
00:00:00.500 --> 00:00:02.800
Want a more fault-tolerant datacenter.
00:00:05.000 --> 00:00:08.110
Bring the availability of cloud computing
inside your datacenter,
00:00:08.160 --> 00:00:10.550
with the only server built
from the cloud up.
00:00:32.990 --> 00:00:36.470
Great. Thanks. Welcome to this edition
of TechNet Radio.
00:00:36.470 --> 00:00:40.660
I'm Tommy Patterson, Technical Evangelist out
of the southeast in the U.S.
00:00:40.660 --> 00:00:42.220
Joining me today is Simon May.
00:00:42.270 --> 00:00:46.010
He is out of our CORAL TP team.
Simon, welcome to the show.
00:00:46.060 --> 00:00:47.530
>> Hi Tommy, how are you doing?
00:00:47.580 --> 00:00:52.820
>> Great. So as I go around, I do
IT cams around the southeast
00:00:52.870 --> 00:00:56.460
and I talk to different people
as we've been doing
00:00:57.740 --> 00:01:01.480
Hyper-V, we've been doing Azure,
we've talked about Windows 8,
00:01:01.530 --> 00:01:05.320
and we're going through that cycle
again now for the second half
00:01:05.370 --> 00:01:11.130
of Microsoft's year. We talk a little
bit about VDI and remote
00:01:11.180 --> 00:01:15.380
desktop server, but tell us a little
bit about, you know, your
00:01:15.430 --> 00:01:18.660
involvement in that, how you got
into this role, and a little
00:01:18.710 --> 00:01:19.730
bit of your history.
00:01:20.030 --> 00:01:23.590
>> Yeah, so I've been working with
client infrastructure basically
00:01:23.640 --> 00:01:26.720
for pretty much all of my career.
Apart from a little tiny,
00:01:26.770 --> 00:01:29.960
horrible segway where I went to
this based process improvement
00:01:30.010 --> 00:01:33.350
for help desk. That was kinda weird,
but apart from that, I've
00:01:33.400 --> 00:01:36.840
basically been focused on actually
managing and deploying desktops.
00:01:36.890 --> 00:01:40.390
Making it so that people can access,
corporate information wherever
00:01:40.440 --> 00:01:43.460
they are and whatever kind of scenario
they are in. For me that
00:01:43.510 --> 00:01:47.690
was banks basically. Working for
large financial institutions.
00:01:47.740 --> 00:01:52.720
Making it so that really massive
field sales forces for banks
00:01:52.770 --> 00:01:56.240
can actually access information.
So we're talking hundred of
00:01:56.290 --> 00:01:59.190
thousands of employees there. In
order to be able to access all
00:01:59.240 --> 00:02:02.590
this different information and we
used various different methods
00:02:02.640 --> 00:02:06.200
for allowing access, so it would
be kind of VPN access back into
00:02:06.250 --> 00:02:08.940
the corporate network, it would
be managing those devices with
00:02:08.990 --> 00:02:12.330
Config Man, it would be actually
delivering virtual desktops
00:02:12.380 --> 00:02:15.870
to people on the devices that they are
able to carry around with them.
00:02:15.920 --> 00:02:18.050
Obviously, banks were really interested
in that sort of thing
00:02:18.100 --> 00:02:21.410
for a couple of reasons. Firstly,
for those mobile guys, you
00:02:21.460 --> 00:02:25.290
have that massive advantage that
they don't have to carry all
00:02:25.340 --> 00:02:28.710
of the kit with them. They can be
opening up a fairly lightweight
00:02:28.760 --> 00:02:31.760
laptop and they can get secure
access back into that data.
00:02:31.810 --> 00:02:36.100
It never leaves the date center.
Secondly though, one of the
00:02:36.150 --> 00:02:39.370
things that folks really forget about
these environments is that,
00:02:39.420 --> 00:02:43.850
take a trade floor environment,
the real skill of IT on a trade
00:02:43.900 --> 00:02:46.780
floor inside of a bank is not about
whether they can make something
00:02:46.830 --> 00:02:49.740
more or less accessible for people,
it's about whether they can
00:02:49.790 --> 00:02:53.890
reduce the latency of access to
the data and that's again where
00:02:53.940 --> 00:02:57.290
VDI comes into play. It helps reduce
the latency of access because
00:02:57.340 --> 00:03:00.410
your connection to a remote session
which is inside of the data center.
00:03:00.460 --> 00:03:03.670
So again, really important stuff
for folks to be able to do.
00:03:03.720 --> 00:03:06.590
That's one of the reasons I love
the approach to VDI. You get
00:03:06.640 --> 00:03:10.570
to select this part over here which
is gonna be kind of the lower
00:03:10.620 --> 00:03:14.290
cost entry area where we're gonna
use what was technical services,
00:03:14.340 --> 00:03:16.980
now remote desktop services, when
over here you might say these
00:03:17.030 --> 00:03:20.130
guys have some higher capacity requirements,
so we need to have
00:03:20.180 --> 00:03:23.400
a VDI desktop where they get their
own amount of RAM assigned
00:03:23.450 --> 00:03:24.050
to them.
00:03:25.010 --> 00:03:28.670
>> Very cool. So, my background
as well in the last few years
00:03:28.720 --> 00:03:32.730
of consulting before I came over
to Microsoft, I was doing VDI
00:03:32.780 --> 00:03:39.160
projects and terminal server projects
with Citrix, VMware, View,
00:03:40.510 --> 00:03:45.850
and also doing some hybrid environments
was in desktop.
00:03:46.400 --> 00:03:51.560
I saw some just native terminal
services installations as well,
00:03:51.610 --> 00:03:55.570
but I really feel like 2012 and
the release that we have now
00:03:55.620 --> 00:04:00.530
with Windows 8, the upgrades that
we put in place technology
00:04:00.580 --> 00:04:04.620
wise in the software, really is
helping us get to that point
00:04:04.670 --> 00:04:10.530
where VDI and remote desktop services
is something that we can
00:04:10.580 --> 00:04:15.140
honestly hand to our end user or to
our customer and say we believe
00:04:15.190 --> 00:04:18.790
this is as good or better than what you
could have as a native experience.
00:04:18.840 --> 00:04:22.350
In the past it used to be very difficult
to even try to say that.
00:04:23.010 --> 00:04:26.170
You know, in certain situations
you might can make it work, but
00:04:26.220 --> 00:04:30.590
now we've really bridged that gap.
We've made it load faster.
00:04:31.020 --> 00:04:33.970
We're more smart about what we send
over the wire and so I know
00:04:34.020 --> 00:04:37.280
you're gonna kinda go through that
with us. What do you think
00:04:37.330 --> 00:04:41.640
the key things that we changed that
have really helped out in 2012?
00:04:41.690 --> 00:04:44.090
>> You've really hit the nail on
the head there. It's all about
00:04:44.140 --> 00:04:47.370
making the experience feel local
because when we've been out
00:04:47.420 --> 00:04:51.230
there, and we don't just go create
some software and hope it works.
00:04:51.280 --> 00:04:53.850
We actually go and talk to people.
We get customers in. We find
00:04:53.900 --> 00:04:56.780
out what makes things usable to
them, what doesn't, and people
00:04:56.830 --> 00:05:00.120
actually told us they just want the
experience to feel more like
00:05:00.170 --> 00:05:03.260
it's a local machine. It might
be remoting to somewhere else,
00:05:03.310 --> 00:05:06.260
but they want it to feel more
like it's local. So that mean
00:05:06.310 --> 00:05:10.410
little tiny things like making sure
that touch feels first class.
00:05:10.460 --> 00:05:14.990
If you've got a brand new device,
one of those nice little tiny
00:05:15.040 --> 00:05:20.500
Dell 8 inch devices, Dell Venue
8 Pro, one of those devices and
00:05:20.550 --> 00:05:23.550
you're remoting back into the
data center. You want that to
00:05:23.600 --> 00:05:27.580
feel natural. If you're opening
up something inside of Windows
00:05:27.630 --> 00:05:30.290
you expect that when you bring the charms
in they're in the right place.
00:05:30.340 --> 00:05:32.700
When you go and tap on something
it's responsive. When you use
00:05:32.750 --> 00:05:36.160
three fingers in order to do a zoom
or two finger or whatever,
00:05:36.210 --> 00:05:39.310
that it does the right thing. So it's
about making the experience local.
00:05:39.980 --> 00:05:43.900
The subtlety of that though is there
are many things that people
00:05:43.950 --> 00:05:48.620
do where VDI experiences didn't make
things go local in the past.
00:05:48.670 --> 00:05:51.320
So browsing a web page is a really
great example. As soon as
00:05:51.370 --> 00:05:54.800
you hit a big image, well traditionally
you've got to get that
00:05:54.850 --> 00:05:58.280
image from the server that's running
the session back in the
00:05:58.330 --> 00:06:01.590
data center down to the client in
some way, and typically that
00:06:01.640 --> 00:06:05.600
bitmap updates to the screen, so
it tends to be kind of painful.
00:06:05.650 --> 00:06:07.940
So we've done some real, by the
engineering guys have done some
00:06:07.990 --> 00:06:12.400
phenomenal work here to make these
aspects of the experience
00:06:12.450 --> 00:06:16.390
just more seamless feel more
like a local experience.
00:06:16.930 --> 00:06:20.300
They've also kind of taken into
account the fact that when we
00:06:20.350 --> 00:06:23.810
do think about these big kind of field
sales forces that people have.
00:06:24.410 --> 00:06:27.880
They're connecting over really different
types of networks the
00:06:27.930 --> 00:06:30.480
way they were doing this in the
past. If we think about the
00:06:30.530 --> 00:06:33.940
types of networks where this kind
of technology first came about
00:06:33.990 --> 00:06:36.570
we're practically talking minimum
hundred megabytes per second
00:06:36.620 --> 00:06:40.770
well connected, well routed LAN.
And as a result of that, you
00:06:40.820 --> 00:06:43.710
kind of know that you're not gonna
get random packet loss.
00:06:43.760 --> 00:06:45.960
The band width is gonna stay pretty
high for the majority of
00:06:46.010 --> 00:06:46.930
the time.
00:06:46.980 --> 00:06:47.750
>> Right.
00:06:47.800 --> 00:06:51.440
>> Today's world, people are connecting
over 4G LTE connections,
00:06:51.490 --> 00:06:54.530
3G connections, 2G connections
occasionally when things just
00:06:54.580 --> 00:06:57.470
drop out. When there's too much
crowding around a cell tower,
00:06:57.520 --> 00:06:59.120
that cell tower actually starts to
00:07:00.370 --> 00:07:04.280
reduce the area that it covers.
So you could start out being
00:07:04.330 --> 00:07:08.320
in a 4G covered area, then a thousand
people hit that cell tower,
00:07:08.370 --> 00:07:11.290
suddenly, instead of it covering
you it just kind of shrinks
00:07:11.340 --> 00:07:13.810
in a little bit and you'll drop
from being in a 4G area into
00:07:13.860 --> 00:07:15.150
a 2G area.
00:07:15.200 --> 00:07:15.360
>> Right.
00:07:15.410 --> 00:07:17.650
>> That kind of stuff happens all
the time that's just the way
00:07:17.700 --> 00:07:20.840
that the network works. So the engineering
guys have though about
00:07:20.890 --> 00:07:23.980
that and they've changed some of
the ways that we are delivering
00:07:24.030 --> 00:07:25.990
content inside of
a VDI session.
00:07:26.850 --> 00:07:32.540
>> Right. We had. The challenges
change, I mean, back in the day
00:07:32.590 --> 00:07:36.570
we would be working at Starbucks
and they had a good connection
00:07:36.620 --> 00:07:41.710
or you know some other method,
even dialup back in the day.
00:07:41.760 --> 00:07:46.170
You know, you would try to present
as little as possible so that
00:07:46.220 --> 00:07:48.250
they didn't have many choices but
they could at least get their
00:07:48.300 --> 00:07:53.840
work done and it worked well. But
you talk about holding it local.
00:07:53.890 --> 00:07:56.510
Local means a lot of things these
days. It doesn't just mean
00:07:57.080 --> 00:08:02.440
I can do my job, be able to ge to
things online, and you know,
00:08:02.490 --> 00:08:06.660
there's more, I would say the criteria
for what needs to be on
00:08:06.710 --> 00:08:10.590
the desktop has changed and the
connectivity has changed.
00:08:10.640 --> 00:08:13.990
So, very cool stuff. Now, we've got
a few technologies that we're
00:08:14.040 --> 00:08:18.030
going to highlight today, but those
top technologies we made
00:08:18.080 --> 00:08:20.630
in 2012. Do you want to highlight
what those are before we jump
00:08:20.680 --> 00:08:21.330
into them?
00:08:21.380 --> 00:08:24.300
>> Yeah, so some of the stuff that
we've actually built in there.
00:08:24.350 --> 00:08:28.710
We've got from a hardware level,
in 2008 R2 we introduced this
00:08:28.760 --> 00:08:33.590
idea of remote effects, which basically
took a graphics card
00:08:33.640 --> 00:08:37.190
and kind of just chunked it up or
virtualized the graphics card
00:08:37.240 --> 00:08:39.170
as well. Just like it
virtualizes CPU.
00:08:39.830 --> 00:08:44.490
In 2012 and 2012 R2 they took the
branding around remote effects
00:08:44.540 --> 00:08:48.210
and extended that so it wasn't
just about a web, it was about
00:08:48.260 --> 00:08:50.340
the software technologies
that enable a
00:08:51.730 --> 00:08:55.760
more local rendering of the desktop
that you're connecting into,
00:08:56.270 --> 00:09:00.410
and as a result that now means that
we worked out that not everybody
00:09:00.460 --> 00:09:03.150
had one of those really nice liquid
cool graphics cards that
00:09:03.200 --> 00:09:07.330
worked with remote effects inside
of box servers, so we've actually
00:09:07.380 --> 00:09:11.270
been able to create the soft GPU.
So now by default, you get
00:09:11.320 --> 00:09:14.700
the abilities to do things like
3D rendering inside all of your
00:09:14.750 --> 00:09:18.070
VDI environment, inside of your remote
desktop services environments.
00:09:18.120 --> 00:09:20.940
Just kind of happens by default
and if you have that hardware
00:09:21.210 --> 00:09:23.290
in the background, which you might
still have if you're doing
00:09:23.340 --> 00:09:27.270
kind of remote heavy workloads like
we see in automotive where
00:09:27.320 --> 00:09:31.030
they're doing kind of really heavy
CAD diagrams and that kind
00:09:31.080 --> 00:09:34.050
of thing and CAD renders. They
do that kind of stuff remotely
00:09:34.100 --> 00:09:38.640
as well, but they kind of have
the investment in the hardware
00:09:38.690 --> 00:09:41.210
to make that work. Not everybody
can do that so we thought we'd
00:09:41.260 --> 00:09:46.170
extend those areas out. We've also
extended out the thought of
00:09:46.220 --> 00:09:49.330
being able to cope with what's happening
on the screen with the
00:09:49.380 --> 00:09:54.010
idea of adaptive rendering. So we now,
inside of the remote session,
00:09:54.060 --> 00:09:56.000
look at what's happening on the
screen and say, hey you know
00:09:56.050 --> 00:09:58.250
what that's a video, that needs
to be rendered like this.
00:09:58.300 --> 00:10:00.860
You know what, that's a picture,
we need to render it like this.
00:10:00.910 --> 00:10:04.830
That's some text, we render it
like this. And we also think,
00:10:04.880 --> 00:10:06.940
well actually, you know what, that's
a video, so not only are
00:10:06.990 --> 00:10:09.000
we gonna render it slightly differently
but we're gonna send
00:10:09.050 --> 00:10:13.800
the data to the client device slightly
differently. So previously,
00:10:13.850 --> 00:10:17.290
and we'll see this a little later
on in the demos, we actually
00:10:17.340 --> 00:10:20.660
sent all of that data down as
TCP packets. Well we all know
00:10:20.710 --> 00:10:24.310
what happens with a TCP packet.
You send a TCP packet. You get
00:10:24.360 --> 00:10:27.440
an AC back. Now when you're doing
a video which is running at
00:10:27.490 --> 00:10:32.750
40/60 frames per second. That's
40 to 60 ACs that have to be
00:10:32.800 --> 00:10:35.680
sent back and that just starts to
cause this real jitter on the
00:10:35.730 --> 00:10:39.830
network and you get really jittery,
stuttery video. So now,
00:10:39.880 --> 00:10:43.360
JDP essentially firing for GAP,
the packet hits the client, the
00:10:43.410 --> 00:10:46.560
client renders it. The packet misses
the client, the client doesn't
00:10:46.610 --> 00:10:49.270
render it, you drop a frame in the
video, you drop two frames,
00:10:49.320 --> 00:10:53.370
three frames. The video remains relatively
watchable during that period.
00:10:53.420 --> 00:10:57.470
Now the idea rendering. The really
key thing and one of the areas
00:10:57.520 --> 00:11:00.530
where we start to see Microsoft
really begin to look around the
00:11:00.580 --> 00:11:03.540
world and go, hey you know what,
don't just about the client
00:11:03.590 --> 00:11:08.550
anymore is that we actually have
first party clients for IOS
00:11:08.600 --> 00:11:12.100
and Andriod as well as for Windows
which means that you get really
00:11:12.150 --> 00:11:15.880
good quality experience by using
those clients because you know
00:11:15.930 --> 00:11:18.310
that their using the latest version
of the protocol which is
00:11:18.360 --> 00:11:21.320
what you need to have in place in
order to get all of this stuff.
00:11:21.370 --> 00:11:25.410
>> So what you're saying is the
remote desktop connection app
00:11:25.460 --> 00:11:30.790
that we have on all three stores,
through Microsoft Windows Store,
00:11:30.840 --> 00:11:36.350
the IOS Store or App Store, and the
then the Android Store, those
00:11:36.400 --> 00:11:40.630
are all built with the new protocol
that is native to our technology
00:11:40.680 --> 00:11:43.350
so that we can take advantage of
all those greatest things we
00:11:43.400 --> 00:11:44.360
just talked about.
00:11:45.060 --> 00:11:45.720
>> Yeah.
00:11:45.770 --> 00:11:49.720
>> Cool. Just for anyone who's watching,
if you're trying to build
00:11:49.770 --> 00:11:53.010
out a lab environment for this, interestingly
enough if you have
00:11:53.060 --> 00:11:57.810
like some of the later media cards
in your laptop you can actually
00:11:57.860 --> 00:12:01.490
pull this off, so check out virtuallycloud9.com.
I've got a
00:12:01.540 --> 00:12:05.370
lab out there around building remote
desktop services and I've
00:12:05.420 --> 00:12:11.280
built it with two Lenovo X30 machines
both with Nvidea cards.
00:12:11.330 --> 00:12:14.580
I was able to enable that hardware
piece there for the 3D.
00:12:14.630 --> 00:12:18.200
So really cool stuff. Simon are
you ready to (inaudible) you're
00:12:18.250 --> 00:12:19.030
talking about?
00:12:19.080 --> 00:12:22.780
>> Yeah. Let's show you some of
this stuff in action. So here
00:12:22.830 --> 00:12:26.290
I've got my desktop and this is
a desktop where I've connected
00:12:26.340 --> 00:12:31.160
into two other subsequent remote
desktop sessions. We look at
00:12:31.210 --> 00:12:33.890
this first desktop session on the
left hand side. I'm not gonna
00:12:33.940 --> 00:12:35.560
zoom in and out on this because
it will kind of make you feel
00:12:35.610 --> 00:12:39.290
a little bit seasick on the video,
but on the left hand side
00:12:39.340 --> 00:12:44.290
we have a server 2008 R2 remote
desktop services session host
00:12:44.340 --> 00:12:48.060
server, and on the right hand side
we have one which is running
00:12:48.110 --> 00:12:51.130
Server 2012 R2, and again running
00:12:52.560 --> 00:12:56.380
remote desktop session hosting role.
Both of these servers are
00:12:56.430 --> 00:13:01.170
actually virtualized on top of Hyper-V
on exactly the same hardware.
00:13:01.220 --> 00:13:03.350
>> What kind of hardware are we
talking about here? I mean, is
00:13:03.400 --> 00:13:05.660
this a big huge machine
or what?
00:13:05.710 --> 00:13:09.010
>> Well, I'm kinda lucky. So I've
got access to a pretty huge
00:13:09.060 --> 00:13:12.070
machine in the background. The machine
that is actually running
00:13:12.120 --> 00:13:14.750
these two sessions is running a
bunch of other stuff as well,
00:13:14.800 --> 00:13:19.600
but it's a 32 core server and it's
also got like half a terabyte
00:13:19.650 --> 00:13:22.140
of RAM in it, so it's
pretty beefy.
00:13:22.190 --> 00:13:25.400
>> But these machines, these virtual
machines, aren't that big right?
00:13:25.450 --> 00:13:29.440
>> No. They're not that big and their
identical as well so they're
00:13:29.490 --> 00:13:32.830
both running off exactly the same
storage which is on a clustered
00:13:32.880 --> 00:13:37.740
shared volume which is backed
up by storage bases. They are
00:13:37.790 --> 00:13:43.680
both running on 4 cores, 4 vertical
cores inside of each virtual
00:13:43.730 --> 00:13:46.660
machine, and they're both consuming
a RAM of about 2-1/2 gigs
00:13:46.710 --> 00:13:49.500
of RAM. Although you've got dynamic
memory in place so they can
00:13:49.550 --> 00:13:53.410
peak up as much as they want to inside
of the overall virtualization
00:13:53.460 --> 00:13:55.690
host's memory capacity.
00:13:56.280 --> 00:13:58.490
So what we're gonna do is have
a quick look at the experience
00:13:58.540 --> 00:14:01.490
and see how similar it is on both of
these and how it it's different.
00:14:01.540 --> 00:14:04.400
The very first thing that you'll
notice on my left hand side
00:14:04.450 --> 00:14:08.530
screen up there, which is running
service RAM 2008 R2.
00:14:08.580 --> 00:14:11.230
You'll notice that I've upgraded
Internet Explorer, updated to
00:14:11.280 --> 00:14:15.590
Internet Explorer 11. No real reason
for that other than I didn't
00:14:15.640 --> 00:14:18.940
want there to be anybody out there
saying, hey you're running
00:14:18.990 --> 00:14:20.990
a different version of Internet Explorer,
it's doing different things.
00:14:21.040 --> 00:14:25.980
I just wanted the same version.
So we support IE 11 on Windows
00:14:26.030 --> 00:14:29.960
7 on that Server 2008 R2. So that's
exactly what we're running.
00:14:30.010 --> 00:14:33.970
And we're looking at right now,
at the really cool Microsoft
00:14:34.020 --> 00:14:36.140
Stories website, microsoft.comwacstories.
00:14:36.920 --> 00:14:39.120
Easy way you can find out about all
the really interesting stuff
00:14:39.170 --> 00:14:42.400
that we do inside of Microsoft
as well as all of the products
00:14:42.450 --> 00:14:45.560
that we carry. So we go to things
like the Microsoft Garage and
00:14:45.610 --> 00:14:49.040
understand what's kind of happening
inside of the Garage, which
00:14:49.090 --> 00:14:52.290
is is a kind of a hobbyist place
that we have on campus where
00:14:52.340 --> 00:14:56.020
people can start to build their
own different projects.
00:14:56.070 --> 00:14:58.430
>> I definitely need to go visit
there next time out.
00:14:59.180 --> 00:15:01.650
>> Yeah. I think so, I need to find
it actually. I'm out here
00:15:01.700 --> 00:15:04.540
all the time. I have no idea where
it is, but you can see that
00:15:04.590 --> 00:15:07.060
I'm scrolling down this web page
and it's looking kind of nice
00:15:07.110 --> 00:15:09.950
and things like the story elements
are basically just kind of
00:15:10.000 --> 00:15:12.960
flying in, all that kind of stuff.
00:15:13.790 --> 00:15:17.180
Exactly the same thing happening
across here except that you
00:15:17.230 --> 00:15:19.830
notice there is something slightly
different in the way that
00:15:19.880 --> 00:15:24.010
it's appearing on the 2012 machine
as well. So you can see it's
00:15:24.060 --> 00:15:27.140
just kind of jumping in and kind
of going fuzzy and then giving
00:15:27.190 --> 00:15:28.230
me more detail.
00:15:29.410 --> 00:15:30.970
Another thing I'm going to do. I'm
just going to go across here
00:15:31.020 --> 00:15:35.710
to this video which is inside of
our You Tube player. I'm just
00:15:35.760 --> 00:15:38.340
gonna press play to both of them
around the same point in time
00:15:39.060 --> 00:15:41.650
and what you can see that
their both kind of
00:15:43.260 --> 00:15:46.940
playing through and look pretty
reasonable. Let's hit refresh
00:15:46.990 --> 00:15:50.460
on both of those videos. It's always
a nice thing to do load
00:15:50.510 --> 00:15:53.250
up a fresh copy of the video. There
we go. Both playing through,
00:15:53.300 --> 00:15:54.770
both look kind of reasonable.
00:15:55.400 --> 00:15:58.500
Finally, I've also got on both
of these machines this kind of
00:15:58.550 --> 00:16:05.220
3D card rendering app which is in
the background. Lets go back
00:16:05.270 --> 00:16:05.840
to that.
00:16:07.710 --> 00:16:13.120
There we go. So, that's actually doing
a live render of the images.
00:16:13.170 --> 00:16:16.760
Not a video, essentially realtime.
It's got all the details
00:16:16.810 --> 00:16:20.180
and actually this CD thing that
you see at the airports.
00:16:20.230 --> 00:16:24.620
It's actually doing that as a live
render and there's no 3D graphics
00:16:24.670 --> 00:16:28.160
hardware in the background here
at all which is kinda cool.
00:16:28.210 --> 00:16:32.340
Both of them cope with it pretty
well. The 2012 R2 server copes
00:16:32.390 --> 00:16:33.710
with it really, really well.
00:16:34.460 --> 00:16:38.930
I'm now gonna do something off screen,
which is, I'm gonna play
00:16:38.980 --> 00:16:42.390
around with one of those really
nice cool features of Hyper-V
00:16:42.640 --> 00:16:46.780
instead of 2012 R2. The ability
to change the amount of band
00:16:46.830 --> 00:16:50.250
width which is allocated to a virtual
machine. I might actually
00:16:50.300 --> 00:16:53.560
want to do that inside of a VDI
environment because by limiting
00:16:53.610 --> 00:16:56.510
the maximum band width that anybody's
got available you start
00:16:56.560 --> 00:17:00.300
to prevent what's called the noisy
neighbor syndrome, which is
00:17:00.350 --> 00:17:04.720
whereby two people say have unlimited
band with and then somebody
00:17:04.770 --> 00:17:07.350
starts downloading a really big
file and it slows both people's
00:17:07.400 --> 00:17:11.530
connections down. So we avoid that
by using band width roughly.
00:17:11.580 --> 00:17:13.560
I'm gonna do something interesting
though. I'm gonna drop the
00:17:13.610 --> 00:17:18.350
band width down so that we actually
drop down to a maximum band
00:17:18.400 --> 00:17:22.720
width of 1 megabyte per second
for both of these connections.
00:17:23.410 --> 00:17:28.650
So both servers now have a maximum
1 megabyte per second band
00:17:28.700 --> 00:17:32.230
width utilization. You can instantly
see kind of what's happening there.
00:17:32.280 --> 00:17:38.210
On the 2008 R2 screen we're now
actually rendering everything
00:17:38.490 --> 00:17:43.700
in a kind of progressive one line,
one line thing. Whereas our
00:17:43.750 --> 00:17:45.020
server 2012 R2
00:17:46.220 --> 00:17:49.430
virtual machine is actually running
through kind of smoothly still.
00:17:49.480 --> 00:17:51.840
It's not completely smooth, but
still dropping frames, but it's
00:17:51.890 --> 00:17:56.050
looking a lot better. I'll go and
drop out of the CAD render
00:17:56.100 --> 00:17:59.140
here and go back to that video.
00:17:59.190 --> 00:18:02.770
>> And just to be clear, there is no,
we aren't using 3D effects cards?
00:18:03.980 --> 00:18:07.490
Right. So this is just software
driven for this to come out.
00:18:07.540 --> 00:18:11.120
>> Yeah, totally software driven
and this is I think kind of the
00:18:11.170 --> 00:18:14.200
most instantly noticeable thing.
So again, we're still running
00:18:14.250 --> 00:18:17.370
at 1 megabytes per second. On our
right hand side window here
00:18:17.420 --> 00:18:21.940
we've got a flash video being played,
which is playing smoothly.
00:18:22.350 --> 00:18:25.810
On the left hand side we have a
video which is kind of chunkily
00:18:25.860 --> 00:18:28.760
having to render, kind of a couple
of lines, couple of lines,
00:18:28.810 --> 00:18:31.850
couple of lines, it's dropping a
lot of frames. Right hand side
00:18:31.900 --> 00:18:37.660
2012 R2 still watchable. Left hand
side 2008 R2 kind of not such
00:18:37.710 --> 00:18:40.780
a great experience by this point.
So that's what the difference
00:18:40.830 --> 00:18:45.230
is of a few years worth of innovation
inside of the space.
00:18:45.280 --> 00:18:47.750
And folks out there at this point
in time. Every time I show
00:18:47.800 --> 00:18:50.750
a demo like this the go, yeah,
but inside of our organization
00:18:50.800 --> 00:18:54.650
nobody watches You Tube videos on
their remote desktop session.
00:18:54.990 --> 00:18:59.470
Well, kind of, actually, Flash video
is the most popular method
00:18:59.520 --> 00:19:03.070
for using online training. So people
are doing some kind of online
00:19:03.120 --> 00:19:05.090
training, maybe have some compliance
training that you have to
00:19:05.140 --> 00:19:09.060
get through. Just like we have to
do our very funny course every
00:19:09.110 --> 00:19:14.620
year that requires us to kind of sit
there and say that we definitely
00:19:14.670 --> 00:19:18.280
know how to deal with various aspects
of the legal requirements
00:19:18.330 --> 00:19:21.560
of working for Microsoft and folk out
there have to do the same thing.
00:19:22.190 --> 00:19:24.460
You might not have it in your organization,
but it's pretty important
00:19:24.510 --> 00:19:27.180
to a lot of people. And then there's
this one final thing, which
00:19:27.230 --> 00:19:30.190
for me makes it feel a little bit more
like a much more local experience.
00:19:30.240 --> 00:19:33.170
I'm just gonna bring both of these
up and again you can see that
00:19:33.220 --> 00:19:34.480
I'm going back to that story.
00:19:35.010 --> 00:19:38.090
The left hand side, if I try and
scroll up and down the page
00:19:38.140 --> 00:19:41.630
it will have to do the progressive
one line at a time thing.
00:19:41.680 --> 00:19:44.290
It's kind of hard for me to keep
the flow of what's happening.
00:19:44.340 --> 00:19:49.860
Where as on my 2012 R2 machine,
I go over here and click on it,
00:19:49.910 --> 00:19:52.760
we just kind of get these progressive
rerenders of the screen
00:19:52.810 --> 00:19:56.140
so it gives us a picture, it gives
us the text on the screen
00:19:56.190 --> 00:19:58.760
so I can read that first, and actually
what it's doing is it's
00:19:58.810 --> 00:20:01.690
loading the pages and then fitting
in a little more detail.
00:20:01.740 --> 00:20:07.150
I'll hit the back button on both
of these and (inaudible) that's
00:20:07.200 --> 00:20:08.920
what's happening. So I can already
start to interact with the
00:20:08.970 --> 00:20:15.330
page here on my Windows Server 2012
machine. Whereas on my Server
00:20:15.380 --> 00:20:19.370
2008 R2 machine that's still loading
the images. So I'm already
00:20:19.420 --> 00:20:21.980
starting to get the advantage of
using 2012 R2. I'm starting
00:20:22.030 --> 00:20:25.250
to be able to use websites the
way that they were intended to
00:20:25.300 --> 00:20:28.050
be used. I can start to browse
through them. I'm just gonna
00:20:28.100 --> 00:20:30.750
find the same story here. I'll just
click down and wait for that
00:20:30.800 --> 00:20:34.190
to rerender the entire page
again. Off it goes.
00:20:34.750 --> 00:20:37.640
Eventually I can, hey see that that's
there, the picture of Andrew Kim.
00:20:37.690 --> 00:20:40.800
I can't click it yet. It's not finished
loading the entire page.
00:20:40.850 --> 00:20:46.650
Now I can click and we'll load
up our story about Andrew Kim.
00:20:46.700 --> 00:20:49.020
Whereas down here I'm able to
start reading through again.
00:20:49.070 --> 00:20:52.620
>> I can imagine that the amount
of band width that it takes for
00:20:52.670 --> 00:20:56.360
that 2008 R2 connection
much higher, right?
00:20:56.410 --> 00:20:56.840
>> Yeah.
00:20:56.890 --> 00:21:00.960
>> There's TCP retransmits going
on and trying to catch up with
00:21:01.010 --> 00:21:03.510
every little click when it has to
redraw the screen and you know
00:21:03.560 --> 00:21:06.950
over here on the right hand side you
actually get things instantly.
00:21:07.350 --> 00:21:09.570
>> Yeah. We just don't have that
issue. It's kind of cool and
00:21:09.620 --> 00:21:12.370
we're really limited this down
to 1 megabyte per second.
00:21:12.420 --> 00:21:15.690
It's sort of a little bit overkill
really to be honest, but it
00:21:15.740 --> 00:21:16.400
gives you the
00:21:18.180 --> 00:21:22.160
idea of what's happening. I'm just
gonna off screen. Bring myself
00:21:22.210 --> 00:21:26.360
back up to using the full band
width and then we'll start to
00:21:26.410 --> 00:21:29.840
see that actually full band width
experiences are pretty similar
00:21:29.890 --> 00:21:31.060
to each other.
00:21:31.110 --> 00:21:31.610
>> Yeah.
00:21:32.120 --> 00:21:33.670
>> Back again. That's kind
00:21:34.890 --> 00:21:37.620
of what we've done to make the
experience feel more local.
00:21:37.670 --> 00:21:41.110
I can browse web pages properly.
I can use my applications as
00:21:41.160 --> 00:21:44.960
they were intended to be used even over
relatively low band width connections.
00:21:45.010 --> 00:21:47.900
And, you know, we reduced band
with there, but we might have
00:21:47.950 --> 00:21:51.950
also wanted to simulate increasing
packet loss. I didn't do
00:21:52.000 --> 00:21:54.860
that because it's more difficult
to do inside of this environment
00:21:54.910 --> 00:21:58.280
than it is to just grab a feature
and say hey, can you manage
00:21:58.330 --> 00:22:02.730
quality servers for me, but it would
do the same kind of thing.
00:22:03.370 --> 00:22:05.870
And the last thing that's really
important when we're talking
00:22:05.920 --> 00:22:09.990
around and looking at the client
improvements, we've actually
00:22:10.040 --> 00:22:13.670
made it easier for people who don't
necessarily have all of the
00:22:13.720 --> 00:22:16.150
information that they might need
to connect into a remote desktop
00:22:16.200 --> 00:22:21.310
environment to get connected. So this
is machine here is my Windows
00:22:22.310 --> 00:22:25.180
8 machine. It's actually running
8.1. I'm just gonna go in and
00:22:25.230 --> 00:22:29.290
I've already downloaded from the Windows
Store the Remote Desktop App.
00:22:29.340 --> 00:22:35.010
So this is the new Remote Desktop
App inside of Windows 8.
00:22:35.060 --> 00:22:37.310
Now, I've got these two options
here. I can either use a remote
00:22:37.360 --> 00:22:41.210
desktop gateway server or I can use
access remote app in desktop
00:22:41.260 --> 00:22:42.650
connections, which is
what I'm gonna do.
00:22:43.690 --> 00:22:47.650
So I do that. User then, all they have
to do is enter their e-mail address.
00:22:48.120 --> 00:22:55.380
Got to spell it right. yeah. They're
into all sorts of different
00:22:55.720 --> 00:23:02.120
things at the moment. It's gone
off, it's found, basically a
00:23:02.170 --> 00:23:05.500
text recording server my public
DNS which is well documented
00:23:05.550 --> 00:23:10.260
now, multinet and then it's then
seeing the published URL from
00:23:10.310 --> 00:23:12.330
my remote desktop web server.
00:23:13.050 --> 00:23:16.570
I hit yes. It's gonna ask me for
my creds again. I'm just gonna
00:23:16.620 --> 00:23:18.390
do that the other way down at.
00:23:19.150 --> 00:23:20.160
Entries password.
00:23:21.370 --> 00:23:24.120
Say render credentials, but notice
I can also sign on with a
00:23:24.170 --> 00:23:27.150
smart card here. That's because I
have a smart card reader attached
00:23:27.200 --> 00:23:30.670
to this machine. oddly enough. then
that's gonna go away, find
00:23:30.720 --> 00:23:33.860
all of the resources that have
been assigned to me as a user
00:23:33.910 --> 00:23:37.610
inside of the environment and then
it will app those into my machine.
00:23:37.660 --> 00:23:41.190
So this is important. It's noticed
that I don't have any remote
00:23:41.240 --> 00:23:45.530
desktops assigned to me. I have
three apps assigned to me.
00:23:46.220 --> 00:23:49.630
It gives me access to those apps
directly here, but moreover,
00:23:49.680 --> 00:23:52.660
if I go back to my start screen.
What I can actually do is go
00:23:52.710 --> 00:23:57.670
down to my all apps area and then across
here and the word resources
00:23:57.720 --> 00:24:01.660
actually see what resources which
have just been published out
00:24:01.710 --> 00:24:04.070
to me from my remote
desktop sever.
00:24:04.120 --> 00:24:06.080
>> And you can pin those
to your start screen?
00:24:06.130 --> 00:24:08.650
>> yeah. Absolutely. They can be
pinned just like a normal app
00:24:08.700 --> 00:24:12.210
to my start screen. So we'll connect
him up and we're gonna obviously
00:24:12.260 --> 00:24:15.030
get to see the best version of calculator,
not the version that
00:24:15.080 --> 00:24:18.320
comes with your Windows 8 client.
It's the version that comes
00:24:18.370 --> 00:24:21.920
on the server. Apparently servers are
just better at doing calculations
00:24:21.970 --> 00:24:27.450
than the desktops are. I've heard
that nasty bit afoot floating
00:24:27.500 --> 00:24:29.530
around out there. It's the batteries
and the like that you'd
00:24:29.580 --> 00:24:34.430
want to publish. The calculator app
off of the server as a remote app.
00:24:35.220 --> 00:24:38.020
What we'll see in a second when
it loads up is something which
00:24:38.070 --> 00:24:41.110
is again kind of important when
we start to look at this kind
00:24:41.160 --> 00:24:44.540
of modern touch centric world that
we're starting to see emerge
00:24:44.830 --> 00:24:49.190
and that is that the app itself
is gonna be rendered as if it's
00:24:49.240 --> 00:24:55.070
a local app. What that means is that
when we see areas of transparency
00:24:55.810 --> 00:24:58.920
inside of an app, particularly apps
that were built a few years
00:24:58.970 --> 00:25:03.880
ago, (inaudible). What we started
to see was that, say you had
00:25:03.930 --> 00:25:06.610
a grey background on your remote
desktop services server or on
00:25:06.660 --> 00:25:10.030
your VDI session and you delivered
that down as a remote app
00:25:10.080 --> 00:25:13.340
to a client machine. They kind
of have this weird greyness to
00:25:13.390 --> 00:25:16.680
them and the reason is that they
were showing the desktop of
00:25:16.730 --> 00:25:20.270
the server, not that nice family
portrait that you've got set
00:25:20.320 --> 00:25:24.180
to your Windows desktop on your
local machine and that was kind
00:25:24.230 --> 00:25:28.270
of disconcerting to people. Particularly
so, when you find applications
00:25:28.320 --> 00:25:32.680
like say Office 2013 where the edge
of the screen was actually
00:25:32.730 --> 00:25:36.600
to make it more touch focused, it
actually has a really big area
00:25:36.650 --> 00:25:40.040
of what's called after shading or
transparency. I can just drag
00:25:40.090 --> 00:25:43.020
this around. It feels very local
to my drag. It doesn't kind
00:25:43.070 --> 00:25:46.270
of leave me with black traces all
over the screen anymore, which
00:25:46.320 --> 00:25:49.360
is what would have happened previously.
That's because we now
00:25:49.410 --> 00:25:52.410
are reflecting the transparency
of the client machine rather
00:25:52.460 --> 00:25:55.990
than the transparency from the server.
So, little tiny improvements
00:25:56.040 --> 00:25:59.240
that have all come together to
make a client experience way,
00:25:59.290 --> 00:26:01.550
way better than it was previously.
00:26:02.750 --> 00:26:03.670
>> Very cool.
00:26:03.720 --> 00:26:09.440
So again, this app that you're in,
this new Remote Desktop App,
00:26:09.490 --> 00:26:13.120
that is the latest one and running
the latest protocol and it's
00:26:13.170 --> 00:26:16.020
available on any of the different
stores that are out there for
00:26:16.070 --> 00:26:17.100
different devices.
00:26:18.550 --> 00:26:23.420
I like that. It's easier to get to people
with the new BYOD initiative,
00:26:23.470 --> 00:26:25.930
you know, people are bringing in
whatever devices they'd like
00:26:25.980 --> 00:26:26.440
to use.
00:26:27.430 --> 00:26:33.310
Making it easy to allow them access
to certain applications no
00:26:33.360 --> 00:26:38.180
matter what device, that's the
top of everyone's mind, but we
00:26:38.230 --> 00:26:41.380
want to make sure it's secure and
looks like you're logging in
00:26:41.430 --> 00:26:46.630
with your regular credentials or
the smart card and very little
00:26:46.680 --> 00:26:50.330
setup involved, so that looked
very seamless. So, well done.
00:26:50.380 --> 00:26:53.710
>> Yeah. Just to, I'm just going
to show you one thing that I've
00:26:53.760 --> 00:26:58.010
got done finally in here which
is always fun. We also thought
00:26:58.060 --> 00:27:01.150
about the administrative experience
as well when we're doing
00:27:01.200 --> 00:27:05.250
this and one of those things that
is really, it gets to be a
00:27:05.300 --> 00:27:08.030
little bit clunky is when your remote
desktoping into a machine
00:27:08.080 --> 00:27:10.720
and the remote desktoping from that
machine to another machine.
00:27:11.100 --> 00:27:16.860
Well, actually this entire demo
has been done by remoting in
00:27:16.910 --> 00:27:20.990
to another desktop. So, I'm remoted
from one desktop to another
00:27:21.040 --> 00:27:24.660
desktop and then hopping across to my
remote desktop services servers.
00:27:25.120 --> 00:27:28.650
So when I'm hitting play on this video
over here inside my Windows
00:27:28.700 --> 00:27:34.150
Server 2012 environment I'm actually
playing that to a remote
00:27:34.200 --> 00:27:37.560
client and then replaying that straight
down to me. What's really
00:27:37.610 --> 00:27:41.020
happening under the hood there is
we're sending all of that video
00:27:41.070 --> 00:27:45.800
stream a VDP packet from the remote
desktop services server down
00:27:45.850 --> 00:27:48.460
to the client I've connected to,
but then just hopping from that.
00:27:48.510 --> 00:27:51.420
Send the packets all the way down
to my client installer, my
00:27:51.470 --> 00:27:55.390
local machine. So it's kind of neat
the way that we can do this
00:27:55.440 --> 00:28:01.190
kind of nested view of remote desktop
services and RDP connections now.
00:28:02.370 --> 00:28:06.320
>> Very cool. So that would also
lower your band width if you're
00:28:06.370 --> 00:28:07.420
doing that kind of thing.
00:28:08.170 --> 00:28:12.290
Another use for this would
be overseas developers.
00:28:13.020 --> 00:28:15.030
They've got to get on and do a little
bit of training here and
00:28:15.080 --> 00:28:22.480
there or they need to watch some instructional
how to on a certain
00:28:22.530 --> 00:28:26.900
feature that we've just rolled
out. You know, if they were to
00:28:26.950 --> 00:28:28.910
say well okay I can't
watch videos at work,
00:28:30.900 --> 00:28:32.580
probably wouldn't get
a lot of work done.
00:28:32.630 --> 00:28:32.860
>> No.
00:28:32.910 --> 00:28:36.330
>> These days I'm looking at stuff
all day. You know, how can
00:28:36.380 --> 00:28:40.980
I do this or that. So I think we
need to make sure when we enable
00:28:41.030 --> 00:28:46.690
our customers to do work or to train
or to investigate new ideas
00:28:46.740 --> 00:28:50.910
that we don't limit them just because
of a network technology
00:28:50.960 --> 00:28:54.370
or a 3D rendering technology and
take that off the table.
00:28:54.420 --> 00:28:57.200
Now it's just a matter of what's
the policy for corporate.
00:28:57.460 --> 00:29:01.510
>> Yeah, also how do I get access
to this stuff? Yeah. Very nice.
00:29:01.560 --> 00:29:03.990
>> Great. Thanks Simon. Always a pleasure
to have you on the show.
00:29:04.040 --> 00:29:06.640
Any other closing thoughts you
want to throw out there?
00:29:06.690 --> 00:29:08.500
>> Well I think the only other thing
that I wanted to actually
00:29:08.550 --> 00:29:11.040
mention is that we're gonna have
a follow up to this show where
00:29:11.090 --> 00:29:13.320
we're gonna actually look at the
back end of this because that
00:29:13.370 --> 00:29:16.640
was all nice and fluffy and we did,
you know, lots of nice rendering
00:29:16.690 --> 00:29:19.670
stuff and showed kind of what the
end user experience is like.
00:29:20.240 --> 00:29:22.140
Tommy, we're IT guys, we need
to see this properly. We need
00:29:22.190 --> 00:29:25.260
to see the nuts, the bolts, the
infrastructure that actually
00:29:25.310 --> 00:29:28.350
runs all of that stuff, so in the
next episode we're actually
00:29:28.400 --> 00:29:31.830
gonna have a look at that. We're
gonna build out some of the
00:29:31.880 --> 00:29:34.360
infrastructure, put some of the
things in place, make some of
00:29:34.410 --> 00:29:37.870
the niceties happen like being
able to do that DNS discovery
00:29:37.920 --> 00:29:38.770
for example.
00:29:39.110 --> 00:29:44.360
>> Right. Excellent. So, thanks
everyone for joining us today.
00:29:44.410 --> 00:29:47.150
Look for the next episode as well
where we dive into the deep
00:29:47.200 --> 00:29:52.130
dive in this and once again thanks
for coming on the show.
00:29:52.180 --> 00:29:52.810
>> Any time.