
The Citrix Session
Welcome to 'The Citrix Session,' where we bring you the latest in Citrix technologies and solutions. Hosted by XenTegra, this podcast dives deep into the world of Citrix digital workspace solutions, exploring everything from virtual apps and desktops to networking and security. Join us each episode as we discuss best practices, new features, and expert strategies to optimize your Citrix environment and enhance your user experience. Whether you're an IT professional seeking to expand your Citrix knowledge or a business leader looking to improve operational efficiency, 'The Citrix Session' is your essential resource for staying ahead in the ever-evolving tech landscape. Tune in to transform the way you work with the power of Citrix and XenTegra."
The Citrix Session
Expanding Citrix DaaS with Amazon WorkSpaces Core Managed Instances
In Episode 184 of The Citrix Session, host Bill Sutton is joined by Citrix experts Geremy Meyers and Todd Smith to explore the newly enhanced integration between Citrix DaaS and Amazon WorkSpaces Core Managed Instances.
The team dives into what's new in this “version 2” release, how it enables flexible, cost-effective VDI deployment, and why it’s a game-changer for customers with AWS and Microsoft licensing commitments.
Key topics include:
- What Account Technology Strategists (ATS) really do
- The evolution from WorkSpaces Core to Core Managed Instances
- Support for Machine Creation Services (MCS) and non-persistent desktops
- Hybrid identity management with Intune and Azure AD
- How Citrix maintains a unified admin and user experience across clouds
- AWS savings plans and funding resources for pilots
Whether you're planning a cloud migration or optimizing your existing DaaS strategy, this episode is packed with valuable insights for IT leaders and practitioners alike.
WEBVTT
1
00:00:02.560 --> 00:00:18.279
Bill Sutton: Hello, everyone, and welcome to episode 183 of the Citrix session. I am your host, Bill Sutton, with Zintegra. I have with me a couple of folks from Citrix like usual Jeremy Myers and Todd Smith. I almost said Jeremy Smith and Todd Myers. Sorry, guys.
2
00:00:19.280 --> 00:00:23.089
Bill Sutton: Nevertheless, Jeremy, you want to say Hello! Introduce yourself.
3
00:00:23.850 --> 00:00:37.450
Geremy Meyers: Ola. So I am the leader. Lead a group of ats as account technology strategist here on the east coast in a in a smidge of Canada. If you listen from week to week I'm a regular if you will.
4
00:00:37.730 --> 00:00:41.700
Bill Sutton: That's right. And another regular Todd, do you want to say Hello? Introduce yourself real quick.
5
00:00:41.920 --> 00:00:47.610
Todd Smith: Yeah, thanks, Bill. My name is Todd Smith, and I guess I should start by saying.
6
00:00:48.270 --> 00:01:01.680
Todd Smith: since we're all speaking different languages today, I'm the account technology strategy leader for the North American public sector team here at Citrix covering both the United States as well as Canada
7
00:01:02.030 --> 00:01:02.680
Todd Smith: and.
8
00:01:02.680 --> 00:01:16.449
Bill Sutton: So so that it's interesting, both of you all. I don't know that I've really made the connection, or Ats leaders. Why don't 1 of you, just for the audience that may not know or need a refresher. What is an Ats? What do they do at Citrix?
9
00:01:16.450 --> 00:01:21.720
Todd Smith: Sure, so I can. I can. I can kind of take this, and Jeremy can correct me if I say anything wrong. But
10
00:01:22.680 --> 00:01:39.600
Todd Smith: an Ats, an account technology strategist from a citrix perspective is someone who is responsible for pretty much the entire technical journey that a customer goes through everything from what would be considered pre-sales
11
00:01:39.660 --> 00:01:58.460
Todd Smith: all the way through the sales processes that have happened throughout this life cycle of a customer. Including things like product adoption right? So rolling out the products that the customer is buying or subscribing to, as well as being able to
12
00:01:58.750 --> 00:02:00.850
Todd Smith: support them.
13
00:02:00.970 --> 00:02:10.620
Todd Smith: You know, throughout their their post sales activities until you know pretty much until their their journey with Citrix is is over.
14
00:02:12.030 --> 00:02:14.770
Todd Smith: covering a variety of different things. Right? So
15
00:02:15.360 --> 00:02:26.920
Todd Smith: some technical sales activities, some technical support and product support, as well as being able to make sure that the customers are extremely successful in
16
00:02:27.070 --> 00:02:33.690
Todd Smith: utilizing all of the products that they are entitled to, and and have that awareness of what's going on.
17
00:02:33.960 --> 00:02:41.049
Todd Smith: Everything from what's new with Citrix to product features that they're they're currently not using that they may have a need for.
18
00:02:41.360 --> 00:02:48.398
Todd Smith: So that's that's kind of the role of the Ats is to make sure that the the customer's technical journey with the with Citrix is
19
00:02:48.820 --> 00:02:49.710
Todd Smith: fulfilling.
20
00:02:51.210 --> 00:02:52.003
Geremy Meyers: You know.
21
00:02:52.680 --> 00:03:03.170
Geremy Meyers: that was actually a pretty good summary, Todd, I think. Citrix has done this in the past, but it's been a few different kinds of roles. So we've had pre sales engineers. We've had
22
00:03:03.660 --> 00:03:13.600
Geremy Meyers: customer success engineers. We've had tams, you know. We've had a few different folks be a part of. You know that I would say that that function if you will.
23
00:03:14.890 --> 00:03:23.110
Geremy Meyers: But I think what's different is now we have an Ats who has some ownership of all 3 of those things. Right? So are they a full on Tam? No, but there are a few things that are very important.
24
00:03:23.140 --> 00:03:38.500
Geremy Meyers: Are they full on customer success? No, but there is a lot that they're responsible for. There are they full pre sales? No, but they are interested in. Really, you know, looking at ways that we can expand and make the best use of stuff. So you know, I think within the industry.
25
00:03:38.790 --> 00:03:57.090
Geremy Meyers: you know. Listen, if you work with Microsoft for a while. Ats have been a thing there for a long time, you know. I think the idea here is, you want to have someone who understands, or at least invest the time to partner and really understand the strategy of a customer, and where Citrix can align to that. And how do we support that? Behind the Ats?
26
00:03:57.490 --> 00:04:20.260
Geremy Meyers: There are a lot of resources available. So, for instance, you know we've got support escalation leaders aligned to us. We've got product managers and product specialists that align to us. We've got, you know. We've got solutions architects and you know, partner Ats, is that align to us as well. So as we're working across the ecosystem. So we're working across the product stack.
27
00:04:20.793 --> 00:04:22.960
Geremy Meyers: You know the Ats is.
28
00:04:23.230 --> 00:04:31.589
Geremy Meyers: you know, use a firm kind of the quarterback from a strategy perspective. And really should have line of sight into all that's going on with the customer. So
29
00:04:32.240 --> 00:04:38.399
Geremy Meyers: it's different. But at the same time, I think you know, Todd will probably tell you, is, you know.
30
00:04:38.580 --> 00:04:44.819
Geremy Meyers: being pre sales entirely in the past, although we've gone off the rails here, we're not even talking about aws, but we'll we'll get back.
31
00:04:44.820 --> 00:04:46.190
Bill Sutton: We'll get there. We'll get there.
32
00:04:46.190 --> 00:05:02.760
Geremy Meyers: Yeah, but from a pre sales perspective, you know, there are things that Todd and I would be technically support a sale, and then we'd go move on to the next one, especially in the space that we were in right. So we had a lot of customers but try to do a handoff to an internal team to either. Do customer success hopefully bought
33
00:05:02.960 --> 00:05:05.050
Geremy Meyers: the Tam Service Trm service.
34
00:05:05.690 --> 00:05:10.900
Geremy Meyers: Now it's a little different. We have some ownership over all of those pieces. With the goal being.
35
00:05:11.240 --> 00:05:17.550
Geremy Meyers: you know. Listen. As a as a customer of Citrix. We want to make you successful. And what does that look like? We'll work with you on that.
36
00:05:19.060 --> 00:05:23.440
Bill Sutton: Yep. So yeah, we did go a little outside of the norm. But we often
37
00:05:23.440 --> 00:05:41.650
Bill Sutton: we often talk about other topics. And I thought it was. It was a good opportunity. I kind of struck me when you guys talked about your roles. Even though I already know them. I already knew them. That there may be folks out there who don't know what an ats is and what their role is. And you know most most of those customers who
38
00:05:41.650 --> 00:06:04.500
Bill Sutton: are large or even medium sized probably have already had contact with an Ats. But they're historically, it's our historically been the the salesperson or ae, and the Se. That was the old model right? And this is a different way of approaching it and largely driven by the way the products are packaged and sold, and the entitlements are are laid out. Is driven. A lot of this, but not all of it. Certainly.
39
00:06:05.410 --> 00:06:31.449
Geremy Meyers: I I mean, it's less about commercial transactions. I mean, the idea is, we have most of our customers have bought in a certain pattern that man. They may have 2 or 3 or 5 different renewals a year right? And so, I think, where we'll land on this is, you know. Listen. You have one renewal. Maybe that happens every 3 years. Maybe it happens every 5 years depends. But you know, what do you do along the way? Well, listen. You've got someone on either Todd or myself. Team, you know, kind of walking through that with you, and
40
00:06:31.590 --> 00:06:44.000
Geremy Meyers: you know, not just from a technical perspective. But in a lot of cases, you know, our contacts are really trying to socialize the business value across the organization as well, so that you know other folks within the business understand exactly what
41
00:06:44.704 --> 00:06:49.109
Geremy Meyers: you know it is up to, and how they're, you know, providing some value.
42
00:06:49.440 --> 00:06:49.780
Bill Sutton: Good.
43
00:06:49.780 --> 00:06:56.609
Todd Smith: Yeah. And and I think, Jeremy, you just hit on a really critical point. There is, you know, every single one of our customers is being
44
00:06:57.100 --> 00:07:07.510
Todd Smith: kind of driven to show business value for every single investment. And the investments can be technical technology investments. It could be
45
00:07:07.710 --> 00:07:22.439
Todd Smith: investment in Hr capital. It could also be investments in, you know. Just think about the amount of office space that's out there. Every business out there, whether it's in the private sector, or even the public sector, is being
46
00:07:22.700 --> 00:07:34.880
Todd Smith: asked to review and show how the how the business is benefiting from these investments. And that's another key thing that the Ats is helping customers understand.
47
00:07:35.270 --> 00:07:42.550
Todd Smith: You know, what exactly. What, exactly does this subscription do to drive the success of the business.
48
00:07:42.800 --> 00:07:43.350
Bill Sutton: Right.
49
00:07:44.480 --> 00:08:04.310
Geremy Meyers: So to bring it home. I think this is this blog post here, and sort of the content that goes along with it is something that I'm sure we'll take to a lot of our customers over the next few weeks that they understand from a delivery model. You know the solution. We're going to talk about not new so to speak. You know, we've been deploying the Ec. 2 for a long time.
50
00:08:04.380 --> 00:08:27.139
Geremy Meyers: and last year, you know Amazon and Citrix, and believe it or not, Microsoft had a had a say in this as well like there's a very big deal, even though we're talking about Amazon. It's a very big deal from a Microsoft perspective. But they came to market with this last year. This is the this is the citrix das integration with Amazon Workspaces. Core. But I heard this described as version 2 today, meaning
51
00:08:27.370 --> 00:08:34.369
Geremy Meyers: this has been out for 6 or 8 or 10 months. Now. There are some updates to it. That are pretty significant, actually.
52
00:08:35.200 --> 00:08:38.710
Geremy Meyers: that that you know worth calling this a version 2, which is pretty neat.
53
00:08:39.059 --> 00:08:58.721
Bill Sutton: So let's get into this. The the blog is is entitled it's on the Citrix blog site. It's entitled, Now Available Citrix das for Amazon Workspaces. Core managed instances, and it's written by Abhilash Verma hopefully. I didn't crucify that name, but nevertheless, so to like Jeremy said, this is
54
00:08:59.600 --> 00:09:27.500
Bill Sutton: This is that Amazon workspaces core integration with Citrix. Das has been out for what a year, maybe maybe a little bit more. What was referred to as Amazon Workspaces. Core. And this article talks about kind of like Jeremy just said, kind of a version, 2. Where it's speaking about Amazon Workspaces. Core managed instances. So why don't we talk 1st about what's the difference between those 2 things? And then we can launch into the details. Anybody want to take that.
55
00:09:28.650 --> 00:09:40.129
Todd Smith: Yeah. So so I think, I think when we 1st introduced the integration with Amazon, specifically, the Workspaces, and, more importantly, their workspaces core capability, which is really
56
00:09:40.260 --> 00:09:49.690
Todd Smith: the focus on windows operating system for the desktop as well as windows operating system on the server side. So it really kind of fit into our overall
57
00:09:49.870 --> 00:09:53.070
Todd Smith: application and desktop delivery piece of it.
58
00:09:53.430 --> 00:10:02.279
Todd Smith: The the 2 dot O version of this which really added in this managed instance, capability right? Which is, I need to have some
59
00:10:02.440 --> 00:10:08.359
Todd Smith: more robust, dedicated instances that are going to be almost
60
00:10:08.640 --> 00:10:15.379
Todd Smith: almost configured specifically for a Das environment or a virtual app virtual desktop environment.
61
00:10:16.190 --> 00:10:18.501
Todd Smith: And that was kind of the key. There.
62
00:10:19.270 --> 00:10:44.470
Todd Smith: it's it's been, you know, a lot of feedback from customers, a lot of feedback from the from both the Aws engineering teams as well as the Citrix engineering teams, and really kind of filling in the gaps of what we're missing on the 1.0 version and kind of making sure that that goes into this. This newly revitalized Amazon Workspaces. Core managed instances capabilities to be included with Das.
63
00:10:46.070 --> 00:10:47.216
Bill Sutton: Yes, so
64
00:10:47.790 --> 00:10:48.280
Geremy Meyers: When.
65
00:10:48.280 --> 00:10:49.345
Bill Sutton: Go ahead, Jeremy!
66
00:10:49.700 --> 00:11:12.580
Geremy Meyers: So when you, when you think about it, like the history of quote unquote Vdi with Amazon, so they had a solution. That was called workspaces, and that Workspaces solution was actually 2 different things. But ultimately this was a Amazon complete turnkey solution. It was a broker. It was either a Vdi, or it was, you know, application training. But either way, that was the original workspaces solution, or
67
00:11:12.750 --> 00:11:21.079
Geremy Meyers: we would give you some Ec 2 Amazon compute space, and you could do what you wanted with it right? Which
68
00:11:21.340 --> 00:11:33.280
Geremy Meyers: it's fine. That's infrastructure. As a service. You could either a had customers that were creating entire. See that environments just the quote unquote on prem licensing. They were just putting that in Amazon and running that
69
00:11:33.589 --> 00:11:56.549
Geremy Meyers: you know as is which is fine, or or they were taking the Citrix das solution. And they were tying that into Ec. 2. And they were treating that almost like a data center, right, which is also fine. There was a kind of a caveat to that. I think we'll get to in here a little bit is man, the Microsoft licensing, and that solution was was a bit prohibitive. So number one, you couldn't use Vdi unless
70
00:11:56.760 --> 00:12:00.769
Geremy Meyers: keep me straight here. You had to do dedicated hosts. I wanna say.
71
00:12:00.770 --> 00:12:01.210
Bill Sutton: That's correct.
72
00:12:01.525 --> 00:12:14.760
Geremy Meyers: So you you had to do, dedicated host. It made it really tough. I don't even think you could use the Microsoft 365 applications. You had to use the web versions of them, so I don't know.
73
00:12:14.760 --> 00:12:21.240
Bill Sutton: Or the or the traditional licensed office version, that if if you could even get that anymore.
74
00:12:21.240 --> 00:12:26.319
Geremy Meyers: Oh, that's right. That's right. Almost like the retail version. I'm gonna go, put reits. Yeah, yeah.
75
00:12:26.580 --> 00:12:37.009
Geremy Meyers: Yeah. Yeah. So you you had 2 different solutions. By the way, we had a lot of customers deployed in aws right solid platform. That's fine. But there were some caveats to think about.
76
00:12:37.180 --> 00:12:52.960
Geremy Meyers: Last year. Amazon introduced workspaces core, and the idea behind that is, listen! I could still tie in. It's Api driven so I could still tie in Citrix das into it. But I think what Amazon did was they said, hey, look! There's a special space
77
00:12:53.220 --> 00:13:02.439
Geremy Meyers: in Amazon for workspaces. Core workloads your Das platform from being very transparent, you know, even though we have a tremendous integration.
78
00:13:02.580 --> 00:13:20.979
Geremy Meyers: it's open. So if you're a horizon customer, you could use that as well, you know the idea was, we're gonna open this thing up. The big difference, though, is you could bring your own Microsoft licensing, which was a game changer. So now I could deploy Vdi. Now I can deploy the entire Microsoft 365 office suite, and I could use my own licenses.
79
00:13:21.010 --> 00:13:44.179
Geremy Meyers: and Microsoft actually partnered with Amazon on that piece. But it did require you to put your workloads. The very specific location which was the core space different here is now I can use. Ec. 2, I can use my own images. And now this opens up some things like my ability to do image management right? So now I can use machine creation services.
80
00:13:44.410 --> 00:13:52.779
Geremy Meyers: which is insane. So now I have a golden image, and I'm creating desktops off this golden image, which is awesome still get the Microsoft flexibility, which is also awesome and
81
00:13:53.560 --> 00:13:58.110
Geremy Meyers: not persistent desktops, which is, which is great. So I don't.
82
00:13:58.250 --> 00:14:04.160
Geremy Meyers: You know, if I'm comparing this to what a lot of folks are looking at in windows 365. That is a persistent desktop.
83
00:14:04.400 --> 00:14:09.509
Geremy Meyers: Hard! Stop! Right? It is what it is now. They have a few different options, of course, depending on your persona. Do I need a
84
00:14:10.014 --> 00:14:14.249
Geremy Meyers: a high end version? Do I need an entry level version? There's some resources there, but
85
00:14:15.040 --> 00:14:28.049
Geremy Meyers: it's a persistent desktop, regardless. This is, you can still do your persistent desktops. But this opens up some cost savings around doing. You know, easier management for sure. But I can do non persistent. So if I have a thousand users.
86
00:14:28.720 --> 00:14:31.129
Geremy Meyers: maybe you only have 500 of these right? So
87
00:14:31.920 --> 00:14:34.845
Geremy Meyers: it's a big difference in terms of how you
88
00:14:35.460 --> 00:14:38.390
Geremy Meyers: you know how you how you account for the cost here.
89
00:14:38.390 --> 00:14:44.889
Bill Sutton: Yeah, I know. A couple several months ago, Jeremy, we were looking at this for a client, and the client wanted.
90
00:14:45.560 --> 00:15:04.057
Bill Sutton: They wanted non persistent, and we at the time Workspaces Core really only supported a persistent image. You couldn't build. Mcs wasn't a wasn't a thing yet, and I was advised to wait. and sure enough, here we are a few months later, and
91
00:15:04.460 --> 00:15:04.880
Geremy Meyers: Is over.
92
00:15:04.880 --> 00:15:26.480
Bill Sutton: Yeah, the waiting is paid off. So I will be going back to that customer now, because they ended up pausing it. To say, this is available. This is available to you. Because that was obviously a a blocker for them the inability to manage the image and and those sorts of things. So that's really the the key, or at least a big part of the key of this new offering.
93
00:15:27.740 --> 00:15:28.870
Geremy Meyers: Yeah. I still have questions.
94
00:15:29.910 --> 00:15:38.220
Todd Smith: So I think the other, I think the other key here is that it really is talking to our overall approach towards a hybrid
95
00:15:38.450 --> 00:15:48.339
Todd Smith: multi cloud environment, right where we understand that customers are going to be using aws, they're going to be using azure. They're going to be using a variety of other
96
00:15:49.150 --> 00:15:55.120
Todd Smith: resource locations. Right? And this is just a yet another extension upon that approach
97
00:15:55.320 --> 00:15:58.340
Todd Smith: for us to make sure that you know customers aren't
98
00:15:58.540 --> 00:16:01.019
Todd Smith: kind of forced into one solution or another.
99
00:16:02.400 --> 00:16:03.010
Bill Sutton: Right.
100
00:16:05.230 --> 00:16:10.420
Geremy Meyers: So out of the gate, you you got Mcs, the operating systems that are supported
101
00:16:10.610 --> 00:16:17.369
Geremy Meyers: windows 11. So this is bringing your own license, Todd. Why aren't we doing windows? 10 I? I don't see that one on the list.
102
00:16:19.180 --> 00:16:20.560
Todd Smith: Interesting question.
103
00:16:21.290 --> 00:16:25.240
Geremy Meyers: Maybe maybe it's the end of life. So there's a there's a there's a plug for.
104
00:16:25.240 --> 00:16:28.069
Bill Sutton: Life is forthcoming. So probably that's probably why.
105
00:16:28.590 --> 00:16:34.541
Geremy Meyers: There's there's the plug for the end of life but windows, server. So we have a lot of customers who are leveraging windows. Server, simply from
106
00:16:34.990 --> 00:16:39.349
Geremy Meyers: you know, from a but actually, this is a really important point. So
107
00:16:40.160 --> 00:16:46.369
Geremy Meyers: we talk about Avd, when we're talking about doing this in azure and a lot of times. It's because we have a multi-session. OS,
108
00:16:46.510 --> 00:16:50.490
Geremy Meyers: we want to deploy. We can do windows 11 multi session in azure. We can't do that
109
00:16:50.590 --> 00:16:55.689
Geremy Meyers: in aws right. That's still that that will still be a thing. So if you need multi-session
110
00:16:55.840 --> 00:16:59.460
Geremy Meyers: post, that will be. That'll be a windows server. But of course we also support
111
00:16:59.740 --> 00:17:04.609
Geremy Meyers: Linux as well. I'm seeing that a lot, more especially from the Dev space so Ubuntu and and Debian.
112
00:17:05.140 --> 00:17:09.129
Geremy Meyers: which are, think they have the same tree at some point.
113
00:17:10.700 --> 00:17:33.660
Bill Sutton: Yeah. Another another thing with this which almost goes without saying. But I think it it's important to mention is that when you leverage like just Amazon Workspaces, not Workspaces, core or core managed instances. You're using a a general protocol to access that when you're leveraging workspaces core with Citrix or core, managed instances with Citrix, which is what we're talking about here.
114
00:17:33.730 --> 00:17:55.900
Bill Sutton: You're getting all that goodness and that rich history of the Hdx Slash Ica protocol. So all of the functionality as a citrix administrator from a policy engine standpoint, from the standpoint of being able to accelerate and offload certain types of content. All that goodness that we've come to expect and and use over the years is available to you
115
00:17:56.690 --> 00:18:09.219
Bill Sutton: in this environment, just as it would be if it were, in another cloud or another on or on Prem environment and managed by Citrix. So you're installing the Vda on these guys, which is enabling that kind of connection right?
116
00:18:10.470 --> 00:18:17.519
Geremy Meyers: Yup. And you know what I think we talked about this last week, which was, it's pretty common to have a very distributed
117
00:18:17.650 --> 00:18:42.639
Geremy Meyers: environment. So historically, 2 different data centers. Fine. Now, all of a sudden, you've got this new use case in the cloud you spun up, which is fine. Now you've got. Maybe your workspaces core, you know resources you want to spin up like, how do you have a single point of management? Right? So, director, monitor, studio configuration. You know. I can do that across clouds, across managed instances.
118
00:18:42.850 --> 00:18:45.939
Geremy Meyers: from a single spot which is a which is a pretty big deal.
119
00:18:47.480 --> 00:18:57.220
Todd Smith: It's not only that, but you also have the tools to measure what productivity looks like or what what reliability and what the overall user experience
120
00:18:57.410 --> 00:19:09.579
Todd Smith: looks like when you start adding in things like Uber agent, which doesn't matter where you're what resources you're pulling from. It still looks at it from a user perspective what their experience is like, what their security looks like.
121
00:19:09.800 --> 00:19:16.980
Todd Smith: And now, all of a sudden, you're not having to go to 15 different consoles to gather that information or have to pull back
122
00:19:17.330 --> 00:19:20.349
Todd Smith: and look at it from a from a metadata perspective.
123
00:19:21.540 --> 00:19:36.810
Bill Sutton: Yeah. And obviously, some of the other things that come with this again, it almost goes without saying, is you? You get to leverage all the traditional citrix capabilities like brokering and management performance, monitoring, etc, and and administrators that are familiar with the
124
00:19:37.490 --> 00:20:05.779
Bill Sutton: with the citrix admin console or studio. It's the same just like like you like, Jeremy was saying. You might have some workloads on Prem. You might have some workloads here in in workspaces. Core managed instances. You might have some in another cloud, but they can all be managed centrally monitored centrally. You're not having. You're not creating pockets of environments that have to be. You have different people managing, or you have different behavior in terms of how you access it and how you function within it.
125
00:20:08.380 --> 00:20:18.409
Geremy Meyers: Yeah, the one thing I also think is interesting about this. So we have a lot of customers who come to any sort of vdi application sort of any eec solution
126
00:20:18.520 --> 00:20:21.180
Geremy Meyers: is identity right? What am I.
127
00:20:21.180 --> 00:20:21.740
Bill Sutton: Good point.
128
00:20:21.740 --> 00:20:25.079
Geremy Meyers: Logging in with like, what identity am I using?
129
00:20:25.890 --> 00:20:28.160
Geremy Meyers: The Citrix solution supports
130
00:20:28.310 --> 00:20:35.400
Geremy Meyers: a pretty good mix, you know. For instance, it's not uncommon for us to see Octa, and we see azure id or intra id, I should say.
131
00:20:35.979 --> 00:20:44.289
Geremy Meyers: You know quite a bit. Now, what's interesting about this solution is not only obviously we support Ad, but not only do we support intra
132
00:20:44.630 --> 00:20:48.050
Geremy Meyers: id is a authentication mechanism.
133
00:20:48.380 --> 00:21:02.390
Geremy Meyers: Even these machines that sit in aws will support intra hybrid joined as well. So, for instance, customers are looking to manage especially their persistent desktops with like intune. Some other solution like that requires, you know, intra id as a part of that
134
00:21:02.660 --> 00:21:05.590
Geremy Meyers: salsa supports hybrid joint instances.
135
00:21:06.840 --> 00:21:13.833
Bill Sutton: Oh, cool! Yep, alright! So there's some other elements in this
136
00:21:14.310 --> 00:21:20.469
Bill Sutton: this blog that talk about complexity and costs. So we don't talk a little bit about costs
137
00:21:20.690 --> 00:21:22.110
Bill Sutton: associated with this.
138
00:21:25.010 --> 00:21:33.229
Geremy Meyers: I mean, I think the biggest one. And I think we kind of hit on this one is we're not giving everyone potentially. We're not giving everyone
139
00:21:33.470 --> 00:21:36.849
Geremy Meyers: persistent desktops, right? So you know.
140
00:21:37.460 --> 00:21:42.850
Geremy Meyers: you know, you asked me a week ago. Everyone was getting persistent desktop. We may have just cut that cost in half, because now we can do
141
00:21:43.245 --> 00:21:54.380
Geremy Meyers: you know, Mcs provision, non persistent desktop. So as opposed to one to one, maybe we're one to 2. Maybe we're one to 5. Who knows? That depends on your workflows. But you know, I think there's some immediate cost savings there.
142
00:21:54.490 --> 00:21:56.929
Geremy Meyers: in addition to I think we have
143
00:21:57.060 --> 00:22:07.409
Geremy Meyers: probably a more flexible array of image types that we can leverage. So when we think about, how do we size these Amis? You know we got a lot of options now.
144
00:22:08.360 --> 00:22:31.319
Bill Sutton: Yeah, I found an article for on on this topic from Aws, that that listed kind of the various instance instance types, and it was significantly more than what I've seen in the past. So clearly this this off. There's a lot more available to administrators and organizations. In terms of building out different types of workloads, whether they be traditional task worker or knowledge worker workloads or all the way up to and including
145
00:22:31.720 --> 00:22:44.150
Bill Sutton: non persistent workloads for things like CAD and Cam, or or high high resolution audio video leveraging gpus, so that capability is available to customers through the solution as well. Right.
146
00:22:44.880 --> 00:22:48.030
Todd Smith: Yeah. And I think that I think that's a critical point, Bill, is that you've got.
147
00:22:48.880 --> 00:22:52.710
Todd Smith: You know, it's not a on or off right
148
00:22:52.710 --> 00:23:02.080
Todd Smith: binary switch, right? This is something that if you understand the personas, and you understand what the requirements are for each of those personas you can then build.
149
00:23:02.360 --> 00:23:03.470
Todd Smith: and a
150
00:23:03.660 --> 00:23:14.889
Todd Smith: image in your catalog, or or or a configuration within your catalog to match that persona which means you're going to be able to to really dial in exactly what the user is going to need
151
00:23:15.130 --> 00:23:21.510
Todd Smith: when they're going to need it, and how frequently they're going to have access to it. That's going to help maintain your costs
152
00:23:21.890 --> 00:23:25.479
Todd Smith: considerably more than just building a 1. Size fits all.
153
00:23:25.750 --> 00:23:27.670
Todd Smith: and try to try to solve it that way.
154
00:23:27.670 --> 00:23:28.960
Bill Sutton: Yeah. Yeah.
155
00:23:29.590 --> 00:23:33.696
Bill Sutton: So the way I see it, this is just another example of Citrix's commitment to
156
00:23:34.020 --> 00:24:01.139
Bill Sutton: to expanding the ecosystem of players you've always had the ability, like you said earlier on Jeremy, to build environments in aws. But by leveraging this, workspaces, workspaces, core managed instances. It just expands the family of of capabilities. And just another example of Citrix, you know, Citrix, focusing on meeting, like they used to say, or still say, meeting you where you are in the cloud journey, whether that's, you know, on, on prem environment, with a
157
00:24:01.310 --> 00:24:09.100
Bill Sutton: fail over to the cloud, or it's active workloads in the cloud or multiple clouds. Just another example of expanding that out here. Wouldn't you agree.
158
00:24:09.640 --> 00:24:10.659
Geremy Meyers: I would agree.
159
00:24:10.930 --> 00:24:17.709
Geremy Meyers: I would agree. Yeah, the other thing I learned today is Amazon, as you might imagine. Very excited about
160
00:24:18.180 --> 00:24:29.570
Geremy Meyers: this new version, this new change as well. And if you are interested in doing a Poc of this technology, there might be some Poc resources available
161
00:24:30.025 --> 00:24:41.030
Geremy Meyers: to you for and from a from an Amazon compute perspective, even from a workspaces. Core perspective. So I would say, reach out to reach out to integra, reach out to your ats just
162
00:24:41.400 --> 00:24:44.070
Geremy Meyers: to figure out and talk through what those options are.
163
00:24:44.070 --> 00:24:44.650
Bill Sutton: Yeah.
164
00:24:45.210 --> 00:24:58.878
Bill Sutton: Yeah. And another thing I'll say is, we, we actually have one of these that is in progress, or about to be in progress with a large company leveraging the funding programs that Citrix has available to customers.
165
00:24:59.500 --> 00:25:13.459
Bill Sutton: to do workspaces. It was originally workspaces core. It will probably pivot now to a part of it being managed. Instances, I would imagine, from the customers requirements, so I I certainly expect it to
166
00:25:13.690 --> 00:25:29.049
Bill Sutton: to flip a little bit towards this, but bottom line is that there is funding available for customers that want to do things like this and other things. Just reach out to your ats or and or Zintegra. We can help you with that. Any final thoughts on this topic. Guys, I think we've
167
00:25:29.170 --> 00:25:31.319
Bill Sutton: we've gotten through it all, or most of it.
168
00:25:33.830 --> 00:25:38.649
Todd Smith: I think the big thing is that you know the flexibility and the understanding that there's
169
00:25:38.820 --> 00:25:43.119
Todd Smith: a lot of customers and a lot of users are move, migrating towards
170
00:25:43.600 --> 00:25:46.609
Todd Smith: better capabilities that are readily available.
171
00:25:47.279 --> 00:26:06.060
Todd Smith: To do things like leverage hgx to do the High End graphics, workloads, leveraging a lot of the adjacent compute power that's required for doing things like AI, and especially things like generative AI, or supporting a variety of different
172
00:26:06.980 --> 00:26:14.680
Todd Smith: high end, high value, use cases that oftentimes with that high end high value came high priced.
173
00:26:15.070 --> 00:26:24.690
Todd Smith: and really, looking at it from a perspective of How do we manage costs? How do we deliver the best experience to the user? And, more importantly, how do we make sure that we're getting what we're paying for?
174
00:26:27.440 --> 00:26:28.540
Bill Sutton: Absolutely
175
00:26:29.700 --> 00:26:38.959
Bill Sutton: so. What I would say is at the bottom of the blog article. There is some a reference to documents and to a deployment guide on tech zone. So for those of you listening that are interested, take a look at that.
176
00:26:39.070 --> 00:27:00.109
Bill Sutton: You need help. We can. We can certainly step in and help as you need be as need be. I think this primary article is just workspaces core, but setting it up from a Das perspective is probably the same or very similar. And I'm sure there'll be some updates to this if they haven't already been made relative to workspaces. Core managed instances, Jeremy, any final thoughts.
177
00:27:01.620 --> 00:27:11.499
Geremy Meyers: You know. The last thing I'll tell you is the one thing I think we forgot to hit on when it comes to cost management is we have a lot of customers who do have commits
178
00:27:12.030 --> 00:27:33.990
Geremy Meyers: with Amazon for compute. And to that point, you know, Amazon has the concept of aws savings plans. So if you're willing to commit to certain amount of of compute, you actually get a better deal on compute as well. So yeah, I would say, reach out to your reach, out this integra, reach out to your Amazon rep. If you got one to talk through where that plays into this as well, because
179
00:27:34.330 --> 00:27:47.879
Geremy Meyers: don't play retail when you could pay discount. Right? So you know, if you know, you're gonna have spending in aws, and you know about what it's gonna be a month. You can probably get a better deal on what that compute looks like if you commit to it. So
180
00:27:49.540 --> 00:27:51.250
Geremy Meyers: great. That was my last bit. Yeah.
181
00:27:51.250 --> 00:27:59.650
Bill Sutton: Great thanks. Alright! That's it for today, guys. Thanks for your participation. And we'll see everybody listening next time.
182
00:28:00.560 --> 00:28:01.370
Geremy Meyers: All right.
183
00:28:01.370 --> 00:28:01.800
Todd Smith: Thank you.
184
00:28:01.800 --> 00:28:02.420
Geremy Meyers: Guys next week.
185
00:28:02.420 --> 00:28:03.210
Bill Sutton: Oh, inner.