Duration 41:46
16+
Play
Video

Citrix Synergy TV - SYN208 - Citrix App Layering: top 10 lessons from the field 2.0

Dan Morgan
Senior Enterprise Architect - US East | Americas Customer Success at Citrix
+ 1 speaker
  • Video
  • Table of contents
  • Video
Citrix Synergy Atlanta 2019
May 21, 2019, Atlanta, GA, United States
Citrix Synergy Atlanta 2019
Video
Citrix Synergy TV - SYN208 - Citrix App Layering: top 10 lessons from the field 2.0
Available
In cart
Free
Free
Free
Free
Free
Free
Add to favorites
575
I like 0
I dislike 0
Available
In cart
Free
Free
Free
Free
Free
Free
  • Description
  • Transcript
  • Discussion

About speakers

Dan Morgan
Senior Enterprise Architect - US East | Americas Customer Success at Citrix
Daniel Lazar
Product Manager at Citrix

Experienced solutions architect and technology expert with superior written and verbal communication skills. Enthusiastic change agent with a track record of proactively identifying problems, mapping out solutions, and taking action to solve them.

View the profile

About the talk

Citrix App Layering is a key tool for application and image management. A major benefit to App Layering is that it can help facilitate a successful shift to the cloud and ease the management overhead of maintaining a hybrid and multi-cloud deployment. This session will discuss the latest recommended practices and strategies from the field, building on and updating our Synergy 2018 session. You will leave this session with a better understanding of how the latest and greatest features (e.g., User Layer) should impact your App Layering strategy, practical tips to maximize your success, and a real-world take on hybrid and multi-cloud management techniques.Note: This session will be live-streamed during the event and available for on-demand viewing post-event on Citrix Synergy TV.

Share

Welcome to Citrix app layering top ten lessons from the seals version 2 & Beyond. So the reason for the title is that this session is actually follow up to the one that robbed the last key and I did last year with her top ten lessons from the fields. But since then there have been a lot of new developments in the product and we've learned a lot of lessons through our various customers and we've been working with ever since so we wanted to make sure that we shared something additional things we learned since then and additionally we want to take the opportunity that we're all so

welcoming Dan Lazar another stage with us the product manager play rings to give you a little bit of an overview of where the products team had. Is that for the future of a flowering so just some quick intros for those of you don't know me I'm Dan Morgan senior architect that are Citrix Consulting team beso Northeast and this is Rob soloski who requires no introduction everyone. Please give the man a round of applause. Answered your form post and you've read his blog to turn purple.

Semi way moving along. We're not really going to repeat things from last year where possible and we're going to keep it primarily focus a new content. We have a pact agenda free here today. So we're not going to be taking questions during the session but will be around throughout the entirety of the conference. Feel free to stop us and hallway ask, whatever your question do you want and we're all staying at the Marriott. So if you find us at the Marriott bar, I you can definitely get some more information from

its there after the presentations are over. So this is a lesson that I really wished that we had actually dressed the last time they were here. How do I know I need Apple iring. So this is a really important question. For those of you who are still early in your journey are looking to embark on the journey because using App layering really is an investment because once you decide to go down that route, you're going to have to do some work to make sure that you get all of your applications in the layers and all of your operating system platforms going to Lakers. So

the two things to factor in when you're making that decision is first off will a flaring make your life easier. So a few the key things to look for the first one being immature. Also the more images you have the more of an operational benefit that you're going to get from using a product like a playroom another key one that we're seeing that is driving customers to go this route for valid reasons is if you're looking to shift to a different platform And you don't want to have to essentially double your image counts to maintain something for example on Fram and vsphere and also

putting additional services in adger additional. I know that many of the customers in my patch have had to use cases that they wanted to dress with non persistence Solutions, but haven't been able to because of they are just there were thinking about the image scroll that would result from having to deal with all the one-off application sets from different user populations. They were looking to address this can really help mitigate that the next question to ask is is your organization ready to die. So as you all know Apple iring requires and non-persistent image management solution.

