Event banner
Managing Windows updates with client policies vs. APIs vs. registry keys
Event details
When we talk about managing Windows updates or Windows Update for Business, what we are really talking about is a set of policies, reg keys, and a cloud APIs in Microsoft Graph. But what is the difference between policies, reg keys, and the graph API and when should you use which? Tune in while Aria and Angie have a conversation discussing the different tools that are used to manage Windows updates as part of Windows Update for Business.
This session is part of the Microsoft Technical Takeoff: Windows + Intune. Add it to your calendar, RSVP for event reminders, and post your questions and comments below! This session will also be recorded and available on demand shortly after conclusion of the live event. |
13 Comments
- Heather_Poulsen
Community Manager
Link referenced in this session: https://aka.ms/wufbds
- Greg SteinBrass ContributorWe are already using Intune to manage update rings, Feature update profiles, and Intelligent Rollouts. Are there any common situations where we would use something like Graph API as well? I was kind of hoping for a demo or some use cases for inspiration.
- Angie_Chen
Microsoft
One great thing about the Graph API is that you can integrate the capabilities you're currently using like feature update profiles and intelligent rollouts into your own custom apps or PowerShell scripts. Check out this blog post for some common scenarios and a custom app example (Teams chat bot) that we built to showcase how you can leverage the Graph API! - AriaUpdated
Microsoft
If you are already using Intune and the Feature update profiles / intelligent rollouts then you in fact *ARE* already using the Graph API. Intune is calling the Graph API on the back end for all of those. If you are looking to get your powershell on and experiment with it further, you can test out the driver and firmware management (currently still in preview with Intune, but also available via the Graph API directly)- AriaUpdated
Microsoft
You may also want to check out: aka.ms/WUfBplusGraph
- AriaUpdated
Microsoft
If you are already using Intune and the Feature update profiles / intelligent rollouts then you in fact *ARE* already using the Graph API. Intune is calling the Graph API on the back end for all of those. If you are looking to get your powershell on and experiment with it further, you can test out the driver and firmware management (currently still in preview with Intune, but also available via the Graph API directly)
- AriaUpdated
Microsoft
Hi all, hope you enjoyed the video! This is your friendly PSA to *stop* setting registry keys directly and some practical information for how to use the new Windows Update for Business Deployment Service Graph API with client policies. 🙂- bdam55Iron ContributorAdds link to RegEdit in startup folder.
- Chad SimmonsIron ContributorBryan Dam... I don't know if that is funny or mean... or both!
- jeddy_Iron ContributorAre there any CSP Tattooing issues with the WUfB or related policies? When that is the case, the only recourse to revert some CSP changes may be to manually overwrite or delete a registry key/value.
- AriaUpdated
Microsoft
The only WUfB CSP that should give you any problems in terms of tattooing is the Allow Other Microsoft Products CSP. The rest you should be able to easily unconfigure or disable in your management interface and have the CSP automatically change the values for you.
- Heather_Poulsen
Community Manager
We’re happy you’re here with us at the Microsoft Technical Takeoff! Whether you are attending one session or many, please take this 2-minute survey and let us know your thoughts on this event.
- Heather_Poulsen
Community Manager
Welcome to Managing Windows updates with client policies vs. APIs vs. registry keys at the Microsoft Technical Takeoff. Let's get started! Today’s presentation will be short and to the point so let’s make this an active Q&A! We'll be here in chat for the full half hour to answer your questions and throughout the week. Have a question? Post it here in the Comments.