On the Horizon: Top 8 reasons to upgrade to Horizon 8

Since the launch of VMware Horizon 8 in 2020, we have released several updates, including two extended service branch (ESB) releases with Horizon 8 2111 and Horizon 8 2212.  

With general support ending for Horizon 7 on April 30, 2023, now is the time to upgrade to Horizon 8. Upgrading will ensure uninterrupted support for your Horizon environment beyond April, plus you’ll also be able to take advantage of some great new features only available on Horizon 8. Let’s look at more reasons to upgrade to Horizon 8.  

Host: Andy Whiteside
Co-host: Philip Sellers

Transcript

WEBVTT

1
00:00:02.360 --> 00:00:21.020
Andy Whiteside: Hi! Everyone. Welcome to episode 32 of on the horizon of your host, Andy White side today. Is march thirtieth sorry March twentieth 2,023. Philip Sellers is with me, Philip. You're a solutions architect at z integr for sure you're also leading the charge. It's integr around some key technologies like Vmware.

2
00:00:21.020 --> 00:00:30.810
Andy Whiteside: Pretty much be more everything. But for the context of this conversation, Workspace V. And where workspace workspace one horizon. I get there right?

3
00:00:30.910 --> 00:00:52.080
Philip Sellers: Yeah, absolutely all of the Euc goodness that's in the Vmware portfolio. That's one of the things about them as a company is. Is their portfolio has gotten really large with acquisitions like carbon black. They play in security space, but they've got a really strong competency when it comes to digital workspaces and how we

4
00:00:52.490 --> 00:00:54.380
Philip Sellers: try to help our customers work

5
00:00:54.790 --> 00:01:01.900
Andy Whiteside: fair to say Vmware has the most robust digital workspace offerings in aggregate on the planet.

6
00:01:02.260 --> 00:01:14.310
Philip Sellers: Yeah, I would say so, because you know where you know. Other competitors focus on delivery and apps. You know, Vmware is focusing on, you know. taking the

7
00:01:14.420 --> 00:01:32.760
Philip Sellers: applications and and abstracting them from the operating systems. They're focused on the security aspects of it. You know, both from a white listing perspective on malware, you know full d that are not disaster. But you know emergency response type

8
00:01:32.810 --> 00:01:41.330
Philip Sellers: posture with the carbon black portfolio. So and also you know how we connect in with Sassy and with.

9
00:01:42.050 --> 00:01:54.810
Philip Sellers: you know that's the way in technologies, you know they they run the gambit when it comes to the networking space and and trying to get connectivity between all your different applications You're delivering out

10
00:01:54.890 --> 00:02:03.730
Andy Whiteside: all right. So i'm gonna i'm gonna put you on the spot to answer this. We didn't stage it. So you've got vmware with the widest portfolio in the digital workspace space.

11
00:02:03.930 --> 00:02:20.610
Andy Whiteside: You know everything from apps to desktops, to mobile device, management and security and profile management, and the the the infrastructure that goes underneath, and about 30 other products that make up what is V and our workspace. You know the port, the the portal, the you know, the landing page.

12
00:02:20.610 --> 00:02:37.700
Andy Whiteside: The workspace itself workspace, one landing page at the same time as a company you can tell over these years. They've been taking all these products and bringing in the full bringing the fold. And now this now, and we're helping them with this. They're doubling down on the application side of the equation.

13
00:02:37.820 --> 00:02:39.620
Andy Whiteside: How do you explain that?

14
00:02:40.150 --> 00:02:47.160
Philip Sellers: Well, I mean that's what we've always cared about? Right? I mean it's always about delivering the application at the end of the day.

15
00:02:47.160 --> 00:03:08.440
Philip Sellers: The application is what makes our user. Productive. And so it's really always been about the application. But there's some things they're doing that, you know. Yeah, they're They're touting. 99% of all applications can be virtualized with their at volumes technology. And that's a a huge

