 Hey folks, Ned Pyle, Program Manager in Windows Server here again from Ignite. I'm going to talk to you about something that we just announced a little bit ago. You may not have noticed it, you may not have heard about it, but it is hot-patching for Windows Server. Now, if you've been paying attention, we've had hot-patch in Windows Server Azure Edition now for about two years. But if you're not heavily into Azure, if you're not into IaaS stuff, if you're working some other cloud, if you're mainly on-prem, you might not even heard about this. Hot-patches are the ability for you to get a security update, patch Tuesday style, bazillions of fixes and not reboot. That's all it is. So, most of the year, instead of every single patch Tuesday rebooting your server, you'll get patched, you'll become secure instantly, and you will not restart. Your processes won't restart, nothing happens at all. So, we decided to put this into regular Windows Server Vnext. And so what you'll be able to do is arc-enable a server, subscribe to this patch service. May or may not be some kind of like moderate fee to this way, I don't really haven't decided this part yet. And then you get hot-patches on the same normal schedule, or you can control through any of your normal management tools, Azure Update Manager, Windows Update for Business, System Center, whatever stuff you use and get these patches, where instead of dealing with every month, a giant orchestration of servers being restarted, can't restart too many because that might impact a workload, can't restart this one until three in the morning because it will definitely hurt somebody's feelings. And I'll give you an example. We had Xbox start using this. Xbox Live has been around for pushing 20 years now. They've got a lot of backend to it, to keep gaming working all the time. About 1,000 servers run in Azure, running the entire backend of Xbox Live gaming solutions. It's got databases, it's got apps, it's got web servers, all this stuff. It's extremely mission critical because nobody wants to hear my game isn't working because of some patch Tuesday going on, right? So for them to go through every month and get fully patched, they must do this very careful orchestration dance. And it takes them about three weeks out of that month to actually take care of all those patches on all those thousands of servers and databases without causing any interruption whatsoever. And so they switched over to Hot Patch a few months ago. And immediately their entire patch management took 48 hours and they didn't have to reboot anything. So they were like, well, this is perfect. Not only am I greatly shortening my window of vulnerability, right? This whole month where I don't have all the necessary hotfixes, I've got to carefully keep my business running to, I don't even have to do any careful orchestration for the two days that it takes me to deploy the patches. So they see a tremendous savings in time, productivity, reliability, just their own staffs, you know, morale. Think about all the time you're going to spend late at night working on things that will just go away. And that option's coming to Windows Server vNext and you'll be able to see it when we release the next version of Windows Server. And I hope you like it. Thanks.