So if you already using PBS or MCS great things going to streamline right into your existing operations on the other hand, if you're not using TV srmc yesterday, that's another Journey that you're going to have to embark on as part of this process. Which is going to definitely involve some conversations with some of your teams that deal with software deployment in management. So another thing to look out for is to what degree you have your entire bills and management process automated Unfortunately today. We don't have apis for the Citrix app layering product. So that

maybe a little bit more difficult to slip stream into a fully debe environment would call it where you have everything from Soup To Nuts automated but this is something that Dan may or may not be talking to you about additionally we found some obstacles and customers with very rigid in his field standards, which we're going to cover in a bit. If you don't do your OS layer that a flaring way you're putting yourself at risk, so you really need a fact that it's in when determining whether or not to go down this path and finally Amazon web services if you're looking to

employee completely native us. Fortunately today we don't have an Enterprise Ledger manager Appliance for AWS or we don't have a connector yet either at this point. So you'll stay some challenges if you're only going that direction. So at the end of the day if apple iring is going to make your life easier and your organization is ready to adopt it's definitely good set to start moving on the other hand. If you're looking at you use case and you choose Dennis images and I've served out your entire user population or you're looking at some big organizational

barriers on the way that you do automation. That may be a red flag to potentially look in another direction again apple. Iring is a great tool that can be used by a large portion of our customers. We see out there, but if you're not one of them, that's okay. So hopefully that's probably not too many of you here which is why you're here today. So just want to review Samoa Slayer basic. The reason I'm calling us out again here is simply because we still get a lot of questions about this within the field again. This is so important

that we needed to just reiterate again Sneaky Pete's here start with an ISO installation of Windows and add in your hypervisor tools and capture that as your face o s Lair store a copy of this forever. Never delete it if you come away from the session with one thing it should be that because that gives you a clean copy that if you run into challenges with your OS later down the road, that's something that you can always shift back to without putting yourself in a situation where you have to rebuild a bunch of layers because as you know application layers are tied to

specific OS layers not operating systems. So if you have to come Restart your own Slayer from scratch same with a pliers that you had built with iOS layer. So that's something that I can't stress enough to keep in mind there. So what thing I think somewhere in there if you're doing a feature update Windows 10, make sure you make your disk size big enough when you do that. You set the size. Make sure you leave 30 good to do that update wheelie in the end store the files to get updated, but that way you'll make sure you have enough room and you don't run out of space when you do

there. Yep. Yeah, that's and that's going to be really important because again, you're going to be doing your Windows 10 feature updates within your Windows 10 OS lighter not creating a new OS liar so you don't have to rebuild your complex. Or it's something that I'm sure that you all have been chomping at the bit to to use or Ave already started applying since we last spoke user layers were still in Labs. So we didn't really have much to comment there. But since the last time we spoke they've been a ga ID for a 64-bit Windows 7 as well as Windows 10. So this is

essentially just read write elastic layer. So it's mounted a log on and after that mount process all rights, go to the user layer. Not just the right in these are contacts to really keep that in mind cuz I'm a PDS side. You're hardly going to see your cash getting touched. The next point there is because of this all your rights are going to be going out to this disk. So you're going to want to put this on Fast storage. We've seen the best success with this being put on flash storage. And of course you want to make sure it's highly available because if you lose connectivity to that user

layer for any particular reason in general that is pretty much get a hose up to the entire user session the next time it tries to write anything to it or read something on system cache already so note though that use away is great because it opens up some new use cases since he wants her seeing is using it for storing user profile data including the OST in the OneDrive cash. Also user-specific app install size is one of the key pieces since I've been touted as part of the functionality. That's great. But you know again just knowing that it mounts. As