16
00:03:10.190 --> 00:03:12.190
Philip Sellers: statement to make, because

17
00:03:12.270 --> 00:03:31.200
Andy Whiteside: we've been after this for years and years in in our space to try and unbuckle that application, and all of the conflicts that come with that application from the other applications we want to put side by side in an operating system image, and we've been chasing this for the better part of 20 years. I I think I've heard you say that right?

18
00:03:31.450 --> 00:03:35.510
Andy Whiteside: It's all about the apps. But here's Vmware has been all about the ecosystem

19
00:03:35.600 --> 00:03:51.860
Andy Whiteside: and a little bit about the apps. Now they're going. Oh, yeah, I get it. It's all about the apps and the ecosystem. So in theory you could argue that they're bringing it all together at the right time where you got this ecosystem of players. But application centric it's it's a pretty, it's pretty bold move, in my opinion.

20
00:03:51.870 --> 00:03:54.540
Andy Whiteside: and probably a good one.

21
00:03:54.720 --> 00:04:16.240
I I think it's a very good one, and their app story doesn't end here in the traditional app space. They're doing a lot inside of cloud, Native and Tanzu, and being able to empower developers to to create apps that scale on cloud architectures. But they're not forgetting the fact that

22
00:04:16.240 --> 00:04:36.240
Philip Sellers: I a. And this is a still statistics. It's not backed up by gardener or Itc. Or anybody else. But I would say 80% of applications that our customers run are still traditional client server applications that have to be delivered, and that's the space we're really kind of talking about today with horizon is is empowering all of those traditional apps

23
00:04:36.240 --> 00:04:48.620
Andy Whiteside: out to our users. Yeah, yeah, you kind of meet me to my my transition here, and I I assume I've done this to you before. If you've heard many of our podcasts, I've done it a lot of people most widely use Microsoft application in the world is

24
00:04:48.930 --> 00:04:57.200
Andy Whiteside: Microsoft windows, windows. And so this is going to make a nice conversational segue Here we're going to talk about Horizon 8, and why people

25
00:04:57.240 --> 00:05:02.770
Andy Whiteside: need to get on to that platform and get off the legacy platforms if they haven't already.

26
00:05:03.210 --> 00:05:07.550
Andy Whiteside: Let me let me share my screen so you can see what i'm looking at.

27
00:05:09.180 --> 00:05:26.360
Andy Whiteside: All right. So the topic is to blog from the Vmware blog site top 8 reasons to upgrade to horizon 8 by Riley. We're gonna say buoy. Hopefully, I got the last name right or close February thirteenth, of 2,023. So Philip in the introductory paragraphs here.

28
00:05:26.370 --> 00:05:43.030
Andy Whiteside: Why is this blog relevant? Well, horizon. 8 came out in 2020, and we're at a point now where the company is really ready to sunset. Horizon 7. So we've got the end of general support, coming up on April the thirtieth

29
00:05:43.030 --> 00:05:59.820
2023, so about a month from where we're at today, so with that end of general support horizon 8 is the path forward for customers. So everyone with active support and subscription SMS agreements, and with

30
00:05:59.820 --> 00:06:21.570
Philip Sellers: vmware, is entitled to an upgrade to Horizon 8, and if you've not already charted your passport, it's a really great time before you end general support. I know a lot of times. We have customers that say you know it's not broken. I don't really need to change. But this is one of the big factors providing support

31
00:06:21.650 --> 00:06:24.610
for the product in in

32
00:06:24.940 --> 00:06:38.920
Andy Whiteside: you know, running without support. That's a pretty risky situation, so it's a good time to start charting your path forward so it's. It's kind of a cure and stick model as we have the car, which is all things we're going to talk about. But at the end of the day, when supports no longer available for it. That's a stick.

33
00:06:39.160 --> 00:06:39.960
Philip Sellers: Yeah.

