Microsoft’s latest desktop reboot is out in the wild and lots of people are getting their hands on it and using it today. Is it time to consider moving to Windows 8? Absolutely.
That doesn’t mean that Windows 8 should be your main desktop later this afternoon, but considering a move to Windows 8 is important to do early. It is a popular approach to hold off on new software updates until systems have been in production use for months or years and there is value to this concept – allowing others to vet, test and uncover issues while you sit back and remain stable on existing, well known software. But there is a reason why so many businesses forge ahead and that is because using software early delivers the latest features and advantages as early as possible.
Unlike software coming from a small company with limited support and testing resources, Microsoft’s software is incredibly well tested both internally and by the community before it is available to end users. Few software is more heavily vetted prior to release. That doesn’t mean that release day rollouts are wise but beginning to evaluate new products early can have major advantages both because of the newest features are available to those that decide to use the new product but also the most time to find an alternative for those decide to migrate away. Early decision making is important to success.
The reality is, that while many businesses should take the time to evaluate Windows 8 versus alternative solutions – a practice that should be done regularly regardless of new features or changes to environments to ensure that traditional choices remain the best current choices, nearly all businesses today will be migrating to Windows 8 and remaining in the Microsoft ecosystem for quite some time to come.
This means that many companies should be looking to make the jump to Windows 8 sooner, rather than later. Windows 8, while seemingly shockingly new and innovative, is based on the same Windows NT 6 family kernel that began with Windows Vista and Windows Server 2008 and continued through the Windows 7 and Windows Server 2008 R2 era and is shared with Windows Server 2012. This kernel is mature and robust and the vast majority of the code and features in Windows 8, user interface aside, are well tested and extremely stable. Windows 8 uses fewer resources, on the same hardware, as Windows 7 which, in turn, was lighter and faster than Windows Vista. The sooner that you move to Windows 8, the sooner you get more performance out of your existing hardware and the longer you have to leverage that advantage.
Windows 8 brings some big changes that will impact the end users, without a doubt. These changes can be, in some cases, quite disruptive but with proper training and preparation users should return to regular productivity levels in a reasonable amount of time and often will be more productive once they are comfortable with the new environment and features. Those that do not fall into one of these two categories are the smaller, niche user group that are prime candidates for moving to a completely different ecosystem where their needs can be more easily met.
If you are an organization destined to be running Windows 8, or its successors, “someday” then most likely you should be running Windows 8 today to start leveraging its advantages as soon as possible so that you can use them as long as possible. If Windows truly is the platform that is best for you you should embrace it and accept the “hit” of transitioning to Windows 8 now, swallow that bitter pill and be done with it, and for the next several years while your competitors are whining about having to move to Windows 8 “someday” you will be happily leveraging your older hardware, your more efficient workflows and your more modern systems day after day, reaping the benefits of an early migration to a stable platform.
It is common for IT departments to take a “wait and see” approach to new system migrations. I am convinced that this is created by a culture of hoping that IT staff will leave their current positions before a migration occurs and that they will land a new position elsewhere where they have already migrated. Or perhaps they hope to avoid the migration completely awaiting a later version of Windows. This second argument does carry some weight as many shops skip operating system revisions but doing so often brings extra overhead in security issues, application compatibility effort and other issues.
Windows 8 is unique in that it is a third release of the Windows NT 6 kernel series so it comes as a rare, very stable late release member of its family (the NT 6 family is sometimes called the “Vista Family.”) Windows 8’s NT designation is 6.2. The only other Microsoft NT operating system to reach the x.2 status was when Windows XP SP3 and Server 2003 R2 released with the NT 5.2 kernel – a part of the Windows 2000 family. Late release kernels are important because they tend to deliver the utmost in reliability and represent an excellent point in which to invest in a very long term deployment strategy that can last for nearly a decade.
Whether you agree with Microsoft’s unified platform vision or the radical approach to user interface included in Windows 8, you need to decide if you are continuing down the path of the Microsoft platform and if so, embrace it rather than fight it and begin evaluating if a move to Windows 8 and, by extension, Windows Server 2012 are right for you. Don’t avoid Windows 8, it isn’t going to go away. For most shops making the decision to move today will sow the seeds for long term benefits that you can reap for years and years to come.
4 thoughts on “Is it Time to Move to Windows 8”
Windows 8 is such a departure UI wise that for a business as a whole, except in rare cases, it would interrupt workflow just trying to learn the idiosyncrasies of the UI. It seems what performance gains are to be had from it are stymied by a decision at Redmond to make the interface one-for-all. Great table gestures, all that do not belong on the desktop.
Also with the rumors that MS is going on a very accelerated OS release schedule it may be worth sitting W8 out to see where MS may take it.
Which all totally differs for Server 2012. While the UI can be an impediment it is far less so given an IT Pro can work around the changes far quicker than the average user. I know personally I am going to be deploying Server 2012 for every server that I can muster.
A factor to consider is where you are regarding current OS deployment. Many companies are still transitioning from XP to Windows 7. If you’re mid-transition adding a third OS to the mix will in fairly short order become a support nightmare.
On the other hand, if you’re still and XP shop and about to upgrade, going to 8 might make sense. I agree that as butt-ugly as the new UI is on a desktop, MS seems to be committed to it. If you plan to stay a MS shop then skip 7 and bite the bullet. Committing now gives you time to perhaps roll out Classic Shell to ease the transition.
I wouldn’t underestimate the cost associated with lost productivity, however. It’s something we in IT tend to do all too readily. Consider, however, this in real-dollar terms. If you have a $20 an hour employee and they only lose 10% productivity during a 6 week transition period (4hr loss per week * 6 weeks * $20) that comes to $480 per employee for that period. Given that Win8 Pro retails for $199, it becomes clear acquisition costs are the LEAST of your budget concerns.
Lost productivity is real and costs real money.
Upgraded from Windows 7 Pro (I had to because the Hyper-V Manager for Windows 7 has limitations compared to Windows 8 version), very happy with the new version so far. It is far more productive for me as an IT Pro and for two employees who got Windows 8 to work with. The only thing I showed them is how “Windows” key works and I printed out the list of keyboard shortcuts (don’t know if they use them or not, but I’m using them all the way: Win+D, Win+E, Win+R, Win+C, Win+L and my favorite Win+X.)
Time to move forward!
I think with a little orientation and some pre-deployment UI cleanup, Win8 is not going to be as steep a learning curve as I anticipated for our staff. Once I started using it (migrating from Win7 this summer on my laptop), and figured out how to turn off the annoying components, it became a more streamlined experience.
From a technology management perspective, Windows 8 is pretty much the same as Windows 7 under the hood, so I won’t have to re-invent many of the tools I had to tweak when migrating from XP to 7. It will be nice to have a unified environment.
I will be finishing out the XP retirement with Windows 7 builds this year, but all the builds after that will have the Windows 8 image on it.