user logs in not to laugh. So we compatible so it's going down that direction just keep that in mind. So again that actually then ties into the next piece which for those of you who have used DVD in the past and maybe are still on it. You're going to need to get off at soon. So user layer is one possible approach that you can take as part of that. The key thing to note though is a PVD loads much earlier in the stack. So some apps that the user had previously installed within their PVD and a flaring world's you may actually need to create a layer for that application. And

then for that out as a separate layered image there. So another key point there is just to make sure that you're analyzing two applications that you're using as part of this migration most of TV these customers that I've seen making this transition. We're going from Windows 7 to Windows 10 anyway, so it's a good opportunity to do that, but you're definitely getting Do you think about this as you make your switch went up there that you can do is if you're wondering if an apple work in the usual are cuz it has the elastic layer rules. You can always create a layer out of it and look

at the elastic V and if it fails the elastic fit Benji's pretty sure that it's not going to work in the usual are either you have to then put it into the images part of the image. Yep, and then one key things to know before I leave. This light here is handling bad news earlier contents. So today there is not a particularly good streamline process for handling this and what I mean by bad user content is one of user install something that is not going to work within the usual are so just make sure that you have the strategy for regularly taking backups of the user layers and

ideally a good help this process to restore from previous version in the event that your user is allowed to and does something that they're not supposed to This one we're going to go through pretty quick. But this is particularly important given it a flaring is really a c c r products. So we've been doing releases nearly on a monthly Cadence since we last spoke. So making sure that you're keeping the product up-to-date when you see new feature that you want or for a fix that you've been waiting for. This is going to be cute. So the general

procedures do this you're going to be downloading your media to your share going through the alarm upgrade process one key things to know to make sure you take a snapshot of your Elon because there is no way to go back otherwise to make sure you do that before. So if you can test everything out and then that way if you need to roll back you have that as a possibility. So once you've upgraded the alarm at that point, you should be updating your OS layers cuz he's release of a blaring is going to come with the updated wiring tools, which is really the set of scripts and other utilities that

comes with an OS so in the event that you've had manually updated some of those scripts for various reasons to accommodate one of your use cases, just make sure that once you run out date that you actually go back and essentially redo the script updates that you'd previously done because it's just going to ride over that obviously know once you've got your layering tools up to date then you're going to be pushed republishing your images which again is going to complish that and then also make sure you get the air filter Drive updates in there. Now

another topic that we talked about last time but no a lot more and now multi-alarm deployment. So why would you do this while they're the primary reason that we see as being a good reason is depending on where your packaging in publishing if you need to package and publish to multiple locations, it's generally good to have a multi-alarm architecture because you can do those operations locally. If you're having to do those over your when they're going to take a lot longer which can make the admin experience. What's good with in as you're going to the

operational other reasons we've seen that are valid are different admin groups for different images. Cuz while we cancel any roles we can save specifically that you can manage this set of layers of this set of images. And then on the other hands, why would you do single elim essentially? It's much less complex because you don't have to worry about replicating your layers across multiple alarms. So basically if you don't have a good reason to have multiple don't we see a lot of customers who say they want a separate one for Dev testing production, but don't actually

have a real need for that. So make sure that you're really looking at that and anyway, so when when making this decision process, you also know as you start to Pilot some of these cases because if you're doing an appointment and asked her for example, you're probably going to start small and you'll see how long the packaging and Publishing is going to take if you're going to be doing it that up there to start making that decision. Yeah, there are some really good use cases for multiple items. We have one customer that's got really low bandwidth really low like under

megabits per second in their data centers that doesn't work really well to have a single to publish the multiple places. So they'd applied install of their data centers around that way. They can pick which layers they want to push through which Data Center and keep them in sink. That way they can also have different admins in each data center to handle the security process of who's allowed to see what so we're going to move on to a player and Asher and this is a really important especially if you use a jury probably know it already. But if you're going looking at it when prove

