IT Expert Voice

Migrating to Windows 7 does not have to be an all-or-nothing proposition for a large enterprise. This article addresses the highest-impact elements of operating system migration and how to balance its cost with support of a heterogeneous environment.

Migrations are disruptive but inevitable.  But nobody said you have to do it all at once. Granted, supporting multiple platforms, even just newer versions of the same platform, raises support costs (including for help desk staff), and can create compatibility issues in intracompany collaboration.  Properly managed, however, these issues are easily contained. You can manage costs while planning the full cut-over on your own schedule.  Let’s look at how to make this half-pregnant scenario work.

The first step in a staged migration path is to take a step back from the assumption that you must migrate everything to Windows 7 (or to any other platform – this advice is useful for any new technology adoption). Look at your migration motivation. Among the reasons to migrate may be:

• To have the latest and greatest technology
• You need software (or a feature) that only runs on the new platform
• You need updated hardware to replace aging systems and don’t want a mixture.

I propose that the first two are not enough to justify an enterprise-wide migration to Windows 7. It has yet to be shown that there is any feature in Windows 7 that you just can’t live without.  Sure, you may be disenchanted with Windows Vista; you may not be happy with Windows Vista or Windows XP security models or the multiple fixes and patches you’ve applied; perhaps you want to make a clean start with a fresh OS.  The cost/benefit of a software-based migration to Windows 7 is not compelling. It requires you to purchase the software, install it on every computer, and in many cases, you likely need to upgrade some hardware.  This is not a great ROI proposition.  This leaves the new hardware acquisition migration and hence, a staged rollout of Windows 7.

This flowchart illustrates the decision and action process for why, when and how to migrate to Windows 7.

Once you reach the decision to use a phased rollout, you need to determine the best way to install and support a new hardware-based heterogeneous environment.  There are three primary areas on which IT managers should focus: application compatibility, end-user/user interface (UI) support, and device (most likely printer) compatibility.

Most peripheral devices, such as printers and scanners, have specialized software that is very OS-dependent. These software drivers are critical to the operation and advanced features of the devices. Even if you buy new devices with your new systems, it is highly likely they do not yet have Windows 7 drivers in the box. This should not dissuade you.  Windows 7 includes basic software for more devices than Windows Vista or prior versions. For advanced hardware features in devices such as scanners and all-in-one printers, generally the Windows 7 drivers are downloadable from the manufacturer’s web site. Over time, this step will become unnecessary.

Windows 7’s user interface (UI) changes are also not a major hurdle. For the most part, common tasks are accomplished the same way as in Windows XP or Windows Vista.  A user reasonably well used to Windows Vista or Windows XP should not have too much trouble navigating Windows 7. Where the UI is a bit different is in the settings and control panel items, especially in terms of security and firewall settings.  Thankfully, most general end users don’t have to go in there very often, if ever, though your administrative staff will need some training.

An ITEV article that describes some of these changes is I Know It Is In Here Somewhere: Windows 7 Networking Controls.

More good news is that anything you already had set up, such as shared drives and other networking facilities, work seamlessly.

So far, this hybrid idea isn’t so bad; right?  Device drivers; okay.  UI issues?  Not a big deal for the end-users, who are the focus of productivity.  So far so good.

The most involved element of any migration is in application support. This could be the deal-breaker in a migration. Specifically, and without singling out any specific applications, Windows 7 has changes that necessitate new versions of some applications.  These new applications may have UI changes or file formats that are incompatible with older versions. You can address application UI differences with training. Happily, file format issues are fast becoming non-issues because of the ever-expanding support of industry standards such as Open Document format.

The real obstacle in an enterprise-wide Windows 7 migration may just be the cost of buying the new software. Older versions may not run, or a newer version may not run on older Windows versions. For example, your company may use MySoft 3.1 today; you have to move to MySoft 3.5 for Windows 7, but version 3.5 will not run on the older Windows XP or Windows Vista systems.

Microsoft addressed this last element effectively with its “XP Mode,” virtualization competing with similar third party solutions such as VMware and Parallels.

Virtualization is the new industry darling. In essence, it allows a computer to act as a host for guest operating systems. Windows 7 XP Mode creates a virtual Windows XP system inside Windows 7, allowing older programs to run.  In the case of VMware or Parallels, one can install a copy of Windows XP inside a virtual machine, and run that inside Windows 7, in essence, creating a second virtual computer inside the Windows 7 system.

Read more about virtualization in Pam Baker’s article, How Desktop Virtualization Eases Windows 7 Migration.

You might decide to buy your new hardware preloaded with Windows 7, and delay any application migration by running the OS as nothing more than a host for XP Mode, VMware or Parallels. Use a prior version of Windows until you are ready to migrate, then just stop using the virtual machine; upgrade the applications when you (and the corporate IT budget) are ready.

Note: If you are considering installing Windows 7 on existing systems with the intent of using XP Mode (as opposed to VMware or Parallels) you must also carefully examine the older PC’s processor. A little known “gotcha” for XP Mode is that only processors with “VT-extensions” support XP Mode in Windows 7.   This extra bit of complexity is something to consider when deciding on a new-hardware-based Windows 7 move versus installing Windows 7 on your existing computers.

Another option is the Software as a Service (SaaS) model for applications.  Google Apps are here now, and Microsoft is beta testing Office Web 2010; other vendors are showing similar functionality. With SaaS, you don’t install any software on the client and run the software over the Internet under a subscription model. With the SaaS model, the operating system version becomes irrelevant (at least for your office suite).

As you can see, determining how fast you need to move to Windows 7 is mostly about the applications.

A phased migration is usually the most cost effective if managed correctly.  You don’t need to get new OS software for older computers, nor worry about upgrading hardware components just to run the new operating system.  You may have some UI growth issues among the user community, but in general, Windows 7 should not be a major help-desk issue.  Peripherals such as printers always are a nuisance, but it’s a very manageable one.  Your big decision point comes when looking at the application suite you use in your business and even there, virtualization can help you move forward at your own pace.

There is no cookbook approach here, and while I provided a programming-like chart above, it is a very subjective decision.