Our last Long Term Service Release (LTSR) was released in 2022, and since then we’ve introduced many new features via our Current Releases (CR). That means 2 years of new features are coming to our newest LTSR. We also know a lot of customers are on our 1912 LTSR, so there are almost 4 years of new features to discover. It is especially important for 1912 customers to begin prepping for an upgrade, as 1912 goes EOL in Dec 2024. Citrix previously announced that our new LTSR will be coming early 2024, which means it’s time to start planning your upgrade!
Host: Andy Whiteside
Co-host: Bill Sutton
Co-host: Philip Sellers
Our last Long Term Service Release (LTSR) was released in 2022, and since then we’ve introduced many new features via our Current Releases (CR). That means 2 years of new features are coming to our newest LTSR. We also know a lot of customers are on our 1912 LTSR, so there are almost 4 years of new features to discover. It is especially important for 1912 customers to begin prepping for an upgrade, as 1912 goes EOL in Dec 2024. Citrix previously announced that our new LTSR will be coming early 2024, which means it’s time to start planning your upgrade!
Host: Andy Whiteside
Co-host: Bill Sutton
Co-host: Philip Sellers
WEBVTT
1
00:00:02.110 --> 00:00:17.180
Andy Whiteside: Hello! Wanna welcome to episode 1 54 of the Citrix session. I'm your host, Andy White side. It's I don't know. It's February twelfth, 2024, and if you're using citrix technologies and not getting what you think you should out of the technology
2
00:00:17.710 --> 00:00:41.669
Andy Whiteside: gifts call reach out to meet through Linkedin reach out to Philip Sellers and Bill Sutton, who are both on the podcast here. We want to help you. We know, there's a lot that goes into end user computing. Bill. If I had to say, the percentage of customers that have either failed or not gotten to their objective in the end. User compute world through your history of, you know, being in the space, what do you think the number is?
3
00:00:42.590 --> 00:00:47.480
Andy Whiteside: They have not gotten into their objective. It's pretty high. Let me give me a number
4
00:00:47.770 --> 00:00:51.220
Bill Sutton: 60%, maybe 50%. 6 out of 10
5
00:00:51.290 --> 00:01:02.450
Andy Whiteside: have a goal, and they don't get there, Philip. II know you've been around the space a long time, too. You've worked for customers that had Citrix in user compute. Did you feel like you guys ever truly
6
00:01:02.580 --> 00:01:04.319
Andy Whiteside: truly succeeded with the product.
7
00:01:04.750 --> 00:01:13.479
Philip Sellers: you know. At times. Yes, but I will say, you know, I inherited more than one struggling deployment. You know it. It.
8
00:01:14.240 --> 00:01:27.530
Philip Sellers: It does take a little bit of art to make some of these things happen. And you need people alongside of you that that really understand it and really understand how to to get the best out of the software.
9
00:01:27.790 --> 00:01:34.790
Andy Whiteside: It would be fair to say that there's a lot of science to it. but it takes art to make it get across the finish line.
10
00:01:35.050 --> 00:01:42.449
Philip Sellers: Yeah, II think that's true. Yeah, there's a lot of things that we probably all know. And then there's a few of us that know
11
00:01:42.570 --> 00:01:58.200
Andy Whiteside: the the art side of it to really make it sing to really make it something special. Yeah. And so, guys, that's the the voice of Bill Sutton, who's with us all the time Bill runs the delivery practice here at Zintigra. Long term in user compute citrix Guy
12
00:01:58.200 --> 00:02:19.429
Andy Whiteside: just got back from the F 5 Conference, where you learn more about, you know, integrations of the 2 and then Philip Sellers, who's leading our what we call modern workspace, practice and Phillip and Bill may be hosting this podcast more without me in the future, as you know, things get busy, and we wanna keep the content flowing. And so that's who those 2 guys are.
13
00:02:19.480 --> 00:02:32.540
Andy Whiteside: We brought a blog today. Let's see the blog we're reviewing today is Citrix, Ltsr, Bill, what is Ltsr stand for long term service release.
14
00:02:32.750 --> 00:02:41.200
Andy Whiteside: plan, upgrade, succeed. Part one. So, Bill, if we're talking about this, there must be a new long-term service release
15
00:02:41.520 --> 00:02:48.060
Bill Sutton: either out or coming out. I guess it's out right it's an early release right now. Hasn't actually been publicly
16
00:02:48.130 --> 00:02:53.189
Bill Sutton: put on the website, at least that not as a Friday.
17
00:02:53.590 --> 00:03:01.940
Andy Whiteside: Okay. So, Ltsr, tell, tell us what lts are in layman's terms means to a citrix customer.
18
00:03:02.010 --> 00:03:30.640
Bill Sutton: Essentially, it means that the that it's it's long term support ability. So typically with a current release. So you have 2 tiers, you have a current release and you have a Ltsr long term service release. The current releases are Re are typically released on about a quarterly or 4 month cadence, and they're supported for about a year and a half or so, 18 months, 18 to 24 months, whereas the long term service release. They're those are released about every 3 years, I think. 2. What is it?
19
00:03:30.830 --> 00:03:43.679
Bill Sutton: 2 years every 2 years or so, and they're typically supported for 5. So it's really giving the customer a well tested well battle worn, if you will. Version of
20
00:03:43.750 --> 00:04:03.560
Andy Whiteside: citrus virtual apps and desktops and supporting it, providing support and maintenance for it for 5 full years. Yeah, hey? And real quick to give em a bland credit for the blogger reviewing. These are her words with our little context added to it. So, Bill, why wouldn't? Why wouldn't everybody just stay on the an Ltsr. If it means it's solid and supported.
21
00:04:03.860 --> 00:04:22.849
Bill Sutton: Well, the Ltsr is is largely fixed in terms of the the feature set when it was released, so they do release cumulative updates for long term service releases but those cumulative updates are typically to integrate bug fixes and not major improvements to the
22
00:04:22.850 --> 00:04:39.280
Bill Sutton: to the core environment. They do that whenever they come out with a new long-term service release they'll bring it up to date, if you will, in terms of feature, set. The current releases, of course, are just what they imply. It's the most current tech at the time they are released, and it's good for about from a support ability perspective for about a year and a half.
23
00:04:39.550 --> 00:05:04.150
Bill Sutton: and and how often you see people staying on Ltsr's because that's their company mandate, or because they have some application that parallel integrates with Citrix, and that makes them stay on. Ltsr, yeah, we there's a lot of customers that do. Ltsr, I expect to see a flood of of migrations this year. Once this is released, and you know the bugs have been worked out. Most folks aren't going to go to this right out again. Some will, but most won't
24
00:05:04.150 --> 00:05:17.279
Bill Sutton: but we see the majority of the customers. Most of the projects we see they go to lps, or we have very few that's that use the current releases. Usually the ones that do crs are those that are smaller.
25
00:05:17.360 --> 00:05:27.150
Andy Whiteside: So, Phil, we were just talking about our management meeting the services demand for our team had kind of waned a little bit for the modern workspace team. But are you expecting to see
26
00:05:27.160 --> 00:05:31.939
Andy Whiteside: plethora of new services coming in from customers that want to move to the latest. Ltsr.
27
00:05:32.280 --> 00:05:39.219
Philip Sellers: yeah, absolutely. I mean, there's a lot of new functionality that has come out in the current releases in between.
28
00:05:39.280 --> 00:06:00.449
Philip Sellers: And you know, one of the other factors. That kind of holds people back is compatibility, or, you know, support ability from their independent service software vendors. So if their Isb software is not certified for the latest current release which a lot of companies don't do. They try to certify their software against these long term releases.
29
00:06:00.790 --> 00:06:10.959
Philip Sellers: You know, that's gonna hold a customer back. So I do think there's a a PIN up demand. That's certainly here. For some of the newer features that are being added in
30
00:06:11.160 --> 00:06:11.920
yeah.
31
00:06:12.290 --> 00:06:20.520
Andy Whiteside: we probably wouldn't be doing it justice. We didn't highlight that. What is it? The 7 dot 15 release? That's the one that officially goes away. Now.
32
00:06:21.350 --> 00:06:29.159
Bill Sutton: it's actually yeah. 7, 15, when it's already gone. End of life, 1912 is coming up.
33
00:06:29.830 --> 00:06:54.510
Bill Sutton: yeah. 1,912 is coming up, 2,203 is still supported. So 1912, you think about that. That typically is the year and month it was released. So that would be the twelfth December of 2,019, so that effectively will be supportability that will end at the end of this year, because that's 5 years hence, and 2,203, which would have been the third month of, or March of 22,02022 that one still supported. But
34
00:06:54.520 --> 00:07:12.949
Bill Sutton: There's a couple of pieces there, you know, some of the operating systems that are supported by that, and they they get into this in the article. But some of the operating systems like 2012 r. 2 no longer supported. So they're in. You'll customers will need to migrate off. If they've got workloads they'll need to figure out how to migrate off those
35
00:07:13.530 --> 00:07:26.180
Bill Sutton: because that that operating system's not supported in our in technically 2,016 went into life in January of last year. So that's also an issue. In in the newest release. So those are some other reasons why folks may
36
00:07:26.260 --> 00:07:38.230
Bill Sutton: may not have moved off of the older Lps. Rs. Because the newer versions require a newer version of the OS. And so they can't really migrate if they're not ready to. Yeah, I can't believe I looked at the
37
00:07:38.480 --> 00:07:46.889
Andy Whiteside: 7 15 as if it was still around. Oh, it is we. We run into it periodically, for sure. Yeah.
38
00:07:47.270 --> 00:07:49.539
Bill Sutton: he's talking to 6, 5. Andy.
39
00:07:49.580 --> 00:07:59.899
Andy Whiteside: Okay, well, that's why it all makes sense for me to say that. I guess we would be doing justice if we might have new listener here. This is the on prem
40
00:07:59.930 --> 00:08:03.249
Andy Whiteside: solution. If you're running. Cvad.
41
00:08:03.270 --> 00:08:26.389
Andy Whiteside: if you're running citrus cloud. Sorry, Citrus Cloud, then this is all. Move. Point to you, the control plane and things upgrade. You just have to upgrade your agents and you keep up to a large degree whether you want to or not. And for the most part you don't have to worry about it. It's dealing a lot of testing done against it, and long as you're not an early early adopter, then you're you're probably in in perfect shape there, and you're getting all the latest features.
42
00:08:27.520 --> 00:08:54.870
Bill Sutton: The, what, what percentage of customers are we seeing that are on prem running Ltsr's or latest releases versus citrus cloud. I'd be curious what those numbers are. It is shifted considerably. A lot of customers have moved to Citrix. They, as now, but we still probably have 30 of our customers that are on premises. Excuse me and the majority of those are larger customers that have more structured environments that
43
00:08:55.010 --> 00:08:56.680
Bill Sutton: that are.
44
00:08:56.720 --> 00:09:13.680
Andy Whiteside: and particularly with older applications that need to be on site. A lot of health care still is on prem so forth. So I'd say, probably at least 30 stab at this last paragraph here, where they're talking about things you need to think about going into a an lts or upgrade.
45
00:09:13.730 --> 00:09:15.690
Philip Sellers: Yeah, absolutely. I mean.
46
00:09:15.730 --> 00:09:31.419
Philip Sellers: you, you called out one of the big ones which is operating system support. Right? You know, as as we've managed farms in the past, and in my past life, you know, moving from 6, 5 to 7, 1 5. This is a huge part of modernizing your your workspaces.
47
00:09:31.420 --> 00:09:46.270
Philip Sellers: You've gotta keep up with the current operating systems. You've gotta test compatibility. So this becomes challenging for a lot of our customers with older software, maybe software that they stopped paying maintenance on, and they're stuck in time at a point in time.
48
00:09:46.620 --> 00:10:13.900
Philip Sellers: But then, beyond that, testing any of the new features, is part of the the big part here. So you know, if if there's new features, I you know I can think about Saml authentication being one that came out, you know, fairly recently testing that, making sure that it works and that you get the correct user experience on the other side. Is really important as you're going forward and validating your upgrade path.
49
00:10:13.950 --> 00:10:32.189
Andy Whiteside: Yeah, I probably push this ahead too fast. supportability. Right? Third party vendors, operating systems. That kind of thing it starts here with an important call out that Cvad. 1912, Ltsr. Is the last Lt. Ltsr. On the supports version server 2012, and that seems like a long
50
00:10:32.200 --> 00:10:34.750
Andy Whiteside: time ago. So no more. 2012
51
00:10:35.420 --> 00:10:47.409
Philip Sellers: seems like a long time ago, and then also seems like yesterday, doesn't it? So? You know, it's it's over a decade old. So that's saying something that. We've been able to support it to this point.
52
00:10:48.020 --> 00:11:00.640
Andy Whiteside: II think I say that because that was kind of the end of my citrus career in the beginning of my Zintigra consulting career, and that was, you know, that was that was, that was the state of the art. That was the that was the most recent operating system.
53
00:11:00.680 --> 00:11:03.570
Andy Whiteside: wow! Time supplies
54
00:11:04.770 --> 00:11:11.340
Andy Whiteside: alright. So, Bill, anything else to add around the operating system. Challenge of going to the latest Ltsr.
55
00:11:11.440 --> 00:11:18.100
Bill Sutton: the only other thing is obviously, when you're doing on premises, citrus, virtual apps and desktops. You need a sequel server.
56
00:11:18.120 --> 00:11:43.790
Bill Sutton: and so the SQL. Server version is also important. If you're running Sebat, 1912. Then there's older versions that you will need to upgrade in order to support the the newer. The new West Lts are. If you're on 2203, you may or may not be, and that's where we can come in and help evaluate where you stand and what the path is. And then important thing here to point out is that most of these
57
00:11:43.850 --> 00:11:58.769
Bill Sutton: you're not going to be doing. We don't do in place and migrations typically anymore. It's a, it's a parallel. Stand up a parallel environment and then slowly move your users over. It's a much cleaner way of doing it. Especially when you talk about much over operating systems.
58
00:11:59.140 --> 00:12:05.610
Andy Whiteside: Yeah. So if it's somewhat up to date, we can do it. We may not recommend it, we can do it. But if it's old, we're definitely gonna build a parallel environment
59
00:12:06.370 --> 00:12:07.420
Bill Sutton: for sure.
60
00:12:07.520 --> 00:12:32.420
Bill Sutton: And there's another consideration. That's that Emma lists in this article is the the you no longer able to add Zenf, 6, 5 resources using storefront used to be. You could aggregate them in storefront. In other words, you have a storefront server sitting there pointing to the new desk environment, or sorry the move. See bad environment. As well as the old 6 5 environment and aggregates the resources into one. Console, if you will, or 1 one web page.
61
00:12:32.450 --> 00:12:55.640
Bill Sutton: That's not. That's that's long gone after. In 24,308, which would have been August of last year, and that will that will be included in the newest storefront. Which means that will be supported anymore. Yeah, we do run into it. It's it's much less frequent. But we have run into it in the past year 6 5,
62
00:12:55.650 --> 00:13:01.430
Andy Whiteside: you know, I wanna go back to the operating system, call out, that is. you know, no more. 2012 r. 2
63
00:13:01.600 --> 00:13:10.799
Andy Whiteside: for both the controllers as well as the Vd vda. So virtual delivery agents. It's both pieces of that correct
64
00:13:11.870 --> 00:13:12.740
Bill Sutton: correct?
65
00:13:15.170 --> 00:13:23.789
Andy Whiteside: And then that goes into something I know Philip is wildly aware of, and that is the application correlations and what's supported, what's not supported, what works, what doesn't work
66
00:13:23.820 --> 00:13:33.560
Andy Whiteside: what's best effort, what's not Bill, the application support ability ties into here, both from OS and from a citrix perspective.
67
00:13:33.780 --> 00:13:51.419
Philip Sellers: It does. And and this is one of the places where you know we we get invented. We get creative, too. Right? So for those customers who have the really old applications sometimes app packaging may come into to play. You know, we work with other vendors like liquidware
68
00:13:51.450 --> 00:14:15.299
Philip Sellers: where we can possibly package the app to let it run on a newer version of windows. But this is this is again. Gonna be best effort kind of stuff. If you have older applications that you've not kept current. Then it becomes a sticking point for your your upgrades. So that's definitely a a bigger part of our conversations during the pre-sale cycle
69
00:14:15.370 --> 00:14:30.729
Philip Sellers: is, where are your applications? And and you know, are you maintaining those. So that's the collaboration that we try to bring to our customers around the application piece. Yeah. And just a quick goes integral commercial for that. If you have an old environment you just can't get rid of.
70
00:14:30.760 --> 00:14:43.289
Andy Whiteside: Yeah, we could support it best effort, but it would be clearly defined and signed off on that it was best effort, and we couldn't get any help from either the vendors in this case the application vendor, the Microsoft vendor, or the Citrix vendor in this case.
71
00:14:43.920 --> 00:15:09.730
Andy Whiteside: I'm gonna read this one out loud, and I can't believe I'm even having to read it. But the agent site, the program. Neighborhood agent site, also known as Zen App Services, is also deprecated from storefront 2308 forward, regarding various compliance guidelines, such as fips common criteria. 508 accessibility. Blah! Blah! Blah! I didn't think I'd ever see the word P. And agent again.
72
00:15:11.170 --> 00:15:18.139
Bill Sutton: It's interesting that that's called out here. But yeah, that's just like the aggregation of version 6 dot 5
73
00:15:18.150 --> 00:15:35.280
Bill Sutton: the P. And a generators that have services. Connectivity is gone as well that, I think, where we've seen that is, is in to enable integration with certain types of access cards in the past. I think that most of those access card environments or vendors have migrated to the latest.
74
00:15:35.280 --> 00:15:49.739
Bill Sutton: Yeah, the latest architecture are using the P. An agent anymore, which is part of the reason why they're getting rid of it. Or there's really old thing clients that just will not die. And people correct. Yeah, but still have that field for P. An agent, and they still want you to populate it to make it work. Yeah, exactly.
75
00:15:49.770 --> 00:15:50.520
Andy Whiteside: Nope.
76
00:15:50.950 --> 00:16:14.690
Andy Whiteside: I'll let you know. This one, too, is probably in your will house for Citrix Workspace app across endpoint devices. So the citrix right? It's an asynchronous solution. You got your big back end or your cloud base back end. But of course you gotta have something on the endpoint, including HTML, 5. What is it about the workspace app that's called out here. Well, it's really just calling out the fact that you need to be using a a version that's supported.
77
00:16:14.690 --> 00:16:23.289
Bill Sutton: 1912 ltsr, with end of life earlier this year. So if you're using that version, they recommend that you upgrade it. There will be a
78
00:16:23.360 --> 00:16:28.859
Bill Sutton: Lts. Our version of the workspace app there always is to match the the version of Cbad.
79
00:16:28.880 --> 00:16:48.899
Bill Sutton: Some customers elect to use the Cr version of the workspace app, which is fine. But many just stick with the Ltsr version. But either way it's best to upgrade to the Ltsr version. But obviously, as the next session section. We'll talk about you. Wanna test this to make sure that you know your workpace will support it.
80
00:16:48.910 --> 00:16:51.110
Bill Sutton: that that
81
00:16:51.470 --> 00:16:56.179
Bill Sutton: it gives you all the features that you need. There aren't any issues with your applications, etc.
82
00:16:57.040 --> 00:17:04.659
Andy Whiteside: Okay. Philip, you started to go into testing a little while ago. The plethora of new features. Good idea to test.
83
00:17:04.930 --> 00:17:28.310
Philip Sellers: Yeah. I mean, you know, II think a lot of people like me sometimes think of Citrix is a pretty stable thing but man just going through the documentation of what new features have been released. It is pages of new features. So Citrix is not not standing still. There's tons of development. There's tons of new things that are coming out.
84
00:17:28.369 --> 00:17:40.879
Philip Sellers: I think education is the first part of that you know, there, there is a tool here linked the Ltsr to Ltsr feature matrix. So I expect that'll get updated when we have a new release officially out there.
85
00:17:41.260 --> 00:17:47.869
Philip Sellers: But education is the first piece of it. What? What do you have access to that you didn't have access to before?
86
00:17:47.960 --> 00:18:03.899
Philip Sellers: And so, you know, if you've got questions around that, that's a place where our pre-sales team can definitely help. You understand what's possible. What do these features mean to you? How do they help your user experience? How do they play in your environment? That's the first place to go.
87
00:18:03.930 --> 00:18:20.230
Philip Sellers: And then you know, we're doing our diligence on the back end. We're running these things and testing these things so that we know and can have a little more information for you about how that impacts you? And then when we go through the actual
88
00:18:20.390 --> 00:18:37.909
Andy Whiteside: scoping process, that's where we can decide which of these features do we want to bundle in. What do we want to focus on to help your environment? Get the most out of your investment on Citrix? Well, and that's something I want to really want to talk to a little bit, you know. Been in lots of organizations where some engineer has
89
00:18:37.960 --> 00:18:47.109
Andy Whiteside: the idea that you wanna turn a feature on, and maybe introduce a whole lot of capability, but also to the problems into the environment. And the business didn't ask for it. They just turned it on.
90
00:18:47.140 --> 00:18:49.090
Andy Whiteside: I assume we still see that happening.
91
00:18:49.900 --> 00:18:51.780
Bill Sutton: Okay.
92
00:18:52.020 --> 00:19:05.839
Philip Sellers: yeah, I mean, it definitely still happens. Yeah. I talked to a customer the other day. And during the course of our our call on a different topic, someone had accidentally pushed out something to their entire server farm.
93
00:19:05.940 --> 00:19:14.589
Philip Sellers: you know. Mistakes will happen. You know. Sometimes you'll check a box and sometimes these things enable by default as part of your upgrade path.
94
00:19:14.670 --> 00:19:24.719
Philip Sellers: And so that, that's we're having good consultation really comes into play as a customer having a partner that you can rely on. Who can bring you that information?
95
00:19:25.270 --> 00:19:40.880
Andy Whiteside: Well, and that partner might have to stand up to you and say, Hey, do this in your test environment. First, let me let me look at your test environment. And they show you one little ser one server that's in production that has, you know, just has all the test stuff on it. That. That's not good enough.
96
00:19:42.520 --> 00:19:44.870
Philip Sellers: Yeah. I mean, it's it's funny, like,
97
00:19:45.520 --> 00:19:52.380
Philip Sellers: you know it. It's hard sometimes to justify a full test environment for something like a citrix deployment
98
00:19:52.420 --> 00:20:06.700
Philip Sellers: but there is value in that doing things in parallel, having the ability to to test things definitely has a lot of value. I found that to be the case, you know, in my prior life, before joining Zentagra.
99
00:20:06.890 --> 00:20:21.600
Philip Sellers: we needed to be able to ensure that our offshore contractors who are working when I'm not wanting to take calls at 2 in the morning. You know, we need to make sure that that's a foolproof sort of login experience for them. We wanna make sure that.
100
00:20:21.700 --> 00:20:30.790
Philip Sellers: you know we're not degrading the overall experience that we're delivering. We wanna only improve upon what we're doing so testing is a critical part of that.
101
00:20:31.260 --> 00:20:47.470
Andy Whiteside: Yeah, Bill, you see, customers with test environments that we're doing. Maybe the the initial upgrades with. And then the production, or we going right into production. Most, I would say, go right into production. They'll build a parallel environment
102
00:20:47.520 --> 00:21:05.880
Bill Sutton: and then go right in and then migrate over from there. But we don't. There are a lot of customers that don't have a quote, unquote test environment. A lot of times. I'll have a test server like a Vba, but not a full test environment. That that's a that's a small percentage, maybe probably 10% or less than mostly larger environments
103
00:21:06.090 --> 00:21:10.739
Andy Whiteside: and 99% of the time you get away with that throughout the year. But that one moment where you don't.
104
00:21:11.130 --> 00:21:12.000
Bill Sutton: Oh, wow.
105
00:21:12.600 --> 00:21:31.030
Philip Sellers: yeah. And and that's why we also have taken the the practice of doing parallel builds. We get to do that during a parallel build. And that becomes essentially a test environment before it goes into production. It reduces the risk factor to a large degree. Yeah, I'm so glad you brought that up, because that that's
106
00:21:31.210 --> 00:21:41.320
Andy Whiteside: that justifies the whole thing right? There is getting to roll it out and and test it, and and all the bad stuff that you knows in the old one. It just goes away because it never went in there.
107
00:21:42.040 --> 00:21:49.969
Bill Sutton: Yeah, I mean to Philip's point, the majority of the implementations we do are parallel. So that environment effectively becomes your
108
00:21:49.990 --> 00:22:13.899
Bill Sutton: your pilot environment if you will. So maybe not test. But it's it's used that way until it's ready to go. Customers that have full blown test environments are leveraging them typically to test upgrades or OS patches and application patches before they go to production. Obviously, in a parallel build you? Would you would do that as well before you start cutting users of it, at least in theory.
109
00:22:14.030 --> 00:22:16.749
Andy Whiteside: and my advice on that is to have a
110
00:22:17.210 --> 00:22:26.890
Andy Whiteside: have a a personal sandbox environment which sometimes gets confused with test, a test environment that mirrors production. And even with that you still do a parallel build
111
00:22:26.980 --> 00:22:35.160
Andy Whiteside: of a new test environment and a new environment that sounds like overkill. But you got your company's relying on this stuff to work in order for the business to go.
112
00:22:35.160 --> 00:23:05.119
Bill Sutton: It's worth it, I mean, if your business relies on this for day to day functionality, you need to do it that way. But another key thing I wanted to point out here she doesn't really mention in this article. But obviously it's important to test new features. It's important to test applications and support, to do parallel builds. But there been some pretty significant changes in the management framework around Citrix, virtual apps and desktops since 2,003. Most notably, we no longer have an Mmc. Based admin experience. It's all web based. Now. So you're gonna that's going to be a
113
00:23:05.120 --> 00:23:28.879
Bill Sutton: a if the if the administrators haven't had any sort of exposure to Citrix, as this is going to be completely new to them. So they're gonna really have to understand the flow of how to create machine catalogs and delivering groups. And I mean a lot of it's very similar. But the look and feel and finding with locations of certain things may be more of a challenge. So that's an important consideration, I think, is part of
114
00:23:28.880 --> 00:23:49.029
Bill Sutton: the process is making sure that your your Admins that are gonna be managing the environment, you know, routinely understand where everything is and how to get to it quickly and how to manage the environment. Because the old, the old skills are gonna not gonna be. They'll they'll be useful for sure. But it'll just be a change in how they how they go about it.
115
00:23:49.330 --> 00:23:51.469
Andy Whiteside: That's why I do everything in Powershell myself.
116
00:23:51.520 --> 00:23:59.819
Bill Sutton: Oh, yeah, okay, I wish I wish I never quite got to be that Guru one to be. But
117
00:24:00.500 --> 00:24:26.489
Andy Whiteside: do other things these days. Well, guys, I appreciate you talking about the Ltsr, there's another part to coming from Emma at some point. We'll be on lookout for that. And yeah, we hope there's a lot of customers out there that they want to move to Ltsr. They're gonna have to at some point, and we're here to help them Bill, any parting any parting comments. No, I would echo what you just said. I mean, obviously, it's integral. We're committed to to helping our customers and new customers with Citrix
118
00:24:26.560 --> 00:24:38.840
Bill Sutton: with the Citrix technology. And among many other things, so reach out to us if you need help. When do you need help? And we've got the the expertise and the team ready to help Philip anything else from you.
119
00:24:38.870 --> 00:24:47.590
Philip Sellers: Yeah, II will tell the listeners the same thing. I told one of our our customers we didn't happen to work with them on another technology. And
120
00:24:47.940 --> 00:25:10.210
Philip Sellers: I said, Look, II will be glad to be your free consultation. I'll be glad to point you in the right directions, and it doesn't matter if you bought the product from from us, we'll still be glad to help you fix it if you're struggling. So if you're in that boat definitely reach out, we we have hopefully, we'll have the answers for you. We've got the expertise and we'll work it together.
121
00:25:10.500 --> 00:25:16.649
Andy Whiteside: Yeah, we we don't. We don't have to have every dollar of your business. We're looking for your business as a partner. Long term.
122
00:25:16.900 --> 00:25:21.129
Bill Sutton: Exactly. Well, gentlemen, thank you, and I will look to do it again next week.
123
00:25:21.620 --> 00:25:23.300
Philip Sellers: Okay, thanks, Andy. Thanks, Andy.