the MCS connector and Azure and the old connector, we actually ran sysprep on the image when you published it which means you had to actually bring me image up and get it running in a VM first grade. I wrote a script to help with that but it took 45 minutes to an hour to do that. It really just add it to the process for no reason. We redid the connector so that now it doesn't run sysprep it published. The desk to Bob storage and you just have to use that three MCS. Right? So publishing now to Azure is a little about an hour less than it was before 4. 15 that change was made in Ford F15 last

year. So it's much better to have a few options. If you're only using Azure, it's easy. You're going to pick her up and ask her and see where it'll be. It'll perform really well doing that. However, if you're doing a dress kind of Dr. Or as your as extra capacity, let's say for your on-prem Elm, which is Midian xenserver or in vsphere you want to have the elm Inn xenserver or vsphere and then publish up to a sure if you're going to do a single. I'm a pro at home approached by the way the tools work of work better that way. It's also probably why you want to

work, right? Cuz you probably started in The Apprentice one to start out with her 10-gig would be better right than you would get a normal speed with publishing. If you don't have that then maybe the multi own design make sense right where you throwing them up and Azure do the next have a share between them and you can copy your images between those guys up to you got a few extra things out of a happy multi on there too that we talked about different happenings Etc if you do that. Another

thing to be understand about Azure. If you are doing the kind of hung Tran publishing up the edger, then the L need to be able to communicate to these endpoint and ask if you can't communicate them the API calls log into excetera won't work and the elm does it use a proxy in the sense that you have to make sure from a network standpoint that you're able to connect to these 10 points when you work with Microsoft to set up your express route ran so that you know the routing going to the right place. Otherwise, you won't get the album to work between both. I think somebody wrote A Blog on that

topic and that block just so happens to have that same list of things than just another really quick thing to know what I've seen happen at a lot of customers that is said before is that they'll have the large on from deployment. They want to dabble and Azure four examples, they're using her on-prem elements part of that and Publishing when they're doing that initial test is slow. But if that's your case, don't let that deter you because again when you go and do it for real, you're going to want to have one up there and Azure so you can do. Publishing locally.

And then at that point, you're only going to be sinking the layers as a change them pretty quick that way. All right, and we change this actually just recently in and change it down a little in this is an important change were changing the way that we're doing activation of office without clearing up this attention thing. It's not a tough have to layer but it's because of the licensing it makes it tough keeps the license for the versions of office into dat files that are monitored by the software protection platform that's managed by the system. So when you cradle are we

actually had to figure out how can we get the information from those dat files to the VA when you deploy that's what we actually do is we make a backup of those files when you're craving the lair using the command that makes that and then we have to get those two files on. Going to be today as the licensing files for office when it's there and the way we used to do that was we had a script and it would find Monitor the software protection platform enough software protection platform. Stop running cuz it runs automatically we were taught me those files. Sometimes it never stopped. So

that would cause problems where when you use it to the launch office wooden activate cuz it didn't really know office was installed. So we had the Roadster on Dead Files and you would get reconfiguring and we try to reconfigure office and then maybe it would work and you did a lot of help desk calls. So we do instead now is we still do the backup, but when we publish the image, we automatically insert those files right into the image so that we don't have to do that process on boot up. Toto much more reliable way to do it through Thwaites where we should have done it in the first place and

how do you implement that now that it's out? It's running and you're not new to this you're going to a diversion to Euro. Let's play are you going to do with Dan said with his update? We call him the gold image schools with the scripts that are part of the layer. So you have them in their final like that. Maybe you do it when you do Windows updates, right? So they go together and then you use that version of the OS to a diversion to your office later. Now what happens when you have urgent your office where the version of those that files is wrong because you had a diversion so it didn't get

updated. So you need to open office and run it that'll actually run the reconfigure. It'll put that version into those files. Then you run the Prep Prep which will back it up and we're putting them in a different location now, but anyone to program files you need us, so that'll put those files there and then importantly you need to remove the old ones that were backed up there. So that's that path Windows system32 App Store to backup from layer and if Delete those then our scripts will not try to copy over when they do that part, right? That'll skip that whole copy over part. And

