General support and updates for Windows 7 will end as of January 14, 2020, which means security updates end after this date, as well, opening your organisation up to potential vulnerabilities. This represents a great opportunity to simplify your workstation estate, rid your organisation of some of the technical debt accrued over the years, and use the improved native security stack made available by Microsoft in Windows 10, including such features as antivirus, host-based IPS, data-loss prevention, code-signing, and OS/Hardware security integration.
Windows 10 migrations are among the (many) projects that have the potential to cause sleepless nights for IT practitioners, architects and project managers alike. They’re not without complexity or risk, and sometimes a typical response is to engage third-party professional services to help, making this kind of pervasive organisational change that much more onerous. It is also tempting to delay migration until endpoints can be replaced through attrition, but that is a risky strategy considering the security implications of not patching and the challenges of managing heterogeneous environments at scale.
As my colleague Josh Schofield examined a few weeks ago, whenever we think about a Windows 10 migration we can broadly delineate the project into three key areas of focus:
Before we even think about the second and third stages, there is crucial information we need that will help us understand what needs to be done in the first stage. To solve the challenge of assessing compatibility, at a minimum we need to be able to answer the following questions:
Join us to learn how Tanium’s speed, scale, and simplicity can facilitate and super-charge your Windows 10 migration projects with our modern approach. We have two sessions for our upcoming webinar, with details below.