34
00:06:40.280 --> 00:06:54.520
Philip Sellers: yeah. And you don't want to. I know where Andy's going. Here. You don't want to get beaten with the stick, so let's try to get out in front of that, and of course get some of this goodness that's included in the horizon 8. And how long is the rising? 8 been out.

35
00:06:54.850 --> 00:07:13.590
Philip Sellers: It's been out since 2020, so it's been out and in mainstream for a couple of years already. Now, granted we have this big thing we're talking about the pandemic that occurred at the same time. So it's understandable that a lot of customers haven't been able to get into the data center and upgrade their horizon infrastructure.

36
00:07:13.590 --> 00:07:17.880
Andy Whiteside: Now, folks are using the full cloud model. Does this even a relevant conversation?

37
00:07:18.350 --> 00:07:30.520
Philip Sellers: It is because you've still got certain components and and pieces where you're gonna need to life cycle those regardless of if you're using the the Vmware provided cloud control planes.

38
00:07:30.520 --> 00:07:42.170
Andy Whiteside: But certainly that does ease the burden for a life cycle project. If you're using the cloud control plan, so it's a great time to think about adapting those.

39
00:07:42.490 --> 00:07:55.680
Andy Whiteside: All right. So we're going to take in 2 sections. There's going to be, I think, 4 that talk about desktop apps and infrastructure, and then for the talk about the user experience. First one is a number one here hybrid and multi-cloud support, as it relates to 8 versus 7 what we have

40
00:07:55.890 --> 00:08:25.880
Philip Sellers: yeah so version 8 has bring it. It's brought a lot of new capabilities. So there's a first party service for horizon on azure, Vmware solution, and and then also the horizon on Amazon workspaces. So you You're seeing Vm. Where work closely with the hyper scale cloud partners providing new capabilities, and so that involves their control plane as well. So within the control plane. You've got the capability

41
00:08:25.880 --> 00:08:42.220
you need to take the known horizon. Console your web, uniform, interface where you control everything else on premises. And now talk to these cloud providers. So 8 brings horizon for Amazon workspaces, as well as the azure virtual solution.

42
00:08:42.220 --> 00:08:50.240
Philip Sellers: So that's in addition to the first party horizon cloud service that is also hosted on azure.

43
00:08:51.630 --> 00:08:52.270
Andy Whiteside: There.

44
00:08:53.450 --> 00:08:59.370
Andy Whiteside: Second was in improved instance, cloning, or in sorry instant cloning. I should know that

45
00:08:59.640 --> 00:09:17.130
Philip Sellers: Yeah. So instant clones. That's a Vmware specific technology, and it really helps rapidly replicate your images out and create quick startups for desktops. Really, in seconds

46
00:09:17.130 --> 00:09:47.130
there's no requirement for a parent virtual machine in that provisioning model which reduces your costs and can also increase your desktop for host consolidation, ratio. So this is a a big deal, because in the Bds space the number of users you can fit onto your actual physical infrastructure has a lot to do with the cost effectiveness of the model. So any kind of increases in that space

47
00:09:47.130 --> 00:09:50.660
Andy Whiteside: they're always welcome from our perspective. Right? Okay?

48
00:09:51.110 --> 00:09:56.860
Andy Whiteside: Well, let's talk about that for a minute. What what percentage of the horizon implementations that are using, I guess, on prem

49
00:09:57.140 --> 00:10:15.040
Philip Sellers: implementations or hardware. Do you think I've gotten instant calls? Do you have any idea what the breakdown between that and maybe the legacy Link Clones. Yeah, I don't. I mean, we. We certainly try and push this as the model. But Link Clones is viable, and there are some things that

50
00:10:15.710 --> 00:10:18.810
Philip Sellers: that differentiated. I mean, you know you've You've got

51
00:10:19.570 --> 00:10:49.570
Philip Sellers: core enhancements for this version. You know where you've got multiple nicks is this app support? So there's a lot of things that they've added in to help adopt instant clones. It's the first place we want to go, because it's the quickest route to getting your infrastructure to scale quickly. And that's that's really the end goal. Here is powering the ability to run just in time and and not have to pre provision and have resources