the last thing you want to do in this process is rearm office again when she don't normally have to do any because you ran it to change those files and you want to rearm it to make sure it gets real hard. Right? So it's not really tough you do that. Say the layer when you're republishing the image will have this much more reliable mechanism to get Office activator than we had before. Couple things on the last declaring that our new first one to big one. Everyone concerned with login times elastic. Larry has a lot of time to login times has is what it starts who actually

change that now by elastic laser mounted simultaneous and they don't stop the login. So you login that go separately the layers get mounted in in their time and then go on to make Loggins Pastor there still a little bit more like in time read just the way it works, but it's not a lot of time it's a little bit of time. So the big issue here is engine 440. So when you upgrade to 4:14 or later, this just changes into comes with the fall. That means you really need to test well because Excuse me. Some applications

might not work with this method. They might have to be mounted before the login to actually work anything. That's Auto launch. Do you know where you have a schedule tasks for a logon script at launch is it you need to make sure house beforehand and we have a way to do that just called compatibility mode. Basically you edit the layer you going to the airplane settings and you click to enable compatibility mode and that'll tell it to do it the old way of the old way. I talked about this. So make sure your chest it's really important when you do this

migration all your lair. Next time you talk about is troubleshooting and this sites and the forms that that I answer questions on his will probably one of the top things that there are questions on right? My last declaring isn't working properly. Why isn't working the biggest thing here is the going to program data Unidad Lodge Boulder. There's a locked file in there that has incredible detail nitty-gritty about what elastic larynx happening still see things like the login time of the user of the mount time of all the apps

weather at Mount Snapper doesn't were Skips a nap and finish times any errors and other things that look like this. Hey, I'm logging into this user. I'm not playing these players are on that mountain meets layers for whatever reason I'm doing that, you know, I got an air I couldn't Mount the way they are right and hopefully some information on why couldn't do that. If not, at least until you got to go look and see what was going on with that later. But that is the most important thing in troubleshooting elastic layers. Alexa is the file share, right what's happening with your file share

and apple airing when we're mounting aware. We're really just doing the exact same thing you would do if you went to the share right click and said now so you can do that, right? That's a good test. Can I go to the share? Can I right click on one of the layer files and say now to do I get an error from Windows when I do that. Usually it's a permission. Most of the time. These are either permission problems or DNS problems, but mostly it's permission problems that cause problems with the share want to make sure that there's a set of Json files that Define who gets what layers

You need to make sure those are there if there aren't there talking to drive the rest of all this process for that one other thing there that was wearing in your image Cube template so that it's turned on when it's another big one for you two layers permissions on the share a little different but they're the exact same permissions you would use on a home drive, right? So if you have set up a home driveway or the Creator owner gets rights to all the files underneath and then you give admin rights to everything. That's the way that you set up the

usual are as well. Usually Episode just a few quick things to note there as well. When you're in the process of upgrading from a pre for 14 version to a post for 14 version. If you don't have time to thoroughly test each of your a player soon dance other sexually registry key where you can change their behavior on the Laird image such that it amounts all elastic layers in that compatibility mode. So it loads it before the logon precedes which could give you some time to publish a test image that doesn't have the registry key set. And then you could go through safely

eat each year layers without without without having to worry about disrupting normal operations as part of that purpose if you don't have the time but you do custom one way or the other couple other things about elastic Larry write the system has to reboot when you're using elastic layers. The system has to reboot on logout right the way that the layers Remove is not because the usual I got it's cuz of Machinery boots once they're attached or detached. So, you know, that's the default for non-persistent vdi some

