We are excited to announce the availability of Citrix Autoscale for Citrix Virtual Apps and Desktops (CVAD) for on-premises customers. Our Autoscale power management solution enables customers to strike the right balance between delivering a great end-user experience and optimizing costs.
Let’s take a closer look at what this means for you.
Host: Andy Whiteside
Co-host: Bill Sutton
Co-host: Geremy Meyers
We are excited to announce the availability of Citrix Autoscale for Citrix Virtual Apps and Desktops (CVAD) for on-premises customers. Our Autoscale power management solution enables customers to strike the right balance between delivering a great end-user experience and optimizing costs.
Let’s take a closer look at what this means for you.
Host: Andy Whiteside
Co-host: Bill Sutton
Co-host: Geremy Meyers
WEBVTT
1
00:00:02.160 --> 00:00:22.050
Andy Whiteside: Everyone and welcome to episode 1, 41 40 right bill that we came up with a minute ago 1 40 of the Citrix session of your host, Andy White side got Bill sudden with us. Bill, was in I say, you're part of the world last week on vacation. So that you guys knocked out a podcast while I was going, what did you guys?
2
00:00:22.280 --> 00:00:23.460
Andy Whiteside: What'd you guys cover?
3
00:00:24.340 --> 00:00:31.449
Geremy Meyers: We didn't, Bill? I think we last week we had did we, before week before? Yeah, we did.
4
00:00:32.790 --> 00:00:40.560
Andy Whiteside: What was it? I don't. I have that chance? Well, I haven't posted it, so I have any merge with the last. This was part, I think this was part 4. This was part 4 of our
5
00:00:40.960 --> 00:00:48.199
Andy Whiteside: of our final our big overview of 2305. Anything stick out that you guys covered?
6
00:00:50.900 --> 00:00:57.279
Geremy Meyers: Well, well, I was. I was at the beach, so I did not get to sit in on that one. Unfortunately.
7
00:00:57.570 --> 00:01:12.730
Andy Whiteside: Well, hopefully, people got a lot of good value out of that whole series took us 4 4 episodes to cover 2,305. I think that's just a highlight that you know. A lot of people are saying that Citrix is dead and they're not investing. And II think it's the exact opposite.
8
00:01:12.770 --> 00:01:22.349
Andy Whiteside: and I think, Jeremy, I think you guys have a problem over cloud software groups getting that word out. Because obviously, you're kind of getting back to basics, what we need you to do. But
9
00:01:22.500 --> 00:01:24.149
Andy Whiteside: a lot of fud around.
10
00:01:25.100 --> 00:01:38.009
Geremy Meyers: Yeah. So the myth that there's nothing's happening is is truly a myth cause. There's a lot going on right now lots being released. And actually, it's happening at a quicker, quicker clip, too. So maybe it's just a messaging thing. I'm not sure. But
11
00:01:38.560 --> 00:01:52.849
Geremy Meyers: oh, it smokes, you know. I get updates internally all the time on feature releases. Obviously, they happen to cloud all the time the things that tend to make the big release on the blogs are, you know, the big quarterly releases. We do on Prem. But yeah, there's a lot going on.
12
00:01:53.630 --> 00:01:57.289
Andy Whiteside: Well, that's the voice of Jeremy Myers. Jeremy is the director, for
13
00:01:57.480 --> 00:02:11.379
Geremy Meyers: I call it sales engineers. What's the official title for those guys these days, Jeremy? I always it's partner technical strategies. And you know, essentially, we are sales engineers. And we focus on partners and their customers.
14
00:02:11.980 --> 00:02:16.179
Andy Whiteside: Yeah, that's how you relate to us. And course, we're.
15
00:02:16.390 --> 00:02:24.070
Andy Whiteside: you know, kind of all over the place, Us. Canada, India, but because of your because of our presence as a partner. You you're here with us quite often.
16
00:02:24.340 --> 00:02:26.130
Geremy Meyers: quite frequently. Yup!
17
00:02:26.830 --> 00:02:28.559
Andy Whiteside: You have to hear all. My
18
00:02:29.600 --> 00:02:30.600
Andy Whiteside: oh, May!
19
00:02:31.060 --> 00:02:38.899
Andy Whiteside: Well, I wish I could! I wish I could scale myself. I wish I could do sort of an automatic scaling
20
00:02:39.080 --> 00:02:46.210
Geremy Meyers: of my time, too, because that'd be fantastic, too. That's a good leader, I would say to this time. So
21
00:02:46.500 --> 00:03:03.020
Andy Whiteside: that's we're gonna talk about today. Today's blog by Mark Mueller came out like 5 days ago bringing the power of Citrix auto scale to on premises. I think that was part of the 2305 stuff, and I'm sure we've been a few minutes on it. But today we're gonna dive into a deeper
22
00:03:03.050 --> 00:03:05.730
Andy Whiteside: Help us by setting this up, Jerry. Why.
23
00:03:06.450 --> 00:03:19.709
Andy Whiteside: where? Where did auto scale come from? What does it apply to when you, when you takes like we were just talking about taking you and auto scaling you up. That'd be awesome. But you know, taking some elements of things and auto scaling, it may not be as awesome. What? What's what's auto scale
24
00:03:19.760 --> 00:03:22.579
Andy Whiteside: historically mean in the Citrix
25
00:03:22.750 --> 00:03:23.590
Andy Whiteside: world.
26
00:03:23.820 --> 00:03:48.090
Geremy Meyers: So it started is a feature, I wanna say, back in 2,000. 2,019. Heck! The article goes into here. It was a feature we introduced in our cloud console, you know, 4 years ago it was focused on managing workloads primarily in the cloud. So, first of all understand the cloud console can manage on Prem. But it was a feature of those part of the cloud, and if I had to argue, is probably meant
27
00:03:48.090 --> 00:03:57.680
Geremy Meyers: initially just to manage costs in the cloud. So you know, spinning up workloads, spinning down workloads and like an azure or native us, or Google specifically to help make
28
00:03:57.780 --> 00:04:16.260
Geremy Meyers: just reduce the spin in the cloud for machines that don't need to be running. So that's spinning up when you need more capacity and spinning down when you don't need it, because help me out with this, you between you and Bill, when I've got a machine sitting there in my cloud, even when it's not turned on. I'm I'm paying for something, aren't I?
29
00:04:17.600 --> 00:04:31.609
Geremy Meyers: You are! You are. So you're paying for storage. You're paying for, not necessarily compute. You know that side of it. But you're definitely paying for storage as well. So yeah, that's a that's a big piece of it, you know you're paying for this that are sitting idle for sure.
30
00:04:31.970 --> 00:04:37.200
Andy Whiteside: Build up. We had any projects where this either scaling up or scaling down, or both, became
31
00:04:37.240 --> 00:04:56.959
Bill Sutton: part of the requirements. Yes, absolutely to help to. To what Jeremy said earlier. In the sense that it helps control the spend the ability to spin machines down when they're not in use to even deallocate them if they're if they're like non persistent, we can completely deal deallocate them which essentially
32
00:04:56.960 --> 00:05:11.220
Bill Sutton: eliminates any sort of storage costs. And then and then there's some other features that are not related. Auto scale that can help with cost is probably maybe related. But they're not included in this article. Like changing the machine type or the disk type, and those sorts of things
33
00:05:11.220 --> 00:05:11.880
Andy Whiteside: right?
34
00:05:11.880 --> 00:05:21.530
Andy Whiteside: And so this, okay, let's the the article here in the first paragraph, toss about 50% of the customers used it in the das in the cloud based version of the platform.
35
00:05:21.530 --> 00:05:31.309
Andy Whiteside: and the ones who reported back said that they saved 70 or more on the cost of running their desktops. Those are pretty compelling numbers. Yes, very much so.
36
00:05:32.020 --> 00:05:44.620
Geremy Meyers: you know what? And it's it's a part of the delivery group configuration and it's easy to miss right? So even though there's a button that says manage auto scale right in the configuration. A lot of folks mix, miss it. You know. The thing that threw me off was.
37
00:05:45.010 --> 00:05:50.629
Geremy Meyers: you know we've only got, you know, I guess when we originally introduced this, only 50 of our customers were using it.
38
00:05:50.750 --> 00:05:54.659
Geremy Meyers: Man, it's an easy one. You already got it, turn it on.
39
00:05:54.730 --> 00:06:02.240
Andy Whiteside: So I've had lots of conversations recently, and some of the things I've been doing around persistent versus non persistent. I probably brought up on this podcast a couple of times.
40
00:06:02.260 --> 00:06:09.039
Andy Whiteside: Is this limited to the non persistent world? Or can I do persistent workloads with auto scaling?
41
00:06:10.240 --> 00:06:32.600
Geremy Meyers: You can do it. It's really more power management at that point. Because we're really just spinning up workloads that just aren't being used but initially, the idea was more for non persistent. So creating a buffer of machines. So you want to. Obviously, at the end of the day, make sure you had machines available for folks to connect to. But you know, I think initially, it was more from a non
42
00:06:32.600 --> 00:06:58.969
Bill Sutton: persistent perspective. If you go back a few years that Citrix had what I think was was originally called in the In the on Prem World Power management, which did some of this. And this is a, you know, an expansion. Significant expansion of this to address the needs in the cloud, particularly around costs and capacity. And now it looks like what they're doing. What they have done is bringing it back to the on-prem world kind of the the marching orders. I think that Citrix
43
00:06:58.970 --> 00:07:10.400
Bill Sutton: has this year is to, you know, to be consistent across all delivery methods, whether it's in the cloud or whether it's on Prem. And this brings it back a lot of the features and functionality that we're in the cloud to the on-prem world.
44
00:07:10.780 --> 00:07:18.060
Andy Whiteside: Well, let's let's make that transition cause. I was talking, you know, non persistent versus persistent. If I've got my own data center.
45
00:07:19.060 --> 00:07:34.549
Andy Whiteside: or maybe I've got a hosted data center by a partner like Zintigra, what is the ability to do this outside of the das world. In other words, not not the platform as a service but now to do it in my own desktop as a service which could be cloud enabled
46
00:07:34.600 --> 00:07:37.360
Andy Whiteside: could be on premises could be both.
47
00:07:37.390 --> 00:07:40.230
Andy Whiteside: What? Why does it matter to me?
48
00:07:43.120 --> 00:08:10.919
Geremy Meyers: I mean. So we've had this debate. You know, I probably on this podcast a few times, which is and I always thought, that is this really relevant on prem, you know, do we have, you know? For the most part, you know, I'm buying hardware in my data center. It's some cost, right? So I've already procured it right, so I don't necessarily need to manage the cost, and at least that's where I originally came to. It is so. If I've already got the hardware I've already provision the hardware. Do do I still need it?
49
00:08:10.920 --> 00:08:23.569
Geremy Meyers: And the one thing one of the things we landed on is, listen, even if it wasn't from a a cost perspective. Listen, there's an environmental footprint we should be considering, too, right? Because data centers cost power. And the more things you have running.
50
00:08:23.820 --> 00:08:33.599
Geremy Meyers: I mean that that 2 different perspectives, one running things and providing power requires, you know, money. The same time you're just trying to be a little social, responsible.
51
00:08:33.630 --> 00:08:41.540
Geremy Meyers: Yup, you know, again. And there's still a cost involved. Right? If I if I use Uber car as a service.
52
00:08:41.590 --> 00:08:49.769
Andy Whiteside: there's still a cost involved. What if I could make that cost less by, you know, making the Uber drivers gasoline more efficient?
53
00:08:49.950 --> 00:09:19.779
Andy Whiteside: And then maybe that cost passes down to me, even though either I use my own car, which will be direct result versus. And even if I use as a service, there's there's impacts all across the board bill. Sorry you were going to say something. Facilities. They make money by leasing space and and providing power, so the less power you consume in theory, you would have presume that you would have less cost and by spinning down machines at a at scale, then that could have a significant impact.
54
00:09:20.320 --> 00:09:24.859
Geremy Meyers: Yeah, there's an aggregate involved is what we're saying. Yep.
55
00:09:25.200 --> 00:09:30.200
Andy Whiteside: And then you factor in like Jeremy pointed out the social responsibility of you know. Turn your lights off.
56
00:09:31.400 --> 00:09:33.180
Bill Sutton: Exactly. Yep.
57
00:09:33.200 --> 00:09:53.320
Andy Whiteside: So they caught a 4 key features of auto scale, as it relates to 2305, which is the on premises version, which, by the way, you can get. If you have a part of like Z integral host that we can host it with the on print version. We just host it for you that way you might end up with the best of both worlds. First one. Here, Jeremy, is a schedule based and load based settings. What does that mean?
58
00:09:53.810 --> 00:10:20.330
Geremy Meyers: So things number one is you can define when your working hours are this is very similar to power management. Now that worked in the past. We set times a day when you've got folks who are gonna be in the office, or, you know, obviously, you don't want someone to log in, click a button and have to wait for virtual machines to spend up right? So if you can anticipate the time of day, then that's a pretty good start. You can define how many machines you won't running? It peak hours.
59
00:10:20.330 --> 00:10:33.089
Geremy Meyers: And then, secondly, you can go through and say, hey, number one, I want this many running at Peak and this money running off peak. So there's that. But you can also define. And this is where the the load based settings come from is you can also define. You know, what kind of buffer
60
00:10:33.370 --> 00:10:56.769
Geremy Meyers: do you want to make available? As well? So, for instance, I'll use easy math here. I want to do a 10% buffer. And I'll I've got 10 machines running. You're always gonna have an eleventh one, or you're gonna have 10 above that available just in case, you know, you just say you happen to Max out let's add a little capacity just in case, but it'll be very dynamic as you go, so you can define an on peak and an off peak buffer as well.
61
00:10:57.460 --> 00:11:01.499
Bill Sutton: Bill. Anything to add to that, Nope. He covered it, covered it well.
62
00:11:02.080 --> 00:11:25.290
Bill Sutton: so Bill will go to you for the next one dynamic session timeouts. So this is yes, this is the old timeouts that we would set, I think, in Gpos where we would say, if you're idle for 10 min or 15 min, go to a disconnected state, and then, if you're disconnected for 30 min, your session gets recycled. So here they're allowing it to be a little bit more dynamic in terms of setting differences between Peak and off Peak
63
00:11:25.320 --> 00:11:31.689
Bill Sutton: to allow the drain of the server to occur in a more timely manner. At least, that's how I read it, Jeremy, am I on the right track?
64
00:11:31.840 --> 00:11:55.349
Andy Whiteside: Okay? You said, no, I thought, Oh, my gosh, so
65
00:11:55.410 --> 00:12:04.469
Geremy Meyers: awesome. Yeah, I mean, so my kids don't turn the light off, and they leave the room. But what what's funny is, and I think most of us, at least, when I
66
00:12:04.550 --> 00:12:10.229
Geremy Meyers: you know, if I'm done with my machine a lot of times, what they'll do is I'll just X out of it, which just throws it in a disconnected state.
67
00:12:10.260 --> 00:12:14.899
which, honestly, is probably the default behavior for most people. They're not going.
68
00:12:14.930 --> 00:12:32.000
Geremy Meyers: you know, necessarily, to start, run, or start shutdown, or disconnect, or or whatever they're just hitting the X, and so that leaves a machine running and that plays into this right? So if you can, if you can maybe set a session timeout. The changes depending on peak hours make sense.
69
00:12:32.470 --> 00:12:48.259
Andy Whiteside: And what I think we're really seeing is what's good for the cloud is also good for your data center. The cloud is just somebody else's machines. In this case it's your machines. You know those some of those same concepts, even though we all, we? We quite often just took them for granted in the past. Those concepts apply the day.
70
00:12:50.910 --> 00:12:56.920
Andy Whiteside: So, Jeremy, I'll go back to you for this one, though. Auto scale, tagged machines, cloud burst and hybrid.
71
00:12:57.080 --> 00:13:07.450
Geremy Meyers: So the one thing that I always forget is what we've reintroduced into the on premise, you know, architecture is the ability to connect out to a cloud.
72
00:13:07.470 --> 00:13:36.210
Geremy Meyers: You know, for work, let's say, for instance, for a while. There, I would say, argue, maybe a year or 2. What we pulled from the on premise product is the ability to create a hosting connection out to a cloud. Right so, or, better yet, if you're hosting all of this infrastructure in a cloud. So again, not using Citrix Cloud, where we've got the management components that we're hosting. But you're setting up Bdc's and sequel servers and those pieces up in the cloud. Long story short. You know, creating a hosting connection to a cloud, something we've reintroduced. So what is not unusual
73
00:13:36.460 --> 00:13:51.570
Geremy Meyers: is, you know, having a single instance. With workloads on a cloud, maybe sitting in a colo, maybe sitting in your data center, and the idea that I would like to be able to define what types of machines participate in the auto scaling process.
74
00:13:51.570 --> 00:14:10.769
Geremy Meyers: So you can tag machines and then say, Hey, I only want to allow, maybe my on premise machines to be the the burstable machines versus like, say, the cloud, or vice versa. Whatever kind of makes sense. But now you can tag machines and define which types of machines based on that tag will participate in the bursting. If you will
75
00:14:13.490 --> 00:14:14.790
Andy Whiteside: sit down.
76
00:14:14.930 --> 00:14:20.200
Andy Whiteside: I don't know how well you guys know, like the azure solutions for this, but this this seems pretty robust
77
00:14:20.480 --> 00:14:27.119
Geremy Meyers: and to be able to do it in both the cloud platform as well as the on-premises platform.
78
00:14:27.400 --> 00:14:31.040
Andy Whiteside: seems to be quite conducive to being successful.
79
00:14:31.620 --> 00:14:41.490
Geremy Meyers: So for someone who doesn't do a lot of we have a team environment, you know. We we work with it. But I don't have 5,000 machines.
80
00:14:41.510 --> 00:15:01.700
Geremy Meyers: Just been up and down and see some of these, some of these things in action on a on a consistent basis, and I kind of forget how much tagging is such a big deal. So creating machines and azure, being able to tag those creating things in Citrix and tagging those. Once you do it a handful of times you go. I mean, this makes sense, though. Let's go retag everything. But tagging has become a
81
00:15:01.770 --> 00:15:10.749
Geremy Meyers: not just from a management perspective. A lot of times. That's how folks are are charging back to the businesses based on tags. But yeah, now we can tag those as or leverage this as well.
82
00:15:11.200 --> 00:15:24.319
Bill Sutton: Yeah, we're leveraging the tags to decide what we want to burst and what we don't want to burst versus trying to create a bunch of delivery groups or something that's segmented in a different way. We we don't have to get. We don't have to create sprawl to do what we need to do here.
83
00:15:25.510 --> 00:15:31.459
Andy Whiteside: Yeah, as you guys were talking about this, right? I've got my my Lg unit running Igl connected to my virtual desktop.
84
00:15:31.650 --> 00:15:37.199
Andy Whiteside: And you know, I just sit there letting it run wouldn't hurt, wouldn't hurt me. So I just let it go
85
00:15:37.590 --> 00:15:40.559
Andy Whiteside: bill user notifications
86
00:15:41.190 --> 00:16:07.589
Bill Sutton: log off notifications. This is around for a while. But it's essentially notifying the user when you're ready to getting ready to force off a linger session. So the session has been inactive for a certain period of time. We can send a custom notification and then force log off the session. I. This is something that we've had for a while, but especially in the cloud. But this is expands the auto scale functionality to enable it there as well.
87
00:16:07.710 --> 00:16:08.370
Yeah.
88
00:16:08.860 --> 00:16:14.480
Andy Whiteside: And then, Jeremy, it covers some of the technical platform support information. Let me just hit these real quick.
89
00:16:14.740 --> 00:16:26.600
Geremy Meyers: Yeah, for starting. So what are we hosting on? You know Citrix. you know we'll say Zen server. But you know, aws, Google Cloud, you know all the yeah, all the standard resources. Right? So it doesn't
90
00:16:26.800 --> 00:16:40.839
Geremy Meyers: doesn't really matter what you're hosting on. That's less important. And of course. you know, though OS type 3, it will do multi session. Zen app if you will zoom desktop. I will point out that, depending on what the delivery type is.
91
00:16:41.040 --> 00:16:54.980
Geremy Meyers: Like, I said earlier. You know, there is no quote unquote power management anymore. It is falls under auto scale. If you're doing this with dedicated desktops, it'll just be straight power management. If you're doing this with non persistence. You'll get a few more options like, for instance, do you? Wanna
92
00:16:55.250 --> 00:17:02.469
Geremy Meyers: do you want to? Especially on a multi-session type? Do you want to scale vertically or horizontally. Always an important question. So that's that's one thing that
93
00:17:02.560 --> 00:17:05.420
Geremy Meyers: you might miss if you're looking at.
94
00:17:05.490 --> 00:17:08.119
Geremy Meyers: You know, a persistent desktop type. But
95
00:17:08.230 --> 00:17:16.160
Geremy Meyers: yeah, we support just about everything that's missing here. Supported Vda. Hosting plaid is new tanics. I assume it's in there as well.
96
00:17:16.290 --> 00:17:22.789
Andy Whiteside: It would work the same way. Yeah, exactly same way. Yup. So with this is, you've got.
97
00:17:22.849 --> 00:17:27.700
Andy Whiteside: you know, Citrix, Hypervisor, Newtonics, vmware Amazon, Google, Microsoft.
98
00:17:27.750 --> 00:17:37.879
Andy Whiteside: That would be a multi cloud hybrid strategy. That's why it's so important that we do this not only for the dazz version, but the the on premises version
99
00:17:38.460 --> 00:17:39.980
Andy Whiteside: cause people are gonna need that
100
00:17:42.170 --> 00:17:55.419
Geremy Meyers: absolutely. Now it is abstracted from the underlying. So I like that. It called out that it's supported. But you know this feature is pretty much extracted or abstracted from the underlying hypervisor. So it'll work with anything you connect to it.
101
00:17:56.270 --> 00:18:02.979
Andy Whiteside: So the next section goes back to what we kind of talk about a little bit, which is, how does auto scale improve by on premises deployments?
102
00:18:03.290 --> 00:18:09.089
Andy Whiteside: let's kind of talk about that just kind of conceptually. What are they trying to call out here?
103
00:18:10.420 --> 00:18:29.780
Bill Sutton: I think they're talking a lot about what we've already talked about, as you said. You know, particularly in the center the middle of this section, the the idea of previously leveraging on prem data centers, you know we would. We would provision them to allow 24 by 7 access, and the resources are always available sitting there running in theory.
104
00:18:29.820 --> 00:18:46.610
Bill Sutton: Obviously, that was great for the user. But you know, we we're keeping the resources powered on and incurring costs and complexity and so forth, and so leveraging auto scale allows us to be a lot more granular than we were able to be in the past more akin to what we see in the cloud.
105
00:18:47.800 --> 00:18:48.500
Yeah.
106
00:18:48.670 --> 00:18:56.209
Geremy Meyers: yep. And what I think is interesting as well as we actually bubble up an estimated cost savings into director. Now, right? So if you go look
107
00:18:56.290 --> 00:19:06.850
Geremy Meyers: within the director, console you're looking at your dashboard. You'll see machine usage. And over on the right, we're actually oh, wow! Okay.
108
00:19:07.800 --> 00:19:09.020
Andy Whiteside: to build that.
109
00:19:09.360 --> 00:19:16.960
Andy Whiteside: You caught that that caught you interest that you sounded interested
110
00:19:17.010 --> 00:19:34.650
Bill Sutton: for now. So II just find it interesting that we're actually that I mean, just like you would do in the Cloud. Citrix has got the ability to say, you know, we're saving you X. Powering things down. I'm sure there's some metrics in the background and go along with this in terms of how it's calculated, but nevertheless, to be able to do that, for on prem resources, I think, is interesting.
111
00:19:34.720 --> 00:19:40.719
Andy Whiteside: Jeremy, can you control those variables? Do you know, and and kind of tune it in for your environment.
112
00:19:40.760 --> 00:19:45.370
Geremy Meyers: Think so. Actually, I'm I'm actually in my cloud console now. And
113
00:19:45.890 --> 00:19:55.139
Geremy Meyers: I wanna say, you could define how much the cost I can't remember if it's at the delivery group level or within auto scaled. So I have to go back and look. But I think you can define what that looks like.
114
00:19:55.830 --> 00:20:04.880
Andy Whiteside: Well, that's that's it. Right? We're we're all in it to deliver apps, including the desktop, our users and help them be productive. At same time, we gotta be able to justify the cost of all this stuff and
115
00:20:05.020 --> 00:20:11.130
Andy Whiteside: having something at least gives us some semblance of the money that's being saved. it's freely. Yup.
116
00:20:11.680 --> 00:20:12.460
yeah.
117
00:20:13.470 --> 00:20:23.200
Andy Whiteside: alright, guys. Well, it's good to be back with you guys Jeremy. any additional things you'd like to add about the idea of auto scaling, or just what Citrix is up to in general.
118
00:20:23.380 --> 00:20:49.370
Geremy Meyers: Well, I'll say this. So this goes back to things that are making it on prem part of what helps facilitate. This is the fact that now we do have the web console. That's been a part of the cloud for many iterations. Now, you know at least 2 or 3 years. That's on Prem. Now, so that Mmc. Has been retired, you know, going forward. You'll want to leverage and I think it might even be the default now, is the web console, for on prem, so you know, much needed refresh even for the ui
119
00:20:49.430 --> 00:20:58.540
Bill Sutton: fix it on Prom Bill. I'm sure you're devastated to lose yet another Mmc. Console. Oh, no, not devastated at all. So you know our IP,
120
00:20:59.010 --> 00:21:04.049
Geremy Meyers: our IP, that was, you know what I remember when that came out in the year 2,000
121
00:21:04.420 --> 00:21:34.169
Geremy Meyers: anyways long story short, Mmc. Came out. I thought they hung the moon. And it's just funny how they feel dated now. Well, the other thing I'd added, this is because it's a web based console. You could partner with Citrix and host it in the cloud. Yeah, you could do it in your own data center. Yeah. And you could also do it. Another part, partner like us, and you would still be able to access it. Because you're just using standard web protocols web security. That's extremely powerful and flexible and useful all the same time.
122
00:21:35.910 --> 00:21:46.360
Andy Whiteside: Yeah, okay, well, guys, thanks. So Jeremy, we spoke earlier this one, we're gonna be doing a podcast on service now and Citrix, looking looking forward to that one, I think that's it's such an exciting
123
00:21:46.420 --> 00:21:48.370
Andy Whiteside: place to be heading with the business.
124
00:21:48.520 --> 00:22:12.900
Geremy Meyers: I'm pretty fired up about that. So I know on 2 or 3 different occasions. You know, we've talked about how rest Apis are just sort of a requirement of the cloud. Now, just so, the different product stacks can integrate easily. And so you know. So we're gonna hit on. There's an its and adapter that hooks into service now, and there's a lot of cool things that we can do as a part of that integration. So we get to hit on that here pretty soon.
125
00:22:13.110 --> 00:22:16.480
Geremy Meyers: Well, guys, I appreciate it, and I look forward to doing it again next week.
126
00:22:17.080 --> 00:22:21.670
Geremy Meyers: Alright, bye, guys, see you, Bill, see, you Andy have a good one. Thanks.