52
00:10:49.570 --> 00:11:00.300
Andy Whiteside: sitting out there idle in a pool, waiting on a user to request it. It's the clones. It's really gonna allow you to to do things just in time. No, it's really awesome.

53
00:11:00.330 --> 00:11:03.530
Number 3 on the list. Here is Apis for automation.

54
00:11:03.670 --> 00:11:13.930
Philip Sellers: Yeah, you know. I mean, this is this is fantastic stuff. I'm: a huge proponent of automating anything you can automate. So you know, Enhance, rest. Apis.

55
00:11:14.340 --> 00:11:44.330
Philip Sellers: It's one step towards getting more and more toolkit out there. So whether your automation is the ansible terraform type route, or if it's power, Cli being able to have the Api available to you, unlocks the power of automation. So this is just another form of goodness, you know. There's a full list available out and link to this blog post, where you can see all the different new Apis that are available in horizon.

56
00:11:44.330 --> 00:11:45.310
But

57
00:11:45.340 --> 00:11:56.610
Philip Sellers: again, this is something where there was some work to do so. Some of the products from Vmware have been Api driven Api. First type implementations.

58
00:11:56.910 --> 00:12:07.770
Andy Whiteside: horizon hasn't necessarily fallen into that category. So there was some catch up, and some new apis that needed to to be developed. But it's great to see them delivering on that today.

59
00:12:07.950 --> 00:12:13.540
Andy Whiteside: Number 4 here and there's actually 5. I'm. Just let us early in 5 and 3, which still equals 8.

60
00:12:13.710 --> 00:12:18.490
Andy Whiteside: Number 4 is scaling more desktops and sessions per pod.

61
00:12:18.710 --> 00:12:29.850
Philip Sellers: Yeah. So, Pod architecture, something we talk about a lot with customers when it comes into fail over and load, balancing across geographic regions or across data centers.

62
00:12:29.890 --> 00:12:43.640
So the pod architecture, something that is alive and well. I had a customer asked me last week. Is that thing still around? Is that still something we can use? And and the answer is resoundingly, Yes, pods still exist.

63
00:12:43.640 --> 00:12:52.110
and they've increased our maximums up to 20,000 desktops and sessions per pod, which is a astronomical number. I mean, that

64
00:12:52.300 --> 00:13:04.900
Andy Whiteside: that is a huge enterprise level type, level up for the product line, and it now supports the maximum of 500 virtual machines for Esx. I. Host

65
00:13:04.900 --> 00:13:22.680
Andy Whiteside: when you're using traditional storage. So that's another huge improvement over where we were at in the previous version. All of that goes to just being able to scale and meet the demands of customers. Right? And that's what it is all about, right. The solution has been solid for a while, but

66
00:13:22.760 --> 00:13:27.310
Andy Whiteside: new needs require new versions, and being we're stepping up to that

67
00:13:27.820 --> 00:13:36.710
Andy Whiteside: apps on demand for published app environment. This goes to our application conversation a while ago. But tell us how this is enabled by getting to horizon 8.

68
00:13:36.760 --> 00:14:04.380
Philip Sellers: Yeah. So apple and demand, and it's just like the instant clone conversation just in time. We really want to accelerate how fast a user gets to productivity. So one of the most common complaints that we get across all digital workspace products is login time, right. So when we're doing a Vdi session, how long it takes to get to that desktop is a source spot for a lot of users.

69
00:14:04.380 --> 00:14:12.300
and so apps on demand is a way of solving that where we don't have to wait for the app to be copied and delivered

70
00:14:12.320 --> 00:14:38.040
Philip Sellers: and merged into the windows operating system. It can be called at the time that the user actually launches it so uses the same app volumes technology that many customers already have deployed. It uses the same agent. It just changes the way, and when the merge activity happens so that the app only gets triggered and pulled into the image when the user actually starts to use it.