people want to use static you can use static. If you can't have it after reboot a log out as part of that we do get, you know, when were using elastic laying our systems are slow or not working the same. So there is a Performance Kit to using elastic layers that usually pretty small not a noticeable thing. It might be most noticeable when you first open an application that takes a little longer to launch because we have to load things a little differently there. And then the second time you loaded it would be fast, right? But the performance of the application shouldn't really be any

different without player. It doesn't have that. Cypress. So where you want to look at there is what kind of storage you're using is a fast enough generally do the stuff on flash storage. But if you're not what matters if it's usually really kind of has to be flash storage, right? It's not going to work well on non-flat stores cuz all the rights of the usual are going to that night. So be aware of that one other thing is if you have a layer that has an extremely large registry that doesn't work. Well elastically because we can't load the whole thing into memory. So it's kind of

swapping out if there's a lot of calls. So if you have a you know officers is an example 500,000 registry entries are visual studio things like that. You put them in the image and they work much better than as an elastic player. If you're using the usual layer in you have a failure of an install than the user has to go and kind of clear that out the next time the food. So let's say they didn't know they installed something girl driver not going to work, right? So I have to do an uninstall when it reboots when they find out it's not working. But if you need something to be deleted so

that you can see files underneath there from the usual are you can't just delete them. They're going to delete him cuz you will remember that deletes where you can do his mouth of yours earlier on another machine and delete them. Then we won't remember the deletes, right? We will keep track of those is tweets so you can actually remove them like they were never there as opposed to actually deleting something. We're we're actually going to remember that it was deleted and Mark. So you won't see the file that is in a layer underneath the usual are Witcher, of course all the other layers on the

image. And the last thing therefore use your layers don't delete the profile on light off for obvious reasons. Is going to delete the profile out of the year. Later. Do that. MPS another one that generates a lot of things out the forms when we usually see is is we get rearms to fail right sometimes and almost all the time when it turns out there's a Time sync problem with the published Master image when it comes up and what happens if you don't use a template, there's actually didn't see em with

the time zone CET. The virtual bias has UTC is its time zone. So when that machine boots up if thinks UTC is the time zone for here in a different time zone, so it's always for 5 hours off there for the entire process can't log into the machine. The rearm sales you really need to do is take your machine and then when you deploy your master and make sure that template it'll all work. Okay, right. You won't have to worry about that. Still worth disabling MCS is rearms I think cuz there's no need to do that

without playing that's a non-apple everything we rearm in the lair and then we rearm Windows automatically right on so for their you can use command Peter by catalog or for the whole TV. She needs you the command to disable rearms right to do my catalog and this will all be posted. Right so, you know, this is if you do if I did you see any advantage to do that. You won't get any of those are the times you think doesn't actually matter on the VM. No matter is for the process of creating them one bad thing. Isn't this whole

radar thing and Citrix Cloud probably so you'll just have to live with the air but it'll all work fine and you go to use it. One last thing I was like to talk about testing. It's one of my favorite discussion points, right? Cuz I think it's one of the most important things not just wrap wearing butt. With Citrix doesn't isolate applications like a p does Frank. So that's on purpose. Right? We want all the applications to work easily with each other which they do but it does me because where we are creating an isolation that you really do

have to worry about them conflicting if they might do that, right and what that means is that you have to throw it out the production right away and not worry about that problem is and that way we don't capture what a process is doing. We capture everything that happens on the packaging machine when it happens. Sometimes you get stuff you didn't intend to get and things don't work. Do you have to test you always have to test no matter how small the difference is one thing you can do is you can

test as an elastic layer that makes it easier going to have to push up an image and do all that stuff. Elastic where it's at Esters and say go test it only good for smoke testing. Unless you're using a lactic the last eclairs. You still need to include that in an image as your next test publishing is an image have the app owners test. Apple is going to reset so well either so I really like the last time I was here which is either I caught three prong ordinary testing, right? That's where you take your image. If you're going to roll out to everyone you don't roll it out to everyone. Out to

