welcome to citrix app layering top 10 lessons from the field version 2 and beyond so the reason for the title is that this session is actually follow-up to the one that Rob's illowsky and I did last year with our top 10 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 that we've been working with ever since so we wanted to make sure that we shared some of the additional things we learned since then and additionally we want to take the opportunity that we're also welcoming Dan Lazar another stage with us the product manager wrap layering to give you a little bit of an overview of where the products team head is at for the future of a player ring so just some quick intros for those of you don't know me I'm Dan Morgan a senior architect than our citrix consulting team based on northeast and this is Rob's illowsky who requires no introduction everyone please give the man a round of applause because I can't answer your forum posts he only does that to get him to turn purple yeah it's it's fun watching Rob turn purple at all these presentations so anyway moving along we're not really gonna repeat things from last year where possible and we're gonna keep it primarily focused on new content we have a packed agenda for you here today so we're not gonna be taking questions during the session but we'll be around throughout the entirety of the conference feel free to stop us in the hallway ask whatever your questions that you want and we're all staying at the Marriott so if you find us at the Marriott bar you can definitely get some more information from us there after the presentations are over so this is a lesson I really wished that we had actually dressed the last time that we're here how do I know I need a plain ring so this is a really important question for those of you who are still early in your journey or looking to embark upon the journey because using a plain ring really is an investment because once you decide to go down that route you're gonna have to do some work make sure that you get all of your applications and layers and all of your operating system platforms and layers so the two things to factor in when you're making that decision is first off we'll app layering make your life easier so a few of the key things to look for the first one being image sprawl so the more images you have the more of an operational benefit that you're gonna get from using a products like a player and 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 count to maintain something for example on pram and vSphere and also putting additional services and Azure additionally I know that many of the customers in my patch have had use cases that they've wanted to address with non persistent solutions but haven't been able to because of you know just they were thinking about the image sprawl that would result from having to deal with all the one-off application sets from different user populations that they were looking to address this can really help mitigate that the next question though to ask is is your organization ready to adopt so as you all know a pyrene requires a non persistent image management solution so if you're already using PBS or MCS great Apple airings going to streamline right into your existing operations on the other hand if you're not using PVS or MCS today 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 and management so another thing to look out for is to what degree you have your entire builds and management process automated unfortunately today we don't have api's for the citrix app layering product so that may be a little bit more difficult to slipstream into a fully DevOps environment let's 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 a little bit additionally we found some obstacles and customers with very rigid image build standards which we're gonna cover in a bit if you don't do your OS layer the app layering way you're putting yourself at risk so you really need to factor this in when determining whether or not to go down this path and finally Amazon Web Services if you're looking to employ completely an AWS unfortunately today we don't have an enterprise layer manager appliance for AWS or we don't have a connector yet either at this point so you'll face some challenges if you're only going that direction so at the end of the day if a plan ring is gonna make your life easier and your organization is ready to adopt it's definitely a good fit to start moving on the other hand if you're looking at your use case and you have you know to Zen up images and that serves 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 app layering 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 some OS layer basics the reason I'm calling this out again here is simply because we still get a lot of questions about this within the field the again this is so important that we needed to just reiterate it again so the key piece here start with an ISO installation of Windows and add in your hypervisor tools and capture that as your base OS layer store a copy of this forever never delete it if you come away from this session with one thing it should be that because that gives you a clean copy that if you run into challenges with your OS layer 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 completely start your OS layer from scratch seam with a players that you had built with iOS layers so that's something that I can't stress enough to keep in mind there so one thing I think is important 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 we only in the end store the files that get updated but that way you'll make sure you have enough room and you don't run out of space when you're doing the upgrade yep yeah and that's and that's gonna be really important because again you're gonna be doing your Windows 10 feature updates within your Windows 10 OS layer not creating a new OS layer such a you don't have to rebuild your app layers all right it's something I'm sure that you all have been shopping in a bit to use or I've already started deploying since we last spoke user layers we're still in labs so we didn't really have much to comment there but since the last time we spoke they've been g84 64-bit windows 7 as well as Windows 10 so this is essentially just a readwrite elastic layer so it's mounted a log on and after that mount process all rights go to the user layer not just the rights in the users context so really keep that in mind because on the PBS side you're hardly going to see your cash getting touched the next point there is it because of this all your rights are going to be going out to this disc 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 going to hose up 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 usually is great because it opens up some new use cases some key ones that we're seeing is using it for storing user profile data including the OST in the onedrive cache also user specific app installs as one of the key pieces that's obviously been touted as part of the functionality that's great but you know again just knowing that it mounts as the user logs in not allow absolutely compatible so if 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 PVD in the past and maybe are still on it you're gonna need to get off it soon so user layer is one possible approach that you can take as part of that the key thing to note though is that PVD loads much earlier in the stack so some apps that the user had previously installed within their PVD in Apple aring worlds you may actually need to create a layer for that application and then fork that out as a separate layered image there so the another key point there is just that make sure that you're analyzing the applications that you're using as part of this migration most of pvd's customers that i've seen making this transition we're going from windows 7 to Windows 10 anyway so is a good opportunity to do that but you're definitely going to need to think about this as you make your switch one tip there that you can do is if you're wondering if an Apple work in the user layer because it has at last declare rules you can always create a lair out of it and look at the elastic fit and if it fails the elastic fit then you're pretty sure that it's not going to work in the usual layer either you'd have to then put it into the image as part of the image yep and then one key thing to note before I leave this slide here is handling bad user layer contents so today there's not a particularly good streamlined process for handling this and what I mean by bad user contents is when a user installs something that is not going to work within the user layer so just make sure that you have a strategy for regularly taking backups of the user layers and ideally a good helpdesk process to restore from a 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 the app layering is really a see our product so we've been doing releases nearly on a monthly cadence since we last spoke so making sure that you're keeping the products up-to-date when you see a new feature that you want or for a fix that you've been waiting for this is going to be a key process so the general procedure to do this you're going to be downloading your media to your share going through the LM upgrade process one key thing to know make sure you take a snapshot of your Elan because there's no way to go back otherwise so make sure you do that before such a you can test everything out and then that way if you need to rollback you have that as a possibility so once you've upgraded the ALM at that point you should be updating your OS layers because each release of Apple airing is going to come with updated layering tools which is really the set of scripts and other utilities that comes that's within the OS so in the event that you had manually updated some of those scripts for various reasons to accommodate one of your use cases just make sure that once you run that update that you actually go back and essentially redo the script updates that you had previously done because it's just going to write over that obviously and then once you've got your layering tools up to date then you're going to be push republishing your images which again it's going to accomplish that and then also make sure you get the filter Drive updates in there now another topic that we talked about last time but know a lot more on now Multi elem deployments so why would you do this well they're the primary reason that we see as being a good reason is depending on where your packaging and publishing if you need to package and publish to multiple locations it's generally good to have a multi gilliam architecture because you can do those operations locally if you're having to do those over your when they're gonna take a lot longer which can make the admin experience less good within as you're going through the operational other reasons that we've seen that are valid are different admin groups for different images because while we can delineate roles we can't 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 a single um essentially it's much less complex because you don't have to worry about replicating your layers across multiple LMS so basically if you don't have a good reason to have them multiple don't we see a lot of customers who say they want a separate one for dev tests and 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'll also know as you start to pilot some of these use cases because if you're doing a deployment in Azure 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 Elms we have one customer that's got really low bandwidth really low like 100 megabits per second between their data centers that doesn't work really well to have a single to publish to multiple places so they deployed all of their data centers are in that way they can pick which layers they want to push to which data center and keep them in sync that way they can also have different admins in each data center to handle that security process of who's allowed to see what so we're going to move on to Apple Area and Azure and this is a really important one especially if you use Azure you probably know it already but if you're go looking at it we improve the MCs connector and Azure and the old connector we actually ran sysprep on the image when we published it which means you had to actually bring the image up and get it running in a VM first right I wrote a script to help with that but it took 45 minutes to an hour to do that it really just added to the process for no reason we redid the connector so that now it doesn't run so scrap it publishes the disk to blob storage and you just have to use that through 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 4.15 last year so it's much better home placement with Azure you have a few options if you're only using Azure it's easy you're gonna put your al manager that's where it'll be it'll perform really well doing that however if you're doing as Ria's kind of dr or azure as extra capacity let's say for your on-prem Elm which is millions and server or in vSphere you'll want to have the Elm within at Zen server or vSphere and then publish up to Azure if you're gonna do a single Emma Pro the home approach right the way the tools work will work better that way it's also probably the way you want to work right because you probably started in the I'm premise one just start out with for that to work well you need at least a gigabit a bandwidth up to Azure ten gig would be better right then you would get normal speed with publishing if you don't have that then maybe the multi yellow design makes sense right where you throwing em up in Azure you're gonna have a share between them and you can copy your images between those guys up to Azure you get a few extra things out of having multi on there too that we talked about different admins etc if you do that okay another thing to be understand about Asia if you are doing the kind of I'm Prem publishing up to Azure then the L needs to be able to communicate to these end points in Azure if it can't communicate them the API calls and logins etc won't work and the Elm doesn't use a proxy the CentOS won't process you have to make sure from a network standpoint that you're able to connect to these endpoints when you work with Microsoft to set up your Express route right so that you know the routing is going to the right place otherwise you won't get the Elm to work between both I think somebody wrote a blog on that topic and that blog just so happens to have that same list of things that anyway just another really quick thing to note what I've seen happen at a lot of customers has said before is that they'll have a large on Prem deployment they want to dabble in Azure for example so they're using her on Prem element as 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 gonna want to have one up there in Azure so you can do that publishing locally and then at that point you're only gonna be syncing the layers has it changed them it's pretty quick that way all right switching gears a little this is an important topic and we change this actually just recently and it's changing again a little and this is an important change we're changing the way that we're doing activation of office with that blaring office it's interesting it's not a tough app to layer but it's because of the licensing that makes it tough office keeps the license for the versions of office in to debt files that are monitored by the software protection platform right that's managed by the system so when you create a layer we actually had to figure out how can we get the information from those data files to the BDA when you deploy it so what we actually do is we make a backup of those files when you're creating the layer using the prep command that makes that and then we have to get those two files on to the VDA 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 monitor the software protection platform when the software protection platform stopped running because it runs automatically we would copy those files sometimes it never stopped that would cause problems where when your users would launch office wouldn't activate because it didn't really know office was installed since it had the wrong data files and you would get reconfiguring and it would try to reconfigure office and then maybe it would work and you get 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 so it's a much more reliable way to do it truthfully it's the way we should have done it in the first place now how do you implement that now that it's out so assuming you already have office running and you're not new to this you're gonna add a version to your OS layer you're going to do with Dan said which is update we call them the golden itch tools but the scripts that are part of the layer so you have them in there finalize 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 add a version to your office layer now what happens when you add a version to your office layer the version of those dat files is wrong because you added a version so it didn't get updated so you need to OpenOffice and run it that'll actually run the reconfigure it'll put that version into those files then you run the prep script which will back it up and we're putting them in a different location now putting in one two Program Files you to desk so that'll put those files there and then importantly you need to remove the old ones that we're backed up there so that's that path windows system32 app store to backup from layer and if you delete those then our scripts will not try to copy over when they do that Park right that'll skip that whole copy over part and the last thing you want to do in this process is rearm office again which you don't normally have to do in the ANA version because you ran it to change those files then you want to rearm it to make sure it gets reared right so it's not really tough you do that save the layer and when you republish the image you'll have this much more reliable mechanism to get office activated than what you had before a couple things on elastic layering that are new first ones a big one everyone's concerned with log in times elastic Larry adds a lot of time to log in times is what it's thought so we actually changed that now by default elastic layers are mounted kind of simultaneous and they don't stop the login so you log in that goes separately the layers get mounted and in their time and you can go on to make logins faster there's still a little bit more login time right 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 that's a change right so if you were running elastic layering before this changed in 414 so when you upgrade to 4 or 14 or later this just changes and becomes the default 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 launched you know where you have a scheduled task for a logon script that launches it you need to make sure that it mounts beforehand and we have a way to do that just call compatibility mode basically you edit the layer you go into the app layering settings and you click enable compatibility mode and that will tell it to do it the old way right and launch it the old way I talked about this so make sure you test it's really important when you do this migration all your layers next thing you talk about is troubleshooting right and this I'd say on the forums that that I answer questions on is probably one of the top things that there are questions on right my elastic blaring isn't working properly why isn't it working the biggest thing here is to go into program data you need s logs folder there's a log file in there that has incredible detail nitty gritty about what elastic layering is happening you'll see things like the log in time of the user the amount time of all the apps whether it mounts an app or doesn't or skips an app and finish times any errors and you know this things will look like this hey I'm logging in to this user mapping these layers or I'm not mounting these layers for whatever reason I'm doing that you know I got an error I couldn't mount right and hopefully some information on why I couldn't do that if not at least to tells you you got to go and look and see what was going on with that layer but that log isn't the most important thing in troubleshooting elastic layers the next thing is the file share right what's happening with your file share and dep blaring when we're mounting a layer we're really just doing the exact same thing you would do if you went to the share right-click and said mount 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 mount or do I get an error from Windows when I do that usually it's a permission quite often most of the time these are either permission problems or DNS problems but mostly it's permission problems that cause problems with the share you do also want to make sure that there's a set of JSON files that define who gets what layers you're not planning you need to make sure those are there if there aren't there it's not going to drive the rest of all this process for that one other thing there that economist was also you want to make sure that you enable elastic layering in your image template so they it's turned on right that's another big one lastly for user 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 drive where I'm 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 user layer as well usually so just a few quick things to note there as well when you're in the process of upgrading from a pre 414 version to a post-war 14 version if you don't have time to thoroughly test each of your app layers in advance there's actually a registry key where you can change the havior on layered image such that it mounts all elastic layers in that compatibility mode so it loads it before the logon proceeds which could give you some time to publish a test image that doesn't have that registry key set and then you could go through safely each each year layers without which out without having to worry about disrupting normal operations as part of that perfect right which is definitely something if you don't have the time right but you do want to test them one way or the other a couple other things about elastic layering right the system has to reboot when you're using elastic layers the system has to reboot on logout right the way that the layers get removed is not because the usual logout it's because the machine reboots once they're attached they're attached so you know that's the default for a non persistent BDI some people want to use static you can use static but you can't have it you have to have a reboot on logout right that's part of that we do get you know when we're using elastic layering our systems are slow or sluggish right they're not working the same so there is a performance hit - using elastic layers it's usually pretty small not a noticeable thing it might be most noticeable when you first open an application that it takes a little longer to launch because we have to load things a little differently there and then the second time you load it it would be fast right but the performance of the application shouldn't really be any different with a player it doesn't have that type of stuff so what you want to look at there is what kind of storage you're using is it fast enough generally you do this stuff on flash storage but if you're not you know it matters if it's user layer it really kind of has to be flash storage right it's not going to work well on non flash storage because all the rights with the user layer go into that right so be aware of that one the other thing is if you have a layer that has an extremely large registry that doesn't work well elastically because and 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 office is an example 500,000 registry entries or visual studio things like that you put them in the image and they work much better than as an elastic layer right if you're using the user layer and you have a failure of an install then the user has to go and kind of clear that out the next time it boots let's say they didn't know they installed something with a kernel driver it's not going to work right they'll 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 user layer you can't just delete them can't go in and delete them because we'll remember the deletes what you can do is Mount the user layer on another machine and delete them and we won't remember the deletes right we will keep track of those is deletes so you can actually remove them like they were never there as opposed to actively deleting something where we're actually going to remember that it was deleted and marked that so you won't see the file that is in a layer underneath the user layer which are of course all the other layers on the image and the last thing there for user layers don't delete the profile on logoff for obvious reasons right it's going to delete the profile out of the user layer do that MCs right this one another one that generates a lot of things out the forum's what we usually see is as we get rearmed to fail right sometimes and almost all the time what it turns out to is a time sync problem with the published master image when it comes up and what happens is if you don't use a template that has actually been a VM with the timezone set the virtual bias has UTC as its timezone so when that machine boots up it thinks UTC is the timezone but you're in a different time zone so it's always four or five hours off therefore the MCS process can't login to the Machine the rearm fails what you really need to do is take your golden image that you started with that was a VM and has the right bios and all that clone that and use that as your template you know configure it however you want your machines to be configured and then when you deploy your master imager that template it'll all work okay right you won't have to worry about that still worth disabling MCS ESRI arms I think because there's no need to do that with that player that's an on a player thing we rearm in the lair and then we rearm windows automatically right on boot so for there you can use commands either by catalog or for the whole DDC these are the commands to disable rearmed right if you're doing buy catalog and this will all be posted right so you know it's like write these down this is if you do it by GDC [Music] and the advantage there is if you do that you won't get any of those rearm errors either way right and the time something doesn't actually matter on the VMS it only matters for the process of creating them one bad thing is in this whole rearm thing in Citrix cloud the SDK doesn't include those commands like for you to run remotely so you just have to live with the error but it'll all work fine and you go to use it one last thing and I was like to talk about testing it's one of my favorite discussion points right because I think it's one of the most important things not just for a planning but period with Citrix Apple airing doesn't isolate applications like Appy does right 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 we're we are creating these in 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 test them well right you can't just say I'm gonna make a little change to a layer and since it was just a little change I'm gonna roll it out to production right away and not worry about that problem is an app player and 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 so 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 right that makes it easier you don't have to push up an image and do all that stuff you just have to sign the elastic layer to testers and say go test it it's only good for smoke testing unless you're using elastic elastic layers you still need to you're going to include that in an image as your next test publish it as an image have the app owners test it hep owners don't always test so well either right so I really like the last kind of bullet here which is either I call a pre prod where canary testing right that's where you take your image that you're going to roll out to everyone you don't roll it out to everyone you roll it out to 10 to 20% of your environment first you let that cook for let's say your reboots are on the weekend right so that cook for a week have 10 to 20% extra capacity so the worst that happens is 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 your next weekend you roll out to the other 80 or 90 percent you're pretty certain now because it's really been news that it's going to work okay and then you start the other process over again if I have changes right I roll that to the 10 to 20 and you just keep rolling that way it's a very successful way to roll tests out to really know what's happening with your images and I think it'll keep everybody much happier in every environment right and by the way I recommend that at every situation customer has nothing to do with that player one really quick thing to add there is that while Apple airing does not isolate apps in a way that Fe does elastic layers the reads are isolated from each other when we're talking about multiple users on as an observer as an example so however any of the rights to any common files you might have between two applications would be going for the same place that is not per user so may it be 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 but you'd have to test because it depends on whether those are writing to files that could be potentially shared all right so 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 Apple Aaron thanks Rob another round of applause for this guy Thanks I like to see them turn purple also so the future of a player actually before we get to the future I want to go back a little bit so as was mentioned earlier we we release a flaring roughly on a monthly cadence so we I'm gonna go back and talk briefly about the last couple releases we've had so in case you guys haven't been you know aware of what we've been doing so in between version 1902 and 1903 of the product we did make some improvements in the area of performance specifically with the hyper V connector that we added to the product last year we've really been working hard to optimize performance in the product overall and this has been some we've been getting some good results out of by decreasing our a player creation times there we are continuously working to improve platform support without blaring and we've added within the 1902 release we added support for Windows 10 version 1809 as an a player or as an OS layer we did release a new Azure connector for Azure gov and we are now supporting layering appliances running on server 2019 hyper-v we've made some usability improvements to the product the ability to package and publish on hyper-v 2019 hosts as 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 LDAP query so and then coming real soon we're hoping in the next week or two we'll be releasing 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 a player we will be officially supporting virtual apps and desktops 1903 current release and the LTS our 715 cumulative cumulative update 4 and provisioning services 1903 we are also continuously as I said improving the connector connected behaviors for hyper-v were changing the behavior here to provide progress as a percentage as opposed to elapsed time which is a little bit easier to to work with and then on the security side we're adding TLS support for email notifications that get 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 Apple airing as an investment so you know we we talked to customers all the time and we believe truly in the value add that Apple airing has but we do understand that there's an investment that goes into adopting the technology so really when we're talking about priorities for Apple airing 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 in trying to utilize this technology and that's really around integration and around automation these are two characteristics in the product that we feel are where there are some limitations that that prevent people from really fully adopting the technology and as they said we really believe that it's worth adopting so we want to address those so the the first one I want to talk about here is a new feature we're calling the user personalization layer for Citrix virtual apps and desktops so this is a feature that's currently in a very early preview and essentially what we're doing here is we are taking the user layer technology that currently exists in the app wearing product and we're kind of integrating that directly into virtual apps and desktops so this is going to be a new feature of virtual apps and desktops it's a feature which get to deploy it along with the VDA when you install it the the driver components that enable the user layer will be part of the VDA and the configuration that you can apply to define the repositories where the user layers attach will be something that you can configure from see that in studio as well this is initially or originally we were positioning this as a replacement for PVD because we know as was said previously there's a lot of customers out there who really are still relying on PVD or are still looking for a user personalization or user persistence 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 a layering appliance to utilize it it will still require a repository on a Windows file share in the environment where the VDA is are running but again it's configurable through Studio ultimately and what's really cool is it fully supports non-persistent pooled catalogs which PVD of course does not fully supports Windows 10 has the full capabilities that the full user layer feature has an app layering today but it's really a direct integration and to see that and therefore we hope will be easier to adopt for customers who haven't been really able to do that forklift to the to the Apple airing product solution so that's pretty exciting we are also as you guys probably heard the keynote there's a great interest all around the company for supporting Microsoft's new Windows virtual desktop solution in Azure as part of that we have a mandate with an app layering to have day1 support for Windows 10 EVD as well and then on the on the automation topic so this one's also pretty exciting we're we're working on a full scope layering management API it's it's a an API that's hosted in Citrix cloud but compatible with your on-prem layering appliances and when we release it the goal here is to enable the full automation of the layering management tasks that from talking to our customers talking to you guys that we found our you know that that can be a struggle for four shops who are heavily dependent on automation initially it will be releasing with basic layering management capabilities so the ability to create new a players the ability to create new a player versions the ability to publish new new a player's and things like that we will be continually continuously working on this API to improve it we'll be expanding the scope of it and ultimately this API is going to drive a lot of the future work we do in a playing around making a blaring more of a consumption service for the rest of our digital party I asked for that 10 years ago that's so exciting so you'll also be excited to know that in about before the end of this year we're hoping in the q3 timeframe we'll 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 lastly and this this kind of ties into really the other two themes around automation and integration is we're hard at work building a new architecture a new highly scalable and performant architecture for apple airing this isn't an effort to get the product to scale better than it has previously and to allow it to more natively operate in cloud environments and any environment where where we may target it in the future so look for we're initially targeting these enhancements in hyper-v because from a technological standpoint it's the easier platform and the quicker platform for us to deploy but this architecture is going to follow through into all of the platforms that we support with 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 Citrix experience Center you can take a look here on the slide there's a demo booth that we have and one of our app learning 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 and about this feature so and that pretty much wraps this up 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 this session and if this was valuable for you please give us a rating we we like sevens right guys seventh 7/7 7s and that's it thanks everybody thanks for coming [Applause]