71
00:14:38.190 --> 00:14:43.920
Philip Sellers: Other huge benefit. It's not just for Vmware. You can use this across

72
00:14:43.960 --> 00:14:49.480
Philip Sellers: any different solution. Citrix Microsoft, from a desktop farms.

73
00:14:49.900 --> 00:15:02.890
Philip Sellers: and there's some other things that are gonna be coming out in the near future. And so I I would just say, let's let's have another conversation after agile disrupt, and be looking for what?

74
00:15:02.890 --> 00:15:10.790
Andy Whiteside: What Vmware has to say during the disrupt conference? Well, it's fair to tie it back to this blog, and say that if you want what could be coming around the corner, you better get to 8,

75
00:15:11.370 --> 00:15:23.600
Philip Sellers: absolutely being current. Also make sure that you get the best of these new features. And this is a potential game changing feature. Really, love what Vmware is doing in this space.

76
00:15:24.030 --> 00:15:33.890
Andy Whiteside: alright, so that moves us on to the user experience portion of the blog. I'm glad she laid it out this way really makes a lot of sense. Number 6 on the list is optimized experience for collaboration.

77
00:15:34.070 --> 00:15:55.530
Philip Sellers: Yeah, I mentioned it a little while ago. But you know, the pandemic has forced our hand on a lot of different things. Collaboration software is one of those things. So across the board I mean, teams was kind of in its infancy pre pandemic back in 2019, 2020, and you know, Zoom

78
00:15:55.550 --> 00:16:08.990
Philip Sellers: capitalized greatly on the pandemic and Zoom Meetings. I mean their brand has become synonymous with it. But delivery of those was shaky in the beginning, and it's gotten progressively better and better

79
00:16:09.110 --> 00:16:25.380
Philip Sellers: version. 8 really came out, and there are releases within the version 8 lineage of horizon that help us with teams, Webex and Zoom. This time of collaboration has become mainstream.

80
00:16:25.380 --> 00:16:37.200
and the controls and the delivery of that are never better than on this new version. So I think anybody that's on version 7. But relying on

81
00:16:37.200 --> 00:16:48.190
Philip Sellers: video conferencing and and collaboration platforms, you're doing a disservice to your customers. If you're not on version 8. There's just too much there to benefit from.

82
00:16:48.360 --> 00:16:48.920
Okay.

83
00:16:48.940 --> 00:17:18.490
Andy Whiteside: So the next one the list is blast improvements, Aka presentation protocol, you know, with somebody missing the other day that the Protocol wars are over, you know. I think if I'm. Vmware, or several other players, but mostly V. And we, if I've got the investment I've made in the blast Protocol. This Udp maybe falls back to Tcp. Or Udp base protocol. I'm adamant to the Protocol wars, or not over especially if you consider all the different channels and enablements that need to. Still, you know, continue to evolve as technology

84
00:17:18.490 --> 00:17:22.069
and use cases, evolve blast improvements cover that one.

85
00:17:22.359 --> 00:17:30.400
Philip Sellers: Yeah, I mean, here here's the the reality of of the situation. If you can't attach peripherals. you're in trouble.

86
00:17:30.500 --> 00:17:47.610
Philip Sellers: And this is where some of the other alternatives really struggle. But we know you know I I I was at the dentist an hour ago for a cleaning. You know my dentist has scanners. They have a

87
00:17:47.610 --> 00:18:04.150
Philip Sellers: logitech camera, and all of these other peripherals on their device. So if you're working in an office like that, these things have to be there you get a credit card machine to attach. So Protocol was far from over, in my opinion, because

88
00:18:04.150 --> 00:18:17.280
Philip Sellers: the technology continues to evolve and change, not just peripherals. But we're talking about 4 K. 5, K. 8, K. Video. I think the delivery has never been

89
00:18:17.320 --> 00:18:31.110
Andy Whiteside: more intensive than what we've got today. With that, you know. I mean it's it's not just a small screen we're delivering anymore. We're we're delivering multimedia live video, all sorts of more complex things.