tend to 20% of your garment first you let that cook for let's say you're free boots on the weekend for excellence that cook for a week at 10 to 20% extra capacity. So the worst that happens if you start to get calls, you just put those machines in maintenance mode everybody moves over to the rest of the machines, right and then you go fix your problem and do it again do next weekend. You roll out to the other day that you're 90% You're pretty certain now cuz it's really didn't use that. It's going to work. Okay, and then you start the other process over again if I have changes right eye

roll back to the 10 to 20 and you just keep rolling that way. It's a very successful way to roll test how to really know what's happening with your images. And I think he'll keep everybody much happier than every environment right? And by the way, I recommend that every Centric customer has nothing to do with a Pearl Earring. F1 really fixing to add there. Is it while a flaring does not isolate apps in the way that I feed does elastic layers the reeds are isolated from each other when we're talking about multiple users on as an observer is an example. So however,

any of the rights to any common files, he might have between two applications would be going to the same place. There's not per user. So maybe possible to have different versions of the same application as an example on the same setup server used by separate user communities. Yes, it may be possible for you to have to test because it depends on whether those are writing to files that could be potentially shared. All right. Now we're going to change gears a bit a little less technical or more what's going on and Dan Lazar our doctor who is going to take us to the future of a

playroom? Another round of applause for this guy. Thanks. I like to see him turn purple also. Tell the future of a player in actually before we get to the future. I want to go back a little bit. So as was mentioned earlier, we be released. So we going to go back and talk briefly about the last couple releases we've had so in case you guys haven't been aware of what we've been doing. So in between version 1902 and 1903 the product we did make some improvements in the area performance specifically with the hyper-v connector that we added to the product last year. We been working hard to optimize

performance in the park overall in this is the Benson we've been getting some good results by decreasing or a player creation X there. We are continuously working to improve platform support with a blaring and we've added within the 1902 release. We added support for Windows 10 version 1809 as an Apple Air or as a player we did release a new Azure connector for a gun. And we are now supporting layering appliances running on server 2019 hyper-v. We made some usability improvements to the product the ability to

package and publish on hyper-v 2019 host part of the hyper-v connector work we're doing and we've been continuously improving Security in the product by adding TLS 1.2 support for all that. So and then coming real soon. We're hoping in the next week or two will be releasing on 1905. There are additional platform enhancements that are coming in version 1905. We will be adding server 2019 as an OS layer. We will be also adding office 2019 as an apple are we will be officially supporting virtual apps and

desktops 1903 current release and the LT sr7010 Camille cumulative update for and provisioning services 1903. We are also continuously as I said improving the connector for the connector behaviors for hyper-v were changing the behavior here to provide progress as a percentage as opposed to last time, which is a little bit easier to work with and then on the security side. We're adding TLS support for email notifications that gets sent from the appliance. So that's that's that's all coming very soon. So now the the

future of a blaring so as you look here, I want you to kind of think back to what Dan had said earlier around a player. So, you know, we we we talk to customers all the time and we we believe truly in the value of that Apple Larry has but we do understand that there's an investment that goes into adopting the technology so really when we were talking about priorities for a player and coming this year and into next year. We're really trying to focus on two areas that really try to directly Target that investment that that you guys are

making an in trying to to utilize this technology and that's really around integration and around automation. These are two characteristics in the product that we feel are our where there's some limitations that that prevent people from really fully document technology in as we said, we really believe that it's worth adopting. So we wanted to dress though. So that the first one I want to talk about here is New future we're calling the user personalization layer for Citrix virtual apps and desktops. So this is a feature that currently in a very early preview. And essentially what we're

doing here is we are taking the user layer technology that currently exist in the app layering product and we're kind of integrating that directly into virtual apps on desktop. So this is going to be a new feature of virtual desktops. It's a feature which gets deployed along with the VA when you install it the driver components that an able to use earlier will be part of the VA in the configuration that you can apply to define. The repositories will use a layer is attached will be something that you can configure from see that in studios. Well, this is initially or originally we

