Many organizations are considering the best infrastructure for deploying virtual apps and desktops. The choice is essentially between on-premises and cloud solutions, or a mix of both. Is on premises or cloud better than the other? On-premises virtual desktop infrastructure (VDI) gives IT departments control over their environments — but requires daily maintenance and can be complicated to scale up. Cloud computing desktop as a service (DaaS) models reduce IT complexity and physical infrastructure costs.
Each infrastructure has its advantages and disadvantages. Determining which model is best for your business will depend on your company’s needs and a few other factors. In this post, we’ll look at some of the most important elements to consider when deciding between cloud computing vs. on premises.
Host: Andy Whiteside
Co-host: Bill Sutton
Co-host: Geremy Meyers
Many organizations are considering the best infrastructure for deploying virtual apps and desktops. The choice is essentially between on-premises and cloud solutions, or a mix of both. Is on premises or cloud better than the other? On-premises virtual desktop infrastructure (VDI) gives IT departments control over their environments — but requires daily maintenance and can be complicated to scale up. Cloud computing desktop as a service (DaaS) models reduce IT complexity and physical infrastructure costs.
Each infrastructure has its advantages and disadvantages. Determining which model is best for your business will depend on your company’s needs and a few other factors. In this post, we’ll look at some of the most important elements to consider when deciding between cloud computing vs. on premises.
Host: Andy Whiteside
Co-host: Bill Sutton
Co-host: Geremy Meyers
WEBVTT
1
00:00:02.490 --> 00:00:17.910
Andy Whiteside: Hello, everyone, and welcome to episode One hundred and fourteen of the Citrix session and our host, Andy White. So I had to hesitate. I just looked it up, and we had a conversation slightly like I don't know ten seconds worth, and I had forgotten. I guess that's because we've got so many of these
2
00:00:18.070 --> 00:00:26.980
Andy Whiteside: that they're all kind of running together. Jeremy Myers is with us. Jeremy is the director of Sales engineering for the East Coast for citrix. Jeremy. How's it going?
3
00:00:26.990 --> 00:00:32.250
Geremy Meyers: Fantastic How you doing Andy good from your perspective? Should we,
4
00:00:33.010 --> 00:00:37.880
Andy Whiteside: Should we do seasons, or should we just keep adding up the sessions.
5
00:00:38.470 --> 00:00:56.490
Geremy Meyers: I like seasons right. I mean I get it the number, you know what. No, the the podcast that I, one of the podcasts I follow a lot is windows weekly out on uh podcasting, and they're up to like episode One thousand four hundred something. Yeah, I just made that up. But I don't know I like that. Let's just keep doing that
6
00:00:56.500 --> 00:01:10.030
Geremy Meyers: all right. So quick sneeze. I know that I I love what we do Here we get down to it. We cover the content, and then we hang up right that windows weekly podcast. I can't listen to it anymore, because it's three and a half hours, and it's. This is only like thirty minutes,
7
00:01:10.040 --> 00:01:25.349
Geremy Meyers: so I mean full disclosure. Here's how I listen because I love, I do love the insight, especially around what's coming on windows desktop when there's ten when there's eleven and stuff like that. Did the hardware, which is great, and Mary Joe also covers some of the upright stuff. But
8
00:01:25.360 --> 00:01:35.149
Geremy Meyers: you're right that that podcast is like two or three hours long, and I only listen to it as i'm coming and going to the gym each day, so I catch it in about eleven minute increments,
9
00:01:35.160 --> 00:01:36.789
Geremy Meyers: and that's about enough.
10
00:01:36.800 --> 00:01:37.689
Geremy Meyers: It's about death,
11
00:01:37.700 --> 00:01:57.190
Geremy Meyers: but it does take me. It takes me a week. It does. You can never get through it. I mean, I I try to listen on the plane. I'll I'll take off and land, and i'm watching. I'm listening at that super fast speed, and I still don't get through the thing because it's just, and I like what to do, and my one of my measurements for a success, and what we're doing here is hopefully someday they're going to reach out to me and ask me to join the podcast for just one episode
12
00:01:57.200 --> 00:02:06.189
Geremy Meyers: on the the Avd. Or M. Three hundred and sixty, five or windows three hundred and sixty five. I know It's never going to happen, but because I listen to it for so many years.
13
00:02:06.200 --> 00:02:12.020
Geremy Meyers: Yeah, Bill Sutton is whether this bill's a director of services as Integrate Bill, How's it going? It's going. Great. Andy,
14
00:02:12.550 --> 00:02:14.290
Andy Whiteside: you Are you staying busy?
15
00:02:14.300 --> 00:02:17.390
Bill Sutton: Oh, yeah, we are really busy, which is a good thing.
16
00:02:17.430 --> 00:02:24.549
Bill Sutton: It's not in many ways. So yeah, we're The team is pretty booked out and working hard.
17
00:02:24.560 --> 00:02:40.299
Andy Whiteside: So if you're listening to this and you're interested in a consulting or helping us with our manage service practice, reach out to myself or Bill and Linkedin, maybe, and you know, let us know we're we're we're growing, and I work. We work really hard to continue to recruit your troops.
18
00:02:40.310 --> 00:02:50.390
Andy Whiteside: Things are good, and we need more help. So if you're interested in working for a very focused end-user, compute digital workspace company that's us and let us know.
19
00:02:50.400 --> 00:02:54.009
Bill Sutton: Yes, I would echo that absolutely reach out.
20
00:02:54.290 --> 00:03:05.980
Andy Whiteside: So. Ah, Jeremy, we got a topic we're going to cover in a minute. But you got rumor of me asking questions at the Idl disrupt in New York last week you were going to ask me about it. I told you to hold off. What? The
21
00:03:06.040 --> 00:03:08.660
Andy Whiteside: what? What? What did you hear happen?
22
00:03:08.670 --> 00:03:13.290
Geremy Meyers: Well, so listen. I didn't get to go to vmware. Um, Is it explorer?
23
00:03:13.300 --> 00:03:24.750
Geremy Meyers: Yeah, all right, Yeah, so I didn't get to go to being worked for um. And then there was an Igel event last week up in New York City, where I think Bm. Were also presented, so I was trying to wrap my head around.
24
00:03:24.760 --> 00:03:39.060
Geremy Meyers: Um! It sounds like there's an evolution of rising cloud. I want to say um, maybe a little bit different than how it worked before, but I wanted to lean into that, and just really understand what that looked like. So from what I gather it's a model that's not unlike
25
00:03:39.070 --> 00:03:57.460
Geremy Meyers: um citrix, and our jazz surface, except for maybe it only covers right now it's an azure out of the gate. Um doesn't include things like gateway type, service functionality. If you're familiar with the the Citrix desk service. So um! I was just trying to understand what it looked like. You know what we're what were some of the
26
00:03:57.470 --> 00:04:02.120
Geremy Meyers: the the high notes there, and kind of where they're headed, obviously as a competitor. I'm trying to understand that's all.
27
00:04:02.130 --> 00:04:05.360
Andy Whiteside: Well, I think it's an interesting conversation, because
28
00:04:05.380 --> 00:04:13.439
Andy Whiteside: you guys have done this. I've done This Citrix has done this where you swing from application-centric conversations
29
00:04:13.450 --> 00:04:25.489
Geremy Meyers: back to maybe desktop conversations which you've ever heard me make the argument I think the windows ui aka. The desktop is the most widely used Microsoft application on the planet.
30
00:04:25.500 --> 00:04:43.830
Geremy Meyers: Um. And so the desktop's just an app to get you to other apps with a convenient, You know you that you're familiar with um. But I think what what a lot of folks are doing, including Citrix. Nbm: Where is really getting conversations trying to steer them back to the world of apps, because as the world moves more towards sass
31
00:04:43.840 --> 00:05:13.199
Andy Whiteside: um modern apps, We were just talking about this in my management. Um! It's gonna be important that players like Citrix, like Vmware um like Microsoft, really stays relevant in that conversation between X eighty six your legacy apps and sas-based modern apps, and I think a lot of the players in this space, including Citrix, is really trying to make sure the conversation um around apps is not neglected, and if the world sees that's where we're all headed,
32
00:05:13.330 --> 00:05:22.720
Andy Whiteside: even though there's been like this ten year timeframe where we try to just get people to desktops, because that's what got more successful quicker. So does that part make sense?
33
00:05:22.780 --> 00:05:41.489
Geremy Meyers: It doesn't, I guess. Um, Maybe this is the last thing you just said. But you know. Why did we and I don't mean like we as in Citrix, were we as in in the two of us? But why did we, as an industry sort of pivot, more towards, maybe a like a I hate to say Vdi, but a full desktop as opposed to an application,
34
00:05:41.500 --> 00:05:45.990
Geremy Meyers: a hosted and presented virtual desktop. Right?
35
00:05:46.000 --> 00:06:14.779
Geremy Meyers: Yeah, that's a good question. And by I see it that way on purpose, because it's virtual because it's running as a virtual object, a virtual entity, and it's also virtual, because It's being presented virtually across a network. It's actually when you talk about a virtual desktop, whether it's vdi or service-based Um! It's. It's two forms of virtual. It's virtualized as a machine, and it's also virtualized as how it's delivered. Um, I that's why I argue all the time. The best thing that Citrix ever had, for in its products was a presentation server, because it truly was presentation for realization.
36
00:06:15.210 --> 00:06:31.219
Geremy Meyers: You you'll appreciate this, then. So I had a conversation with a customer this week who said, and they were just delivering applications, you know. I guess they've been doing that health care for many years. Right? So that's not an unusual use case in healthcare. It's just, you know, presenting the you know the Emr.
37
00:06:31.230 --> 00:06:48.889
Geremy Meyers: But um! They they came to us and said, Hey, you know we're We're thinking about it. Yeah, right? So can we do that? I was happy to tell them that with their bad licensing that they own today. They could do vdi if they wanted to. So we kind of picked apart the use case, and Andy, I was probably talking about Vdi talking about windows ten,
38
00:06:48.900 --> 00:07:02.390
Geremy Meyers: maybe not so much when there's eleven at this point, but windows ten to my head for maybe fifteen minutes before you know we had the conversation around. Well, scaling the back end. What does that look like? And I go, hey? If you're thinking about Vdi, you know it's a single user operating system. You know that's going to have an impact
39
00:07:02.400 --> 00:07:16.829
Geremy Meyers: uh on your resources on the back end uh as opposed to maybe a a server-based Os, you know Rdsh style where you give me several users, and he goes. Yeah, You were thinking about using windows, server two thousand and sixteen, and I go. Oh,
40
00:07:16.840 --> 00:07:28.169
Geremy Meyers: so this fifteen minute conversation about me. Yeah, I didn't tell him this was really just the same old thing we've been doing for years, and I didn't correct him, because honestly, then, today wasn't super super relevant. But
41
00:07:28.380 --> 00:07:32.790
Geremy Meyers: listen it's it's confusing, and you know the whole idea of Vdi is just
42
00:07:32.800 --> 00:07:34.779
Geremy Meyers: It's a sort of a generic term.
43
00:07:34.790 --> 00:08:04.780
Geremy Meyers: That's why I talk about it in terms of um, you know digital workspace, and then you break that down to more. Ah, desktop virtualization, whether it's media or server hosted single single session, multi session um. And And so, Jeremy, your question was, why did we push people towards Vdi for the past ten years, and that's because all the complexities of you know, taking a server desktop and presenting that as a virtual or physical machine to the endpoint, and meanwhile be calling the apps and delivering the apps through streaming, or later,
44
00:08:04.790 --> 00:08:30.719
Andy Whiteside: or presentation into that virtual session, to then turn around and be virtually delivered again. All that got squashed when you did, Bdi, or it didn't didn't have to, but it made it easy. If you just said, Okay, you know that thing you do on the physical desktop. Just do that on the virtual desktop on top of a hypervisor, and then present that for the endpoint. And what you have to know, Mr. Customer, is different, but not that different. If you can just do that, there's a chance that you
45
00:08:30.790 --> 00:08:39.690
Andy Whiteside: be successful, and that's pretty much been. Why, the last ten years have been the year of Vdi. Well have been Vdi above all else
46
00:08:40.520 --> 00:08:44.539
Geremy Meyers: that that makes sense. You know It's a learning curve thing right? So you
47
00:08:45.140 --> 00:08:46.319
Geremy Meyers: I get it,
48
00:08:47.120 --> 00:08:57.060
Andy Whiteside: and that's the key Right? I mean. There's just so many different ways. You can go left or right. Okay. So the thing last week I was at the the biggest part of the presentation was around app
49
00:08:57.070 --> 00:09:19.109
Andy Whiteside: virtualization of some type, not layering, not streaming something in between that's supposed to increase the percentage of applications that you can virtualize and decouple from physical endpoint, virtual endpoints, server desktops, client desktops, physical, virtual, all all the same time presented or presented inside of Ei um. That was the real topic was
50
00:09:19.120 --> 00:09:39.550
Geremy Meyers: the claim that you can now do that and have a positive impact from the administrator, yet not a negative impact for the end-user And that's What I was really asking about? Okay, if that's the case. Then tell me how you're going to get both of those, because our experience with like ah like the unit desk solution at Citrix Bomb and cloud cloud apps. A cloud volume. Cloud apps
51
00:09:39.560 --> 00:09:54.429
Geremy Meyers: from Vmware and others has been: Yeah, you can. You can do that? And the administrator get to win because they have one package to update for everything. But the end user gets a little bit lesser of a user experience. And if that's the case, do I really want to go that route. I've got a way, you know, one versus the other.
52
00:09:55.440 --> 00:09:56.970
Geremy Meyers: Okay, I got it.
53
00:09:56.980 --> 00:09:58.910
Geremy Meyers: Listen. That is a
54
00:09:59.060 --> 00:10:04.839
Geremy Meyers: for a reason. I've had an apple in conversation. Come up a few times in the last two or three weeks, and
55
00:10:04.900 --> 00:10:20.769
Geremy Meyers: I've got an opinion on my own. But what is it? What is it? Just get a high level? Did you? Should Should someone do it, or should someone not do it? Um! Well, so it all goes down to is the juice word to squeeze, I think, with app layering. You've got to decide that that is going to be your method
56
00:10:20.780 --> 00:10:35.289
Geremy Meyers: of packaging images delivering, layering apps into a user's desktop. I mean, you've got to decide that that's going to be your approach. You can't be. I'm gonna do a little bit of applearing and a little bit of what I used to do, because part of the whole app layering approach is
57
00:10:35.440 --> 00:10:52.990
Geremy Meyers: um! It's certainly packaging the apps right, and so you can do elastic layers if you need to. But you can also. Do you know the layered image for the layered cake, and it's really tough to mix and match, And I would argue a lot of customers. Don't quite understand, maybe, where app learning makes sense,
58
00:10:53.000 --> 00:10:56.460
Geremy Meyers: you might be using a solution to build
59
00:10:56.610 --> 00:11:09.430
Geremy Meyers: one or two images, and that might be a lot of uptick, a lot of administration just to support a couple of images on the flip side. You can get hospitals. We've got organizations who have, you know, fifteen images, and that might be an easy win where now it's easier to
60
00:11:09.440 --> 00:11:19.119
Geremy Meyers: package and update applications across a bunch of different images. But if you got one or two, probably not worth it. I had a customer up in Raleigh a bunch of years ago,
61
00:11:19.130 --> 00:11:31.489
Andy Whiteside: and I fired, and it had to fire the customer. They they! They solved all their problems. I was there one week, and I came back two weeks later, and they solved all their problem by using app layering in your desk at the time.
62
00:11:31.500 --> 00:11:51.299
Andy Whiteside: And the problem they actually solved was their own administrative problem, and i'm in a meeting with their boss and their bosses, you know. Kind of beat me up on. Why, this isn't done the project isn't done. I'm like well, because we can't make any progress, because you're solving the wrong things, and she's like you're yelling at me about. What are you talking about like? Well, hold on a second. Have you ever logged into the virtual desktop?
63
00:11:51.310 --> 00:12:08.990
Andy Whiteside: Well, no, I've never logged into it. Okay, log into it. Seven. Eight minutes later she still Hasn't gotten the desktop yet, and all this layering man this is happening in the background. I was like, Look your guys focus on the wrong problem. It's all about user experience until we focus on happy users. Let's forget about how we manage the application like
64
00:12:10.770 --> 00:12:21.370
Geremy Meyers: I don't it's spot on I I literally got up, walked out and told him. Look, here's my number. You got it. Call me if you need to, for now I can't work with this until you guys get on the same p as what you're trying to.
65
00:12:24.250 --> 00:12:26.049
Geremy Meyers: All right, Bill. I think
66
00:12:26.410 --> 00:12:28.599
Geremy Meyers: I think our rant is over.
67
00:12:33.700 --> 00:12:44.510
Bill Sutton: I mean, I You know I I can see it from both directions, I mean from A, from A. As a technologist or from a technology perspective. I love the concept of that layering, but it to Jeremy's point.
68
00:12:44.520 --> 00:12:54.099
Bill Sutton: If you're a small shop and you've got a limited number of apps, the infrastructure and knowledge that's required to implement something like that, no matter what the vendor,
69
00:12:54.110 --> 00:13:22.499
Bill Sutton: it's a new way of doing things. And if you've got folks that are willing to invest the time and effort and understanding how to do it, understanding its use case, and it makes sense sure. But you know, for your average medium, small customer that's delivering a desktop. It. It may not make sense. It's really it Really, you need to. You need to look at the use cases, and you need to consider to your point in the the true end user experience, and it's going to significantly impact the log in time or the performance of the app or something along those lines. Then you need to
70
00:13:22.530 --> 00:13:27.360
Bill Sutton: consider the alternatives whether that's a posted shared app. Whether that's a locally installed app.
71
00:13:27.490 --> 00:13:33.390
Andy Whiteside: You need to consider the alternatives I take as if it's going to have any impact on user experience. Be careful.
72
00:13:33.400 --> 00:13:34.270
Yeah,
73
00:13:34.780 --> 00:13:46.049
Andy Whiteside: I mean, the users are used to clicking an app, especially with Ssds these days, and like it, launches in half a second. But it's going to go from three seconds to eight seconds to be careful.
74
00:13:48.450 --> 00:14:06.020
Andy Whiteside: All right. Well, the um blog that we chose to do today, fresh fresh out today from a Monica grismer who's been great, and on a bunch of these. I wish I kind of. Now that we started I was like, would have waited for her to join us, but I think we cover it very well based on the topic she's put together here. The title of it is um on premises
75
00:14:06.030 --> 00:14:24.819
Andy Whiteside: ah versus Cloud, which is best for your business solution. Jeremy is. Is she talking about the platform piece like Citrix Cloud, or or Citrix Jazz. Um, let's say Cedric Dazz or citrix? Ah, se bad, you know, on premises versus managing the cloud, or she's talking about.
76
00:14:24.830 --> 00:14:29.720
Andy Whiteside: Is Monica talking about where the actual host desktops live?
77
00:14:29.730 --> 00:14:47.289
Geremy Meyers: You know what I I think? That was The first question I had about this uh blog post was, Is she talking about the platform itself? So Citrix, as a management platform being delivered out of the cloud, or hosted on premise? Or are we specifically talking about uh the the workloads themselves? And, as it turns out, maybe a little bit of both,
78
00:14:48.170 --> 00:14:51.560
Andy Whiteside: probably a little of both. Bill, what your thoughts after reading through this?
79
00:14:51.570 --> 00:15:00.750
Bill Sutton: Yeah, after reading through it, I think it's a little bit. I think you're right. I think it's a little bit of both, I think, if you scroll down a little bit to that, or the the pros and cons, it kind of covers a lot of it.
80
00:15:00.830 --> 00:15:01.850
Help?
81
00:15:01.860 --> 00:15:10.589
Geremy Meyers: Yeah, there's a section where we're talking about Iaz and and and pads and sass and containers and things like that. I think that's where we kind of get into the nitty-gritty. But
82
00:15:10.600 --> 00:15:12.409
Geremy Meyers: yeah, yeah, it's a little bit of both.
83
00:15:12.420 --> 00:15:20.249
Andy Whiteside: So here's my overall. Take, and you guys tell me. If you agree or disagree, unless you can tell me why it shouldn't be. The The management plane
84
00:15:20.260 --> 00:15:35.420
Andy Whiteside: should be as it passed platform as a service hosted in a cloud and managed by Citrix, and even accessed by the user through the Citrix access plane. Unless there's a good reason, both from a technical in business, both really combined together.
85
00:15:35.530 --> 00:15:37.879
Andy Whiteside: You guys agree with that at this point
86
00:15:38.780 --> 00:15:56.409
Bill Sutton: at this point I would generally agree with that. I mean, there are exceptions. Maybe you know, really high security environments or something along those lines. But, generally speaking, I think I think that the when you think about the concept of where we're going today with Sas apps and everything hosted in the cloud, and managed by a third party,
87
00:15:56.420 --> 00:16:09.129
Bill Sutton: and to the extent you can reduce the amount of components you have to manage on premises. You're going to reduce your your risk, and you're going to reduce the amount of the labor cost one hundred and fifty,
88
00:16:10.140 --> 00:16:10.690
right,
89
00:16:10.700 --> 00:16:27.580
Andy Whiteside: I mean, and you include it, and you increase your ability to scale across multiple places. I use places. It can be your your private place. It can be your Colo. It can be your Partner's Kolo, which all of a sudden becomes cloud. It can be public cloud. It can be other types of public clouds.
90
00:16:29.680 --> 00:16:45.529
Geremy Meyers: Yeah, I mean, I would agree, You know, I think the um. What's funny is um, you know, in the Blog Post Here Monica talks about use cases for on-premise environments, and even in all three of these she talks about low up time requirements. You know, high demand workloads. You know
91
00:16:45.630 --> 00:16:54.239
Geremy Meyers: large numbers of devices and tools connected to the Ethernet. You know. Even this is what confused me because I read that and go. You know there's still a use case, I mean, if you've got
92
00:16:54.250 --> 00:17:16.479
Geremy Meyers: um, you know Citrix Jazz has solution right? The management solution, you know these are still relevant, so you know it looks like we're talking about on-premise workloads as opposed to on-premise, management. But either way, you know, I would say um, you know governance is probably the biggest one. Um! But then I would argue if you were using the citrics management plane. It actually makes governance a lot easier. Um, In fact, we've got A.
93
00:17:16.550 --> 00:17:27.310
Geremy Meyers: You know, an area where governments a lot of times. We're talking about data sovereignty, and this makes it easy. The idea that you can. You can place these workloads wherever they need to sit.
94
00:17:27.380 --> 00:17:38.519
Geremy Meyers: I do have customers who have told me that their citrix i'm using air quotes here right because they're talking about the management plane, too, can't connect to the Internet. And
95
00:17:38.530 --> 00:17:56.429
Geremy Meyers: i'm not saying that that's not true. But you know that's a highly niche scenario that a customer in some cases is chosen to do as opposed to required to do. I get it sometimes, you know you're just kind of fed the requirements, but you know, even in that case it's a small percentage. So I i'm finding,
96
00:17:56.880 --> 00:18:06.830
Geremy Meyers: you know, in a majority of use cases, the dazz management stack and the cloud makes sense. Yeah, put a number on that. What What percentage of customers
97
00:18:07.050 --> 00:18:15.020
Andy Whiteside: does platform as a service for managing your citrix environment? You see, Citrix generically, there will give me. Give me a number, Jeremy.
98
00:18:15.530 --> 00:18:22.489
Geremy Meyers: All right, So i'm going to exclude public sector because I just don't understand that customer base. So let me ask the question,
99
00:18:22.500 --> 00:18:36.449
Geremy Meyers: technically thinking technical only what percentage of customers forget about the the money conversation that's coming up next. But when it comes to Citrix in as a platform as a service versus on-premises. Give me a number.
100
00:18:36.740 --> 00:18:53.790
Geremy Meyers: What was the question again, What we were deployed now? What a percentage of customers should. If they're going to consider Citrix. Either they already have it or they're going to buy it. Ah! Be considering it as a service platform as a service because it meets their technical needs better versus going with on premises.
101
00:18:53.970 --> 00:18:55.759
Geremy Meyers: Um, ninety-nine percent.
102
00:18:56.050 --> 00:18:57.170
Andy Whiteside: It's it's
103
00:18:57.180 --> 00:18:59.120
Andy Whiteside: okay, nine. I'm bill. What's your number
104
00:18:59.420 --> 00:19:08.590
Andy Whiteside: would have been lower than that. But I would have considered I would probably been in the high Eightys. Okay. So somewhere between eighty, five to ninety, nine percent.
105
00:19:09.390 --> 00:19:10.430
Yeah,
106
00:19:10.440 --> 00:19:19.760
Andy Whiteside: I don't disagree. It's it's somewhere high now. You asked me three years ago to give you something much lower, fifty over fifty, even, but at this point you've got to convince me why
107
00:19:19.770 --> 00:19:37.250
Andy Whiteside: platform as a service technically doesn't make sense and keep it in mind, We can always use some type of brokering technology, a citrus gateway, and that scalar Adcs to to handle the traffic and just manage the thing in the cloud. So when you give us ninety nine percent, you're keeping in your back pocket that you can have the traffic
108
00:19:37.260 --> 00:19:41.690
Andy Whiteside: still flow, not necessarily in the cloud, but be managed from the cloud. The
109
00:19:41.700 --> 00:20:09.550
Geremy Meyers: exactly, I mean. Listen, Netscaler. I'm going to eat my words on this because i'm sure someone's going to say they don't want to manage that scalar. But you know having a netscaler on front having a storefront to run from. You know It's not a lot of management there outside of maintaining the net scale from a security, perspective, you know. Certainly windows from a windows perspective store front. But I think a lot of the a lot of the challenge with managing an arm from citrix environment, at least from a management stack is things like databases, You know the Dvcs. You know those
110
00:20:09.560 --> 00:20:29.299
Geremy Meyers: components, I mean, that's the hardware. And sometimes on upgrades. That's why we talk about doing parallel upgrades is, you know, if the database goes sideways during an upgrade, you know, if the Dvcs do a half upgrade as you're in between. I mean, that is the that's the work. And so, knowing that that's the brands, and knowing that we have an offline mode,
111
00:20:29.310 --> 00:20:36.199
Geremy Meyers: you lose connectivity to the cloud plane. Not that citric vlog goes down. But what if your Internet connection went down right? So let's
112
00:20:36.250 --> 00:20:51.900
Geremy Meyers: differentiate there. But you know if there's any reason that you've been offline, and you can't contact the cloud. You know. There's a scenario where it still works. You You lose some things here right. You can't make changes, but your users should not be impacted. That can be architected and I think that's important to understand.
113
00:20:52.310 --> 00:21:13.069
Geremy Meyers: Here's another pseudo-technical reasoning. I mean, how many customers, Jeremy, do you have? Have you run into across your time period that you know they didn't have a true test environment, because they never took the tide to build out a second total environment. The best they had was a, you know, a delivery group or two where they you know where they throw garbage workloads to try to figure out their work or not.
114
00:21:13.080 --> 00:21:23.580
Andy Whiteside: This in the cloud all of a sudden, you say, Okay, I've about one thousand licenses. I'm. Going to take twenty of them, or five of them, or whatever, and put it over here in this separate environment. And it truly is. You know my test of our
115
00:21:23.710 --> 00:21:41.189
Geremy Meyers: yeah, And there's actually some interesting things with that as well. So And if you were to transition all those licenses, you can curve out and create a separate burg. Id just to be tested, and we've got a tool in the automated config tool that will let you migrate over configurations if you need to. So I think
116
00:21:41.200 --> 00:21:49.630
Geremy Meyers: it opens up a lot of possibility around test ad that maybe folks push back on when it was on-prem, because just the effort involved in standing stuff, you know things out.
117
00:21:51.810 --> 00:21:59.699
Andy Whiteside: Ah, Bill, before we move away from the platform side of this conversation, and more into the workloads and infrastructures. Need anything else you want to?
118
00:21:59.760 --> 00:22:29.659
Bill Sutton: No, I think Jeremy hit the the mail in the head there, particularly as it relates to, uh, the availability of the environment. We We sometimes hear customers that are concerned about going to cloud and all into the cloud, using gaway service and things like that about what happens if Gaway service service goes down to my user sitting in home, or can my user sitting in the office where the data center is or connected to the data center, but they still access my applications and the answers, Yes, there are. There are, generally speaking, it's. Yes, If you have connectivity to that data center, then there are.
119
00:22:29.670 --> 00:22:42.269
Bill Sutton: There are techniques that Citrix has developed that can enable the availability of those resources. So I think that argument, which may have been much more valid Twelve, eighteen, twenty, four months ago, is not nearly as valid today.
120
00:22:42.280 --> 00:22:42.890
He's:
121
00:22:42.900 --> 00:22:47.739
Andy Whiteside: Yeah, that's one of the things that's made that number pick up more into the ninety range.
122
00:22:48.220 --> 00:23:10.489
Andy Whiteside: Yeah, I guess one of the things to clear up. Ah, and we will talk about, maybe in a minute. But the when you use Citrix dazz, you know the platform as a service piece of it, the the data that's actually you're residing in the public cloud at that point under the citric Senate is is not much other than like metadata type metadata type stuff. So unless you've got some so massive security requirements on that part of the data.
123
00:23:10.500 --> 00:23:11.809
You're fine.
124
00:23:13.190 --> 00:23:14.680
Bill Sutton: Yes, that's true.
125
00:23:15.500 --> 00:23:22.089
Andy Whiteside: All right. So for the rest of this conversation. Let's assume we're talking about the workloads running in A,
126
00:23:22.770 --> 00:23:40.530
Andy Whiteside: either on-premises would be your private data center or your private data center color or in a partner's environment data center like us that all of a sudden becomes cloud-ish or cloud-like, or in the public cloud is that is, that? Does that make sense? Why, I call Why, i'd break those out that way
127
00:23:41.460 --> 00:23:44.320
Geremy Meyers: it does. That makes a whole sense for sure,
128
00:23:44.590 --> 00:23:46.740
Andy Whiteside: Jeremy, is it cloud or clouds
129
00:23:47.660 --> 00:24:08.879
Geremy Meyers: clouds about it's floral. The whole world calls it cloud it's not. The cloud by Microsoft would like for it to be in the cloud, but it's clouds right. It's Amazon, Microsoft Gcps integral data Center, and on the east Coast and tiger data cent on the West Coast Rackspace Data Center. All those are clouds that built give us the the typical smart Alec response to what is the cloud?
130
00:24:09.330 --> 00:24:17.690
Geremy Meyers: It's just a day that somebody else's data center. It says somebody else's computer doing the same thing. Yours did. You just Don't have to make the upfront investment and maintain it.
131
00:24:17.700 --> 00:24:19.040
Geremy Meyers: Exactly.
132
00:24:19.270 --> 00:24:34.220
Geremy Meyers: Yeah. And and I would argue, the only difference between that in a in a Colo is sometimes with the cola. You have more insight into what's going on. And so, you know, this is a V center server, or you know, just because they've kind of opened up the hood and shown you, but you know for the most part again, it's just someone else's days, and that's it.
133
00:24:34.450 --> 00:24:52.820
Geremy Meyers: Well, and and I guess physically I was asking that question. You guys answered it. What is a You know public? What is it? I ask? Cloud. And then there's pas cloud, and there's Sass cloud, and there's Dance cloud, and there's also Dance cloud, which is device as a service. I mean your Your cloud is just way overused for
134
00:24:52.850 --> 00:25:04.730
Andy Whiteside: things, and that's fine. When you're having a you know, high-level marketing mind me, But when you're really trying to have a conversation telling me about. What are we talking about here? That you should never use the word cloud all by itself?
135
00:25:05.830 --> 00:25:06.890
Geremy Meyers: No,
136
00:25:06.900 --> 00:25:24.669
Geremy Meyers: you're you're correct. So this piece here goes through the pros and cons specifically those workloads and considerations. Yeah, Well, let's talk about the first one. The first one is a resource deployment. Ah, for on-premises. Notice I keep parking on premises because people says people say on frown,
137
00:25:24.730 --> 00:25:27.900
Andy Whiteside: they drop me nuts on premises. Um,
138
00:25:28.380 --> 00:25:31.600
Andy Whiteside: it's prem and proper not premises. Um.
139
00:25:32.730 --> 00:25:49.089
Andy Whiteside: Okay, so resource are cut off on the and there ah! Resource resources deployment. Ah! So for the definition of on-premises is resources are deployed in-house. I don't know what that means in-house. I guess that means you're on private data center on your own private gear. Right?
140
00:25:49.100 --> 00:25:53.320
Geremy Meyers: You probably own the underlying hypervisor is probably what it means,
141
00:25:53.340 --> 00:25:55.110
Yeah, hardware.
142
00:25:55.120 --> 00:26:00.590
Geremy Meyers: Yeah, yeah, You you own the hardware it's executing on is that that's how we'll.
143
00:26:00.640 --> 00:26:09.689
Geremy Meyers: That's how we'll call it. Yeah, as opposed to the cloud where you're basically accessing any of that through some sort of managed portal. This is what it is.
144
00:26:09.700 --> 00:26:18.109
Andy Whiteside: And and I love what Monica's done here. The the answer For what is the resources? Deployment definition, when we're talking about? Cloud is resources are deployed on a third Party's.
145
00:26:18.120 --> 00:26:33.120
Geremy Meyers: I'll put the apostrophe out there. Servers, which again, that's all. Cloud, is It's just somebody else's infrastructure. Cloud it's just somebody else's servers that they provide a layer of management and accessibility. Too. You just don't buy them and maintain the in the blinky lights.
146
00:26:33.860 --> 00:26:34.940
Yep.
147
00:26:35.890 --> 00:26:49.149
Andy Whiteside: So the next line down talks about cost um it says on-premise requires upfront investment whereas most cloud providers you just pay as you go model. I guess that's Mrr Ar, you know, on topics
148
00:26:49.390 --> 00:26:50.720
Andy Whiteside: television.
149
00:26:50.730 --> 00:27:10.410
Geremy Meyers: Yeah. So let me ask you guys this because you're in this space. Um. So from a requires an upfront investment, you know. A few years ago, when I was selling servers um, I did see where some of the vendors were looking at, providing. I guess they're scoping out subscription based hardware, which I think maybe I can't wrap my head around that because i'm sold wide.
150
00:27:10.420 --> 00:27:12.390
Geremy Meyers: I mean, what does that look like? I I feel like
151
00:27:12.400 --> 00:27:39.959
Geremy Meyers: I've had someone from mechanics. Tell me recently that they're going subscription, and maybe I don't. I I misunderstood how they worked, but I've also heard maybe Cisco and Hp. Doing the same thing like, Let me try as the partner eventually bring those together. The hardware guys have their model of subscription, which is really you just, you know, just pay for however much consumption of the hardware you're using. Maybe you you get a piece of hardware that's got this really high scale, but you're only paying for what percentage of that physical hardware that's being used, or maybe you have the ability to,
152
00:27:39.970 --> 00:28:09.769
Geremy Meyers: you know. Go into a month-to-month model, where you get hardware it comes and goes as needed. Ah, each piece is called Green Lake Leno. Is it called true scale? So when you're talking to the hardware guys that's their conversation. We talk to a new mechanics. It's really more ah, around a monthly subscription model of licensing, where you probably pay more overall. But you get to do it by the month, and so you either scale it up or scale it down. Maybe you do about a year, but it's two different conversations that have been on there. Are you talking about hardware, coming or talk about software
153
00:28:09.780 --> 00:28:22.199
Andy Whiteside: company. In some cases the L. Novos and the Hp. Of the world can bring it all together under one thing, but it's pretty much just subscription optics type of model for for software and hardware.
154
00:28:22.270 --> 00:28:23.430
Geremy Meyers: Okay,
155
00:28:23.440 --> 00:28:30.890
Geremy Meyers: So in a sense, there's a little bit of maybe page ago, but it's probably not as flexible as a cloud provider. Clouds Provider.
156
00:28:31.060 --> 00:28:37.589
Geremy Meyers: Third-party server provider it's. It's not as responsive to your changes. I wouldn't think
157
00:28:37.600 --> 00:28:38.489
Bill Sutton: that was elastic.
158
00:28:38.500 --> 00:28:39.990
Geremy Meyers: Right?
159
00:28:40.000 --> 00:28:49.430
Geremy Meyers: Yeah, I got it and remember elastic. I mean, stretching out and also contracting. Yeah, super easy to do that in a true public cloud offerings.
160
00:28:51.070 --> 00:29:00.109
Geremy Meyers: I got it. Okay? Well, I I guess. And then yeah, the next one here, right? So we talk about all them in. So I want to say on the cost one, because there's a conversation to be had around the cost. One which is
161
00:29:00.120 --> 00:29:13.209
Andy Whiteside: It's important to consider, too, when you go to a like a cloud provider model. You are committing to them that you are going to spend money with them every month, and you are going to pay your bill, and if you don't,
162
00:29:13.310 --> 00:29:29.269
Andy Whiteside: they're going to tell you, hey? You didn't pay your bill. We're going to turn you down a little bit. We're going to turn you off versus when you go with the you know the ah investment upfront. You either paid it up front, and then you decide whether you keep paying for it, because it's now, you know nine tenths the Walt rule of law like possession. Are you on it? You have it
163
00:29:29.280 --> 00:29:35.140
Andy Whiteside: uh. It's a lot hard for somebody to turn you off. There's leverage that goes on when you move to a true cloud model.
164
00:29:35.530 --> 00:29:51.689
Geremy Meyers: Oh, there's something else, too, right? So um I haven't. Obviously I don't pay a cloud bill myself, but I talk to customers who I mean there's a different economy to the cloud in terms of like how you get charged, and how you can reserve instances and how you,
165
00:29:51.700 --> 00:29:55.639
Geremy Meyers: you know, contract with the vendor and things like that, right? So
166
00:29:55.650 --> 00:30:13.110
Geremy Meyers: yeah, I've found in a lot of cases, you know, customers who just had no idea that they should be reserving instances on on Vms, and have been paying much more than necessarily they need to. Um. Have you guys gotten the situations as in Turk? Again, in situations where you've helped evaluate that for customer made recommendations around saving costs.
167
00:30:13.210 --> 00:30:30.720
Geremy Meyers: Yeah, I I jokingly say that our our good customers don't put any of their desktop, and that virtualization in the public cloud, because they Don't get exactly the machines they need, and they pay way too much for now preserved instances or the ability to live migrate instances using some of the software as it's out there
168
00:30:30.730 --> 00:30:57.130
Andy Whiteside: has made that much more doable. And we do have some customers that do use public cloud. Ah, but where most of the time are really good customers that we're helping a ton. They put their stuff in our data center, or we put a cage in their kolo, and at that point. It's our stuff. It's our software, our servers. Therefore you could argue that is cloud, but it's not like the true public Cloud Providers would ask you to define it.
169
00:30:57.890 --> 00:31:05.439
Geremy Meyers: I got I mean, so there's an obvious question to ask. But maybe when we get to end of the end of this section here. We'll come back to that,
170
00:31:05.490 --> 00:31:10.100
Andy Whiteside: so i'll let Bill refund it, too. But I will tell you a quicksore. Zintegra
171
00:31:10.110 --> 00:31:26.849
Geremy Meyers: has the ability to. If you said the tech. I want this stuff out of my cage. Therefore I want to go cloud. But I want to do what fits my needs. The best we can do with what we do with one of our banks. I'm. In the New York area. We actually put um gear in the cage right beside theirs,
172
00:31:27.060 --> 00:31:32.220
Andy Whiteside: and we also replicate that to our data center in Atlanta.
173
00:31:32.230 --> 00:31:49.359
Andy Whiteside: And so they got the true. You know they got a cloud. They got it. It wasn't theirs anymore. They just have a connection cross connection over to our cage redundant cross-connections. Therefore it became cloud to them but we created no additional latency, because we're still in the same building, like literally twelve feet away,
174
00:31:49.370 --> 00:31:55.070
Andy Whiteside: but they accomplished the goal of getting it off their stuff. Therefore they moved their desktop to the cloud a cloud.
175
00:31:56.250 --> 00:31:57.290
You're all
176
00:31:57.690 --> 00:32:09.340
Bill Sutton: yeah, I mean, i'll let go in. And he said, I mean, we have a lot of customers that that want to go to the public cloud, and some will dip their toes in it and test it out, but a lot of them end up back with some form of
177
00:32:09.350 --> 00:32:21.760
Bill Sutton: alternate cloud, whether it's their own private cloud, or it's an entire cloud, or it's some other colo that they're leveraging. We do have some that end up in the public cloud, and many of them are.
178
00:32:21.770 --> 00:32:35.179
Bill Sutton: Most of them are happy with it, but you have to frame it, and then architect it in a way that helps minimize those costs, things like auto-scaling and and tools like reserved instances, and those sorts of things that can help keep the costs in check for those customers.
179
00:32:35.860 --> 00:32:36.870
Yes,
180
00:32:36.880 --> 00:32:40.569
Geremy Meyers: and there are okay tools like the citrix auto scale
181
00:32:40.580 --> 00:32:59.099
Andy Whiteside: comes into play big time, you know, using non- persistent images to scale up and scale down, and you know, make sure you balance out. I mean, you literally could think about. Okay, I've got, you know, one hundred desktop running over here on it over there, this cloud, that cloud, and at any point in time I can just determine which of where I want the workload to go based on who's charging me the most or the least,
182
00:32:59.420 --> 00:33:09.089
Geremy Meyers: you know. And so, you know, i'll get forward in here right? So we're going to talk about scalability, data, security and compliance here. But you know, I think the ultimate question is, you know, Andy, where am I putting my workplace?
183
00:33:09.100 --> 00:33:12.260
Geremy Meyers: My, you see, workloads. It's probably the best question,
184
00:33:13.570 --> 00:33:16.600
Andy Whiteside: and there's lots of things to ask
185
00:33:17.030 --> 00:33:22.680
Andy Whiteside: to determine where you want to put it some, you know. Honestly, Jeremy, what I've seen a lot.
186
00:33:22.970 --> 00:33:34.690
Andy Whiteside: Um is that whoever we're talking to at like the Cio level he's looking for a resume builder, so he's moving everything to the cloud. And you're like. Why, it's like Well, that's the way to do it. That's how we're going to do it, and then he doesn't
187
00:33:34.700 --> 00:33:52.559
Andy Whiteside: customers spending a fortune on um, you know, infrastructure as a service hosting those desktop app workloads, and you know, Six months later he went and got a job somewhere else and put that on his resume as to how he did that. And you're going Well, that's great, but I don't know why you decided to do that, and you. The logic was just, you know, just to follow the maths all the herd and get your next good job.
188
00:33:54.210 --> 00:34:09.020
Geremy Meyers: Yeah, you're not wrong, you know. I think Bill said it last when he said, It depends right. The customers who move to the cloud for that exact reason. And then the Cio leaves, or someone got the bill and realized that you know that's not sustainable.
189
00:34:09.030 --> 00:34:24.140
Geremy Meyers: And so they end up moving from a cost perspective. You know they move the workloads where it makes sense right? I think that's the advantage. But in and what plays into that is certainly scalability. In some cases supply chain is limited the scalability of the on-premises model for sure
190
00:34:24.150 --> 00:34:32.880
Geremy Meyers: with the data security, right? So where do the Where's the data need to live? So I think that plays into it, and you know compliance is probably closely tied to that. But,
191
00:34:32.949 --> 00:34:36.819
Geremy Meyers: um! It's interesting. I don't know. In some cases the
192
00:34:36.880 --> 00:34:54.910
Geremy Meyers: you know, all four of these are really considered in a lot of cases. And so it ends up. Being more of a you know, we need to be dynamic, and maybe Dr. Goes to the cloud. Maybe that's a good place to start A. But yeah, I love that. All four of these were called out because these should be what we ask about in our cloud conversations,
193
00:34:54.920 --> 00:35:01.680
Geremy Meyers: Then that's not going to be Dr. When we're talking about you, you see workloads we can. We can put our workloads
194
00:35:01.690 --> 00:35:19.610
Geremy Meyers: in multiple places because of the platform as a service concept we're talking about here at the same time, and so users can literally, you know, log in today and get one over here. The next person logs in gets one over there. And then she said, Is it working well? Yeah, it's working. I know my recovery is working because they're musical simultaneously, and nobody even knows It's happening.
195
00:35:21.870 --> 00:35:23.779
Geremy Meyers: Yeah, yeah, okay
196
00:35:24.090 --> 00:35:25.270
Geremy Meyers: of us,
197
00:35:26.440 --> 00:35:32.700
Geremy Meyers: Bill, Do you have examples of customers that are simultaneously using more than one back in and not even realizing it.
198
00:35:32.710 --> 00:35:49.500
Bill Sutton: Um, yeah. Well, in in a lot of cases where they have their own private data centers that are going between the Mid East coast, West Coast and the users, or maybe even East Coast Central West coast. The users may not even realize that we also have some that are doing, or either are already doing or looking to do
199
00:35:49.510 --> 00:36:02.389
Bill Sutton: kind of what I refer to as bursting in the cloud, and that is where the user doesn't really know whether they're on the on-prem data center, or whether they are in a cloud running their desktop cloud. It shouldn't matter to them as long as they have access to their data. And we do have some customers that are doing that today,
200
00:36:03.000 --> 00:36:14.350
Andy Whiteside: and historically, when it would show up that it was going to be. A problem is when they go to run that application inside that desktop or on that app server, and it needs to talk to some, you know, back-end Server. Okay, where there's where's that thing sitting at? But now, with
201
00:36:14.360 --> 00:36:30.659
Andy Whiteside: you know, with these direct connects and the Sd. Wind capabilities, and just the raw bandwidth and latency um things that have been enhanced, not one hundred percent solved. But it enhances, you know, to even notice that it took an extra half a second to launch and give that data or or not.
202
00:36:31.110 --> 00:36:49.730
Geremy Meyers: Well, well, maybe not. But I think it's something that has still has to be considered right, because it's always been the golden rule of End user compute. As you've got to put that front end um close to the back end for that experience to your point. Right? Um, Originally, which was that anything that impacts the user experience needs to be challenged right. So
203
00:36:50.110 --> 00:36:56.989
Geremy Meyers: you know, I think that's a part that's got to be a part of the architecture is, you know, Is the latency going to be worth it, you know, depending on the application. It depends.
204
00:36:57.000 --> 00:37:05.669
Andy Whiteside: It's. I always use the example. If you're if you have kids and you're going to travel for Christmas, where the kids going to be. They're going to be a grandma's house. Well, where should the presence be
205
00:37:07.110 --> 00:37:09.220
Geremy Meyers: you? Very well, Sales?
206
00:37:09.230 --> 00:37:13.680
Andy Whiteside: If not, it's gonna be a really bad uh It's really bad Christmas morning.
207
00:37:13.690 --> 00:37:14.890
Geremy Meyers: Yes, sir.
208
00:37:14.900 --> 00:37:15.810
Geremy Meyers: Yeah,
209
00:37:15.910 --> 00:37:38.679
Andy Whiteside: all right. So scaling up scaling down clouds, bring that into the mix for you. Ah, data security. We talked about the you know, the ip that's associated with the metadata with the platform as a service. Let's just hit this one again real quick. I so security um of the data that's going to be in that environment, or at least transferred through that environment
210
00:37:38.690 --> 00:37:43.359
Andy Whiteside: that should be part of what you decide may help you decide on where those workloads should run right?
211
00:37:44.840 --> 00:37:46.089
Geremy Meyers: Absolutely.
212
00:37:46.100 --> 00:38:00.319
Geremy Meyers: Yeah, I mean, you know, certainly from ah from a access layer for sure. But then, secondly, you know how I mean, Listen. All that. All data is the same. You know most companies, most organizations tier their data, and I don't mean in a backup scenario, but just in terms of security.
213
00:38:00.330 --> 00:38:12.740
Geremy Meyers: And so I think that's got to be considered as well, and then that bleeds right into compliance. Where there are countries who require data to be in certain locations. I mean, that's Gdpr: in a nutshell,
214
00:38:12.840 --> 00:38:13.919
right?
215
00:38:14.660 --> 00:38:24.099
Geremy Meyers: And so yeah, I mean, that leads right to the next one. Compliance, If compliance says it has to be here, and you just follow the rules to the letter of whatever the rules are. Then there's your decision in criteria. Right there
216
00:38:25.500 --> 00:38:27.449
Geremy Meyers: it is. Yeah.
217
00:38:28.020 --> 00:38:45.020
Andy Whiteside: Um: Okay. So okay. So before we move on the next section, i'm going to do another question for you, Jeremy, Give me your answer first. What percentage of compute will end up in the public clouds, and what percentage of the compute will have to end up somewhere other than the public cloud.
218
00:38:48.350 --> 00:38:54.810
Geremy Meyers: Okay? Well, i'll start off by saying that most. It appears right now to be on-prem
219
00:38:54.820 --> 00:39:00.809
Geremy Meyers: still. So you Don't go sixty over forty. I would have, I would have said, eighty over twenty, because that's the
220
00:39:01.140 --> 00:39:15.890
Geremy Meyers: sort of industry the running industry joke eight percent on from twenty percent of the cloud, but I think it probably skews down a little bit, so i'll say sixty, four, so sixty percent, not in the public cloud, but somewhere else, and then forty percent in the true public cloud
221
00:39:18.700 --> 00:39:20.189
Andy Whiteside: Build your thoughts.
222
00:39:20.200 --> 00:39:24.789
Bill Sutton: I would say this I would. I was initially my first thought when you asked the question was fifty over fifty.
223
00:39:24.800 --> 00:39:40.979
Bill Sutton: Um! But I think you know it's Jeremy's probably right that it will end up being more like sixty percent on-premise what we're finding today with customers that want to do. You know, they're running an older version of of Citrix seven, fifteen, or or even one thousand nine hundred and twelve, and they want to go to the latest.
224
00:39:40.990 --> 00:40:04.640
Bill Sutton: They're taking on most of them, or many of them are staying on ground. We do we are We are finding that some are going to the cloud. Some of them are Are we're doing on-prem and they're evaluating the cloud, So they're not really ready to make the leap. And when I say the cloud i'm talking both the workloads and the the control play, so I think there's still some reluctance, and I think a lot of it has to do with not really understanding it. A and B. The cost.
225
00:40:04.650 --> 00:40:21.089
Andy Whiteside: And to be clear, I was talking about. I was about compute just in general, not just desktop, not just in the user but just in general compute like what we currently have for X. Eighty six workloads, server-based whatever not desktops, but you know, client server applications to well what would you say the
226
00:40:21.100 --> 00:40:34.089
Geremy Meyers: I'm going to go in a P It's probably going to be around sixty forty, I mean, because I think you're encompassing in that those situations where the customers I as today, but they might be pas, or even sass tomorrow. That's a good point.
227
00:40:34.100 --> 00:40:47.490
Geremy Meyers: Yeah, let me take your erp right If you've been running that on premises for years, your migration project probably looks like i'm not forklifting to the newest version. Sitting in a cloud infrastructure somewhere, i'm. Probably it's probably s at that point.
228
00:40:47.510 --> 00:40:50.040
Geremy Meyers: I know it's probably Oracle Cloud, or
229
00:40:50.400 --> 00:40:55.250
Geremy Meyers: something like that, I don't know, but you know it's probably a different delivery model.
230
00:40:55.780 --> 00:41:25.029
Andy Whiteside: Alright, So let's get through the rest of this. Remember out of time. But uh, so the next section is uh, what is an on-premise? It's environment. What are the pros the pros that are listed? Uh, i'll run through these. And then, you guys in comment uh infrastructure control. So we control, uh where these workloads are running security. We We know that it's within our four walls, which it took up to a cable that takes it out to the rest of the world. But that's all Another topic uh compliance, you know, go by our our rules and regulations, and then efficiency uh low latency.
231
00:41:25.080 --> 00:41:31.410
Andy Whiteside: Any of those that you guys want to highlight or disagree with, as far as pros of on-premise. This environments.
232
00:41:32.050 --> 00:41:43.750
Geremy Meyers: I think this is why the on-premises versus cloud you know are we talking about infrastructure? You know, just workloads only or are we talking about the management stack? Confuse me a little bit, because
233
00:41:45.700 --> 00:41:59.039
Geremy Meyers: with on-premise? Um, all of this is true infrastructure control, share right security, You know. I think you could get that out of the cloud version of It's the plat, the Pas version, the dance service, if you will, from Citrix same thing for compliance and efficiency,
234
00:41:59.050 --> 00:42:10.300
Geremy Meyers: you know, just lower latency close to users. So yeah, like, I don't disagree with any of this. But you know this is where it confused me a little bit, because you get all of this out of a sass delivered, you know, citric service.
235
00:42:12.020 --> 00:42:17.390
Bill Sutton: No, I agree. I don't really have anything to add to that to Jeremy. What Jeremy said.
236
00:42:17.750 --> 00:42:26.200
Andy Whiteside: It's just a new way of thinking right. So going back to Jeremy's comments around security, I mean if I put it up there. Then I turn on all the bells and whistles that are exist up there,
237
00:42:26.210 --> 00:42:39.160
Andy Whiteside: and know that well all the bells and whistles that exist This up there can I do? I get better security? Potentially It's just because it's in my four walls, and you know I don't have all these tools turned on to look at it. Does that that doesn't mean It's better,
238
00:42:39.390 --> 00:42:40.700
Andy Whiteside: more secure,
239
00:42:40.710 --> 00:42:59.470
Geremy Meyers: you know you're absolutely right. And so, um you know I would argue and listen. I gotta understand what your security posture is, and like your approach to securities and organization. But I, you know, obviously being sass delivered might make you more secure. You know, I think that's a smaller footprint to manage um. You get a lot of the same.
240
00:42:59.480 --> 00:43:07.570
Geremy Meyers: You still managing your, your, your, your your workloads themselves. So you know that's a tough one. I think you can equal there for sure.
241
00:43:07.730 --> 00:43:33.210
Andy Whiteside: Yeah, all right. So the cons listed for on premises is scalability both up and down uh infrastructure costs. If somebody's got to break out the check and at least commit to it or pay for it upfront maintenance. Now you got that it, guy that is back to swapping out hard drives and other things for them uh security. You've got both physical and network and other technology related securities that you're You're on the hook for all by yourself,
242
00:43:33.220 --> 00:43:40.889
Andy Whiteside: and then reliability. And having a team that you can trust to keep these things up up, up and up Period Bill, you will go first.
243
00:43:40.900 --> 00:44:01.529
Bill Sutton: Yeah, I mean, I think all of these make sense. So the one that I would. Highlight is really the third one maintenance. Um. And I would argue that what we've seen anyways is a lot of organizations have scaled back their It staffs over the past couple of three years, and what I mean by that is is, the folks are really more focused on what it says here maintenance and updates. So it's accurate.
244
00:44:01.540 --> 00:44:31.530
Bill Sutton: But being able to to run the environment to understand how the environment interacts with the rest of the environment, that kind of what I would call a higher level of knowledge and capabilities. We're finding that a lot of that has gone to the public cloud vendors, or two partners, or or folks like us, that the customers don't often seem to have Some customers. Don't often seem to have the real skill set that they did five six years ago about end-user computing. And so that's that's definitely a con of the owner of an on-premises event
245
00:44:31.540 --> 00:44:41.789
Bill Sutton: environment. You really need to understand your environment to manage it. And if you don't really have that fundamental understanding of how it works, and how the pieces interact with one another, then that can be a real challenge for maintaining it.
246
00:44:41.800 --> 00:44:48.470
Andy Whiteside: So you think it will be hard to find the next generation of employee that understands how to go add a riser board to a system work.
247
00:44:50.050 --> 00:44:55.720
Geremy Meyers: Know I know exactly what you meant when you said that. Which is that going to be a diary?
248
00:44:55.730 --> 00:45:05.290
Andy Whiteside: I mean, change, Change your oil. It was like my car didn't have a wheel, but I can't change. Well, what are you talking about with this this thing. We have center here still has oil, and I need you to change it. Okay, Good luck,
249
00:45:05.300 --> 00:45:10.490
Andy Whiteside: right? Right? Exactly. Jeremy need any call outs on the cons. They are listed there.
250
00:45:10.500 --> 00:45:11.700
Geremy Meyers: Um,
251
00:45:11.770 --> 00:45:14.629
Geremy Meyers: you know. I think infrastructure costs. I mean
252
00:45:16.400 --> 00:45:24.470
Geremy Meyers: It's a capital. It's expenditure versus operational right? And so I think that's what it boils down to, and it's much easier.
253
00:45:25.620 --> 00:45:30.100
Geremy Meyers: It's much easier to buy up front, and then try to depreciate for sure. But
254
00:45:30.110 --> 00:45:48.759
Geremy Meyers: you might end up buying more than you need, and that's hard for a lot of organizations to predict these days. Um! And that's pretty much across the board, so I I think, with a sort of a subscription model to the cloud, to to clouds, to things like that. Um, you know, even though it changes month to month. It is something a little bit more predictable,
255
00:45:48.770 --> 00:46:05.430
Geremy Meyers: and I think that's what organizations appreciate about that model. I granted. Sometimes the accounting hasn't caught up, so i'll still bump into customers. Who are They'll tell me we only you know we only do capital expenses. We don't do optics. I go. That's not true, but because a lot of what you're buying right now is opex, but
256
00:46:05.440 --> 00:46:08.890
Geremy Meyers: you know it does take some organizations a lot to come around for. Sure.
257
00:46:08.900 --> 00:46:09.740
She
258
00:46:10.280 --> 00:46:16.339
Andy Whiteside: I got to go back to this when Jeremy, you said you don't you don't have any cloud that you pay for you. You have Netflix right?
259
00:46:16.350 --> 00:46:33.540
Geremy Meyers: Oh, well, man, I have a ton of cloud. You have a ton of cloud, right? And I mean you didn't have to buy that What used to be six hundred dollars. Dvd. Player. By now you can get up for sixty bucks. But my point is, we all have cloud over, and we're choosing to go that way for the conveniences
260
00:46:33.550 --> 00:46:41.040
Andy Whiteside: as well as the lack of having to pay. I bought my son. I I had to buy new X boxes. By the time I was done. It was six hundred dollars,
261
00:46:42.210 --> 00:46:54.689
Geremy Meyers: I mean. Listen. Even place Dvds: It does. It plays Bluetooth these days, too. But you know the one thing that used to give me a little bit of heartburn is. Do you guys ever buy Microsoft office, you know, Like for the house,
262
00:46:54.700 --> 00:47:07.470
Geremy Meyers: and not like not like the student edition, and not like the fifteen dollars version that then you got through work, which is, you buy for your house. I mean, if you wanted the version that you used to work. It was three hundred dollars, three hundred bucks, which is insane.
263
00:47:07.480 --> 00:47:25.069
Geremy Meyers: And now i'm paying nine bucks a month, you know I can pay it yearly, but I'm I'm have to do nine bucks a month, because I like the idea of being able to turn it off. Is it cheaper if I buy a year in advance share. But I also like the idea that this is not what a month I got five devices that i'll have office, and over the course of three years is more expensive. But,
264
00:47:25.300 --> 00:47:29.589
Geremy Meyers: man, it's just a I've been walking into like cop. Usa: If you guys remember that place.
265
00:47:29.600 --> 00:47:34.290
Geremy Meyers: Yeah, and just dropping some coin down on the Microsoft Office once every three years is just
266
00:47:34.590 --> 00:47:49.549
Geremy Meyers: so. I don't want to go back to them. There's the convenience as well as There's the uh, the costing out. Model the optics model, and here's the the flip side of that, Jeremy. When in your life. You you anticipate, anticipate not paying for Microsoft's office under the kernel,
267
00:47:49.990 --> 00:48:01.919
Geremy Meyers: I mean, I don't see a time unless we just change what we do from an application perspective. I'll probably do it for a long time forever. And do you put your personal like pictures and stuff up in there?
268
00:48:02.100 --> 00:48:03.140
Geremy Meyers: Yeah,
269
00:48:03.150 --> 00:48:14.620
Geremy Meyers: what's gonna happen. You're gonna keep paying for it until you're gone, and then you just wonder it's sticky. It's sticky before you die. Make sure you download all those pictures. Give it to somebody else to put up in theirs.
270
00:48:14.630 --> 00:48:17.989
Geremy Meyers: Exactly. Exactly. Sorry, Bill. Go ahead.
271
00:48:18.000 --> 00:48:32.289
Geremy Meyers: No, I was gonna say Yeah, I do the same. I mean. I'm almost ashamed to admit that until, like March, February March of this year, I was still using outlook, two thousand and ten on my home computer. And I finally got the point. This is just crazy,
272
00:48:32.300 --> 00:48:47.639
Bill Sutton: you know, and that I have older children, children who are who want to be able to use one drive and things like that. So I finally just get the bullet and and bought the subscription like Jeremy said and we moved from paying for a cloud-based storage place for our pictures to on drive,
273
00:48:47.650 --> 00:48:54.769
Bill Sutton: I I mean, and to your to your point. Yeah, we'll i'll be using that thing until you know until either it goes away or I go away.
274
00:48:54.780 --> 00:48:57.790
Geremy Meyers: Yeah, Can you even buy Microsoft Office outright?
275
00:48:57.800 --> 00:48:59.869
Geremy Meyers: Yeah, that's the little thing you can.
276
00:49:00.510 --> 00:49:07.989
Geremy Meyers: We can. Here we go behind Microsoft office business. Twenty is two hundred and fifty dollars. Okay, what it is. Yeah,
277
00:49:08.210 --> 00:49:17.390
Geremy Meyers: hey? That's a one-time purchase for one Mac or Pc: right? Yeah, I've got four machines in my house. So you know that's a thousand bucks right There you go.
278
00:49:17.400 --> 00:49:18.370
Geremy Meyers: Okay,
279
00:49:18.820 --> 00:49:30.890
Andy Whiteside: all right. So last section of this Ah, Blog from Monica says, Use cases for on-premises environments. It's almost like number one number two contradicts themselves. You have low up time requirements,
280
00:49:31.410 --> 00:49:43.009
Andy Whiteside: therefore you can get away with on-premises, and the next one number two is You have high demand workloads. I guess that's performance. Okay. Graphics things that just become cost prohibited in the cloud.
281
00:49:43.940 --> 00:49:57.820
Geremy Meyers: Um: yeah, yeah, I mean, let's be clear. You can do high demand workloads out of you know. Amazon azure. I'm: assuming a Gcp haven. I haven't ded into that one, but they're not.
282
00:49:58.780 --> 00:50:00.490
Geremy Meyers: It's the taka ou disintegra.
283
00:50:00.500 --> 00:50:01.600
Geremy Meyers: Yes,
284
00:50:01.610 --> 00:50:09.600
Geremy Meyers: yeah, everything to do it like we required. But we've almost forced every customer to have some type of Gpu, because we know their end-user experience can be improved.
285
00:50:10.140 --> 00:50:12.499
Geremy Meyers: You know what I haven't talked about
286
00:50:12.770 --> 00:50:14.290
Geremy Meyers: a hardware gpu in a long time.
287
00:50:14.300 --> 00:50:19.980
Geremy Meyers: I'd love to revisit what that looks like at some point. Just yeah, there was the Irish chip. There was obviously Nvidia
288
00:50:19.990 --> 00:50:49.979
Geremy Meyers: the A. And B. Was doing something for a while. There might be some some. I think we're all in video detail for the stuff ever in yeah materializing. I don't get involved in it. It's okay. You got low up time requirements which you know I mean. Look, I ran entire data centers with a single servers with, you know redundant discontrollers. Um! What we think of high availability today is so much greater than what we used to. But at the day, if you're not taking advantage of the the greatest ways of being redundant about how the available
289
00:50:49.990 --> 00:50:58.970
Geremy Meyers: Then you're, you know, potentially letting the organization down So it's. It is real. So I just wonder when Monica's low up time requirements. Is there a number? And you can put on that?
290
00:51:00.200 --> 00:51:19.960
Geremy Meyers: Yeah, I think it's really the smallest of the small. If you're, you know. If you want to have your your infrastructure in a closet in your main office, then you can. You can handle a power outage or maintenance, or such. Then, you know, maybe you can. You can do it in a local office versus putting it at a colo or something. I think that's really what it says here. What you say in here
291
00:51:20.760 --> 00:51:21.819
now
292
00:51:22.360 --> 00:51:29.910
Andy Whiteside: you last one is your organization has a large number of devices and tools connected via Ethernet.
293
00:51:30.060 --> 00:51:43.419
Geremy Meyers: Yeah, that's a I mean keeping a work, I mean, especially manufacturing, you know, having some sort of, you know, end user compute workload sitting in a regional location makes sense. What's interesting is, I think, we enable that more
294
00:51:43.430 --> 00:52:01.140
Geremy Meyers: out of you know the Citrix and dad's service, because you know, trying to do this with on-prem infrastructure zoning out different locations Didn't make a whole lot of sense whereas you know the way this architecture works is putting cloud connectors in a regional manufacturing. So it's pretty easy.
295
00:52:01.150 --> 00:52:30.749
Geremy Meyers: Well, first thing that pops up my head, we get to that point. It's okay. It sounds like we're now talking about edge. Where Where does the edge? They didn't don't purchase this first. Wow! That's true. I think that's exactly what we're talking about here, because you're going to have some manufacturing facilities and and other types of facilities that are going to be very rural parts of the country that may not have really high speed or decent speed access even to the platform layer or the control plane. And that's where you really get into the edge computing question about, you know. Do we want to deliver that using edge technologies in that
296
00:52:30.760 --> 00:52:49.390
Geremy Meyers: location that are that may be connected to the, to the mothership, so to speak, But in a very high latency or a low bandwidth connection.
297
00:52:49.400 --> 00:52:54.789
Geremy Meyers: I was thinking the same thing, by the way, and I was like we're going to turn this in the Windows weekly it'll be a two-hour episode of the Content
298
00:52:54.800 --> 00:52:57.590
Geremy Meyers: part one part, two right.
299
00:52:57.600 --> 00:53:03.810
Andy Whiteside: Yeah. Well, that's, what we're gonna do. We're gonna we're gonna pause here, and we'll come back next week and jump into the pros and cons of clouds, computing
300
00:53:03.820 --> 00:53:18.089
Andy Whiteside: after a brief recap on what we've covered so far. But guys I appreciate it, and hopefully hopefully it's the cliffhanger. I'm just in imagining the dukes of hazard the general E-car going from one side of the bank to the other, and we're just going to be waiting all week for a
301
00:53:19.530 --> 00:53:20.749
Geremy Meyers: It's pretty funny,
302
00:53:20.930 --> 00:53:28.010
Andy Whiteside: all right, guys. Well, thanks for joining, and we will jump on the same topic next week. Maybe maybe Todd will be with us in.
303
00:53:28.180 --> 00:53:32.390
Andy Whiteside: You can just uh tell us everything we did was correctly right or wrong with
304
00:53:32.400 --> 00:53:36.189
Geremy Meyers: we There are yeah, awesome, all right. Palace. Good to see you again.
305
00:53:36.200 --> 00:53:37.290
Geremy Meyers: See you next week.
306
00:53:37.300 --> 00:53:38.549
Andy Whiteside: See you next week? Thanks.