Over the past three years. I have probably spoken to dozens if not hundreds of IT managers, executives, schedulers, and other folks involved in Windows-as-a-Service management, and there is one common thread. They are all wondering how they can lower the risk of business disruption while getting through this upgrade as efficiently as possible to be able to prepare for the next.
The best answer — next to creating a repeatable, scalable and automated process managed by an IT Transformation tool like Dashworks, of course — is to utilize the concept of Windows Deployment Rings, Microsoft's preferred way of rolling out new feature updates. However, that begs another question — maybe the biggest practical implementation question that IT managers have regarding deploying Windows-as-a-Service: "What criteria do you use to enroll users and devices into deployment rings that still achieves the velocity required while managing the risk of accelerated upgrades?