were positioning this as a functional replacement for PVD cuz we know as as was said previously there's a lot of customers out there who really are still relying on TVD or are still looking for a user personalization or used? Persistence of a technology that really works for them. We are targeting this feature for that but really it's also a next-generation feature. This feature will not require the deployment of layering Appliance to utilize it it will still require a repository on a Windows file share in the environment where the VTA the running but again, it's configurable

ultimately and what's really cool is it fully supports non-persistent food catalogs with DVD of course does not fully supports Windows 10 has the full capabilities that the user layer feature has an app layering today, but it's really a direct integration in to see that and therefore we hope will be easier to adopt for customers who haven't been really able to do that for me to go to the app layering product solution. So that's pretty exciting. We are also as you guys probably heard the keynote there is a great interest all around the company for supporting Microsoft new

Windows Virtual desktop solution and Azure as part of that. We have a mandate with an apple are going to have Day One support for Windows 10 DVD as well. And then on the automation topic, so this was also pretty exciting. We're working on a full scope. Larry management API. It's it's a an API that hosted in Citrix Cloud, but compatible with your on-prem Larry appliances and when we release it, the goal here is to enable the full automation of the layering management tasks that I'm talking to our customers talking to you guys that we found

rrr, you know, that that can be a struggle for first shots were heavily dependent on automation. Initially will be releasing with basic Larry management capabilities. So the ability to create new Apple Air has the ability to create an ocular versions the ability to publish new new a players and things like that. We will be continually continuously working on this API to improve it will be expanding the scope of it. And ultimately this API is going to drive a lot of the future work. We do an apple a ring around making up Larry more of a consumption service for for the

rest of our pictures also called you before the end of this year. We're hoping in the Q3 time frame will be releasing an early Tech preview for the API as well that you guys can sign up for and try out. So that's pretty cool and then laughs in this this kind of Pies into the other two themes around Automation and in an integration is we're building a new architecture a new Highly scalable and Performing architecture for a flaring this is in an effort to get

the product to scale better than has previously and to allow it to more natively operate in Cloud environments and in any environment where where we met at Target in the future, so look for these enhancements in hyper-v, because from a technological standpoint, it's the easier platform of the quicker platform for us to deploy, but this architecture is going to fall off through into all of the platforms that we support for that blaring. So keep an eye out on that, too. And then if you guys have a chance this week, we are actually demoing

the preview of the user personalization layer. So if you guys head over to the Pacific to experience Center how you can take a look here on the slide. There's a demo booth that we have in one of our a player Engineers is running the demo this week. I definitely encourage you to go check it out and ask him all the questions that you have about the product in about this feature. So and that pretty much wraps up a you know, there's a few other sessions that we have available this week that we encourage you guys to check out and then lastly here.

If you enjoyed the session and if this was valuable for you, please give us a rating. We we like sevens right now. Anna thanks. Everybody likes.

Cackle comments for the website

Buy this talk

Access to the talk “Citrix Synergy TV - SYN208 - Citrix App Layering: top 10 lessons from the field 2.0”
Available
In cart
Free
Free
Free
Free
Free
Free

Access to all the recordings of the event

Get access to all videos “Citrix Synergy Atlanta 2019”
Available
In cart
Free
Free
Free
Free
Free
Free
Ticket

Interested in topic “Software development”?

You might be interested in videos from this event

September 28, 2018
Moscow
16
129
app store, apps, development, google play, mobile, soft

Buy this video

Video

Access to the talk “Citrix Synergy TV - SYN208 - Citrix App Layering: top 10 lessons from the field 2.0”
Available
In cart
Free
Free
Free
Free
Free
Free

Conference Cast

With ConferenceCast.tv, you get access to our library of the world's best conference talks.

Conference Cast
525 conferences
20515 speakers
7489 hours of content