Patch My PC Update Rings: Mastering Phased Rollouts in Intune | Tips for a Better User Experience

Levie, we have you up next. Talk about update rings. >> Yeah, thank you. Let's let's have some fun. So, I hope everyone can see my screen. I'm currently sharing the patch my PC cloud portal and we're going to talk about update rings. But before we do, I want to set the scene on why

update rings were built and introduced in the cloud portal and what issue they solve. Because currently when when you're thinking about adding Win32 apps in in tune, right, you might think I want to face this out. I have a lot of devices. I don't want to hit every device at the same time and I want to

pace them out. So you can do that natively with in tune and the way you can do it is by leveraging availability and deadline that's an inune native functionality and a lot of people use that and when they come to the patch my PC cloud portal they expect the same functionality right but there is a good

reason why we introduced up rings availability and deadlines can be problematic in certain cases and here I have an example I've packaged Google Chrome I I have this win32 app and I've configured the following um groups. I have my beta group and I have it configured to install as soon as possible. We can see it here. That's the

availability and I have my pilot group. This is set to install a few days later. I think it's 15 days later. And then I have my production group which is set to install I'm bad at math maths 22 days later something like that or 20 days later. Now what can happen is there is a bug in

in tune. So for instance if you have a device or a resource a device or user that's a member of all of the three groups you would expect this particular app to install as soon as possible right because it's part of first beta group but we can see I referenced it as soon