Windows 10: Regular Cadence of Change
Windows 10 is the first Operating System (OS) Microsoft has provided under the “Software-As-a-Service” model.
Supporting Window 10 requires major changes to how IT operates. Windows 10 introduces and requires a paradigm shift to a state of “constant implementation of changes” so that machines continue to receive security updates. Even though the steps of supporting Windows 10 also apply to previous versions of Windows, supporting Windows 10 as Software-As-a-Service increases the frequency in which many of these items need to be managed and implemented.
Servicing each component of a Windows 10 implementation requires planning, testing, implementation, post-implementation testing, resolving potential issues, adaptation to the implemented changes and mitigation of the impact of loss and/or change of functionality. Attempting to perform all of the necessary steps without an overall plan to keep underlying systems properly synchronized may result in one or more items falling out of step. In order to keep all of the pieces in synchronicity, a schedule of events should be established and rigorously followed. Separating components into manageable size pieces is extremely important to ensure each component is correctly managed.
Establishing a “Regular Cadence of Change” as the norm integrates these Windows 10 requirements into an environment and eliminates the disruption that previously occurred when changes were required. The traditional state of desktop environments was static, or “revolutionary”, where changes were infrequently implemented. Long periods elapsed between major changes such as an OS upgrade. The requirements for Windows 10 force an “evolutionary” or “dynamic” state to accommodate the constant change. This “evolutionary” state can allow an organization to become far more capable of quickly implementing changes when a new business need is found or when a rapid response is needed to address an urgent issue.
This blog is the first in a series on Windows 10. The following posts in this series will explore:
- The implications of supporting Software-As-a-Service
- Security updates
- Feature updates
- OS Version upgrades
- Hardware updates such as firmware and drivers
- Updating infrastructure and the importance keeping it in sync
- Servicing and updating reference images
- Advantages of a “dynamic” environment
- Creating the schedule of change implementations
- Updating Group Policy to support new (and changed) features