VMware is attempting to disrupt the app publishing market with the introduction of its new "Apps On Demand" technology in App Volumes. Apps On Demand enables just in time delivery of applications to users without the typical delays during login and with ease of administration. With many choices for packing, App Volumes enables Apps On Demand to leverage your existing application packages and deliver them seamlessly to your users. Boasting 99% success rate in packaging, VMware's App Volumes is succeeding where other solutions struggle.
Host: Philip Sellers
Co-host: Rizwan Shaikh
00:00:02.960 --> 00:00:13.510
Philip Sellers: Hello, and welcome. This is Phil Sellers. Thank you for joining Episode Number 31 Vmware on the horizon, podcast from Zendegra.
00:00:13.650 --> 00:00:25.890
Philip Sellers: We are happy to have you join us today. Can't believe that we're already in month number 3 of the year, 2,023 it's incredible how time is just flying by.
00:00:25.890 --> 00:00:34.710
Philip Sellers: I i'm joined today with Rizzwan Sheikh, one of our solutions Architect I'm. Also a solutions architect here at Integra. And
00:00:34.920 --> 00:00:44.370
Philip Sellers: Yeah, this is the podcast where we get to talk about all the fun things that are happening inside of the Vmware world and in user compute. So this one how you doing today?
00:00:46.160 --> 00:00:56.830
Rizwan Shaikh: I'm: absolutely fine. Well, how about you doing Well, can you believe we're already in March? I mean, it just seems like this year's flying by. Yeah. Exactly. Yeah, we
00:00:56.910 --> 00:01:08.770
Rizwan Shaikh: we've just crossed to February, and it's all yeah, we've been looking at some more, Some more technologies coming in, and we have March here, actually, and they're still learning a lot of new things coming up. The
00:01:09.320 --> 00:01:17.480
Philip Sellers: yeah. Indeed, You know, our technology partners are not resting. They are certainly keeping things interesting and pushing forward.
00:01:17.480 --> 00:01:38.400
Philip Sellers: There's a lot of change going on for sure, but they, you know, I I think we've got a really good topic. One of the great changes that we've seen from Vmware is, you know, around a technology called add volumes, and they've released a new service offering and called apps on demand
00:01:38.400 --> 00:01:44.430
Philip Sellers: as part of that at volumes. And so i'm excited to to get to dig into this today with you.
00:01:44.460 --> 00:02:01.130
Philip Sellers: Talk about it because it's not just something that's being more specific. It's it's something that can help any of our Euc customers whether they're running horizon or citrix. It it's not limited, and so you know this: this is an area, though, that
00:02:01.390 --> 00:02:11.700
Philip Sellers: we've we've spent a lot of time as an industry for the last. I don't know 20 years trying to solve the app problem, particularly when we come to
00:02:12.570 --> 00:02:25.920
Rizwan Shaikh: yeah, like, if you, if you look at the if we could be complete virtualization segment that we have to do since we are the they've been managing these, this segment of the most critical segment across
00:02:25.920 --> 00:02:43.210
Rizwan Shaikh: across all the organizations. If look at this talk about symmetrics, for is in that. What's your applications? I'll be in the horizon applications all of these, all of the solutions actually the big agenda that pulls across the new solutions is to deploy and
00:02:43.210 --> 00:02:55.180
Rizwan Shaikh: provision access to the applications in the most secure way. The more optimized it. Right. I mean, we look at all the use cases that we have today. But but it is. It is a hospital positions for the it is
00:02:55.350 --> 00:03:13.840
Rizwan Shaikh: manufacturing. B. If it's a banking infrastructure to that matter of financing. For that matter, all of these they use the solutions to have a secure delivery of applications on the other side. If I look at this flip side, maybe have the it segment to manage all of these applications.
00:03:13.840 --> 00:03:24.970
Rizwan Shaikh: They need to have a solution which can manage the solution which can manage the complete infrastructure in a more optimized way they can, making use of the resources of the more optimized way.
00:03:25.120 --> 00:03:44.080
Rizwan Shaikh: So the new feature of apps on the demand. That's that's a feature which is this is the part of the we under app volume, infrastructure. We have a solution that provides a certain degree of resource optimization in terms of in terms of eliminating
00:03:44.080 --> 00:03:47.430
Rizwan Shaikh: the complete sign of a application from the operating system level.
00:03:47.550 --> 00:04:05.500
Rizwan Shaikh: Now, what the the main reason why being there well with this kind of solutions is, if you look at the if you look at it, to trace environment as such, for specifically, for the app publishing part where you have an Rdsf segment or a strict or being there
00:04:05.500 --> 00:04:16.890
Rizwan Shaikh: Verizon application segment. We have multiple silo that we have multiple silos of the infrastructure which are being deployed across, ready to be called farms for those of all the
00:04:17.000 --> 00:04:19.870
Rizwan Shaikh: But these infrastructure needs to be managed, that mean
00:04:20.079 --> 00:04:21.990
Rizwan Shaikh: motive of the main
00:04:22.170 --> 00:04:37.850
Rizwan Shaikh: purpose of having these kind of infrastructure is to is to permission applications on these silos of these on these farms, and then this this application will be interacted across multiple users. Now, what really happens here is if you look at this, I mean.
00:04:37.970 --> 00:04:45.480
Rizwan Shaikh: it needs to manage a lot of things here right? We need to manage the operating system. The entire platform is sitting on.
00:04:45.490 --> 00:04:54.440
Rizwan Shaikh: We need to manage the applications they need to. We need to update the security signatures, the security security updates.
00:04:54.470 --> 00:05:12.000
Rizwan Shaikh: You also need to ensure that the applications are all these updated so that users can get new features, and the organization is also secured that we have to be able to security enough, and so that they can get rid of me of all the vulnerability that can come across on the operating system level of the application level.
00:05:12.610 --> 00:05:27.280
Rizwan Shaikh: Now, this brings a real big challenge for for all the it organizations here, and that is there you you keep on going with with it. I mean we you You have heard about about past Tuesday, right? That's that's the most dangerous times.
00:05:27.280 --> 00:05:36.980
That's the most critical time, I would say, for all the it organizations to to match each and every component that they have, including application. You send the operating system
00:05:37.160 --> 00:05:38.610
Rizwan Shaikh: now.
00:05:38.770 --> 00:05:58.770
Philip Sellers: So so I do want to break in. I mean, you know, before we we go down like the the full rabbit hole here with with this, I mean, I I do want to spend a little bit of time talking about the problem. I mean, because this is pervasive right like this isn't new just to Vdi. It's not new just to
00:05:59.720 --> 00:06:21.950
Philip Sellers: the things we're trying to do in in user compute. I mean, these are same sort of application problems that we had years ago before virtualization, right? I mean, we. We used to put many applications on a single operating system back when hardware was very limited, and then virtualization allowed us to put many individual virtual machines dedicated to one app
00:06:21.950 --> 00:06:23.860
Philip Sellers: and encapsulate that
00:06:23.910 --> 00:06:42.600
Philip Sellers: and and run that securely. And before that, you know we would put SQL server in exchange, and maybe a domain controller. I mean I I I did those. Since you know I I deployed my small business server, where you know everything, for the company was all on a single physical box.
00:06:42.600 --> 00:06:54.900
Rizwan Shaikh: you know. And and really that's the problem that we're talking about. Here is you start layering those applications together. Things get messy, right? I mean, that's that's the easy way to simplify it right? Things get messy.
00:06:56.550 --> 00:07:13.560
Rizwan Shaikh: Yeah, how are for the If you. If you look at the the virtualization in suspicion that we talk about it's all about layering right. I mean we. We. We we go into virtualization solution. It's a layered, of course, that we take, and you have a Vdi which is basically nothing but an operating system.
00:07:13.560 --> 00:07:31.250
Rizwan Shaikh: a virtual machine which is having an operating system with the minimal set of resources. Then we have the application layer, and then we have the user layer which most most of them, because the data layer actually, which which is basically a user profile. And then we have the complete environment. So all of this is bundled across
00:07:31.250 --> 00:07:37.450
into one virtual machine which is then presented to the end user for the most critical segment.
00:07:37.660 --> 00:07:51.180
Rizwan Shaikh: Yeah, one of the most particular segments here is the application part. Now, with the app volume. The biggest benefit that we get here is, as you as you rightly mentioned, right. I mean, all of these applications have been removed
00:07:51.180 --> 00:08:06.660
Rizwan Shaikh: from one single host of one single unit machine, and these applications are layered across under one single side of. So what I can do here is, no matter what kind of machine I have, what kind of virtual machine I have, I can simply entitle users
00:08:06.680 --> 00:08:19.850
Rizwan Shaikh: for group of users for a specific application, which means that I no longer have to depend on the golden image of that of that Vdi. I. I don't have to create multiple templates of that machine
00:08:19.850 --> 00:08:27.640
there by reducing the storage which I, which I obviously even the infrastructure. That's the biggest for the most biggest advantage that I get from the app volume.
00:08:27.830 --> 00:08:33.679
Philip Sellers: Well, it's for the number of of images in a different way to I mean, you know
00:08:33.679 --> 00:08:52.730
Philip Sellers: we used to have, you know, desktop images that were built specifically for a use case or for a a user group in the company, because, you know, the only way to get just the apps that the user needs onto their desktop. And the old way was well. You had to stamp out a different image for each one of those
00:08:52.740 --> 00:09:10.660
now by image from the applications and the application delivery. You can tailor that and make it a very customized. So you know, if if a user in finance doesn't need the marketing applications. They don't see the marketing applications in their Vdi session.
00:09:11.780 --> 00:09:25.150
Rizwan Shaikh: You're absolutely right? Yes, absolutely. That's that's how that's how they compete with solution works. Yeah. So a better way would be like the like. The you more desktop services that we do that tumble, serve an environment that we use here
00:09:25.160 --> 00:09:39.570
Rizwan Shaikh: where you, you don't go ahead and deploy the completely desktop. I mean. You can simply go ahead and only permission the application that you want to see the the marketing example is one. What good example of that? You can only see
00:09:39.610 --> 00:09:46.700
Rizwan Shaikh: of marketing applications itself. But the engineering users can only see them only the applications, and not any other applications.
00:09:46.800 --> 00:09:49.030
Rizwan Shaikh: Well, that's something which which.
00:09:49.450 --> 00:10:04.350
Philip Sellers: and and the blog goes to a little bit about this I mean one of the other benefits to that. I mean, you get the division of ownership, you know, so that you, your application teams, you know, or they have an easier job of updating those applications.
00:10:04.350 --> 00:10:23.800
Philip Sellers: you know, in a business continuity setting you, you can update the farm, but then, you know, critical applications, temporary farm you can configure, you know, on on the fly a lot more easily than you know All of the testing it takes to create a a separate image, and you know
00:10:23.800 --> 00:10:31.530
Philip Sellers: the conflict resolution between all of the applications, you know. Does Microsoft office, you know 20,
00:10:31.720 --> 00:10:43.540
Philip Sellers: 1720, 19 play well with, You know Microsoft Dynamics. Crm: You know those kind of problems that come into play as you're creating an app image and stuff.
00:10:43.540 --> 00:11:14.990
Philip Sellers: And the other one I liked out of this is entitlements right. So because you're only entitling it, or only delivering it to certain users. You keep a lot more control over your software licensing for third party apps, you know they've got a w acrobat icon right here on the the screen. So you know that's a great one, You know you pay per user for acrobat. And so you only want to deliver acrobat to the users who need to edit Pdfs. Not to everyone in your. You don't want to pay for everyone right?
00:11:16.250 --> 00:11:35.070
Rizwan Shaikh: Absolutely, absolutely. This is. This is a perfect example of what what we talk about in the app quality itself. So the app volume actually leverages all of these all of these benefits for an organization you cannot. You could actually go ahead. Say, for example, slack for that. But Slack is a user base licenses, and you can actually control
00:11:35.130 --> 00:11:48.040
Rizwan Shaikh: who are the users who are going to use this application by simple means of entire element. You can simply go ahead and title a lot of these users for the grip of us, and only these users will be able to have access to this back and everything else.
00:11:48.400 --> 00:11:56.540
Rizwan Shaikh: So that's something which which brings a lot of benefits by having having the apple infrastructure of our clearing structure actually in a virtualization environment.
00:11:56.810 --> 00:12:03.890
Rizwan Shaikh: And the longest other features that we can. We can also actually have a look in terms of in terms of operations. If you look at
00:12:04.530 --> 00:12:09.740
Rizwan Shaikh: today deploying, deploying an application in in a server or in a machine.
00:12:09.790 --> 00:12:20.330
Rizwan Shaikh: You need to factor a lot of things in the machine itself. The machine needs to be compatible for that application to get it installed with the app volume. This is no longer needed.
00:12:20.810 --> 00:12:33.120
Rizwan Shaikh: and we still no longer need. It is because I am not installing that application on that particular machine around that particular server. What i'm doing here is, i'm laying that application across the separate silo all together.
00:12:33.120 --> 00:12:48.140
Rizwan Shaikh: and then entitle that application across to the users and the users can log into the Bbi's, or to be orderly any of the servers that they that they want to, and they can access those applications, feeling that that's something which I do. So With this I get a lot of benefits
00:12:48.140 --> 00:13:09.810
Rizwan Shaikh: in terms of in in terms of I don't have to restart, and at least at least out of any server. Any Vdi is not be needed. I don't have to do amazing of all of these Vdi is just because I need to update the applications. Or let's say, for example, if I want to go with version one dot x, 2 Dot x. I need to do a lot of things on the email, on the on the machine itself.
00:13:09.810 --> 00:13:14.430
Rizwan Shaikh: with the app. Wall, I don't need to do it at all actually. and
00:13:14.520 --> 00:13:27.580
Rizwan Shaikh: and the best part here is a single app copy will be, will be enough for all all the users. What they would be entitled for all of this, all the for for for that particular applications actually now.
00:13:27.890 --> 00:13:42.110
Rizwan Shaikh: And as you I mentioned right, I mean, how about the application management are you talking to talk about like application updates? How do we do testing? And how do we? How do you bring that new 86 to production
00:13:42.130 --> 00:14:01.440
Rizwan Shaikh: that's phenomenally well described and well well configured across from the appholding structure. You can go ahead, define a test or to find a Uat test a bit for the application. See how the applications working with the grip of users, the group of test users, and then deploy that application to production. Once
00:14:01.440 --> 00:14:09.930
Rizwan Shaikh: the application is ready for for the end us to to to be provisioned across. That's something which which which is, which is the beauty of our
00:14:10.180 --> 00:14:10.880
Rizwan Shaikh: No.
00:14:10.970 --> 00:14:21.530
Philip Sellers: So I I do want to spend a and and again just kind of point out we're talking a lot about the at volumes capabilities, kind of giving you an introduction to the problem
00:14:21.530 --> 00:14:31.560
Philip Sellers: to what at volume solves. But you know, I I think we also have to realize that there's a lot of solutions out in the marketplace
00:14:31.560 --> 00:14:51.540
Philip Sellers: that have tried to solve this problem. Right? You know the block. Those points out here. A lot of different solutions have tried to solve it. They've come close, but no cigar. Yeah. So can you talk a little bit about like, you know app stacks, you know, before at volumes? Maybe a little bit about Citrix app layering and kind of. Where did they fall short?
00:14:53.320 --> 00:15:13.270
Rizwan Shaikh: Well, the the all that you see in the in the in the abstract. So we've got more licenses out. Clearing was these applications of these static, which means that once you some applications are installed on the on the desk, I you. It can zoom. That's particular storage on the on the desk itself, which means that when I go ahead and title the apple issue.
00:15:13.270 --> 00:15:19.580
these applications are made ready for me once the moment I I and log into the media, so i'll be able to see
00:15:19.630 --> 00:15:24.800
Rizwan Shaikh: my adobe acrobat, my slack, my zoom chrome Chrome browser.
00:15:24.880 --> 00:15:34.890
Rizwan Shaikh: At the same time, when i'm not into the Vdi. Probably I may not be using all of these applications in one Co. Itself. Right? Let's say, For example, imagine the scenario where I have 300 applications.
00:15:35.370 --> 00:15:47.400
Rizwan Shaikh: and all of these 300 applications are published across from an app audio, and when I log in. What really happens is at the back end. I have the app volume provisioning all of these app stacks the moment I buy
00:15:47.420 --> 00:16:06.460
Rizwan Shaikh: I logic. So what really happens? My login reduces my my, my my profile, time, my my my my profile increases, but the find log in time increases. That that's something causes the poor end user experience. Probably I I was able to log into the Vdi, and almost like 10 s 15 s
00:16:06.460 --> 00:16:13.800
now the same Vdi, the same as the credential. It's almost it's taking almost a minute for me to log into that media, and that's only because I have
00:16:13.840 --> 00:16:26.750
Rizwan Shaikh: 300 app stacks, so 300 applications being deployed across in one to itself, I may, I may not be needing all of those applications in my in my regular regular usage, but still those are getting installed.
00:16:27.120 --> 00:16:43.860
Rizwan Shaikh: Now, that's something which is pretty. It's just pretty common, if you to look at the All all the today. How ever, what really happens and what what is, what is there on the like? A charity on top basically is if you talk about option, demand today
00:16:43.880 --> 00:17:01.420
Rizwan Shaikh: the actual demand from Vmware actually brings a near real time delivery of the applications to the end users, which means today. But I I go ahead and title. These users across the end users today to the end users for the end users when they log in, they don't see all of these applications coming in.
00:17:01.420 --> 00:17:12.220
Rizwan Shaikh: They would only see this application getting getting deployed across from the machine the moment I need those applications. A typical example is, let's say, for example, I have a Pdf file.
00:17:12.359 --> 00:17:31.450
Rizwan Shaikh: and I want to see the Pdf. File and the adobe acrobat will be permission through apps on demand. The moment I double click on that in your file it will be acrobat will get, will then get installed across for me. Will that provisioned across to me on that particular on that particular usage. It is on the fly that I get the application, which means
00:17:31.450 --> 00:17:39.860
Rizwan Shaikh: I am not pre-loading my image my machine with all of the application which I may not be needing. It also at that moment of time.
00:17:40.200 --> 00:17:56.310
Rizwan Shaikh: That's the best part which apps on demand. Reason. It brings in the real real time access to the applications for me whenever these applications are needed for the action. And that's the beauty that that comes across. That's when we talk about resource, utilization, a proper way of resource utilization.
00:17:56.310 --> 00:18:13.980
Rizwan Shaikh: This is where apps on Demand plays a very important piece. It doesn't. Go ahead. Your storage or or infrastructure or resources. It simply goes ahead. It makes use of it, but it is needed, otherwise it will. It will not be. It will not be deploying it across the
00:18:14.630 --> 00:18:32.600
Philip Sellers: yeah. I mean it's a it's a huge step forward for us. I mean, just kind of hitting that just in time. Used case right, you know not until you ask, Where is it delivered to you? So yeah, you and you're not. Both have experienced the the calls from our users. Man, you know it's so slow it's so slow.
00:18:32.600 --> 00:18:54.390
Philip Sellers: What does it mean? User Perspective, when we get it's so slow Well, a lot of times. It's that login time, because you know, we're doing things with profiles. We're doing things with loading and apps and things like that. So anything we can do to accelerate that log in time. That's gonna change user perspective of slowness. And and this is a great example, too, of
00:18:54.390 --> 00:19:10.450
Philip Sellers: of centralization. Do you want to talk a little bit about. You know the administrative advantages there for apps on demand. I I know there's a few here that yeah, and you've mentioned a few of them. But previously in the podcast. But can you go into some of those administrative benefits?
00:19:11.300 --> 00:19:15.450
Rizwan Shaikh: Well, the biggest benefit that the industry gets is the self optimization.
00:19:15.970 --> 00:19:28.510
Rizwan Shaikh: right? I mean you you are not pre-loading the storage here. You have the application that you're not using the storage in the time it is needed in it to be used, and that same story that we use it for something else.
00:19:28.510 --> 00:19:47.510
Rizwan Shaikh: That's something which which which i'm and and based on that I can design a complete solution. I can go ahead and say that I'll be needing this much amount of storage, and I can reserve this a month, which is much amount of so for some of the work, but that the intern that doesn't mean that i'll be preloading this applications across on that particular on that particular. This or the particular storage.
00:19:47.510 --> 00:20:07.340
Rizwan Shaikh: Yeah, you know, we we also get the the centralized management, though as well, I mean you. You've got the centralized location for managing the images. You you get a single copy that that works for all users, and and you know we get compliance. I mean, I know, coming from
00:20:07.340 --> 00:20:24.030
Philip Sellers: a system center config manager world, you know. We would have groups and entitlements to applications, and it would push out the applications. But it wasn't ever really good at taking the application away if the user wasn't using it, you know we
00:20:24.030 --> 00:20:33.400
Philip Sellers: we tried, but it was cumbersome with this, for users not entitled. They never see it right. It doesn't matter if it's on this machine or not.
00:20:35.620 --> 00:20:36.450
Rizwan Shaikh: Yeah.
00:20:36.470 --> 00:20:51.190
Rizwan Shaikh: I mean that's that's something which which you can see here as well, right. I mean, if you look at the utilization perspective, that's that's a huge benefit which which comes across in terms of so when I say the source is, it's totally destroying it's also.
00:20:51.210 --> 00:21:08.690
Rizwan Shaikh: or the CPU as well as memory, because you you are not loading up your memory. You're not loading up your your CPU, just because just because you have an application there somewhere, sitting at the demon process, you simply simply go ahead, Make use of that application when it is needed. Until that time
00:21:08.690 --> 00:21:13.910
Rizwan Shaikh: you have your resources being properly utilized, you haven't you have it so it's been properly optimized, the cost.
00:21:13.930 --> 00:21:25.200
Rizwan Shaikh: So that's the biggest benefit that the the operations we can get across Most importantly. Most of the benefits that you see here is already been covered in the in the app or in between. You. Have
00:21:25.650 --> 00:21:41.210
Rizwan Shaikh: you have that copy of the application which which you can keep on updating? You Don't, have to go ahead, Update the operating system. But you should be update the application itself, and definitely one single application. One single application can be entitled to multiple users, and
00:21:41.210 --> 00:21:51.320
Rizwan Shaikh: it can be either on a Vdi segment or virtual desktop, that we say, or it can be on a terminal server platform like a remote desktop. So this is that's something which
00:21:51.340 --> 00:21:57.980
Rizwan Shaikh: which, if it's on on both descent, I mean you. You have the end users as well as that's what I was talking on. The
00:21:59.800 --> 00:22:09.290
Philip Sellers: yeah, absolutely. And and again, you know, all of this leads to radical simplification, which yields lower cost to maintain
00:22:09.310 --> 00:22:31.920
Philip Sellers: easier administration, better resource, utilization, I mean there there's so many benefits to having a good solid app strategy when it comes to your end. User compute. And this isn't just inside of a a Vdi environment. Right? I think Vmware is offering this on a bare metal on on, you know, windows endpoints, laptops as well.
00:22:32.680 --> 00:22:46.720
Philip Sellers: That's correct. Yeah. And so that's a for customers. You've got one way of of entitling and centralizing all of your app delivering. That's that's that's huge in my book.
00:22:48.020 --> 00:23:02.260
Rizwan Shaikh: That's correct. Yeah, and the most important part here is well. I mean this application volume that we have only supports all kinds of opportunities we look at, if it can be legacy of the legacy applications that we have today. It supports that as well.
00:23:02.340 --> 00:23:21.300
Rizwan Shaikh: Newer applications are definitely supported. But then we have a lot of customers who use legacy application, using a lot of other. A lot of other older applications. App Volume is the key for that. They can simply go ahead and leverage all of these features across on these applications, and they have a better utilization of their environment.
00:23:22.270 --> 00:23:32.750
Philip Sellers: Yeah. And and that's the last point of the blog we'll, we'll call this one out. Yeah, this is all awesome, but we'll add volume. Support my applications. You you're talking about this.
00:23:32.780 --> 00:23:44.230
Philip Sellers: Can you tell us a little bit about the different at volume formats. You know what support there is, and how users can leverage it.
00:23:45.880 --> 00:24:05.580
Rizwan Shaikh: Yup. So basically if you look at the it's, look at the format up all it will. Basically nothing. But it's just the staff, right? It's just an application start, which is, which is then deployed across for all the head users. So typically, if you, if you look at if you look at it in the application that you see right, let's say, for example, the graphics based applications or
00:24:05.580 --> 00:24:16.880
Rizwan Shaikh: our office space application. Usually a task worker knowledge. We'll be using it any any kind of any sign applications or ex, for that matter, any kind of likings for that. But I think that
00:24:17.010 --> 00:24:18.150
Rizwan Shaikh: I don't for that
00:24:18.260 --> 00:24:37.400
Rizwan Shaikh: even shale extension set me also to be supported. Actually, so the best part here is any application that you have, I mean today is the biggest fear of what the customers have here is. They're going to bring in the application. They're in an application, but they do. I have to record my application. The answer is, No.
00:24:37.430 --> 00:24:53.470
Rizwan Shaikh: you don't have to do that. You don't need to record your application. You don't need to put that development efforts to to to do the recording of the application. You simply go ahead. Provision that application the way it is at least provisioned across, and that's it, Apple. It will do the job
00:24:53.520 --> 00:24:58.330
Rizwan Shaikh: and the other good part. Here is a lot of applications which are Still.
00:24:58.410 --> 00:25:11.480
Rizwan Shaikh: it's typically very old, and on a legacy, fashion, application to that matter and it and you may have applications which are not supported on the newer newer operating system. So the newer
00:25:11.650 --> 00:25:31.520
Rizwan Shaikh: so we can. We can still use those applications on a, on a, on a, on a, on a, on a, on a on a machine on a Vdi, and it can do an isolation of all these applications. The process which which we call the sandboxing, and typically that is called, and it's called
00:25:31.520 --> 00:25:46.290
Rizwan Shaikh: so. You can sandbox and application across, which is pretty old legacy, which is not supported in a virtualization perspective. You simply go ahead and use and sample through the application published with applications across an a virtualization environment.
00:25:46.430 --> 00:25:49.650
Rizwan Shaikh: Typically, this was called as an application.
00:25:49.730 --> 00:25:59.670
Rizwan Shaikh: It's it's it's not. It's a. It's a. But yeah, we have to be. We can even go ahead. And we can also also isolate those applications across
00:25:59.720 --> 00:26:01.390
Rizwan Shaikh: on on a via environment.
00:26:01.610 --> 00:26:09.970
Philip Sellers: Yeah. So customers end up with 3 different ways. They they've got their appliance format, which supports many of the installable ways of packaging.
00:26:09.970 --> 00:26:21.860
Philip Sellers: They got the an app format, but they also have support for Microsoft's, Msi. X. And and talking a little bit with with some folks over at Vmware, about Ms. Ix.
00:26:21.860 --> 00:26:32.880
You know my my question was, and and so our listeners may have the same question. Seems a lot like at volumes. Right? So what's the advantage to Msi. X inside of that volumes.
00:26:32.880 --> 00:26:51.560
And what my being where folks are telling me is that it allows us to do attachment at an individual user session. So Msi. X. Gives you some of the at volumes like features, but it's going to attach at the the device we're at the computer level, not at the user level. So
00:26:51.840 --> 00:27:07.010
Philip Sellers: if you've already spent time, you've already invested in Msi. X. You can reuse those you can pull those into at volumes as well, and deliver them out with that volumes on demand on a per user basis. And that's a huge, huge advantage, because
00:27:07.020 --> 00:27:25.600
Philip Sellers: you know, regardless of what standard or what investment you've previously made. You're gonna get good outcomes you're gonna get, you know. Return on that investment, whether it's your time or money, You know, with any of these packaging solutions. So I like the fact that that at volumes is is supporting.
00:27:25.600 --> 00:27:36.080
Philip Sellers: You know, multiple different formats that you don't have to completely start from scratch you can import and and use the things that you've already established today. So that's a huge win for me
00:27:36.260 --> 00:27:46.600
Philip Sellers: last section kind of closing out here. I want to talk about support for other third parties, you know. We set it at the top of the podcast, but
00:27:46.600 --> 00:27:57.360
Philip Sellers: it it repeat it. It deserves to be repeated in my mind. This Isn't: just a Vmware technology it's supported across more places. Can you tell us a little more about that? Was one.
00:27:58.500 --> 00:28:09.110
Rizwan Shaikh: Yeah, it's. It's a look at the if you look at the complete solution of our polling. So in this is more like a separate separate solution altogether right. I mean that this can actually work on any
00:28:09.180 --> 00:28:21.150
Rizwan Shaikh: virtualization technology that we use, then Citrix, and that it can be a Verizon or even Microsoft, that one. So I think we have a dash solution, or you have a typical service solution
00:28:21.230 --> 00:28:37.500
Rizwan Shaikh: or a solution which is deployed or an on that environment. And you can leverage app for you, and that's on demand features, and you can go ahead and and optimize your applications across all of these segments, and you have citrix after machine
00:28:37.860 --> 00:28:56.710
Rizwan Shaikh: or or a license cloud environment, or Microsoft visual Platforms, or even the avd for that part of it those kind of multi-session or windows. They're not windows. They've been monkey system, environment as well. So so any any solution that you have today, you can. You can actually go ahead and we can leverage the out volume, and we can start
00:28:56.710 --> 00:29:00.400
Rizwan Shaikh: start building up something like up here and start optimizing your applications.
00:29:01.150 --> 00:29:10.090
Philip Sellers: Yeah, and and that's that's truly cool to see. You know a. Again as a nod to that being a different application.
00:29:10.090 --> 00:29:40.090
Philip Sellers: you know, talking with with Vmware, there are licensing subscriptions for the technology that are specific for it's it's called horizon at Universal, I believe, is the subscription that gets you all this great technology. It does not mean you have to license horizon for Vdi, you can come in, and for a simple subscription you're able to get the at volumes. Technology completely separated to use in any of these other.
00:29:40.090 --> 00:29:47.280
Philip Sellers: So it's pretty friendly, pretty easy to understand, and definitely has a lot of benefits.
00:29:48.530 --> 00:29:54.350
Philip Sellers: Anything else you can think of, that our listeners should know about apps on demand.
00:29:55.790 --> 00:29:59.860
Rizwan Shaikh: Well, I would say that this just go ahead and try it out. I mean, just go ahead and
00:29:59.980 --> 00:30:17.680
Rizwan Shaikh: and reach out to us, and we can help you across and and and show you like how absolutely demands. Get work for you, no matter what kind of environment that you have. We can go ahead, and we can optimize your applications in much better way that you could get it to do today, and you would see the difference, the woman that has been installed, and we will deploy.
00:30:17.680 --> 00:30:20.240
Rizwan Shaikh: And and this is this is about a reaction from
00:30:20.250 --> 00:30:35.680
Rizwan Shaikh: individually from us. And this is the reaction from all of our customers where we have deployed, apps on demands. Well, this is this: it's, it's such a magic which works it well actually for the users and for the administrative side of that I need to see the same difference happening in your
00:30:35.710 --> 00:30:41.170
Rizwan Shaikh: Just let us know if we need any help we just to call away, and we should be able to help you out.
00:30:41.210 --> 00:31:05.840
Philip Sellers: Yeah, you You were telling me at the before the podcast started. You've done several of these pocs. You've got hands on the experience with it, and this is a brand new product. So we we love digging into those new products here is integral. And so we're excited to to get it out there and help you learn more about it so definitely echoing what riz one said, reach out to us.
00:31:06.890 --> 00:31:21.500
Philip Sellers: So, r one, I really appreciate getting together with you to talk about this. It was it was fun today, I know Andy's normally our our host. But we can sub in sometimes, too, Can't we?
00:31:23.460 --> 00:31:25.810
Rizwan Shaikh: Sure, definitely definitely
00:31:26.970 --> 00:31:38.700
Philip Sellers: Well, with that we appreciate everybody listening until next time. This has been episode 31 of Vmware horizon v. And we're on the horizon.
00:31:39.150 --> 00:31:46.200
Philip Sellers: My name again was Phil Rizwan was also joining us. Today we appreciate you listening, and we'll see you next time.
00:31:48.430 --> 00:31:50.340
Rizwan Shaikh: Thank you very much, Bill. Thank you.