Think about your last migration project. Was it part of a larger project that also replaced all the hardware, upgraded servers and Active Directory, deployed one or two new organization-wide applications and performed a general spring clean? If you answered yes to even half of this list, then the project was too complex. OS migrations should be discrete BAU projects, without all these interdependencies that simply over-complicate the project by technology, process and resources involved.
Today, new OS’s tend not to require faster hardware (unless it is very old), removing the need for new PC hardware to be installed. Additionally, tools are available to fully automate the migration independently of other projects, and there is much greater flexibility with Microsoft’s backend infrastructure like AD, removing the need for a spring clean. Keep the scope of the project as narrow as possible, and focus on speed through full automation to get over this hurdle of perceived complexity.
Why do large organizations delay in migrating their users to the latest Windows operating system (OS)? According to Sumir Karayi, CEO of 1E, they often hear five major excuses that prevent IT from staying current in terms of the operating system, and many other technologies. This understanding comes from the work 1E has done with more than 1500 organizations over the last 15 years, and offers insight to combat these commonly overheard defenses.