90
00:18:31.110 --> 00:18:37.810
Philip Sellers: And the way you saw, for that is the protocol. So we talk about it on a technology layer. But the

91
00:18:38.040 --> 00:18:45.900
Philip Sellers: the correlation is all of these new demands to provide very high quality. very

92
00:18:46.110 --> 00:19:01.350
Andy Whiteside: intricate displays, and and all you need is one thing that you need to work in order for that project. In that group of users within your organization to be successful. And if you plug that one thing in, or have that one use case and the protocol you're using, doesn't. Enable that

93
00:19:01.520 --> 00:19:14.440
Andy Whiteside: then your project essentially fails just because of one feature that needed to be enabled through a channel through the protocol.

94
00:19:14.820 --> 00:19:19.600
Philip Sellers: You know all of the different things required to make the job work at the end of the day.

95
00:19:19.880 --> 00:19:23.330
Andy Whiteside: If you're missing that core function gone

96
00:19:23.970 --> 00:19:48.300
Andy Whiteside: and and the call transparently here, if you're talking about a solution that just uses Microsoft, Rdp: which, by the way, has gotten pretty okay. I'm: pretty good at delivering the the of the screen and the keyboard and mouse like. But it's just that one missing channel that might be in what I would call today's minimal viable product that everybody has access to all of a sudden you got a project that's on the verge of failing just because you went with the minimal viable protocol, which again has come a long way.

97
00:19:48.300 --> 00:19:58.050
Andy Whiteside: But there's still things it doesn't do well in, and you know my lineage as an administrator, hands on keyboard, using Rdp. For remote administration. It was always good enough for that.

98
00:19:58.110 --> 00:20:03.960
Philip Sellers: but the differences I wasn't attaching peripherals, I wasn't attaching credit cards.

99
00:20:04.000 --> 00:20:10.370
things like that. So when you get into those use cases. It's not a corner case. This is a mainstream

100
00:20:10.370 --> 00:20:27.090
Andy Whiteside: use case that we talk about every day with our our different customer basis. You know whether that's, you know, banking retail, I mean even clinical, as as we said, like I was at the dentist. I get credit card machines attached to to the systems for sure.

101
00:20:27.160 --> 00:20:31.180
Andy Whiteside: All right. Well, Riley kind of set us up here because the last one is a whole bunch of them.

102
00:20:31.330 --> 00:20:38.300
Andy Whiteside: So i'm just gonna read through them, and if you could just succinctly hit each as I read through, and the first one is Linux hosted Apps.

103
00:20:38.340 --> 00:20:52.070
Yeah, Linux hosted apps is is a really great capability. You know. We've had the ability to do Linux desktops. Now we can actually deliver just the app itself, just like we do in the traditional horizon

104
00:20:52.070 --> 00:20:59.530
Andy Whiteside: on windows products. Next one is additional support for Ipv. 6, such as Cpa and HTML access.

105
00:20:59.650 --> 00:21:15.610
Philip Sellers: So this is another great thing. I mean we've been. We've been talking about the exhaustion of Ipv. 4 public addresses and the move to ipv 6. It's still lags behind, but it's great to see that they're putting in the time and effort to make these work over. Ipv. 6.

106
00:21:15.700 --> 00:21:18.730
Philip Sellers: There are some places where it's in use.

107
00:21:20.380 --> 00:21:31.240
Philip Sellers: but you know we Haven't talked anywhere about HTML access, so I will put a plug in here, since it's listed. This is one of the great differentiated features

108
00:21:31.240 --> 00:21:43.120
you can take horizon and deliver to any product whether that's an ipad without a client or a chromebook, it really allows you a lot of flexibility to deliver your apps

109
00:21:43.680 --> 00:21:46.600
Andy Whiteside: next one is session recording for horizon.

