It’s no secret that Citrix continues to innovate and deliver new capabilities to make your environments more flexible, increase deployment speed, and improve end user experiences. Citrix is also fully committed to meeting organizations where they are in their deployment journeys, and the Citrix Universal subscription is only our first step in this journey.
With the move toward Citrix Universal subscription, we are not only adding features to our Citrix DaaS cloud service, but we are continuing to add features and capabilities to on-premises deployments.
That’s why we are excited to announce the release of Citrix Virtual Apps and Desktops 7 2305! This IT-managed current release delivers new end user enhancements, security capabilities, and much more that we will discuss below.
As we evolve and gain input from our customers, we are building more functionality inside of four major categories. We have broken out our feature updates into each of these groups:
Our approach goes beyond the traditional cloud and on-prem categorizations, providing a comprehensive overview of the capabilities offered by the Citrix platform. Let’s dive right into these developments!
Host: Andy Whiteside
Co-host: Bill Sutton
Co-host: Geremy Meyers
It’s no secret that Citrix continues to innovate and deliver new capabilities to make your environments more flexible, increase deployment speed, and improve end user experiences. Citrix is also fully committed to meeting organizations where they are in their deployment journeys, and the Citrix Universal subscription is only our first step in this journey.
With the move toward Citrix Universal subscription, we are not only adding features to our Citrix DaaS cloud service, but we are continuing to add features and capabilities to on-premises deployments.
That’s why we are excited to announce the release of Citrix Virtual Apps and Desktops 7 2305! This IT-managed current release delivers new end user enhancements, security capabilities, and much more that we will discuss below.
As we evolve and gain input from our customers, we are building more functionality inside of four major categories. We have broken out our feature updates into each of these groups:
Our approach goes beyond the traditional cloud and on-prem categorizations, providing a comprehensive overview of the capabilities offered by the Citrix platform. Let’s dive right into these developments!
Host: Andy Whiteside
Co-host: Bill Sutton
Co-host: Geremy Meyers
WEBVTT
1
00:00:02.940 --> 00:00:05.870
Andy Whiteside: Hello! Welcome to Episode 136 of
2
00:00:06.100 --> 00:00:12.060
Andy Whiteside: citric session. I had to pause for a second. There, I've been going for 2 weeks, and nothing is coming back easily.
3
00:00:12.120 --> 00:00:14.510
Andy Whiteside: I've got Bill sudden with you. Bill is going
4
00:00:14.770 --> 00:00:19.059
Bill Sutton: going. Well, Andy. yeah, we missed you, but glad to be back.
5
00:00:19.480 --> 00:00:31.769
Andy Whiteside: Yeah, that's good. The European vacation, almost just like the movie you're be on vacation. It was amazing to see other cultures. And I used, I used to citric session a couple of times on the plane and
6
00:00:32.100 --> 00:00:37.260
Andy Whiteside: from a hotel one time it was neat to see it work just like I expected, you know, just from somewhere else.
7
00:00:37.880 --> 00:00:38.880
Bill Sutton: That's cool.
8
00:00:39.690 --> 00:00:43.060
Andy Whiteside: You have you been on your summer adventure yet?
9
00:00:43.230 --> 00:00:51.210
Bill Sutton: my summer venture will probably be a cruise in September, but I'm sure we'll end up doing something shorter term
10
00:00:51.370 --> 00:00:59.020
Bill Sutton: with family at some point we don't really have anything scheduled per se. But we did go to Boston a couple of weeks ago for
11
00:00:59.450 --> 00:01:05.300
Bill Sutton: engagement party for a nice, and spent some time at Penway, which was nice, even though they lost.
12
00:01:05.760 --> 00:01:08.149
Andy Whiteside: Now, how can you get away with the
13
00:01:08.740 --> 00:01:25.030
Bill Sutton: trip in September? You have kids that'll just be out of school, is it? You know it'll just be a. It's a long weekend type thing, so we'll pull them out. It's a we have a couple of milestone birthdays this year, so we're going to celebrate them on a cruise going to cocoa and Baham and Nassau.
14
00:01:26.090 --> 00:01:28.920
Geremy Meyers: Okay, so that means you're is this a.
15
00:01:28.950 --> 00:01:33.160
Bill Sutton: So Disney crews, are you doing?
16
00:01:33.180 --> 00:01:47.930
Geremy Meyers: Oh, okay, okay, that's what we did for honeymoon, is we? That's what the name sounds familiar with the cocoa. I I look so forward to being able to vacation in September and October, and not have to work around the school calendar. Not be there with the masses.
17
00:01:49.380 --> 00:01:55.590
Andy Whiteside: Well, that was the voice of Jeremy Myers. Jeremy is with us. Jeremy is part of cloud software group. Jeremy, how's it going.
18
00:01:55.660 --> 00:02:14.630
Geremy Meyers: Bonjour? No. Was it the right language? By the way, I don't. That's might be the only Italian I know that is, that is Italian. Yes, and as somebody took a bunch of French in high school and college, it took me a couple of days to get used to saying Italian phrases, and then by that time I was in France, and then I was screwing up for to undo that
19
00:02:15.050 --> 00:02:23.140
Andy Whiteside: I will say that I think about 10% of what I do paid off, and then I it it would really be good. And I I know this going into it. But
20
00:02:23.260 --> 00:02:27.990
Andy Whiteside: if you could go to a place like France after taking French for a couple of years, and really just
21
00:02:28.000 --> 00:02:32.469
Andy Whiteside: try to get get by. It would be really cool to see how much of it you could do.
22
00:02:33.650 --> 00:02:35.210
Geremy Meyers: Yeah, yeah.
23
00:02:35.290 --> 00:02:51.680
Geremy Meyers: that would be fun. I know random bits and pieces of the Spanish I took, so if I went to Spain one day and tried to bring that with me, I can describe all the parts of a house several different colors. I think I can count to well, over a hundred, but that wouldn't get me very far.
24
00:02:52.040 --> 00:03:00.629
Bill Sutton: I really know is to tell them that I don't speak French so
25
00:03:01.590 --> 00:03:09.539
Andy Whiteside: well in Spanish to be a weird one, because it's there's so many different dialects of it, and you almost offend somebody just by using their own one.
26
00:03:10.210 --> 00:03:14.279
Andy Whiteside: that should get something you picked up off yeah, us TV or something.
27
00:03:14.420 --> 00:03:20.889
Geremy Meyers: That's all right. I I think Bill got away going up to Boston and bringing that Southern accent with him. So
28
00:03:22.220 --> 00:03:30.549
Andy Whiteside: it works. So one or both of you guys were at the Citrus conference last week. I don't know I was.
29
00:03:30.820 --> 00:03:39.180
Geremy Meyers: I was yeah. So this was our internal mid-year kick off which, as in tech response or so I got a chance to sit down with quite a few folks.
30
00:03:39.370 --> 00:03:48.090
Andy Whiteside: I heard there were only a few partners there. We were one of them. Jeremy, any publicly discussable things from last week?
31
00:03:48.530 --> 00:04:04.540
Geremy Meyers: No, so it wasn't a public announcement kind of event. So we've done that in years past where we've had a sales kick off. We've invited partners, and this is even when we've had synergy. That's been kind of mid year, if you will. But this is more of a I mean, since Covid
32
00:04:04.560 --> 00:04:15.429
Geremy Meyers: kicked off 2 or 3 years ago, you know, we hadn't had a chance as an organization to get together. So I think that was that was a big piece of it is just getting getting the team together, which you know was really good for me.
33
00:04:15.920 --> 00:04:21.809
Geremy Meyers: certainly. So there's folks who have been on my team, not no one, or on my team that I've not seen in person since.
34
00:04:22.019 --> 00:04:31.230
Geremy Meyers: You know all that kicked off. So I mean, that was a big part of it. it's the first chance for the Tipco side of the business to get in the same room as well. So you know, you know, having
35
00:04:31.260 --> 00:04:45.199
Geremy Meyers: the general manager of the typical business. In fact, there's 2 or 3 different business units there. you got a sense of kind of what Tipco does a spot fire does. So here's some products that I'm still sort of wrapping my head around. But you know, there wasn't really an announcement or anything like that.
36
00:04:45.520 --> 00:05:11.220
Geremy Meyers: and so help me under. So Tipco and this the partners are the 2 owners behind Cloud Software group. And I'm saying that right So Tipco is one of the business units much like Citrix as a business unit. And that scalar is a business unit. In fact, there are 2 or 3 different technologies that came over from Tipco. So there is a tip of be you? There's also a separate product called spot fire, which is its own. Be you?
37
00:05:11.380 --> 00:05:22.530
Geremy Meyers: It's it's a data visualization platform. I guess you could say so almost along the lines of like. maybe like a power bi, or you know, tableau, that sort of thing. But
38
00:05:22.710 --> 00:05:37.320
Geremy Meyers: vista is private equity. and they actually own on top of group. Yeah. So Vista and Elliot are part owners. Okay, yeah. Again, I've been for 2 weeks. It's like, I've forgotten everything on new
39
00:05:37.470 --> 00:05:44.590
Andy Whiteside: back at it. all right. So we got a blog that we're going to review today. Let me share my screen.
40
00:05:45.730 --> 00:05:48.099
Andy Whiteside: and it is kinda
41
00:05:49.200 --> 00:05:56.220
Andy Whiteside: back to I don't know. I won't say old school, but it's you know what we what we're best at, which is talking about the tech.
42
00:05:56.290 --> 00:06:08.460
Andy Whiteside: And this is by Monica. Grimmer has been a good friend of ours on the podcast several times, and it's what's new with citrix. C. Bad, 2305, and cloud update. So, Jeremy, we're talking briefly, going into this. This is
43
00:06:08.810 --> 00:06:29.339
Geremy Meyers: this is both the on-premises version as well as the dazz version that we're gonna intermingle and talk through as part of this.
44
00:06:30.060 --> 00:06:40.219
Andy Whiteside: and it does highlight in paragraph 2 universal subscription. This is all. I guess, by default, these days under the universal subscription model. More than likely.
45
00:06:41.190 --> 00:07:03.639
Geremy Meyers: well, so the universal subscription includes both as and on premium. So you've got some customers that might just have dazz, so that would just be the cloud service. We got some folks who would have an on premises license as well. So that's see bad citrix virtual apps. That sort of thing the universal license gives you both. So you know, in the past we've had customers who were traditionally on prem.
46
00:07:04.000 --> 00:07:06.949
Geremy Meyers: They transition to the cloud. You know they
47
00:07:07.050 --> 00:07:34.340
Geremy Meyers: had something called hybrid rights in the past which gave them the ability to continue to use on-prem, and as at the same time. That's kind of gone away. It's just universal licensing. And then the other thing. If you were a a fresh customer, a green field customer, if you will. That did known any sort of citrix There was no concept of hybrid rights for you. You just had to buy one of the other. Now you can buy universal if you want but you know I think universal is geared towards folks who have some sort of hybrid.
48
00:07:34.590 --> 00:07:44.960
Geremy Meyers: You know, mentality, I mean, which, by the way, you can do it as, or even on premium. But you know, just understanding that you can deploy in a couple of different ways is where universal really makes sense.
49
00:07:45.410 --> 00:07:47.530
Andy Whiteside: It's it's all starting to come back.
50
00:07:47.900 --> 00:07:54.570
Geremy Meyers: And I think what we're talking about today is the the continued investment by Citrix as part of
51
00:07:55.010 --> 00:08:03.569
Andy Whiteside: cloud software group and the investment in both the on-premises and cloud control plane solutions.
52
00:08:03.870 --> 00:08:22.910
Geremy Meyers: Yeah, which is really important, because I think lot of customers, even partners. got the impression that we were moving away from on from and only focusing in on the cloud. If I'm being very transparent, I probably help perpetuate that message, you know, and talking about how features would come to the cloud first, and eventually make them on Prem if they made it at all.
53
00:08:23.040 --> 00:08:24.670
Geremy Meyers: But I think
54
00:08:25.130 --> 00:08:35.490
Geremy Meyers: what we've started to understand is just the landscape of it is very hybrid. We've got. Folks who are going to keep an on primitive prim environment need to connect it to a cloud. So
55
00:08:35.730 --> 00:08:43.509
Geremy Meyers: yeah, we're we're finding releases. Make it to the on-prem. See? Bad environment. In fact, we're starting to see it happen fairly quick. So
56
00:08:43.640 --> 00:08:51.350
Geremy Meyers: you know, not only some of the things we'll talk about today. But you know, we we've touched on this and other podcasts, you know, secure private access, has only ever been a cloud service
57
00:08:51.370 --> 00:09:03.380
Andy Whiteside: that has made its way back on Prem. And that's a pretty big deal. Is is that because all this stuff was running as a Vm. Or containers in the cloud, or were they true? True native services? Is the fact that it was
58
00:09:03.390 --> 00:09:09.070
Andy Whiteside: kind of the same machines up in the cloud is that what's made it portable to on from so quick.
59
00:09:09.140 --> 00:09:34.079
Geremy Meyers: You know it's a good question I don't know so I don't know if it's a good thing that I don't know or bad thing, but you know for me it's always just been a service, right? And so I'm sure I could have gone to some of the developers and cloud Ops team and try to understand what's actually happening under the hood. But you know for me it's always just been a service, and maybe originally it was with some vms. But I'm not sure if that's still the case or not, honestly.
60
00:09:34.420 --> 00:09:54.009
Andy Whiteside: But I guess it can still be just a service. You just you're gonna need to know you're gonna run that I don't know a windows box in many cases, or is it appliances, or both? which pieces, like all of it.
61
00:09:54.080 --> 00:09:59.039
Andy Whiteside: I I just have to assume. That's because there's some type of service running
62
00:09:59.270 --> 00:10:03.449
Andy Whiteside: in many cases on a windows. Well with the server of some time.
63
00:10:04.130 --> 00:10:13.069
Geremy Meyers: So, with the understanding that I don't know how it works, I gotta assume. Probably I mean, it would take a large engineering effort, I would think, to take something that we might be
64
00:10:13.380 --> 00:10:22.940
Geremy Meyers: maybe cloud native and then port it to a windows platform. I'm not sure but yeah, that's a really good point. Now, there are some things that are appliance base that are on premium. So, for instance,
65
00:10:23.010 --> 00:10:36.510
Geremy Meyers: I'm thinking, the license server. I think we still make a like an appliance version of that. Maybe we don't. I can go back and look. Most folks have always deployed the the windows version and the Andy. You always made a really good point around supporting Linux, as most folks didn't understand Linux. So we
66
00:10:36.610 --> 00:10:44.829
Geremy Meyers: you know it would be tough to support as a administrator a new platform. You didn't quite have your hands around, but
67
00:10:45.390 --> 00:10:47.819
Geremy Meyers: but even spa, that is
68
00:10:48.220 --> 00:10:59.160
Geremy Meyers: that is actually a part of the C, that product. I don't know what that looks like in the cloud, but secure private access on Prem is a little bit net scalar a little bit storefront a little bit, you know. Delivery controller
69
00:10:59.240 --> 00:11:04.000
Andy Whiteside: and I have to imagine that's probably not what it is in the cloud. But I don't know either.
70
00:11:04.080 --> 00:11:05.469
Andy Whiteside: Yeah, I'd love to.
71
00:11:05.610 --> 00:11:11.259
Geremy Meyers: I guess the point here is, you don't need to know. but someone like me is curious and wants to know.
72
00:11:11.750 --> 00:11:40.369
Geremy Meyers: So you know, we talked to customers all the time where they they they do pick our brains about what this looks like in the clouds, because there's a lot of resiliency built into these cloud services, and they want to know exactly well how many Vdcs you get. How many of this that meal you got and it, to be perfectly honest, I don't know. I mean, I know we have 2 different we have this whole process of canaries in the cloud meeting. We've got an entire see? Bad that's running in the cloud per customer. Then we also have another one altogether.
73
00:11:40.470 --> 00:11:52.730
Geremy Meyers: it's so sort of like the backup version, if you will. And so whenever it's time to upgrade the cloud release, it always happens in the canary version before it happens in the so which is an interesting.
74
00:11:52.780 --> 00:11:58.500
Geremy Meyers: you know, sort of devops model, right? So you know, just knowing that that's how that works.
75
00:11:58.690 --> 00:12:21.450
Geremy Meyers: I don't know. I forgot what the question was at this point, just to understand how the cloud services. Oh, yeah, yeah. So like folks who want to know. But to be fair, Andy, and you're a perfect example of this is once you know how it works on Prem. You can't help but start asking the questions, how does this work in the cloud? Whereas we do have some customers who have never experienced an on print version they just want. It's just a service. It is what it is. it's almost like the burden of too much knowledge. You just kind of want to know.
76
00:12:22.050 --> 00:12:23.000
Andy Whiteside: Yeah.
77
00:12:23.470 --> 00:12:36.850
Andy Whiteside: Well, let's Let's talk about what has been released with the 2305. So 2,005 for C bad would be the on-premise is your 23 month. Oh, 5 may so may may 23, for C. Bad
78
00:12:36.850 --> 00:12:53.859
Andy Whiteside: The 4 bullets listed here. Operational it of N. It. Efficiencies workload and device, flexibility, security and compliance and employee experience. Let's dig into those starting with the improving operational and it efficiencies.
79
00:12:54.050 --> 00:12:56.949
Andy Whiteside: I mean, there's quite a few of those you wanna
80
00:12:57.510 --> 00:13:23.670
Bill Sutton: Bill, you want to take the first one that talks about auto scaling and how you've seen that work in the cloud, and what you would expect to see how this for on purposes. Yeah, I mean, the biggest advantage of auto scaling from my perspective is in the cloud is particularly where the not always, but where the workloads are also running in the cloud, the ability to be able to scale down scale up to dynamically or on demand and the ability to when you're like in a in a hyper scale or a public cloud.
81
00:13:23.670 --> 00:13:42.979
Bill Sutton: the ability to when the user is not using the machine to not just turn it off, but to the allocated, and in some cases remove it all entirely to to minimize cost and then the ability obviously to go the other way. If you have a burst to be able to scale up. And it looks like, what they're doing here is bringing a lot of this, those features, similarly to the on-premise world.
82
00:13:43.110 --> 00:13:55.719
Bill Sutton: there where they can. They can dynamically provision machines as needed, and then delete them if they're if they're not being used to allow the customer to provision more. And there's also this concept
83
00:13:55.850 --> 00:14:00.889
Bill Sutton: vertical load balancing, which is kind of we. We've seen this back in the old days, where you would.
84
00:14:00.930 --> 00:14:15.730
Bill Sutton: You would take a a bank of of servers, or perhaps it perhaps, desktop, if you were doing certain things with it, but mostly with servers where you would have the ability to load the server up to its capacity before you start
85
00:14:16.160 --> 00:14:37.379
Bill Sutton: moving the sessions to another server, so what they call vertical load balancing versus horizontal, which is the traditional, you know, session on server. A. Then the next session goes to be. The next session goes to C, etc. This way, you know all the the first 20 sessions go on one server, and then the 20 first session goes on another server, assuming that's what your scaling model is.
86
00:14:38.480 --> 00:14:47.730
Geremy Meyers: that. That's what this is. So I mean, the first thing you think of is, why does this matter on? Prem So when you think about it, most
87
00:14:47.850 --> 00:15:03.150
Geremy Meyers: most hardware is a sunk cost. You buy a stack of servers. Guess what I mean. Granted, I haven't bought servers in a while, so I'm not sure if there's a subscription model to servers anymore. But bear with me here, and just with the understanding of a back by a stack of hardware. It's on, Prem. Do I need to worry about auto scaling?
88
00:15:03.170 --> 00:15:17.159
Geremy Meyers: Well, the answer is probably not for your on-prem, and unless you guys tell me otherwise, however, what was added to the on-prem version, here is the ability to provision to a cloud. So now I can create a connector with my on-prem, you know. Control plane
89
00:15:17.160 --> 00:15:38.259
Geremy Meyers: right? I can build a connector out to azure Aws or Gcp. Or whatever. Right now, all of a sudden, I do care about auto provisioning and auto-scaling and things like that, because obviously I'm trying to manage consumption in the cloud. So at first glance, when I first saw this feature, I go. Why does this even matter? What does matter? Because now I can provision out to a cloud, and I do want to manage that. But you're absolutely right, Andy.
90
00:15:38.570 --> 00:15:40.540
Geremy Meyers: this is what this is.
91
00:15:40.960 --> 00:15:41.680
Yup.
92
00:15:42.780 --> 00:15:52.869
Andy Whiteside: yeah, I think I want to dig in that a little bit more. So you have these some costs where you buy hardware. And are you saying that we can now.
93
00:15:53.290 --> 00:16:02.740
Andy Whiteside: Well, I mean, look, we've always I get it to some cost, but there's always a cost to it. Whether or not we really paid attention to it as much as we do in the cloud has always been the
94
00:16:02.790 --> 00:16:05.199
Andy Whiteside: well. Probably it wasn't the question that should have been
95
00:16:06.930 --> 00:16:07.890
Geremy Meyers: so.
96
00:16:08.060 --> 00:16:14.589
Geremy Meyers: I mean, even though it's a some cost. The the idea that I mean. Listen, I can power manage on that hardware
97
00:16:14.690 --> 00:16:24.900
Geremy Meyers: on prem today. And that's fine. I mean, that's always been there, you know. I think the auto scaling I mean, it's the dynamic for provisioning the idea that you could go out and actually create
98
00:16:25.030 --> 00:16:32.800
Geremy Meyers: and delete machines based on some, some, some controls. and the other piece is just being able to vertically load balance. So
99
00:16:33.100 --> 00:16:46.149
Geremy Meyers: you know, how do you want to scale out. Do you want to do it with a larger number of smaller machines? Or, you know, a handful of larger machines? I mean, I think that's a that's a great design question to have with yourself when you're building out an environment.
100
00:16:46.290 --> 00:16:57.430
Geremy Meyers: But you know we can do that with with on-prem, and that's fine. But typically the hardware I'm gonna say it's already paid for. But you know, we've not really cared about it as much
101
00:16:57.510 --> 00:17:03.510
Geremy Meyers: on Prem, outside of just making sure we had enough vms running for the load that we're throwing at it.
102
00:17:03.570 --> 00:17:09.190
Geremy Meyers: but I think where this is really important is when you're provisioning out to a cloud, it's really what it is. But
103
00:17:09.530 --> 00:17:20.309
Andy Whiteside: so the the image that comes to my mind is, you care you? You you care about fuel efficiency. But no one. You get to stop and spend money and buy more gas versus having to plan for an electric car trip.
104
00:17:21.530 --> 00:17:25.889
Geremy Meyers: Right? Yeah, it's a good way to look at it
105
00:17:26.339 --> 00:17:27.900
Andy Whiteside: now. You gotta care more.
106
00:17:28.359 --> 00:17:37.399
Geremy Meyers: I I should probably should have always cared. But I didn't care, because, you know I was from all practical purposes. It's already paid for. It's all you can eat, whereas
107
00:17:37.900 --> 00:17:45.729
Geremy Meyers: I mean, listen! If I had to trade, I had to pay for every trip to the buffet. That might be different. But the fact that it's 20 bucks all you can eat I'll just go forward.
108
00:17:45.950 --> 00:17:55.189
Geremy Meyers: Yeah. Maybe it was a terrible analogy. But it's a all right. Next section says you can now create a Pvs catalogs
109
00:17:55.330 --> 00:18:01.979
Andy Whiteside: from Citrix des Studio tech Preview. I guess I don't really know what Citrix as studio tech preview is.
110
00:18:02.210 --> 00:18:08.550
Geremy Meyers: it's the it's the web.
111
00:18:08.760 --> 00:18:14.549
Andy Whiteside: and I guess you plug that in and tell it to talk to your provisioning services, server, and it manages that as well.
112
00:18:16.610 --> 00:18:21.419
Geremy Meyers: I think so. It's tech preview. This link takes you out to a podium forum.
113
00:18:22.310 --> 00:18:26.799
Geremy Meyers: Mcs provision to create the Vms for Pbs, so
114
00:18:26.820 --> 00:18:36.519
Geremy Meyers: it's got to be the target devices is what it is. Let me think about it right? So you know. Obviously, I have to have target devices for Pbs to stream, too.
115
00:18:36.860 --> 00:18:40.899
Geremy Meyers: So Mcs can manage the identity disc cache. And
116
00:18:41.200 --> 00:18:54.340
Bill Sutton: I don't. I don't think this eliminates the Pbs servers, but it allows you to orchestrate. The management of the Pds. Servers from studio, you know, at least in it. I haven't seen it yet, because it's tech preview. But
117
00:18:54.400 --> 00:18:56.909
Bill Sutton: based on just reading this, it's what it looks like.
118
00:18:57.660 --> 00:18:58.370
Andy Whiteside: Okay?
119
00:18:58.680 --> 00:19:13.320
Geremy Meyers: Yeah. Because in the past you would use the the Pvs target device Wizard to go out. And it's talking to your your delivery controllers is talking to, or even the cloud right? Because you do Pbs in the cloud, and then just talking to your Hypervisor, and then it will go out and create
120
00:19:13.720 --> 00:19:24.490
Geremy Meyers: the target devices for you on the Hypervisor and manage the identities and that that sort of thing. But it sounds like. maybe you can do that with Pbs, now, have Pbs create the Vms, the target devices for? Pbs.
121
00:19:24.700 --> 00:19:25.550
Bill Sutton: yeah.
122
00:19:26.660 --> 00:19:35.100
Geremy Meyers: And this takes you out. I haven't clicked the link yet, but this this link takes you out to the The tech preview sites. You can go request it
123
00:19:36.990 --> 00:19:46.970
Andy Whiteside: all right. The next section, the simplifying provisioning with Mcs enhancements. Citrix is bringing machine creation services updates to on-prem Hypervisor
124
00:19:47.970 --> 00:19:50.669
Andy Whiteside: Jeremy, what's that covering?
125
00:19:52.210 --> 00:19:59.830
Geremy Meyers: So, Mac, ad activation is probably the biggest right? So I think historically, it's been entirely
126
00:20:00.070 --> 00:20:03.199
Bill Sutton: km.
127
00:20:03.280 --> 00:20:06.199
Geremy Meyers: yeah. So I mean, Bill, or folks still use them back.
128
00:20:06.470 --> 00:20:16.309
Bill Sutton: We don't know we, don't we? Well, we we run into it, maybe one out of 10 projects. I will. We'll have someone that's a small enough where they're still using Mac.
129
00:20:16.380 --> 00:20:35.950
Bill Sutton: But to to be honest, those smaller ones typically are not even using Mcs. They may just be using a, you know, manually provisioned vms for their session hosts. so we haven't had a a a need for this, but I know there are some that don't want the infrastructure needs of Kms, and
130
00:20:35.950 --> 00:20:53.780
Bill Sutton: they've got Max Keys built into their workflow. So this would make sense for those folks. The other. The other items under this category are mostly kind of a nice to have being able to add descriptions for updates, and then some additional identifiers like tags. for control and tracking purposes.
131
00:20:56.240 --> 00:21:04.080
Andy Whiteside: It just a quick question for you. these last, these things we've been talking about these see? Bad? Does both.
132
00:21:04.370 --> 00:21:15.469
Geremy Meyers: this last one is is is, see that right? So it's it's up based on from Hypervisors is what it is. Actually, you know what? I'll take that back, you know, it's just talking about on from Hypervisors. I don't think
133
00:21:16.350 --> 00:21:26.860
Geremy Meyers: the desk studio tech Preview that would be on pro. No, actually, this is cloud, because when you click the podium link, it takes you to a spot. You have to identify your your cloud tenant. So
134
00:21:27.540 --> 00:21:30.339
Geremy Meyers: the pbs, like, yeah, yeah.
135
00:21:30.770 --> 00:21:44.460
Andy Whiteside: Okay, so the Pvs one is as, yeah from desk studio. Okay, I think it's probably good going forward. Call that out. Okay? So the next one is integrating introducing vda upgrade service.
136
00:21:44.570 --> 00:21:46.229
Andy Whiteside: Is this a
137
00:21:46.630 --> 00:21:50.359
Geremy Meyers: that is a bad or both thing? I think this is
138
00:21:50.460 --> 00:22:01.040
Geremy Meyers: well, so it would be a service in itself. is it only the blog here? Real quick? While we're pulling that piece up.
139
00:22:01.510 --> 00:22:15.989
Geremy Meyers: it's it's for das is what it is. Yeah. So if you if you go out to the if you click into the upgrade service blog So this specifically for dads, and I think it's specifically for probably persistent desktops, considering.
140
00:22:16.010 --> 00:22:29.649
Geremy Meyers: you know, if you did, a non persistent desktop, whatever upgrade happened, it would just get wiped away. But you know, within your persistent desktop, which would probably extend out to remote PC as well. you can schedule vda upgrades of those machines. So.
141
00:22:29.670 --> 00:22:37.470
Geremy Meyers: in fact, it calls that out. It's upgrades to persistent machines. So, being able to not have to push this out with like secm or script it out.
142
00:22:37.620 --> 00:22:45.449
Geremy Meyers: you can actually have the Vda up there. There's a service that runs in the cloud that can push out the update to the Vda.
143
00:22:45.470 --> 00:22:53.390
Geremy Meyers: and you can schedule that as well
144
00:22:53.760 --> 00:22:58.320
Bill Sutton: with with the understanding that you've got no active sessions running. But you schedule it.
145
00:23:00.160 --> 00:23:11.600
Andy Whiteside: you know this is an interesting talk for me. I don't know if I brought up with you guys. But at the I Joe Conference few weeks ago that was one of the the folks in the industry, and they were really pushing the idea of persistence.
146
00:23:11.910 --> 00:23:13.770
Andy Whiteside: Vdi, as
147
00:23:13.910 --> 00:23:24.679
Andy Whiteside: a game changer. And you know the companies that haven't adopted it, or the ones that are holding themselves back when it comes to desktop virtualization strategies. This non persistent world is
148
00:23:24.800 --> 00:23:29.149
Andy Whiteside: has been kind of a detriment overall to the adoption of Vdi. What do you guys think?
149
00:23:30.850 --> 00:23:35.549
Geremy Meyers: I think they both have their place? and I think that
150
00:23:36.470 --> 00:24:05.790
Geremy Meyers: it's really easy, like we live in a little bit of a, we kind of want a black and white solution like, we just want to decide, this is the thing we're gonna go do. So we're gonna go all persistent. Okay, fine, you know. I just want to pick a line to go with it. The idea that most of our consulting engagements, as I've always been. You guys, is integrity. Does this as well as you think through the use cases, and you pick the right delivery mechanism. You go not persistent makes sense for this user group. You know, it's been saying to think that you're gonna put dedicated desktops out for like a simple task worker, right?
151
00:24:05.940 --> 00:24:06.950
Geremy Meyers: But
152
00:24:07.070 --> 00:24:15.560
Geremy Meyers: if that's the mentality is, let's go all in with one delivery model. It's cost more. And if you're okay with that, then share. But there's management overhead. There's.
153
00:24:15.580 --> 00:24:18.479
Geremy Meyers: you know, consumption overhead, things that go along with that. But
154
00:24:18.850 --> 00:24:28.970
Geremy Meyers: you know, if you're looking for the best solution for the best user group, then there's a little upfront energy required to go figure what what that looks like. So I'm up with the opinion that
155
00:24:29.250 --> 00:24:37.970
Geremy Meyers: you know, you kind of pick what makes sense, and you can manage it better. You know you don't want to manage a bunch of persistent desktops, but
156
00:24:38.850 --> 00:25:00.599
Andy Whiteside: but see, that's what they're saying is, go persistent with everybody I'm like, and then just manage it with sccm and manage it with the security postures that you put in place, and I mean. The wildcard for me is always been well, I want reboot to a gold image known good image. I don't want to have to rely on tools to tell me. I want to know that as far as I know, it was sealed up nice and solid, and a reboot away from being clean.
157
00:25:01.660 --> 00:25:04.729
Geremy Meyers: Yeah, maybe we take this offline. I'm kind of curious now who said that?
158
00:25:04.870 --> 00:25:10.200
Andy Whiteside: Oh, it's it's a. It's someone very near and dear to the industry.
159
00:25:10.210 --> 00:25:36.340
Andy Whiteside: Oh, that's interesting. Yeah, it's probably since getting the game there. And the first thing I said was, that can't be right. And then I start thinking about when I was like. Look if I have to choose between Vdi persistent versus not Vdi at all, I guess I'll take Vdi persistent, and that was their argument is that we we got 10% penetration. We could be 70% penetration. And by the way, Microsoft Cloud, PC. Is, you know, not persistent. Excuse me is persistent.
160
00:25:36.540 --> 00:25:41.990
Andy Whiteside: and that's the play there is just here by a bunch of desktops and manage it like you do all the other desktops. Virtual desktops.
161
00:25:42.330 --> 00:26:12.199
Bill Sutton: Yeah, I mean, we've we've had, you know, going on persistent a lot of challenges in the past, where we were in a mature environment where they had a very mature, you know. sccm process for updating desktops, managing them, patching them, etc. And so we we would often fight this battle. Who's gonna manage the desktop, and it's not persistent. Well, your Citrix guys are gonna mention. Well, we want to use Sccm, well, you can use sccm. But you have to do this, this and this. Well, we'd rather just have persistent and manage it the way we've always done it.
162
00:26:12.210 --> 00:26:31.080
Bill Sutton: So that's the challenge that we one of the challenges, the other challenges. A lot of folks. Think, when you do persistent, that you don't really need to do anything else. In other words, you. You need to manage the apps, obviously. But I I often worry about folks that are considering things like full redirection. And and what's in that profile? What happens at that desktop ends up doing.
163
00:26:31.080 --> 00:26:56.630
Bill Sutton: you know, going south completely. Everything goes with it. We still need to to have some consideration or discussion during the design effort where we're establishing those use cases to make sure that we consider the the users data, and where that needs to reside it, should it reside directly on that persistent desktop. Generally, I think the answer is probably no, it needs to be somewhere backed up separately. Not everybody thinks that way which which means they introduce additional risk to to that desktop.
164
00:26:57.950 --> 00:27:10.109
Geremy Meyers: Yeah, I I mean, it's it's a it's a physical PC at that point. I mean, I know it's it's a physical. PC, you're not treated like that which is. Listen I, for for organizations who have run it that way, and they understand that model.
165
00:27:10.160 --> 00:27:11.910
Geremy Meyers: I get it just call smart.
166
00:27:11.970 --> 00:27:23.670
Bill Sutton: Yeah. But with things like on drive, known folders and things like that, we can mitigate the the potential for failure data loss in those environments that we couldn't do in a physical world in the past until now.
167
00:27:24.290 --> 00:27:25.600
Andy Whiteside: So Bill.
168
00:27:26.420 --> 00:27:42.789
Andy Whiteside: going back 10 years ago, it was all, how we're going to solve this, how we're going to solve this now with Fs logics and one drive. And yeah, O, 365. And I mean we. It's pretty much all been sold. How often do you guys run into a project where you know the majority of users can be a non persistent.
169
00:27:44.750 --> 00:28:07.939
Andy Whiteside: say that again, how? How often with all the tools we have these days with whim. And you know, Fs logics, and the fact that your data is going to be, you know, either it's it's going to be somewhere else, not on the machine. And and users shouldn't be installing applications, anyway. How often do you find that customers? What like, what percentage of users really do need a persistent desktop?
170
00:28:08.100 --> 00:28:29.899
Bill Sutton: We've come a long way in the past 10 years with solving the non persistent challenges. Yeah, I mean, we still have a lot that want to do non persistent, it. It's a it's a large percentage that still go non persistent that they the it's the. It's the the kind of the exception where we see persistent most of the time these days. There's still a lot of folks that that want to go non persistent, that are going on persistent.
171
00:28:30.640 --> 00:28:52.960
Bill Sutton: those that that aren't are probably loop using a solution from Microsoft or somebody where it's a fully persistent desktop. And they are willing to take the risk like Jeremy alluded to a minute ago. It's basically a physical PC in the cloud, right? And with all the warts that a physical PC. Has, if you're not managing it properly. But there are some benefits where I can access it from anywhere I can snap every night.
172
00:28:53.210 --> 00:28:55.909
Andy Whiteside: It's it's not
173
00:28:56.190 --> 00:29:07.699
Andy Whiteside: like with somebody. When they said that to me of the day I was like, no, that'd be horrible. Don't do that, and it's starting well, you could snapshot it. You can access it from anywhere. there's all kinds of benefits to it being delivered, not deployed.
174
00:29:07.710 --> 00:29:16.169
Andy Whiteside: And then, if I Microsoft like well, that's good, I'm gonna to deliver it hosted and still manage it with sccm into whatever that's they're winning all the way around that one.
175
00:29:16.300 --> 00:29:29.219
Geremy Meyers: So if I do that model right? So I'm snapshotting it like, what solution am I using to back up? Well, let me ask 2 questions. Number one, am I bothering with profile, management and redirection and those sorts of things, or am I simply relying on like some sort of
176
00:29:29.330 --> 00:29:36.080
Geremy Meyers: backup solution just to snap the whole backup? I mean the whole, the whole desktop. You're just snapping it. You don't even have to back it up. You're just snapping it.
177
00:29:37.230 --> 00:29:43.149
Geremy Meyers: some of the snapshot like at a hypervisor or a cloud level. I got it so I can.
178
00:29:43.260 --> 00:29:59.090
Andy Whiteside: I mean, I've been thinking about a lot. I I when they said that to me I was like, Oh, that's don't do that. We all. We follow these years to get away from that. And then I start thinking, well, you know, it's not necessarily wrong. And if it gets us from 10% saturation to 30. That's still a huge win.
179
00:29:59.550 --> 00:30:12.299
Geremy Meyers: I think. I I think, where my challenge lies is not that it can't be done, but in most instances, when I'm talking to a customer and we're trying to justify it always goes down a cost.
180
00:30:12.410 --> 00:30:32.479
Geremy Meyers: And so trying to cost justify a project. If it's a dedicated desktop, it's the most expensive solution. I mean, we've talked about this Andy Cloud, PC. By the way, it's a dedicated desktop for Microsoft. But it's the most expensive version of the desktop you can get. If you're okay with that, then maybe it's the right solution. So the challenge we have is, most customers are trying to figure out how to make it less expensive.
181
00:30:32.960 --> 00:30:36.810
Geremy Meyers: And if we're talking dedicated to desktop, that is the most expensive solution.
182
00:30:37.200 --> 00:30:38.420
Andy Whiteside: Yup.
183
00:30:38.970 --> 00:30:43.269
Andy Whiteside: that that certainly is a conversation to be had, because now I still got to have an endpoint.
184
00:30:43.580 --> 00:30:45.549
Geremy Meyers: It's probably a PC. Of some type
185
00:30:46.440 --> 00:30:50.729
Andy Whiteside: could be a Byod, but more than likely not. And then I've got to have
186
00:30:51.010 --> 00:30:57.419
Andy Whiteside: You know that thing in the cloud is there enough value? And what that thing in the cloud is to be paying twice plus some
187
00:30:58.700 --> 00:31:01.399
Geremy Meyers: right? Yeah about her dream.
188
00:31:02.730 --> 00:31:17.379
Geremy Meyers: This is completely unrelated. But kids are home for the summer. I don't know if you guys can hear. But I have a madhouse in the other room. So we do. We do the podcast from a, he's in his office. I'm assuming bills at his house
189
00:31:17.510 --> 00:31:23.630
Geremy Meyers: and my my house, and I can hear that sounds like a murder in the next room. So if you guys can't hear it. Then I know my Mike's doing his job.
190
00:31:23.910 --> 00:31:26.320
Bill Sutton: I don't hear anything
191
00:31:27.900 --> 00:31:44.090
Andy Whiteside: alright. next topic here, implementing session launch diagnostics in Citrix dazz monitoring tech preview. So this must be a dazz related. Item Jim, I'm I'm keeping you on the spot for these, because you probably know a little more about them than Bill and I do at this point. What what is this?
192
00:31:44.700 --> 00:31:56.819
Geremy Meyers: Actually, I haven't dug into this one just yet, but I know that between this and I think there's another feature on the Codex side. But you know, one of the challenges we've always had
193
00:31:56.830 --> 00:32:03.749
Geremy Meyers: has been, you know you get that error that says, you know, session didn't launch. And then we're up to trying to figure out what that exactly meant.
194
00:32:03.780 --> 00:32:15.990
Geremy Meyers: it sounds like we're giving the Administrator a little bit more insight into what caused that launch failure than just error code 1,009, or I can't remember what it is. It was, you know, 1011, or something like that.
195
00:32:16.100 --> 00:32:41.379
Bill Sutton: and then it it probably will redirect you out to some documentation, or what the issue might be to resolve. So I've seen this. have you seen it? Yeah, I've seen it recently, and what it, what it, what it did was the user. You know, they would get the error and then be a copy. It was shown air code. Actually, it was like a grid, and then they would allow them to copy it to their clipboard, and they could send it to
196
00:32:41.530 --> 00:32:48.030
Bill Sutton: to us, and we were working on a project, and the customer was seeing issues. So they sent it to us, and we could plug it into
197
00:32:48.060 --> 00:33:03.550
Bill Sutton: the Monitor console, and it will give us a complete history of that session. So it's it kind of links that situation to an actual session and provide some additional detail that then we could go off and use this to to troubleshoot. And actually some of the error codes actually link to
198
00:33:03.850 --> 00:33:17.919
Bill Sutton: articles that can help help us work with the customer to get things resolved. So it was helpful. you know a lot of the articles at the time. They weren't. They weren't out there yet, but at least getting the history was a good source of information to start the troubleshooting effort.
199
00:33:19.020 --> 00:33:23.640
Andy Whiteside: So so the end user gets a dump of some type. You take that and stick it into this
200
00:33:23.960 --> 00:33:29.059
Bill Sutton: service in the Monitor. You just go into the Monitor, and you can look it up in in Citrix
201
00:33:29.120 --> 00:33:38.529
Bill Sutton: das Monitor, which is what we used to call on premises. Director. basically just go in and drop that code in there, and it'll show you the history of that session.
202
00:33:38.600 --> 00:34:03.449
Bill Sutton: and the failures that occurred from an administrative perspective and not a this is not an end user looking at this, of course. and and you can use that to help link to articles, or I think some of them eventually are gonna have steps to help you resolve it. Now, I don't know when we get the 1,001 or the to 1030. Or what have you errors over time? I'm sure that the information will be a lot more helpful than obviously it has been in the past.
203
00:34:03.710 --> 00:34:27.259
Geremy Meyers: Yeah. So I I just popped into monitor real quick. And so normally, if you're a help desk user. Or if you're trying to troubleshoot a session, you know, would normally go in. You can do it. You can click, search and you can look up a user that sort of thing. Now there is an option to search for a transaction. And so if you fill in that transaction, Id. From the from the end user. It sounds like you can get a pretty pretty good detail of what that looks like.
204
00:34:29.050 --> 00:34:34.249
Geremy Meyers: I haven't. I haven't tried this yet. I kind of want to break it so I can get a transaction I didn't work with
205
00:34:34.739 --> 00:34:43.050
Andy Whiteside: in my current role. I never get a chance to that, plus. I usually click it once it fails, and if it does fail, I just click it again, and it works I could see where it would be super powerful.
206
00:34:45.050 --> 00:34:51.420
Andy Whiteside: All right. reduce costs with vda Reclamation service. Tech preview.
207
00:34:51.560 --> 00:35:06.500
Andy Whiteside: All right, Jeremy, what is this Reclamation service? Oh, let me get back to the let me get back to the block. But let me get out of monitor here, leveraging unused virtual resources, huge capability for organizations working to reduce cloud spin.
208
00:35:06.960 --> 00:35:23.409
Geremy Meyers: so it sounds like back in the day as in before this came out. trying to identify vms running in a cloud specifically that go unused. there's a way to identify them. you could script this But now there's a way to automatically tag these.
209
00:35:23.440 --> 00:35:29.899
Geremy Meyers: Then you probably want to script, or at least go in and look for these tag resources and figure out what's not being used. And
210
00:35:30.510 --> 00:35:34.100
Geremy Meyers: and and maybe we're turn those vms off.
211
00:35:34.180 --> 00:35:41.599
Geremy Meyers: So, for instance. this actually takes you out to a different blog post that walks you through.
212
00:35:41.820 --> 00:35:56.229
Geremy Meyers: exactly what this looks like. But you include a tag, maybe call it a an unus Vdi tag and go release them. So let's just say you've got users who have vdi that they haven't logged in for a while. I get this every so often. You know it, Citrix, where
213
00:35:56.670 --> 00:36:02.080
Geremy Meyers: you know, folks have their machines that are are let back, and they go back into the pool because they haven't used them in a while.
214
00:36:02.520 --> 00:36:06.229
Geremy Meyers: Yeah, not me. I've got a lot of things I need to get to internally. But
215
00:36:07.500 --> 00:36:10.720
Andy Whiteside: so, Bill, you see, our customers needing this
216
00:36:11.620 --> 00:36:22.319
Bill Sutton: very large ones. Yes, smaller ones. Probably not. But definitely. The you know, the north 1,000 machines, maybe a little bit less than that and
217
00:36:22.360 --> 00:36:34.449
Bill Sutton: and more. you. You can't really manage those individually at that level at that scale, maybe even low, smaller than that. So this would definitely help those folks to be able to identify machines that aren't being used.
218
00:36:34.480 --> 00:36:38.749
Bill Sutton: And if they're especially if they're running or consuming storage and a hyper scalar.
219
00:36:38.840 --> 00:36:45.090
Bill Sutton: Get them out of there because you're paying for that stuff, you know. I I I'm willing to bet that
220
00:36:45.200 --> 00:36:56.550
Geremy Meyers: You probably don't know you need it until you need it. And so I mean, here's something that you've got machines sitting out there that you probably don't even know that no one are using So basically go out and say, Hey, if this hasn't been touched in the last 30 days.
221
00:36:56.950 --> 00:36:59.040
Bill Sutton: you know this tag it? Yeah.
222
00:36:59.470 --> 00:37:02.530
Geremy Meyers: Now, is this a daz or C bad thing
223
00:37:03.840 --> 00:37:08.729
Geremy Meyers: It could be both here. Yeah, I don't see why not.
224
00:37:08.820 --> 00:37:18.239
Andy Whiteside: Yeah. I mean, I personally adds integrity, I have a non persistent virtual desktop. I use a lot, and then I had a persistent one for a while, and I didn't use it for a while. I was like, I wonder if they know I don't use this anymore?
225
00:37:18.440 --> 00:37:22.520
Geremy Meyers: And this would. That'd be a great example of something.
226
00:37:23.730 --> 00:37:24.590
Andy Whiteside: Yeah.
227
00:37:25.100 --> 00:37:41.980
Andy Whiteside: well, guys, we're at the end of this section. This is probably going to be a multi-part podcast the next topic or next section. It's called delivering workload and device flexibility and let me scan through it. Yeah, it's pretty long. I think we'll wrap up with this one. we'll we'll get tied back and we'll we'll knock this out over the next couple of weeks.
228
00:37:42.290 --> 00:37:58.070
Geremy Meyers: Yeah, the next few sessions are. The next session should be pretty good. We've got some pieces around Google. The marketplace aws! Some azure stuff, and even the I don't know we hit on. It's cloud clusters a few weeks back, but you know we touch on that as well. So should be good.
229
00:37:58.270 --> 00:38:00.520
Andy Whiteside: Yeah, I think for me, this just takes
230
00:38:00.590 --> 00:38:05.100
Andy Whiteside: the evidence that Citrix is continuing to invest in the solutions. And
231
00:38:05.700 --> 00:38:13.290
Andy Whiteside: from a technology perspective, huge hit start on everybody else in the industry. And then there's no, there's no slowing down. There's gonna be more and more that keeps coming.
232
00:38:13.770 --> 00:38:27.109
Geremy Meyers: Yeah, the pace has been pretty quick. You know. What's interesting is, it hasn't necessarily been like, Oh, my gosh! There's this brand new whoppy do. It's just you see, the evolution, the feedback from customers around. You know, we really need this.
233
00:38:27.260 --> 00:38:43.549
Geremy Meyers: you know these small things for sure. So you see, some adjustments around just being able to tag machines that are being used. I mean, that's a big deal, even though it's it feels like a small feature to just the update service. And you know, Pbs, using Mcs provision target devices for Pvs, like, it's a big deal. But
234
00:38:43.630 --> 00:38:58.120
Geremy Meyers: yeah, there's just a lot of nuance here that is really, really interesting to see. And it's coming up pretty quick. Actually.
235
00:38:58.420 --> 00:39:05.750
Geremy Meyers: I mean, listen. I tell my team all the time that I'm one of the biggest chiefs out there, like, I will take a good idea and just expand on it. So
236
00:39:05.770 --> 00:39:21.020
Bill Sutton: I mean, that's just how the industry works. You see what it's kind of good for the goose right there. A lot of the the development, you see, and and the newer players are coming from things that Citrix is done over the years, and others, so you know, turn about fair play right?
237
00:39:21.810 --> 00:39:38.579
Andy Whiteside: Well, it's funny for me, because I go to conferences, and I'll have somebody talk about another player in the space doing something like we didn't even do that for 20 years. I don't know that was in. Have you ever done this with Sit? And I've never used Citrix. Well, no wonder you have no idea that this stuff's been doable for 20 years or 10 years.
238
00:39:38.980 --> 00:39:43.639
Andy Whiteside: All right, guys. Well, thanks. Glad to be back. And we'll knock these out over the next couple of weeks.
239
00:39:44.140 --> 00:39:47.449
Geremy Meyers: Excellent thanks, Bill. Thanks, Andy.