WEBVTT 1 00:00:00.210 --> 00:00:01.620 Virtualization is everywhere 2 00:00:01.620 --> 00:00:02.790 in our enterprise networks. 3 00:00:02.790 --> 00:00:04.710 And what began with virtualized servers 4 00:00:04.710 --> 00:00:06.480 has now moved into the desktops 5 00:00:06.480 --> 00:00:09.570 with virtual desktop infrastructure or VDI. 6 00:00:09.570 --> 00:00:12.330 These systems can host desktop operating systems 7 00:00:12.330 --> 00:00:13.890 within a virtualized environment 8 00:00:13.890 --> 00:00:14.723 that's going to be hosted 9 00:00:14.723 --> 00:00:17.280 by a centralized server or server farm. 10 00:00:17.280 --> 00:00:19.470 This is a virtualization implementation 11 00:00:19.470 --> 00:00:21.510 that separates the personal computing environment 12 00:00:21.510 --> 00:00:23.520 from a user's physical computer. 13 00:00:23.520 --> 00:00:25.200 The end user is then able to access 14 00:00:25.200 --> 00:00:27.060 the virtual desktop from a thin client 15 00:00:27.060 --> 00:00:28.410 or through a web browser. 16 00:00:28.410 --> 00:00:29.760 And then they can interact 17 00:00:29.760 --> 00:00:31.050 with that virtualized desktop 18 00:00:31.050 --> 00:00:32.040 as if they were sitting right 19 00:00:32.040 --> 00:00:34.350 in front of a standard desktop computer. 20 00:00:34.350 --> 00:00:36.750 So for example, I have a Windows 10 machine 21 00:00:36.750 --> 00:00:38.460 that I can access in the cloud 22 00:00:38.460 --> 00:00:40.320 as part of a VDI network. 23 00:00:40.320 --> 00:00:42.450 So if I want to use it, I launch a piece 24 00:00:42.450 --> 00:00:45.090 of software on my Mac and it reaches out to the cloud 25 00:00:45.090 --> 00:00:46.980 and I connect to that Windows 10 machine 26 00:00:46.980 --> 00:00:49.020 and have access to all the resources I need 27 00:00:49.020 --> 00:00:51.060 being run on that cloud. 28 00:00:51.060 --> 00:00:52.820 Now, these VDI services have all 29 00:00:52.820 --> 00:00:54.090 of the operating system, 30 00:00:54.090 --> 00:00:56.250 the applications and everything else I need 31 00:00:56.250 --> 00:00:58.440 to operate this Windows 10 machine. 32 00:00:58.440 --> 00:01:00.150 Every time I try to run a command, 33 00:01:00.150 --> 00:01:02.430 it processes it on that cloud server. 34 00:01:02.430 --> 00:01:04.980 It doesn't process it on my local machine. 35 00:01:04.980 --> 00:01:07.560 Instead, my local machine is just a dummy box 36 00:01:07.560 --> 00:01:08.910 it's used to connect to it. 37 00:01:08.910 --> 00:01:10.920 That's the idea of VDI. 38 00:01:10.920 --> 00:01:12.690 This allows you to have it on a desktop, 39 00:01:12.690 --> 00:01:15.570 a laptop, a phone, a tablet, anything. 40 00:01:15.570 --> 00:01:16.830 It really doesn't matter 41 00:01:16.830 --> 00:01:18.720 because the device is just there to connect 42 00:01:18.720 --> 00:01:21.120 to the server and run that virtual image 43 00:01:21.120 --> 00:01:23.010 which is just going to be doing all the processing 44 00:01:23.010 --> 00:01:25.980 of the data for you on that remote server in the cloud. 45 00:01:25.980 --> 00:01:27.660 And so, as I've been saying, 46 00:01:27.660 --> 00:01:29.010 this server is now performing 47 00:01:29.010 --> 00:01:31.920 all the application processing and the data storage. 48 00:01:31.920 --> 00:01:33.750 This means you can use a Chromebook, 49 00:01:33.750 --> 00:01:35.400 a MacBook, a Windows machine. 50 00:01:35.400 --> 00:01:37.350 And again, it really doesn't matter 51 00:01:37.350 --> 00:01:39.450 because, with VDI, we're really focused 52 00:01:39.450 --> 00:01:41.790 on just connecting to the VDI environment, 53 00:01:41.790 --> 00:01:43.650 but all the processing is being done 54 00:01:43.650 --> 00:01:46.380 on the application and the server side for you 55 00:01:46.380 --> 00:01:48.690 because of this, many enterprise networks 56 00:01:48.690 --> 00:01:49.740 are going through an evolution 57 00:01:49.740 --> 00:01:52.080 into VDI with a lot of companies 58 00:01:52.080 --> 00:01:54.960 completely offloading their entire IT infrastructure 59 00:01:54.960 --> 00:01:57.720 by using third party services that use VDI. 60 00:01:57.720 --> 00:02:00.030 It's really tempting for a CIO to do this 61 00:02:00.030 --> 00:02:01.620 because now they don't have to run 62 00:02:01.620 --> 00:02:03.000 the operating systems anymore. 63 00:02:03.000 --> 00:02:04.560 They don't have to worry about patching them 64 00:02:04.560 --> 00:02:05.760 because the third party provider 65 00:02:05.760 --> 00:02:07.440 can do all of it for 'em. 66 00:02:07.440 --> 00:02:09.690 That's one of the huge benefits of VDI 67 00:02:09.690 --> 00:02:11.220 and one of the main selling features. 68 00:02:11.220 --> 00:02:13.380 But it isn't all good news. 69 00:02:13.380 --> 00:02:15.180 One of the bad things about VDI 70 00:02:15.180 --> 00:02:16.560 is that users have very limited 71 00:02:16.560 --> 00:02:18.150 local processing ability. 72 00:02:18.150 --> 00:02:21.360 So if the server is down or the network goes down 73 00:02:21.360 --> 00:02:22.860 or the connectivity is down, 74 00:02:22.860 --> 00:02:24.990 your users can't do any work. 75 00:02:24.990 --> 00:02:26.730 So if there's an outage on that server, 76 00:02:26.730 --> 00:02:28.020 everybody is down. 77 00:02:28.020 --> 00:02:30.420 Whereas right now I'm sitting on my laptop 78 00:02:30.420 --> 00:02:31.920 and if my internet connection goes out, 79 00:02:31.920 --> 00:02:33.570 I could still do my work. 80 00:02:33.570 --> 00:02:35.790 But in VDI, I couldn't do that 81 00:02:35.790 --> 00:02:37.560 because if my network connection goes down, 82 00:02:37.560 --> 00:02:38.940 I can't reach the server. 83 00:02:38.940 --> 00:02:40.800 And so I would be out of luck. 84 00:02:40.800 --> 00:02:41.910 So these are some of the things 85 00:02:41.910 --> 00:02:43.830 you have to think about as considerations 86 00:02:43.830 --> 00:02:44.670 when you talk about moving 87 00:02:44.670 --> 00:02:47.310 to a VDI-based virtualization solution. 88 00:02:47.310 --> 00:02:48.780 Now there are currently three models 89 00:02:48.780 --> 00:02:51.060 for implementing virtual desktop infrastructures 90 00:02:51.060 --> 00:02:52.290 within our network. 91 00:02:52.290 --> 00:02:54.090 The first is a centralized model. 92 00:02:54.090 --> 00:02:55.980 And this hosts all the desktop instances 93 00:02:55.980 --> 00:02:58.200 on a single server or server farm. 94 00:02:58.200 --> 00:02:59.970 The second is a hosted model. 95 00:02:59.970 --> 00:03:02.250 In this model, the desktops are instead maintained 96 00:03:02.250 --> 00:03:03.840 by a service provider and provided 97 00:03:03.840 --> 00:03:05.640 to the end user as a service. 98 00:03:05.640 --> 00:03:08.700 We call this DAAS or desktop as a service. 99 00:03:08.700 --> 00:03:10.740 Services like Amazon Workspaces, 100 00:03:10.740 --> 00:03:13.560 VMware Horizon Air, and Citrix Xen desktop 101 00:03:13.560 --> 00:03:15.000 are just a few of the most popular 102 00:03:15.000 --> 00:03:16.500 providers of this service. 103 00:03:16.500 --> 00:03:19.260 The third model is a remote virtual desktop model, 104 00:03:19.260 --> 00:03:21.030 which involves copying the desktop image 105 00:03:21.030 --> 00:03:24.420 to a local machine prior to being used by an end user. 106 00:03:24.420 --> 00:03:25.680 This model eliminates the need 107 00:03:25.680 --> 00:03:27.060 for constant network connections 108 00:03:27.060 --> 00:03:28.410 and has much less requirements 109 00:03:28.410 --> 00:03:30.410 for bandwidth than the other two models.