110
00:21:47.080 --> 00:22:14.920
Philip Sellers: You know this. This may be a support type. Use case, but it's helpful to have, you know, a picture of videos worth of 1,000 words. But you can do session recordings. You can use it and leverage it for other things. But I think in my mind I think of it as a support type mechanism. But i'm sure there's other ways that we can do it, including integrations from third parties to do compliance. I know that

111
00:22:14.920 --> 00:22:22.250
working in the the insurance or the banking space. Sometimes we have to record contractors and things like that. So this gives

112
00:22:22.370 --> 00:22:31.720
Andy Whiteside: third parties ways to integrate and get that kind of session recording next one is post-ree SQL database support

113
00:22:31.900 --> 00:22:58.600
Philip Sellers: Yeah. So traditionally, we've relied on Microsoft Sequel for the underlying things and you know, as far back as the center, you know, being a windows application based on SQL. Server, we didn't really have a choice. Vmware is pushed really hard in giving customers choice, particularly a free database Postgres is the one that they've standardized on, and that comes here to horizon 8 as well.

114
00:22:59.480 --> 00:23:02.280
Andy Whiteside: Importation of Ssl. Certificates

115
00:23:02.670 --> 00:23:03.270
it.

116
00:23:03.480 --> 00:23:10.570
Philip Sellers: So this is a good one, and it's a very technical thing. But this allows you to

117
00:23:10.570 --> 00:23:27.970
Philip Sellers: to move your Ssl certificates from implementation a little more easily. I'm not sure that it has a huge user impact at the end of the day, but certainly can make some transitions and some migrations a lot easier

118
00:23:28.630 --> 00:23:32.840
Andy Whiteside: upgrading, multiple horizon connection servers at one time.

119
00:23:33.480 --> 00:23:51.910
Philip Sellers: So for our large scale customers who have to scale out connection servers, this is a a huge time saver, you know, for the customer that has one or 2 connection servers. Probably not a feature they're going to tap into. But for our enterprise customers. Certainly something that's a welcome change.

120
00:23:52.280 --> 00:24:14.500
Andy Whiteside: And then, finally, the last one which i'm super passionate, interested in, and that is the kind of grand any of them all, at least in the X. 86 world, and that's a. V. Sphere, which is also, you know, Esx. But Esx. I. With the Sphere Management V. Sphere 8, and then the the kind of upstart one which has been around for a while. But to to my knowledge, is really taking a leap forward, and that's Vc. And 8 support.

121
00:24:14.570 --> 00:24:17.590
Philip Sellers: Yeah. So these fear 8

122
00:24:17.620 --> 00:24:35.310
may seem like just an incremental release. But there's a lot that Vmware has really put into the platform, and V. Sands no different. V. Sand got a huge upgrade with version 8. They've got an entirely rewritten stack to make use of it.

123
00:24:35.330 --> 00:24:54.800
Philip Sellers: This new version is far more performant. It is a a huge, huge step forward for customers who run the Vmware hyper converge stack. I met a guy for coffee this morning, and he was educating me on the same 8, and what all it can do and, man.

124
00:24:54.800 --> 00:25:04.590
Andy Whiteside: it really has to come along the way, and really is a game changer. And you know again highlighting the Vmware side of the equation. Here you got workspace one that brings all this stuff together. You've got this

125
00:25:04.590 --> 00:25:22.570
underlying hypervisor which you know hypervisor. Wars have been over for a while. I don't know stuff like this starts to tell you that that hypervisor, and something like this, and and the ability to have a turbo charger under the cover for your your vmware horizon world is, you know, still very relevant.

126
00:25:22.570 --> 00:25:41.560
Philip Sellers: and something that we can't just rest on our laurels on. Well, this is the place where competition is rewarding for the customer right? So each company coming up with their next iteration, their next innovation. It forces the competition to to keep up. And so

127
00:25:41.560 --> 00:25:57.300
Philip Sellers: you know who's the competition? Well, that changes year year, but competition does yield better performance, better innovation for the customer. So all the hypervisor wars may be over, and that's debatable.

