Whichever option you choose, you want to test the best you can within the first deployment ring, during Windows Insider build times, working with that in production. It's a sort of hope for the best thing. The idea is to test "good enough"—making sure mission critial software is working. Have a plan in place if something minor doesn't, like Adobe Reader or an older web browser. Plan and test and have a fallback and rollback plan in place.
- [Instructor] Windows as a service…has completely changed the Windows landscape.…With Windows 10 installed and Windows as a service in place,…you don't need to endure…another major upgrade in your enterprise.…Such as you might have experienced…when moving from Windows XP to 7,…or Windows 7 to 10.…Instead, Windows will now receive future updates…twice a year,…and security updates once a month.…What this means to you is that servicing Windows…is no longer a project,…but instead an ongoing process.…
However, the process is one that still requires planning,…testing and deploying,…and you can use many of the same tools…you've always used to manage it.…The difference is that your mindset has to change.…Servicing Windows needs to be a process…that can be repeated regularly,…not one you plan for once and forget about.…The process needs to be perfected…to limit or avoid employee and computer downtime as well.…That's what we'll discuss here.…The first step in creating a workable and effective process…is to select and configure your test devices.…
- What is Windows as a service?
- Types of updates
- Choosing a servicing channel
- Becoming a Windows Insider
- Testing, deployment, and rollback strategies
- Deploying Windows as a service
- Where Windows as a service is headed