I’ve said this before, and I’ll say it again – if you are on the Citrix Long Term Service Release (LTSR) track, you’ve most likely been missing out on a lot of great features. But I get it; there are many valid reasons for choosing this path, including extended support. The good news is that Citrix Virtual Apps and Desktops 2402 LTSR is now available, and you can now take advantage of all the great features and enhancements made available over the last couple of years.
This post is focused exclusively on our high-definition experience (HDX) capabilities. More specifically, the key HDX features and enhancements that we’ve introduced since the last LTSR (2203) was released. If you are still using Citrix Virtual Apps and Desktops 1912 LTSR, you should also take a look at my other post that talks about key features released between Citrix Virtual Apps and Desktops 1912 LTSR and Citrix Virtual Apps and Desktops 2203 LTSR.
Host: Andy Whiteside
Co-host: Bill Sutton
I’ve said this before, and I’ll say it again – if you are on the Citrix Long Term Service Release (LTSR) track, you’ve most likely been missing out on a lot of great features. But I get it; there are many valid reasons for choosing this path, including extended support. The good news is that Citrix Virtual Apps and Desktops 2402 LTSR is now available, and you can now take advantage of all the great features and enhancements made available over the last couple of years.
This post is focused exclusively on our high-definition experience (HDX) capabilities. More specifically, the key HDX features and enhancements that we’ve introduced since the last LTSR (2203) was released. If you are still using Citrix Virtual Apps and Desktops 1912 LTSR, you should also take a look at my other post that talks about key features released between Citrix Virtual Apps and Desktops 1912 LTSR and Citrix Virtual Apps and Desktops 2203 LTSR.
Host: Andy Whiteside
Co-host: Bill Sutton
WEBVTT
1
00:00:02.290 --> 00:00:21.150
Andy Whiteside: Hello, everyone! Welcome to episode 1 60 of the Citrix session. I'm your host, Andy Whiteside. Today is April April 20, s 2024. Quick commercial time. Zintra is a partner that really focuses on end user compute technologies. We call it the modern Workspace practice. Here. Citrix is a big part of that.
2
00:00:21.470 --> 00:00:38.279
Andy Whiteside: And if you are currently working with the platform, or want to be working with the platform, or, you know, trying to integrate the platform with something like Microsoft, Avd. Or Amazon Aws or Google Cloud. We are definitely the partner to help you. I've got with me Bill Sutton Bill runs the modern Workspace practice Bill. How are you.
3
00:00:38.280 --> 00:00:40.709
Bill Sutton: I'm doing well today, Andy. Thank you.
4
00:00:41.020 --> 00:00:48.809
Andy Whiteside: I'm I'm excited, and then we'll jump right into it. I'm excited about the topic you brought, because we get to talk about hdx. You know the brooms from home depot.
5
00:00:49.050 --> 00:00:51.029
Bill Sutton: Right exactly, or the trash bags.
6
00:00:51.030 --> 00:01:08.497
Andy Whiteside: No, I'm joking. I'm picking slightly because I do wanna highlight the acronym Hdx. High definition experience from Citrix. It is very, very misleading how a lot of people talk about Hdx. And today we're gonna review a blog from Miguel Contreras, and it's what's new with Hdx in
7
00:01:08.840 --> 00:01:25.049
Andy Whiteside: the 2402 ltsr, long term service release. We talk about long term service releases a lot and that is all about high definition, user experience. That is not necessarily the protocol which is part of it. What a lot of us older guys call Ica protocol
8
00:01:25.367 --> 00:01:34.879
Andy Whiteside: independent computing architecture. Protocol what Citrix is famous, for which, by the way, has a different, had a different meaning in the beginning. I think they changed it.
9
00:01:35.488 --> 00:01:39.509
Andy Whiteside: Bill, do you know what that is. You know what Ica originally originally stood for.
10
00:01:39.510 --> 00:01:41.449
Bill Sutton: Independent computing, architecture.
11
00:01:41.450 --> 00:01:43.030
Andy Whiteside: That that's actually not true. I don't think that's.
12
00:01:43.030 --> 00:01:44.340
Bill Sutton: That's not true. Okay.
13
00:01:44.340 --> 00:01:45.859
Andy Whiteside: Something before that
14
00:01:46.030 --> 00:01:53.119
Andy Whiteside: I'll have to look it up. I I knew it the other day, and I I can't remember it now. There was something before that, and they changed it. I'll look into it.
15
00:01:53.601 --> 00:02:16.400
Andy Whiteside: But nonetheless, it's not just the protocol. It's lots of things. And now that they have a new long term service release. We thought it would be good to talk about more of those items, Bill. Anything specific around the concept of hdx. The look. It's a marketing term, just like it is a home depot. It's a marketing term to help articulate these things. We're gonna dive into.
16
00:02:16.400 --> 00:02:33.350
Bill Sutton: Yeah, I mean it, was it what? It is a marketing term that was basically brought about a number of years ago. I remember when they announced it when they started adding some of the really big key features, particularly around H. 2, 64, acceleration. So the video encoding and decoding
17
00:02:34.002 --> 00:02:48.637
Bill Sutton: they modified the the name. They didn't really modify it, they added on Hdx as a as a high definition experience, and they have continued to innovate and develop on top of that stack since then, significantly. And we'll highlight some of that today.
18
00:02:49.620 --> 00:02:59.820
Andy Whiteside: So it's it's interesting. They start the first or Miguel starts the first section with security. You know, as we talk about user experience. To me it comes down to
19
00:02:59.820 --> 00:03:20.590
Andy Whiteside: to 2 things, of course, just usability in general, but user experience and security and depending on who you're talking to in the space. Whether it's a security guy, whether it's a a desktop user experience guy, they'll usually lead with whatever one they think's most important. And here we're talking about security first, and it's a Tls 1.3 support.
20
00:03:21.240 --> 00:03:31.613
Bill Sutton: Yeah, exactly. And this is, you know, like, like you said under the security banner, and it discusses a lot of things that are that are enhanced to to enhance from a security perspective
21
00:03:31.930 --> 00:03:51.491
Bill Sutton: with respect to the traffic that's being that's being set across the wire. So lots of enhancements to, you know, virtual channel, virtual channel supports for wild cards, environment, variables, and and a lot of enhancements in the logging side of things to help secure the data that's in transit.
22
00:03:52.230 --> 00:04:05.890
Andy Whiteside: I mean at at a minimum. You can look at Citrix, which I do as a very big security play. But when you go to the typical thing. People talk about security, and that's that communication effort being highly encrypted and hard to correct.
23
00:04:07.250 --> 00:04:13.049
Andy Whiteside: Next, it talks about the universal print server also supports Tls, 1.3
24
00:04:13.417 --> 00:04:16.630
Andy Whiteside: virtual channel list enhancements. That's the next real topic.
25
00:04:17.019 --> 00:04:24.319
Bill Sutton: Yeah, you know, this is really just about being able to. If you use custom virtual channels in the environment.
26
00:04:24.617 --> 00:04:48.119
Bill Sutton: Then they simplify the configuration and management of the feature, and it discusses. I mentioned this just a second ago. Support for wild cards. When you're telling which processes you want to be part of that virtual channel? You can use wild cards, environment, variables, and then you can set the level of logging associated with those those custom virtual channels. We don't see that that much, but I know that there are some folks that use
27
00:04:48.119 --> 00:04:56.759
Bill Sutton: custom virtual channels for certain types of telephony or voice. But I I in in my my path. I haven't seen it. That much.
28
00:04:56.760 --> 00:05:00.464
Andy Whiteside: Yeah, it's not all that common. You hopefully don't have to ever do that. But if you did
29
00:05:01.140 --> 00:05:07.040
Andy Whiteside: wanna make sure you can support it, and it's secure it log settings. Next topic.
30
00:05:09.970 --> 00:05:22.040
Bill Sutton: Yeah, this again is where they where you could set the level of logging associated with the virtually custom virtual channels as well as throttling periods for the events that are listed in the logs.
31
00:05:23.120 --> 00:05:31.709
Andy Whiteside: Okay, so we're through with the networking. I'm sorry the security stuff now to to networking transport of those packets. This is where it gets well
32
00:05:31.990 --> 00:05:44.950
Andy Whiteside: for the more technical it gets a little sexier. For other people. They might not be so interested. But first one is enhanced ed congestion control. Ed, maybe to start with what that acronym even means.
33
00:05:44.950 --> 00:06:02.640
Bill Sutton: Oh, gosh! I think you're gonna call me on that enlighten data transport or enhanced data transport. I don't remember which I think it was. It was originally called enlightened, which I thought was interesting. This is what what is often referred to. You're looking it up here, enlightened with, believe it or not. I've remembered it.
34
00:06:03.240 --> 00:06:08.120
Andy Whiteside: You gotta write what's currently because it enhances what I was what it was originally called. I believe.
35
00:06:08.120 --> 00:06:33.109
Bill Sutton: Yeah could be but I guess technically, now it is, or it is enlightened. Nevertheless. This, this is what some folks know is and I don't know what this acronym stand for. But Dtls, that's a a protocol that you've run on your typically on your net scalar on the gateway service. And this is really about responsiveness it leverages udp and they've enhanced this a good bit to to
36
00:06:33.110 --> 00:06:42.486
Bill Sutton: to reflect roughly a 5 x improvement and transfer and they've got a separate blog associated with this, where you can see metrics that compare the old and the new.
37
00:06:43.110 --> 00:07:12.819
Andy Whiteside: You know, I was thinking about this literally. The other day I was driving from Point A to Point B, and the and the roads were empty on the way there, and busy on the way back you got latency latency latency, no matter how busy it is or not. And then and then you have the the bandwidth, which is how wide the roads are. And then you have the congestion control. You know, Citrix is doing some really amazing things with Ed using Udp and falling back to Tcp when necessary, and then turning around and optimizing the Udp is what we're really talking about in this case.
38
00:07:13.440 --> 00:07:14.900
Bill Sutton: Yeah, exactly.
39
00:07:15.970 --> 00:07:18.350
Andy Whiteside: Next section is a loss tolerant mode.
40
00:07:18.640 --> 00:07:42.124
Bill Sutton: Yeah, so th, this is enhancements to primarily to the 2 bullets below that Andy which are audio and graphics. And this is enhancements to the ed protocol to to help with real time traffic and networks that are that are challenging. So like for audio, for example that allows you to maintain a high quality experience, even in poor network environments. By by
41
00:07:42.460 --> 00:07:55.730
Bill Sutton: leveraging losses. So you might see you might see high, you'll see high quality experience and and less dropped packets and things of that nature, because we're leveraging E, we're leveraging Ed, which leverages Udp.
42
00:07:55.920 --> 00:08:10.980
Andy Whiteside: Yeah, well, what's so interesting around the the security as well. But the user experience section of this is, you will be judged on the worst possible moment and the worst possible user experience. When a user uses it. Happily for days and days on end, no issue.
43
00:08:11.190 --> 00:08:25.315
Andy Whiteside: they don't turn around send you love letters. It's the minute doesn't work. They automatically qualify everything as bad. And so it's super important that you gotta be prepared for the worst possible scenarios which, by the way, the worst possible scenario is packet loss, total.
44
00:08:26.270 --> 00:08:34.700
Andy Whiteside: but with Udp it does a good job of even packet loss to the best it can to the best ability can, knowing that the you know bad scenarios are coming.
45
00:08:35.130 --> 00:08:58.549
Bill Sutton: Yeah. And the next one they're lost tolerant mode for graphics very similar. But here you can set you could define latency and loss thresholds. And there's a graph. There's a video in here that actually shows it. And it's actually pretty pretty cool. If you get a chance. If the listeners get a chance, go out to the blog and look at that video. It really demonstrates particularly when you're dealing with high resolution graphics how you can.
46
00:08:58.550 --> 00:09:10.080
Bill Sutton: You can maintain the interactivity of the like. If you're trying to rotate an image, you can maintain the activity even when the the network conditions are degraded or or poor.
47
00:09:10.080 --> 00:09:13.280
Andy Whiteside: And billing. To the best of my knowledge, this stuff's just turned on these days.
48
00:09:13.280 --> 00:09:14.210
Bill Sutton: Yes, it is.
49
00:09:14.210 --> 00:09:23.940
Andy Whiteside: So awesome, would wouldn't you love, when you were an admin or a consultant to be able to have this stuff just turned on, instead of having to go and try to, you know, figure out and test to whether you needed to turn it on.
50
00:09:23.940 --> 00:09:25.409
Bill Sutton: Exactly. Yeah.
51
00:09:26.740 --> 00:09:28.340
Andy Whiteside: Next one is enhanced compression.
52
00:09:28.340 --> 00:09:53.359
Bill Sutton: Yeah. So compression has always been a part of the part of the the delivery method. We've always tried to compress the data stream. Basically. What Citrix is saying here is they've increased it. By, they've increased the compression which enables you to reduce the amount of bandwidth required by about 15%. So they've reduced they've increased the compression by about 15%. So you should be able to get better performance over lower bandwidth connections.
53
00:09:53.920 --> 00:10:04.499
Andy Whiteside: I. I like this part of the conversation because we're in a world where Microsoft is doing a lot with Avd. And Rdp. To try to get better. Citrix isn't just standing around waiting on them to catch up.
54
00:10:04.809 --> 00:10:31.420
Andy Whiteside: Citrix is continuing to make the Hdx protocol ica better at the same time. Which creates this. You know this race condition. A lot of people are moving to Microsoft, Abd. Some people are moving to Citrix on top of Abd. You know, azure virtual desktops, that Citrix value is still there, and continues to improve itself, and prepares you for that. You know that moment in time when things get bad and you need the best possible protocol to handle it
55
00:10:32.816 --> 00:10:36.410
Andy Whiteside: new platforms for virtual loop back. I have no idea what this is.
56
00:10:36.410 --> 00:10:59.159
Bill Sutton: Yeah, this one. I was trying to remember this. I I've used this before, but it has been a long time. This was taken out of the product for a while, but was still available, I think, in the native operating system. So the issue was with multi user session hosts you can now use it on 2019 server and 2022 server within hdx. I think this this had to do with
57
00:10:59.515 --> 00:11:29.170
Bill Sutton: assigning an IP or a private IP to a session for certain types of licensing requirements, I'd have to go back and look but I believe that's what it was something along those lines and it was available cause. I remember using it in some of the early versions. I mean, this goes back to Andy to, I think. Metaph. So we're talking, you know. Windows NT. 4 maybe windows early windows 2,000. So it was available then, but I think they pulled it out of the product at some point, and and looks like it's back.
58
00:11:30.406 --> 00:11:32.339
Andy Whiteside: Next bullet is rendezvous version.
59
00:11:32.690 --> 00:12:01.090
Bill Sutton: Yeah. So rendezvous is basically the the capability of the Vda running on the endpoint to communicate directly with the control plane rather than going through the delivery controller itself. I'm sorry rather than going through the cloud connector itself. You can optimize your connection path so that it goes directly back to the to the delivery controller up. And then, once the user establishes a session, it's actually directly between the user and the Vda
60
00:12:01.446 --> 00:12:11.079
Bill Sutton: and that's what version 2 enables is that direct connection between the Users device and the Vd and the Vda. And they've they've they've improved that
61
00:12:11.180 --> 00:12:14.599
Bill Sutton: that that connection, path process. In this latest version
62
00:12:14.630 --> 00:12:15.700
Bill Sutton: do things.
63
00:12:15.930 --> 00:12:32.519
Andy Whiteside: Alright. Next talks about the next section is around graphics. I need to talk about this. But I wanna set it up when when you say graphics, does that mean high definition? Graphics? Does that mean just graphics for day to day use cases? Or is there some place where there's a that's murky as to which one you're talking about, and how relevant it is.
64
00:12:32.520 --> 00:12:49.210
Bill Sutton: It gets a little murky to be honest with you. You know. Obviously, if you're talking about really high resolution graphics and Gpus and things of that nature. It's gonna leverage a lot of these same things. It's just going to be more potentially more efficient with really high graphics needs because you're able to offload it from the CPU to the Gpu.
65
00:12:50.570 --> 00:12:55.220
Andy Whiteside: And that's a that's a key. Part of the conversation is having that
66
00:12:55.280 --> 00:13:20.870
Andy Whiteside: capability to have Gpus first of all, and to have cost effective CPU and Gpu resources where you're not running as lean as possible. I was with a customer this weekend. The conversation said they were, you know, moving to Microsoft azure for hosting all their desktop workloads. But every time they needed just the slightest bit of improvement and performance increase, it was like an act of Congress to get that approved, because it, you know, would run the bill up across the scale of how many desktops they had.
67
00:13:20.870 --> 00:13:30.879
Bill Sutton: Exactly. Yeah. And that and an important point here when it comes to, I know this is not necessarily in this article. When it comes to Gpus. A lot of folks don't realize you don't have to have.
68
00:13:31.100 --> 00:13:54.379
Bill Sutton: you know, massive like autocad workloads to justify Gpus Gpus are used on endpoints all the time for basic Powerpoint transitions. Perhaps some excel calculations. Things of that nature adobe, you know, some of the adobe suites. You'd leverage them as well. So having them even for knowledge worker, knowledge worker roles are are important to make the performance really good.
69
00:13:54.510 --> 00:13:55.200
Bill Sutton: Him.
70
00:13:55.200 --> 00:13:59.770
Andy Whiteside: Yeah, for sure. Maybe even task workers, just for snappier screens.
71
00:13:59.770 --> 00:14:00.650
Bill Sutton: Maybe yes.
72
00:14:00.650 --> 00:14:01.260
Andy Whiteside: Yeah.
73
00:14:01.460 --> 00:14:05.060
Andy Whiteside: Alright. Next section says, automatic video codec selection.
74
00:14:05.360 --> 00:14:28.481
Bill Sutton: Yeah, this is AV one. I haven't heard a lot about this, but this is a newer protocol or newer method of delivering images as compared to H. 264, which has been around a long time in 2 65, which is been around a few years. So this essentially is just a higher compression and quality protocol as compared to them. And there's a video here that that shows them side by side. It's pretty slick as well.
75
00:14:29.100 --> 00:14:32.329
Bill Sutton: and there are some details in the docs on how to take advantage of this.
76
00:14:33.540 --> 00:14:48.650
Andy Whiteside: Adaptive refresh rate man, refresh rate. I I know that's almost silly to be talking about to a normal PC person. But when you're delivering this stuff across a network instead of a little wire that goes from a card to a monitor. Yeah, you gotta understand where this what this means.
77
00:14:48.650 --> 00:14:56.479
Bill Sutton: Yeah, this one in the one right before which is automatic video codec selection, they kind of become like the easy buttons. They're turned on automatically.
78
00:14:57.071 --> 00:15:21.218
Bill Sutton: There really isn't anything for an administrator to do. I mean, you can tweak it if you want to. But the majority of users or administrators are gonna leverage these technologies. Out of the box, and advance our automatic video codec selection. Is essentially where it picks the codec that's needed, based on the workload automatically for you. So Citrix actually calls it in the article The Easy Button. And it does the same thing with a
79
00:15:21.520 --> 00:15:26.860
Bill Sutton: adaptive refresh rate. It adjusts automatically based on what's optimal for the session.
80
00:15:27.010 --> 00:15:34.650
Andy Whiteside: I mean again, that's so nice to have these days versus trying to predict it. And just, you know, going with lowest common denominator
81
00:15:35.410 --> 00:15:36.649
Andy Whiteside: like we had to
82
00:15:37.788 --> 00:15:43.540
Andy Whiteside: h HEVC. How do you say? The acronym, I know, has a name.
83
00:15:43.540 --> 00:15:46.830
Bill Sutton: I don't know what that is. To be honest with you, I mean I know what it.
84
00:15:46.830 --> 00:15:49.327
Andy Whiteside: Vic. I think it's a Vic or something.
85
00:15:49.640 --> 00:15:50.040
Bill Sutton: Something like.
86
00:15:50.040 --> 00:15:56.570
Andy Whiteside: Epic. Epic 4, 4, 4. Visually lossless, with hardware, encoding.
87
00:15:57.270 --> 00:16:16.381
Bill Sutton: Yeah, I think this is about those that those things that need the highest graphic fidelity. With the lowest CPU impact. And there's some details on enabling this in an article on Citrix's website. But this is just again, another example of Citrix's commitment to improving the graphics fidelity of the workloads that are delivered via the Vda.
88
00:16:17.596 --> 00:16:21.859
Andy Whiteside: Enhance Bill to lost lists, not Lossy, but lost lists.
89
00:16:22.330 --> 00:16:40.989
Bill Sutton: Yeah, this is the the built, the lossless functionality. That that they've had for years, which is essentially where you're. You're an images pops up on the screen quickly, but then it starts to build the image out as you move around, or as you wait a second or so or start interacting with it. It snaps to pixel perfect images.
90
00:16:41.300 --> 00:16:48.957
Bill Sutton: and this is especially this build the loss. This is especially beneficial. For 3D graphics use cases.
91
00:16:49.340 --> 00:16:58.369
Andy Whiteside: Yeah for. And you know, human being necessarily doesn't necessarily care what it looks like as you're moving it around the screen. We want to see what looks like in sharp, clear image when you stop.
92
00:16:58.770 --> 00:16:59.490
Andy Whiteside: Yeah.
93
00:17:00.296 --> 00:17:10.220
Andy Whiteside: next one is virtual display layout per monitor. We're we're an interesting world. I don't know if you have dual monitors these days or not, or if you have one great big one, but you gotta be prepared for both scenarios.
94
00:17:10.220 --> 00:17:19.332
Bill Sutton: Yeah, I've got 2 and they're they're aging, but they're they still work. This is interesting cause they came out with this virtual display layout
95
00:17:19.670 --> 00:17:42.319
Bill Sutton: a few years ago, where you could actually carve up the display a a big display into 4 pieces. You might remember that, and but one of the downsides was you had 2 monitors. You couldn't stretch them across there. And I think they've they. Now they're basically allowing you to create virtual monitors if you will, and spread it across all the monitors. I haven't tried this, but I'm now very interested in spinning up 200402. To try it.
96
00:17:42.680 --> 00:17:50.190
Andy Whiteside: So you have that. Who? So you could have 2 big monitors? But that person that likes to have multi monitors could have 8 monitors spread across those 2 big ones.
97
00:17:50.190 --> 00:17:59.080
Bill Sutton: Yeah, they'd be small. But you could do that or you could split each of those 2 monitors into 2 virtual monitors. So you'd effectively have 4.
98
00:17:59.080 --> 00:17:59.660
Andy Whiteside: Yeah.
99
00:17:59.780 --> 00:18:02.019
Andy Whiteside: that might make for some happy users out there.
100
00:18:02.020 --> 00:18:03.249
Bill Sutton: Might do it. Yeah.
101
00:18:03.834 --> 00:18:06.170
Andy Whiteside: Citrix, indirect display, driver.
102
00:18:06.590 --> 00:18:09.532
Bill Sutton: Yeah, this is for demanding use cases.
103
00:18:09.930 --> 00:18:13.280
Bill Sutton: gives. You know the best response time. And really.
104
00:18:13.290 --> 00:18:28.720
Bill Sutton: you know, time, sensitive situations. It's now the default, the the default. Excuse me, display driver user. Hdx, I I haven't really seen much with this, but this is a default use case. So it's one of those things that you really don't have to do a whole lot with.
105
00:18:29.640 --> 00:18:57.524
Andy Whiteside: Alright. So I told this. I tell this story all time. Citrix is not just the the back end system delivering that endpoint has to be capable understanding all this magical stuff to you'd be shocked, Tommy Citrix people out there that just underestimate the value of the endpoint the next section talks about endpoint synchronization first section is but cause, by the way, that's where the user is. Gonna ultimately see where the rubber meets the road. It's kinda like tires on a sports car. They better be good tires, or you're not getting the value of the sports car
106
00:18:58.176 --> 00:19:00.880
Andy Whiteside: first one is audio volume, synchronization.
107
00:19:01.300 --> 00:19:06.040
Bill Sutton: Yeah. So this is really something that that it works
108
00:19:06.240 --> 00:19:22.509
Bill Sutton: sometimes. But now it's clearly something that they take, putting some effort into which I'm pleased to see, and that is where you. You might have the volume in your session set at one level on the volume on your endpoint set at a different level. Now they can synchronize them, so that when you move up one up or down the other, one moves
109
00:19:22.510 --> 00:19:47.479
Bill Sutton: the same way, up or down so that you don't have these situations where, you know, you've turned it up all the way on your local machine and and in your session. You've got it turned down, and then you turn it all the way up all the way up, and you get blasted so and then con, and also the next one support for multiple audio devices is related to this. I know I've got this a lot of times. You have. Folks have different audio devices available. You might have your local speakers.
110
00:19:47.480 --> 00:20:07.139
Bill Sutton: You might have speakers in your monitor. You might have a headset, maybe headphones. And you can now define. You can now choose which one you want to use in your session. If it's something other than the client default device device. So you can use. You can even use different use different devices with different applications inside the session.
111
00:20:07.140 --> 00:20:11.650
Bill Sutton: This is actually might actually be better than what we get on a regular workstation.
112
00:20:11.650 --> 00:20:21.970
Andy Whiteside: You know, Bill, this all kind of sounds like what should be table stakes. And it's just great example of how the how this all just keeps moving forward and forward. And how takes companies like Citrix, that are focused on the space to keep up.
113
00:20:22.130 --> 00:20:22.949
Bill Sutton: Yeah, exactly.
114
00:20:24.118 --> 00:20:32.280
Andy Whiteside: Alright. Next section here. Last section before the conclusion is multimedia collaboration. First one is multiple webcam resolutions.
115
00:20:32.550 --> 00:20:50.609
Bill Sutton: So yeah, historically, webcam resolutions. There was usually one or 2 that were supported when you use a webcam inside the session. And often those weren't the real high def resolutions. Well, now they've supported. They're now supporting the high def resolutions. And there's deep more details in related articles.
116
00:20:51.080 --> 00:20:53.870
Andy Whiteside: And then finally, teams app sharing for custom apps.
117
00:20:53.870 --> 00:21:15.920
Bill Sutton: This is interesting. Apparently there are there. I wasn't aware of this, because I haven't run into it. If you're using teams, and you have, like a Java based application. Apparently you couldn't share that in your meeting. Now, with the new optimized teams through Citrix you have the ability to share a Java based application and other homegrown apps directly from within teams in a Vda.
118
00:21:16.450 --> 00:21:33.620
Andy Whiteside: And I think that what that really highlights is you got you got Microsoft. You got the apps that are typically installed. You've got Citrix being the Middleware delivery layer. And then you have all this stuff that has to come together in applications beyond. You know what every company has. It might be a one off Java. Based application. Gotta be prepared for that stuff, too.
119
00:21:33.620 --> 00:21:35.310
Bill Sutton: Yes, you do. Yes, we do.
120
00:21:35.310 --> 00:21:42.930
Andy Whiteside: Hey, Bill, I'm gonna ask you a question. Kinda summarize this, as it relates to. You know, Citrix and Zinta, how much time
121
00:21:42.940 --> 00:21:45.650
Andy Whiteside: did you prep for that discussion? We just had.
122
00:21:46.007 --> 00:21:51.370
Bill Sutton: Less than 5 min, and some of it was being done while you were talking
123
00:21:51.420 --> 00:21:53.879
Bill Sutton: before you moved on to the next topic. So.
124
00:21:53.880 --> 00:22:08.190
Andy Whiteside: And and what that highlights is you don't have to, you know. Go out and research all this. Citrix did a great job writing a blog. You. You've lived this stuff for you know, the last 6 months and the last 20 years. It's what we do is what you do. That's why people should work with us.
125
00:22:08.190 --> 00:22:31.470
Bill Sutton: And and an important point is that sometimes you and I, I mean, I think you would agree. We learn things on by doing these podcasts? Not, you know, we. We've got a lot of foundation. But we might discover something that we weren't aware of or weren't fully aware of and what do we do with that? I take it back and try to understand it, or get with my team and talk about it. So that we can bring it to customers when it's appropriate.
126
00:22:31.640 --> 00:22:47.040
Andy Whiteside: And that's the value we bring. Right. We're we're a partner who eats, sleeps, breathe this stuff we can't keep up. So the partners that don't eat, sleep, and breathe this stuff, and customers who may have a really smart guy. But you you just can't. And if you don't have the history of all this stuff. That's the first starting point.
127
00:22:47.040 --> 00:22:47.980
Bill Sutton: Exactly.
128
00:22:48.590 --> 00:22:57.039
Andy Whiteside: Alright, Bill. Well, thank you for jumping on and doing this, we look forward to more conversations with what Citrix is doing, and us adding value to it along the way.
129
00:22:57.430 --> 00:22:58.810
Bill Sutton: Exactly. Thanks, Andy.