If you have a large organization, you might want to consider assigning devices to rings based on geographic location. As mentioned previously, you might want to ensure zero downtime for mission-critical devices by putting them in their own ring. There are no definite rules for exactly how many rings to have for your deployments. Organizations often use different names for their “rings," for example: For each ring, IT administrators set criteria to control deferral time or adoption (completion) that should be met before deployment to the next broader ring of devices or users can occur.Ī common ring structure uses three deployment groups:
#Microsoft excel help desktop rollout project plan examle update
They're simply a method to separate devices into a deployment timeline.Īt the highest level, each “ring” comprises a group of users or devices that receive a particular update concurrently. Deployment rings in Windows client are similar to the deployment groups most organizations constructed for previous major revision upgrades. We’ve found that a ring-based deployment works well for us at Microsoft and many other organizations across the globe. When you move to a service management model, you need effective ways of rolling out updates to representative groups of devices.
And once you use this process for feature updates, quality updates become a lightweight procedure that is simple and fast to execute, ultimately increasing velocity. A "service management" mindset means that the devices in your organization fall into a continuum, with the software update process being constantly planned, deployed, monitored, and optimized.
0 kommentar(er)