128
00:25:57.470 --> 00:26:14.360
Andy Whiteside: I I think that we benefit by all these companies, continuing to push each other, not only at the hypervisor wars not really over, but the intelligence that goes along with it to nested on top of hyper scalar, at least hyper scalar data centers and just makes it even more relevant potentially.

129
00:26:14.600 --> 00:26:16.240
Philip Sellers: Yeah, I am.

130
00:26:16.320 --> 00:26:32.240
Philip Sellers: I'm just finishing up Vmware Cloud on Aws training the official classes and learn quite a bit about how that solution is is implemented. You know we've we've worked with a number of customers on it. But

131
00:26:32.240 --> 00:26:58.900
Philip Sellers: you know, with all of our partnership things, we we do the official training and things like that to go along with it, and it really is cool to see how what we've done on Prem. Translate to them to these hyper scale clouds, and then how that feeds back in. You know one of the things that I didn't talk about with these fear 8. But that is an idea that I feel like was born in a hyper scale cloud. Is this this idea of offloading

132
00:26:58.900 --> 00:27:06.250
Philip Sellers: some of your management functions to Dp use or to sidecar type processors? That's a a

133
00:27:06.350 --> 00:27:25.610
Philip Sellers: Amazon very centric where they have a Co. Management thing sitting next to their bare metal. And now that idea is coming into V 4 8, with, you know, the introduction of data, processing units and smart nicks and things like that that are part of the V's. For 8. But that's a whole. Another topic for another time.

134
00:27:25.730 --> 00:27:42.950
Andy Whiteside: Yeah. Well, Philip, that was great, and i'm sure there's other reasons. But this is really well laid out. Conversation around the top reasons, or some of the top reasons, and you just pointed out yet another one. Was there anything that Riley left off that you're aware of? That would be on your list if you could have come up with Number 9.

135
00:27:43.500 --> 00:28:00.190
Philip Sellers: If I can add number 9, I would say the integration across all the Vmware products is another reason to move forward with horizon 8. We've been on this trajectory where they're merging together the horizon at volumes.

136
00:28:00.190 --> 00:28:18.580
Philip Sellers: workspace one, and and pulling the ecosystem together closer and closer, so that we have that single pain of glass for our user experience. And that really is another reason. I think, that that horizon aid is the right platform because

137
00:28:18.950 --> 00:28:38.730
Philip Sellers: we've got those pieces coming together from from workspace, one to be able to do modern management to be able to do non windows device and endpoint management. We've got so much from a holistic and 0 trust security type model

138
00:28:38.770 --> 00:28:44.060
where this becomes part of a much bigger picture when you take it together as a whole.

139
00:28:45.090 --> 00:28:46.190
sir.

140
00:28:46.700 --> 00:29:01.880
Andy Whiteside: I'm. Trying to find a good way to in these podcasts. It's kind of catchy across all my different podcasts that we do. And if I were to say Phillip well, Magua, I think you've done it well, because I think we've died of Google. The phrase it's been so long. You know what i'm talking about.

141
00:29:02.050 --> 00:29:04.850
I don't. I don't recognize that one.

142
00:29:05.530 --> 00:29:24.350
Andy Whiteside: You don't want to do the Bob Barker, you know. Make sure to get your your pets paid or neutered, I mean. Well, let's do that. So I use this this podcast to encourage you to check out computers for community.org and get involved over there, which is the nonprofit that we, as in tech rep that started

143
00:29:24.350 --> 00:29:37.450
Andy Whiteside: so go check that out, and maybe get involved over there as a way to give back to what you get out of the efforts we put into this. Well, Philip, thank you for your time, and going over this I can't wait. To share with people. Content was awesome.

144
00:29:38.360 --> 00:29:40.590
Philip Sellers: Appreciate it, Andy, always a pleasure.

145
00:29:41.100 --> 00:29:43.510
Andy Whiteside: and we'll look forward to doing again in 2 weeks.